• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SCSI harddrive probs after upgrade to Win2k?????

mcveigh

mcveigh

Diamond Member
I recently upgraded a computer to win2k from win98. its an all scsi system with HD, cdrw, ZIP, JAZZ all scsi.

its on an adaptec 19i60n card. everything is terminated as far as I can tell (no errors)

1 of three things happens,
1 it boots up normally, abnout 20% of the time
2 it comes to the scsi bios screen and the hard drive isnt listed , it then goes to a no OS found error
3 it starts to boot up , gets to the windows loading screen, then blue screen with
STOP 0x0000007B (more stuff)
INACESSABLE_BOOT_DEVICE
SOME MORE STUFF

any ideas? it worked fine in win98(according to owner)
I changed no hardware only upped the ram to 384Mb from 128 (crucial ram BTW)
 
make sure SCSI is the only thing set to boot to in the BIOS and make sure the drive is SCSI ID 0 on the chain. Ive had the same thing happen before.

Viper22
 
win2k drivers? during install I saw it correctly idenify the controller. are there other drivers I should add? this is my first time with SCSI

Goosemaster:
HP cdrw nad IBM on separate internal ports, I cant tell what is what, I think 1 is 80 pin, one is 68
external connetor ->scanner ->zip ->dead sygate drive -> jazz.
the dead drive is still in the chain because he'd have to buy new cables and is too cheap.
I think it's termniated correctly because if there is no power to the jazz or zip drives I can't an error mesage saying it's not terminated.
 


<< make sure SCSI is the only thing set to boot to in the BIOS and make sure the drive is SCSI ID 0 on the chain. Ive had the same thing happen before.

Viper22 >>



its set to ID 0
i'm pretty sure it's set to boot scsi only, can't check till next week


BTW its an intel 440BX mobo w/ p3 850
 
Sounds to me like either a loose card in the slot, a loose or bad interface cable, or a loose pin in the drives molex power cable, especially if you use Y splitter. Sometimes you can have too many devices on one branch of the PSU and the power loss causes the drive to fail to initialize. Your PSU may be too light on the juice too.
 
perhaps power supply but there is only 1 hard drive, cdrw, sound,nic,vidcard

the strange thing is there were no problems under windows 98
 
Have you installed service pack 2 and checked for updates? I know there was one for SCSI especially back when I used Win2K. Board drivers may also need updated or even a bios flash.. so many possibilities when you change OS, move system, etc.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top