Linda Proulx wrote in a message to Nick Andre:

 AS> Hmm... I had the same problem.  All I can think of right now is that if
 AS> you have a previous version of OS/2 or any copy of OS/2 with applied
 AS> fixpaks, you can't re-install it properly.  But if that's not the
 AS> problem, then I don't know.

 LP> I just read somthing that said the installer may have to
 LP> delete or rename autoexec.bak files.  Is that there?  Check
 LP> for the backups of autoexec/config files.

Autoexec.bat is a DOS file, not an OS/2 file.  OS/2 does not create an
automatic executable file on install.  If one is needed later, it uses it's
own auto executable called STARTUP.CMD.  

Keep in mind that a BAT file is ALWAYS a DOS file, NEVER an OS/2 file.  If
OS/2 sees a BAT file, it will open a DOS session and run the thing, but, it is 
running a DOS session, not an OS/2 session.  When it opens the DOS session it
will use the AUTOEXEC.BAT file in your root to set up the DOS session.  That
is all the AUTOEXEC.BAT file is used for, ie, the default DOS session
autoexec.bat.

While I'm thinking of it, remember, or know, that OS/2 sessions will open DOS
sessions for you automatically, or forceably, but, an OS/2 DOS session will
not open an OS/2 session for you.  Meaning for example, if in a DOS session,
you try to run a CMD file, it won't open an OS/2 session and run it.  Nor will 
START start an OS/2 session from a DOS session unless you run 4DOS or use
HSTART, or similar 3rd party utilities.   START btw is used to open sessions.  
If you type an OS/2 command from an OS/2 command line, it runs the app much as 
would a DOS command line.  If you use START, as in "START application.exe"
OS/2 will create another OS/2 session/window and run the app.  You will then
have a new task running in your task window.   This is important stuff to know 
when playing with your new OS/2 OS.  If you familarize yourself with this
stuff a little, you will have fun quicker with OS/2.  You shouldn't need to
know all the little quirks and tricks and applications we all use until you
familarize yourself with the basic concepts.  

One VERY neat thing about OS/2 (and UNIX as well) that is VERY different from
DOS/WIN is it grows WITH you.  The more you learn, the BETTER it gets.  With
DOS/WIN the more you learn, the WORSE it gets.  When you can't do something
with OS/2 or UNIX, it is almost always because you don't know how.  With
DOS/WIN, it is mostly because the OS can't do it.  Big difference.  Very nice
to know the problem is you, rather than the OS.  YOU are capable of learning,
your OS is pretty much written in stone.   I'm still learning neat things with 
OS/2 after 9 years.  With DOS, after 9 weeks I was running into stupid
limitations.  I didn't know at that time that UNIX had none of the barriers
that I was running into with DOS.  Things haven't changed much in 20 years
either.
               
                               Jack 
--- timEd/2-B11
140/1
278/111