Hi Linda,

 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.

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

 LP> True.  But according to 'Unleashed' if there is a .bak or config
 LP> backup dos file, it can stop the original install.  That's what it says.

Now this drags up old memories...  If I remember correctly - the VERY FIRST
release of OS/2 Warp 3 (non-connect) RED BOX, came out with an install bug if
there was a DOS CONFIG.SYS and CONFIG.BAK on drive C:, and you were installing 
to a DUAL BOOT system on a FAT drive. This was found and fixed BEFORE the
release of Warp 3, and about 2 days into first diskette production run and
only affected a very small number of packages. I have not heard of anyone ever 
running into a set of these disks, however it was very easy to fix this
problem.

Warp 3 Connect and BLUE spine boxes did not have this problem, they were
released later.

Cheers.........pk.


--- Maximus/2 3.01