🚀 go-pugleaf

In message <4dk0eb$hol@cpcug.org> - kbennett@cpcug.org (Keith Bennett) writes:

:>
:>I'm having a helluva time trying to install Warp on a Dell Pentium.  It 
:>was running fine before, but a power failure occurred and tahe disk got 
:>trashed.  I try to install Warp Connect, everything's fine up until the 
:>first reboot.
:>
:>It starts up a little, loads a few device drivers, and then displays the 
:>message:
:>
:>OS/2 is unable to operate your hard disk or diskette drive.  Correct the 
:>preceding error and restart the system.
:>
:>This happens even when doing the Alt-F1, C bare boot.  I tried creating 
:>partitions on different parts of the physical drive, using FAT and HPFS, 
:>but always get the same error.
:>
:>It is an all-IDE (unfortuantely) system with an IDE CD-ROM.  Are there 
:>newer drivers I must use than the ones on the Warp Connect install disks?

I seem to recall that Dell used some motherboards with the braindead CMD640 
PCI controller embedded on them. Something that Dell did to this stops the 
specific CMD640X.ADD driver that ships with Warp Connect from working 
correctly. IBM1S506.ADD doesn't load because it knows that CMD640X.ADD will 
be along in a minute to run the HD controller and then CMD640X finds the Dell 
modified CMD controller and refuses to drive it.

A couple of possible solutions: first get PJ19409.ZIP which you should have 
in any case with the CMD640 since it solves a data loss problem with the 
controller. Use CMD640X.ADD and CMDATAPI.FLT from that package instead and 
see if it helps with your problem (these two drivers are included in fixpack 
10 or later so if you have a machine running that around...). The other 
possibility is to add the switch /FL to the IBM1S506.ADD line in CONFIG.SYS 
and Force Load IBM1S506. This will leave you exposed to the data loss problem 
but might work. The third of my couple of solutions <g> is to REM both of 
them out and use IBMINT13.I13 instead. This is the BIOS driver and will be 
slow.



Trevor-Hemsley@dial.pipex.com