News:

If you need help with OS/2 visit http://forum.os2world.com

Main Menu

Recent posts

#61
Hardware / Re: eCS v2GA - Questions for h...
Last post by NNYITGuy - 2012.09.24, 04:09:47
Hi,

Have there been any updates that I have missed for successfully hibernating of eCS?

Thank you,
Todd
#62
Article Discussions / Re: What is the future of this...
Last post by dryeo - 2012.09.24, 02:11:34
Here's a couple of porting guides. Understand that they are old and geared towards EMX and many of the referenced problems have been fixed in kLIBC.
http://www.os2site.com/sw/dev/guide.html
http://www.os2site.com/sw/dev/porting-faq.zip

Quote from: Joop on 2012.09.23, 16:36:00
Quote from: DougB on 2012.09.23, 07:46:23
Quotebecause the things where the compilation hangs are always the same things

I'll bet that Paul, and the others, are rolling on the floor, laughing at that statement. They are also crying, because it isn't always that simple.
Keep on rolling laughing on the floor  ;D, at the end we'll see.

Some compilation hangs are simple, eg needing socklen_t typedef. Some are complex such as our TCPIP stack not having getaddrinfo(), a very common function now a days as it supports both ipv4 and ipv6.
The real problems often happen after compilation succeeds, line ending issues is probably the most common. Many times you can find where the issues have already been fixed for Windows and just adding __OS2__ to a define may fix it.
A lot depends on the original source being written with portability in mind. If it uses calls to the Linux kernel such as Gnome does now, then even compiling on *BSD becomes very hard.
#63
Article Discussions / Re: What is the future of this...
Last post by Joop - 2012.09.23, 16:36:00
Quote from: DougB on 2012.09.23, 07:46:23
Quotebecause the things where the compilation hangs are always the same things

I'll bet that Paul, and the others, are rolling on the floor, laughing at that statement. They are also crying, because it isn't always that simple.
Keep on rolling laughing on the floor  ;D, at the end we'll see.
#64
Utilities / Re: dfsee
Last post by Ben - 2012.09.23, 14:51:38

Hello, Phil,


Just FYI, DFSee has an E-mail support system and a
mailing list which when subscribed to for a while, provides an excellent knowledge base for new and longtime DFSee users.

You'll find most common problems and situations, (and some uncommon), all ready addressed there.

Just hoping to save you some future anquish... 8)

#65
Article Discussions / Re: What is the future of this...
Last post by DougB - 2012.09.23, 07:46:23
Quoteand it still doesn't set me on going. Its too short

Actually, it is enough to get you going, but you need to pick a relatively simple project to start with. Something that has already been done, so you know that it will compile  a proper program, so that you aren't fighting with program incompatibilities, as well as with setup problems.

Quotebecause the things where the compilation hangs are always the same things

I'll bet that Paul, and the others, are rolling on the floor, laughing at that statement. They are also crying, because it isn't always that simple.

Paul suggests getting the WGET source, and work with that to get started. It is an excellent starting point because the program is not all that complicated, and you don't need to worry about fancy things, like which direction the window locations count. Once you get the basics to work, you can progress into more complicated things. After you do a few of those types of project, you can move on to more advanced projects, learning as you go.

I found that the hardest part, of getting started, was to tweak my setup so that it would work. Once I got that going, other things were easier. You don't want to be starting off by trying to build Firefox, simply because you would have no idea if a problem was caused by your setup, or by some code incompatibility.  The most important thing, is don't be afraid to try things, but be aware, that doing that can cause damage to your system, if you get really unlucky.
#66
Utilities / Re: dfsee
Last post by Phil - 2012.09.23, 03:51:14
DougB
Problem solved  (operator error)
Finally stumbled across the ikeyos2 exe
and replaced keys ok.
again thanks for help
Phil
#67
Utilities / Re: dfsee
Last post by Phil - 2012.09.23, 02:20:23
dougb  thanks for your reply.  If my understanding
of instructions in the readme and your input is clear.
the command at os2/ecs commandline should look like
this    ikeyos2 dfsee11x.iso.  Same error msg.
My first thought from the readme was subistute xxx with
the os2 version, assuming a numeric value, tried and
same error msg

Phil
#68
Utilities / Re: dfsee
Last post by DougB - 2012.09.23, 00:35:21
ikeyxxx is not the program name. You need to use ikeyos2 when booted to OS/2 (eCS) or ikeywin when booted to windows.
#69
Utilities / dfsee
Last post by Phil - 2012.09.22, 21:18:48
am trying to add my key to dfsee 114 via ikeyxxx.  By instructions
dfsee.key and dfsee iso are in same directory.  I have tried win ver
while logged on to win7, and ecs\os2 ver while logged on to ecs.
via command line  while in the dfsee directory. result is sys error 1041,
the name ikey and my version sub for xxx is not recognized as an internal or
external command, operable program or batch file.  What am I doing wrong.
suggestions ar greatly appreciated
regards Phil 
#70
Article Discussions / Re: What is the future of this...
Last post by Joop - 2012.09.22, 20:59:51
Quote from: DougB on 2012.09.22, 20:07:34
QuoteSo we have to invest in "how do you do that" in development

QuoteI also agree we need more information on porting software.

Paul Smedley actually released his whole build environment, and others have been using that to port things. I don't know what the details are now, I got the package when it first appeared, and it does work. I am pretty sure that you need to request the package, and possibly pay a modest fee, to get it now. The package does contain a very brief set of instructions on how to use it, but a user does have to do some serious digging, to learn how to go about porting software, especially when it won't build without modifying the code.

Unfortunately, it is probably not as simple as saying "do this..." with a set of instructions. Each program could require something different, so you would need a set of instructions for each program. The trick is, to get good enough at doing the job, that you can write your own instructions, but learning how to do it, is a lot of work.
I have Paul's environment and it still doesn't set me on going. Its too short, an example program to do yourself and how to might help a lot. And I'm willing to pay a humble fee for that, but it has to set me on the right track! Sorry, I don't agree with you. I even think that you can port automated programs because the things where the compilation hangs are always the same things. So you can publish these problems so we haven't to re-invent the wheel time after time. We need to work together, otherwise we can kiss OS/2 goodbye in the future.