Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!uwm.edu!rutgers!spcvxb!terry From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) Newsgroups: comp.unix.bsd Subject: Re: The SCSI Controller saga continues... Message-ID: <1992Nov17.224351.4470@spcvxb.spc.edu> Date: 18 Nov 92 03:43:51 GMT References: <1eb50mINNoc@hrd769.brooks.af.mil> Organization: St. Peter's College, US Lines: 24 In article <1eb50mINNoc@hrd769.brooks.af.mil>, burgess@hrd769.brooks.af.mil (Dave Burgess) writes: > 2) If a floppy is in the disk drive, the system will boot, and identify the > hard disk controller as IRQ 14, 0x1f0. Isn't that the combo for the IDE drive? > The hard drive is then mountable, fillable, fsckable, etc01.*-able, etc. Every > check seems to work, all systems go. But only as wd0*. Remember, this is an > SCSI drive. > > Huh? It looks your hard disk controller provides emulation registers for the AT- type controller. That means that it can be used without special drivers for things like DOS, Novell Netware, etc. However, depending on what the OS does to poke the registers on a boot, the controller may change the drive's reported geometry. That would cause all sorts of odd behavior on booting. I'd try sticking the wdboot out there and see if that makes it bootable. Of course, you're liable to get better performance if you can run the controller in native (SCSI) mode, rather than relying on the emulation registers. Terry Kennedy Operations Manager, Academic Computing terry@spcvxa.bitnet St. Peter's College, Jersey City, NJ USA terry@spcvxa.spc.edu +1 201 915 9381