Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - hush

Pages: [1]
1
i will give that a shot and report back, thank you!

2
Also how are the drives and CDRom connected and is the RAID in the BIOS or? Seems that at least the VM/CMS side of the hardware has some weird DASD drivers. I'd assume any drivers that Warp 3 hads are present on 4.52.
the drives are just connected to "cheetah" RAID controllers via a SCSI backplane, the IBMRAID.ADD driver from those option diskettes works to get them to show up in 4 but not 4.5. i will have a look into LVM, as i can't really think of any reason this shouldn't work in 4.5. even using the same driver and basedev line in config.sys doesn't do it, it's strange.

3
hey all! first off, thanks for maintaining a space for niche computing topics.

i am currently working with an IBM PC server 500 system/390, a first generation pentium system with the fast/wide "cheetah" RAID controllers. i have a set of boot floppies for warp 4.52 that claim to include support for large disks, and have two RAID arrays- one 9GB, and one 18GB. i am able to get as far as loading the third floppy and continuing the install from CD before the SYSINST2.EXE error rears its ugly head, and i cannot continue. i am able to drop to a command line before that point, and i have seen that running X:\OS2IMAGE\DISK_1\SYSINST2.EXE manually may work, but i am unable to get to that directory on the CD- the shell simply complains that DISK_1 does not exist.

the system previously ran warp 3 and i have been able to reinstall it, but i would like to get 4.52 running if at all possible. appreciate any insight you can provide!

edit: for anyone reading this and having the same issue, i was able to get warp 4 installed, but not 4.52. for some reason warp 4 will accept the IBMRAID.ADD driver for my devices, but 4.52 will not using the exact same method of modifying boot floppies and installing from CD. i am unfortunately just not sure why this is. my initial suspicion was that the DAC960 driver is conflicting as having both installed will cause this system to panic on boot blaming the DAC960 driver, but booting without that driver does not help.

Pages: [1]