tom@quad1.quad.com (Tom Friel) (01/21/89)
We have a disk controller that handles both fixed and removeable RLL hard disks, and we have a SCO XENIX 2.2+ driver for it. We are exploring ways of shipping this driver so that users can easily boot XENIX from the RLL devices **without** a WD controller and disk. Currently, we specify that a standard WD based system be used to construct a kernel that includes our driver and is rooted to our controller, and then place this kernel onto a removeable hard disk (our Tandon Data Pac) along with a minimal file system. Then use custom to install the rest of the system. (serialization is performed) This approach was used because the SCO XENIX "N1" boot disk, as shipped, doesn't know about our controller and thus will not allow for installation onto our disk drives. Our question is, has anyone ever run into this type of situation before, and if so, what did was done to solve it? Is it possible to make a script that modifies a retail N1 disk (a copy that is) to incorporate our driver with a new rooted kernel? Or what ever? Any response would be helpful. -- Tom Friel | Tandon Computer Corporation | (805) | Software Development Manager | 609 Science Drive | 378-7881 | ..!uunet!ccicpg!quad1!tandon!tom | Moorpark, CA 93021 | |