SPONSORED LINKS
> > > Hi! I read the instructions that came w/ the Dock II, but my Syquest > > still insists on being assigned SCSI ID #1. I even set the jumper on the > > back of the drive to read "ID 0" but i think the SCAM support in the Dock > > II forces it to go to SCSI ID 1. Does anyone know how to get my SCSI > > drive recognized as ID 0? > > They key question here is in asking whether ThinkPad Owners using > a the Dock II can use the SCSI setup to *boot* from. I don't know the > answer to that... > > In order for a SCSI hard drive to be assigned ID 0, it has to be > the first drive on the system--meaning, it can't be competing with the > likes of another IDE drive. If there is an IDE drive on the system (namely, > the one inside your ThinkPad), then it can't do its thing--at least not > as a boot drive. First thing I'd do is remove my ThinkPad's IDE hard drive > and see what happens. > > The second thing that is necessary is for your SCSI card (again, I > don't know exactly how IBM impliments SCSI in its Dock II) to have a > "Boot ROM" in it, allowing you to boot from a SCSI hard drive. Most cheap > SCSI cards you see sold with the likes of CD-ROM drives simply don't have > such a thing, but better SCSI cards do. On my desktop machine, I used to > boot off a SCSI drive but now I boot off of an IDE and use the SCSI as > extra hard drive space. Hence, I have a Boot ROM in my Adaptec SCSI card, > but I don't need it right now since I boot off the IDE (which, as long as > you have a non-SCSI drive in the system, you have to boot off that non-SCSI > drive). > > Let us know what you do and how you do it. I have a particular > interest in the SyQuest 270 as I have one myself! ;) I figured out the problem (w/ mine, at least). I had to unplug my Syquest and plug it back in for the new scsi id's on the back to recognized (<sigh>). However, I also figured out how to boot from the 270. Just use the setup (F1) and set your computer to start up HDD-2 before HDD-1. It'll go to the syquest first, then the internal. However, if you have the syquest on but no disk in the syquest, the cmoputer hangs...kinda annoying to say the least. Furthermore, you have to make the syquest bootable via a disk editor of some kind...I don't think that fdisk works. Use norton diskedit and examine the partition table of the syquest. If you have a new syquest disk (PC formatted), there should only be one partition I think. Or, low level format the disk. Then, use diskedit and set the partition you want booted, bootable. Hmmmm...I guess I'll try installing boot manager onto it ;-). On the other hand, I think LILO from Linux can boot different hard drives. Maybe it's time to do away with the pretty Boot Manager.