![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#11
| |||
| |||
|
|
"DanR" <dhr22 (AT) sorrynospam (DOT) com> wrote in message news:%BCQh.2455$H_5.1980 (AT) newssvr23 (DOT) news.prodigy.net "DanR" <dhr22 (AT) sorrynospam (DOT) com> wrote in message news:Wf7Qh.4431$YL5.675 (AT) newssvr29 (DOT) news.prodigy.net... "Rob Turk" wipe_this_r.turk (AT) chello (DOT) nl> wrote in message news:9c14f$46109963$3ec2f251$7417 (AT) news (DOT) chello.nl... "DanR" dhr22 (AT) sorrynospam (DOT) com> wrote in message news 7XPh.4370$YL5.530 (AT) newssvr29 (DOT) news.prodigy.net...Rob, thanks for you help. I have a saved readout from Belarc Advisor before the drive corrupted. But that readout is on a work computer. (not available now) I did go in today but mainly to load missing software on the new C:. I did the Control A to bring up the LSI Logic config page but didn't know how to interpret it. I'll stick the old/bad drive in another computer and see if I can determine if it had 2 active partitions. Even after it quit booting I could use BartPE to look around on it. (ran chkdsk /f and there were many many bad files) The history of this computer is like I said earlier to encode video. The person who installed the extra drives is long gone so can't ask him. But it was set up to encode to the E: drive. (the missing drive) So I'm guessing that the E: drive was the fastest drive in the machine. And therefore the SCSI drive. Or at least one of them. I doubt he would have set it up to mirror as loosing data on these drives is not a big deal. Device manager has unknown device for SCSI Controller. I should have mentioned that earlier. Your old disk may also have a C: and D: partition on it. That would make the partition on the SCSI drive(s) the E: disk in the original config. If you install a brand new config on a new IDE disk with just a C: partition, any other detected partition would become D:. Are you sure you have an LSI Logic card? Control-A is usually for Adaptec cards. On older systems, Dell used to offer only floppy disk images. It insists on unpacking the image to a 1.44MB floppy, after which you can the load the driver from it. Your best option is to find another computer that has a floppy drive, generate the floppy, and then transfer the files on it to your system using a CD, USB key or across a network. In device manager you can then point it to the location of the files. Rob Thanks again Rob. I will do the floppy load on Tuesday. Also will install the old drive in another computer and look for partitions. Dan All is well. I extracted the downloaded driver to floppy and copied those files to the problem computer. Pointed device manager to this folder and the SCSI driver was installed and immediately I had my missing drive back. (no restart) Seems so simple looking back. The fact that the driver insisted on extracting to floppy confused me. This is text from the driver "version.txt" file: Title : SCSI non-RAID:Ultra320 SCSI Controller Driver Version : A00 OEM Name : LSI Logic OEM V er : 1.08.15 Compute rs : Precision - 650 OS : Windows XP Languages : English I had a RAID and non-RAID version and just guessed non-RAID. Because it's working I assume that was the correct guess. Doesn't necessarily mean it wouldn't work if you used the raid driver. What still baffles me is that it could see the other SCSI drive and not the 'missing' one. AFAIK the NT flavors of Windows need a driver to see drives, whether they are BIOS included or not where in Win9x the drive would still be seen through BIOS. Maybe this changed when Win9x and WinNT were crossed? One explanation could then be that the drive seen is included in the BIOS scan and the other is not. Anyone -including OP- that can shed light on that? Thanks again for the help. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |