last updated at 09 Jul, 2005 01:58 (1 times)
Hi,If I understand correctly the system is rebooting when Disk 0 is still trying to boot, and you never get to the blue IBM screen saying "put disk 1 in" (or something like that). If this is correct, then updated drivers on Disk 1 and the config.sys isn't likely the problem because the system never gets to the point of actually reading those drivers into memory.
If I recall correctly there were some early versions of Warp 3 which Disk 0 didn't like to boot properly. Have a look at the date on the folders on your CD Rom and see when they were created. If it has a date of 07/08/95 or later then you should be okay (one copy I have has this date on the folders and it installs pretty well), but if it is earlier then that, (for example, I have a copy of Warp 3 which has dates of 02/06/95 which does not install on a lot of machines properly) then you'll probably need a newer "disk 0".
As for the config.sys, here's that portion from the file that I have on one of the install disks I have used in the past:
rem basedev=cmd640x.add
basedev=ibmkbd.sys
rem basedev=i2oxport.sys
basedev=ibm1flpy.add
basedev=ibm1s506.add
rem basedev=ibm2flpy.add
rem basedev=ibm2adsk.add
rem basedev=ibm2scsi.add
basedev=ibmint13.i13
basedev=os2dasd.dmd
device=testcfg.sys
set os2_shell=cdinst.exe
set saveconnect=1
set cdrominst=1
ifs=cdfs.ifs
rem basedev=aha152x.add
rem basedev=aha154x.add
rem basedev=aha164x.add
rem basedev=aha174x.add
rem basedev=aic7770.add
rem basedev=aic7870.add
rem basedev=btscsi.add
rem basedev=fd16-700.add
rem basedev=fd8xx.add
rem basedev=fd7000ex.add
rem basedev=dpt20xx.add
rem basedev=chincds1.flt
rem basedev=cmdatapi.flt
rem basedev=hitcds1.flt
rem basedev=neccds1.flt
rem basedev=sonycds1.flt
rem basedev=toshcds1.flt
basedev=ibmidecd.flt
rem basedev=tmv1scsi.add
rem basedev=sony535.add
rem basedev=lms206.add
rem basedev=mitfx001.add
rem basedev=sbcd2.add
rem basedev=sony31a.add
device=os2cdrom.dmd
Just to note, from reading your post you'll need to put back in the IBMIDECD.FLT line. As I recall this is a generic driver for IDE CD-Rom drives. Also I believe you can REM out the basedev=toshcds1.flt
line. I'm not fully familiar with that Toshiba, but if it is using a standard IDE type CD Rom drive, then that drive is handled by the
ibm1s506.add
os2cdrom.dmd
ibmidecd.flt
CDFS.IFS
OS2DASD.DMD
The SET COPYFROMFLOPPY=1 can go anywhere in the file.
As for the other items you mention, the USB and stuff, this can be tricky under Warp 3, but not impossible. The first step is to get the OS up and running and install the latest fixpak(s). Then worry about USB and stuff. Also, once up and running your system may not recognize all 80 MB that you have (on some systems OS/2 only "sees" 64 Megs), although there is also a fix for this. But again, that can be worried about later.
Hope this helps!