SPONSORED LINKS
At 04:37 PM 6/17/97 -0400, Brooks McNeely wrote:
>At 10:02 AM 6/17/97 +0500, Victor Kress wrote:
>>I am in the process of upgrading all my computers to warp 4, and I am
>>now ready to tackle the tp750. The geezers on this list will remember
>>that the 750 came from a time that laptops didn't have internal cdroms.
>>
>>On my 750 I have a pcmcia scsi cdrom, and network card. I would
>>prefer to do a cdrom install. It is clearly possible to create boot
install
>>floppies which will get the thingpad up to the cdrom reading stages.
>>Has anybody on the list done this? I would REALLY appreciate the
>>benefit of your experience.
>>
>Victor,
>
>I've done this on my TP755C. First I have an IBM SCSI Credit Card adapter;
>it is a PCMCIA (aka PC Card) SCSI adapter.
>
>I had a pre-existing Warp version on my TP from a diskette install (BTW, I
>think you can create the 20-30 something diskettes off the CD, and use
>diskettes to install Warp), so I installed the OS2 software for the SCSI
>card onto my system, which enabled me to use the SCSI CDRom from Warp.
>Then, with some trial and error, I figured out what drivers were installed
>to make the CDRom work. Finally, I used these new drivers, basedev's, etc,
>to update the Warp 4 boot floppies; I also had to make some changes to the
>config.sys on the boot floppies.
>
>After lots of fiddling, cursing, and rebooting, I finally got Warp 4 to
>install directly from the CD with my modified boot floppies. I think I had
>to find some drivers which would _not_ be used, in order to delete enough
>space off the boot floppies to make room for the extra drivers for the
>PCMCIA SCSI.
>
>The main problem I had was that one of the drivers for the SCSI adapter
>replaced a driver of the same name in the standard Warp install.
>
Sorry, I never finished this last thought (interrupted while writing
previous message). I found that the install overwrote the driver by the
same name, and when the system rebooted during the install process, the
CDRom was no longer usable. Plus I had had problems previously installing
fixpacks, because the fixpacks almost always replaced this driver.
What I discovered was that I could rename this driver to some arbitrary
name not used anywhere else (with the proper extension), and everything
magically worked fine thereafter.
Brooks
Brooks McNeely
Lockheed Martin Energy Systems, Inc.
E-mail:
bnm@ornl.gov (work)
brooks_mcneely@ibm.net (non-work)
Phone:
423-574-4612 (voice)
423-576-6608 (fax)