I'm not sure if this is relevant, Stan - but the date/time of your
computer seems to be mis-set. (Unless you are posting from well east of
the UK - it's still the 3rd October here!)
Dave
I am using the on-board RAID of the ABIT KU8 motherboard. Please sayStan Hilliard said:My OS is XP-Pro, I built the computer from components a couple years
ago.
Background -- Earlier this year I had a problem with automatic updates
to XP SP2 not installing and contacted Microsoft. MS helped me solve
that problem and also helped me update to XP-Pro SP3. When I told them
that also some DLLs failed to register when I tried to install the
software for my Blackberry, they requested I run a Windows repair from
the CD.
The following is the current problem. The CD couldn't find any hard
drives. We determined that I had a OEM CD so they sent me a new
genuine XP-Pro CD (but SP2, not SP3). The new CD cannot find hard
drives either.
I have three hard drives. Two of them are in a RAID 0 array.
Other than that, the computer seems to run normally except that
backups of C: freeze the computer before they run to completion.
The place where I get the message is at the screen:
a) To set up windows XP now, press enter.
b) To repair a windows XP installation using Recovery Console, Press
R.
c) To quit setup without installing Windows XP, press R
After [return] I get the message:
"Setup did not find any hard disk drives installed on your computer."
What would make the windows setup to not find the hard drives.
Advice will be appreciated,
Stan Hilliard
I guess you are using the unstable software raid or on-board raid rather
than a proper card
There was no BSOD 7B error. I was able to F6 and read the drivers fromWindows Setup may require additional driver. Use F6 to load them if you get
a BSOD 7B error
My OS is XP-Pro, I built the computer from components a couple years
ago.
Background -- Earlier this year I had a problem with automatic updates
to XP SP2 not installing and contacted Microsoft. MS helped me solve
that problem and also helped me update to XP-Pro SP3. When I told them
that also some DLLs failed to register when I tried to install the
software for my Blackberry, they requested I run a Windows repair from
the CD.
The following is the current problem. The CD couldn't find any hard
drives. We determined that I had a OEM CD so they sent me a new
genuine XP-Pro CD (but SP2, not SP3). The new CD cannot find hard
drives either.
I have three hard drives. Two of them are in a RAID 0 array.
Other than that, the computer seems to run normally except that
backups of C: freeze the computer before they run to completion.
The place where I get the message is at the screen:
a) To set up windows XP now, press enter.
b) To repair a windows XP installation using Recovery Console, Press
R.
c) To quit setup without installing Windows XP, press R
After [return] I get the message:
"Setup did not find any hard disk drives installed on your computer."
What would make the windows setup to not find the hard drives.
Stan said:My OS is XP-Pro, I built the computer from components a couple years
ago.
Background -- Earlier this year I had a problem with automatic updates
to XP SP2 not installing and contacted Microsoft. MS helped me solve
that problem and also helped me update to XP-Pro SP3. When I told them
that also some DLLs failed to register when I tried to install the
software for my Blackberry, they requested I run a Windows repair from
the CD.
The following is the current problem. The CD couldn't find any hard
drives. We determined that I had a OEM CD so they sent me a new
genuine XP-Pro CD (but SP2, not SP3). The new CD cannot find hard
drives either.
I have three hard drives. Two of them are in a RAID 0 array.
Other than that, the computer seems to run normally except that
backups of C: freeze the computer before they run to completion.
The place where I get the message is at the screen:
a) To set up windows XP now, press enter.
b) To repair a windows XP installation using Recovery Console, Press
R.
c) To quit setup without installing Windows XP, press R
After [return] I get the message:
"Setup did not find any hard disk drives installed on your computer."
What would make the windows setup to not find the hard drives.
I have discovered additional worrisome things about my computer's hard
drive configuration.
1) When I started the windows setup CD and inserted the motherboard
driver floppy, it offered a selection of drivers for the RAID. The one
that seemed to match my XP and AMD 64 was M5288. The current installed
item under "SCSI and RAID controllers" is "ULi SATA/RAID controller
(M1689/M1567)" and the driver file is M5289.sys. Could that be the
wrong driver file?
2) There are two items under SCSI and RAID controllers. The second
item is "VIA VT6421 RAID controller" and the driver file is
vaimraid.sys. Should I have both ULi and VIA drivers?
Stan Hilliard
Stan Hilliard said:I am using the on-board RAID of the ABIT KU8 motherboard. Please sayStan Hilliard said:My OS is XP-Pro, I built the computer from components a couple years
ago.
Background -- Earlier this year I had a problem with automatic updates
to XP SP2 not installing and contacted Microsoft. MS helped me solve
that problem and also helped me update to XP-Pro SP3. When I told them
that also some DLLs failed to register when I tried to install the
software for my Blackberry, they requested I run a Windows repair from
the CD.
The following is the current problem. The CD couldn't find any hard
drives. We determined that I had a OEM CD so they sent me a new
genuine XP-Pro CD (but SP2, not SP3). The new CD cannot find hard
drives either.
I have three hard drives. Two of them are in a RAID 0 array.
Other than that, the computer seems to run normally except that
backups of C: freeze the computer before they run to completion.
The place where I get the message is at the screen:
a) To set up windows XP now, press enter.
b) To repair a windows XP installation using Recovery Console, Press
R.
c) To quit setup without installing Windows XP, press R
After [return] I get the message:
"Setup did not find any hard disk drives installed on your computer."
What would make the windows setup to not find the hard drives.
Advice will be appreciated,
Stan Hilliard
I guess you are using the unstable software raid or on-board raid rather
than a proper card
more about the proper card?
Stan Hilliard
There was no BSOD 7B error. I was able to F6 and read the drivers fromWindows Setup may require additional driver. Use F6 to load them if you
get
a BSOD 7B error
a RAID driver disk. On the next screen setup showed the partitions on
the RAID array but did not show the other single HDD. It did not say
anything about XP repair. It offered to create a partition, delete a
partition, or to set up windows on the partition I select. It looked
to me like it was going to do a complete install so I quit.
Stan Hilliard
Stan Hilliard said:I am using the on-board RAID of the ABIT KU8 motherboard. Please sayMy OS is XP-Pro, I built the computer from components a couple years
ago.
Background -- Earlier this year I had a problem with automatic updates
to XP SP2 not installing and contacted Microsoft. MS helped me solve
that problem and also helped me update to XP-Pro SP3. When I told them
that also some DLLs failed to register when I tried to install the
software for my Blackberry, they requested I run a Windows repair from
the CD.
The following is the current problem. The CD couldn't find any hard
drives. We determined that I had a OEM CD so they sent me a new
genuine XP-Pro CD (but SP2, not SP3). The new CD cannot find hard
drives either.
I have three hard drives. Two of them are in a RAID 0 array.
Other than that, the computer seems to run normally except that
backups of C: freeze the computer before they run to completion.
The place where I get the message is at the screen:
a) To set up windows XP now, press enter.
b) To repair a windows XP installation using Recovery Console, Press
R.
c) To quit setup without installing Windows XP, press R
After [return] I get the message:
"Setup did not find any hard disk drives installed on your computer."
What would make the windows setup to not find the hard drives.
Advice will be appreciated,
Stan Hilliard
I guess you are using the unstable software raid or on-board raid rather
than a proper card
more about the proper card?
Stan Hilliard
There was no BSOD 7B error. I was able to F6 and read the drivers fromWindows Setup may require additional driver. Use F6 to load them if you
get
a BSOD 7B error
a RAID driver disk. On the next screen setup showed the partitions on
the RAID array but did not show the other single HDD. It did not say
anything about XP repair. It offered to create a partition, delete a
partition, or to set up windows on the partition I select. It looked
to me like it was going to do a complete install so I quit.
Stan Hilliard
If the drives are raided then they should show up as one drive because the
second is mirrored
Setup should ask you to repair an existing installation by pressing ENTER
SPAMCOP User
Stan said:My OS is XP-Pro, I built the computer from components a couple years
ago.
Background -- Earlier this year I had a problem with automatic updates
to XP SP2 not installing and contacted Microsoft. MS helped me solve
that problem and also helped me update to XP-Pro SP3. When I told them
that also some DLLs failed to register when I tried to install the
software for my Blackberry, they requested I run a Windows repair from
the CD.
The following is the current problem. The CD couldn't find any hard
drives. We determined that I had a OEM CD so they sent me a new
genuine XP-Pro CD (but SP2, not SP3). The new CD cannot find hard
drives either.
I have three hard drives. Two of them are in a RAID 0 array.
Other than that, the computer seems to run normally except that
backups of C: freeze the computer before they run to completion.
The place where I get the message is at the screen:
a) To set up windows XP now, press enter.
b) To repair a windows XP installation using Recovery Console, Press
R.
c) To quit setup without installing Windows XP, press R
After [return] I get the message:
"Setup did not find any hard disk drives installed on your computer."
What would make the windows setup to not find the hard drives.
I have discovered additional worrisome things about my computer's hard
drive configuration.
1) When I started the windows setup CD and inserted the motherboard
driver floppy, it offered a selection of drivers for the RAID. The one
that seemed to match my XP and AMD 64 was M5288. The current installed
item under "SCSI and RAID controllers" is "ULi SATA/RAID controller
(M1689/M1567)" and the driver file is M5289.sys. Could that be the
wrong driver file?
2) There are two items under SCSI and RAID controllers. The second
item is "VIA VT6421 RAID controller" and the driver file is
viamraid.sys. Should I have both ULi and VIA drivers?
Stan Hilliard
I found drivers here. (Nvidia bought ULI, and has a ULI link on the driver
page, but the available drivers don't cover everything.) I got here
via uabit.com, the parent company.
http://www.abit.com.tw/page/en/down...&pTITLE_ON_SCREEN=KU8&pSOCKET_TYPE=Socket 754
In the user manual for your board, I don't see a VIA VT6421. Just the
ULI single chip Northbridge/Southbridge. So the VT6421 must be
coming from a separate plug-in PCI card.
And that means, you need to verify the cabling inside your PC. Check
to see if the disk(s) are connected to a PCI card, or to the motherboard
surface. If connected to the PCI card, then you might need a floppy
with VT6421 driver. If connected to the motherboard, something
for the M1689/M1567.
Also, if you're making a RAID 0 boot array, you'd have to "create"
the array first. If the array is an existing array, from a previous
creation, then there is no work to do.
I downloaded this since the RAID array is cabled to the motherboard. IOtherwise, to "declare" a
RAID array, typically a BIOS setup screen is used to write
metadata near the end of each disk in the array. The metadata
(less than 64KB worth), indicates how each disk fits into the
array. The usage of metadata, makes it possible to move the drives
around later, plug them into different ports than originally used,
and the software still figures everything out. The RAID driver
can't "take" and be effective for your installation, unless the
array has been set up first.
If the disks are plugged into the motherboard two SATA ports,
then try this. This would be for ULI RAID.
ftp://ftp-usa.abit.com.tw/pub/download/driver2/sata_driverdisk/uli_sata_v103.zip
When unzipped, copy the contents to a floppy. The TXTSETUP.OEM
should be at the top level of the floppy. along
with the folders.
This is for VT6421. VRAID. Likely on a PCI card.
http://www.viaarena.com/ViaDisplayDrivers.aspx?PageID=1&OSID=1&CatID=1180&SubCatID=117
http://www.viaarena.com/Driver/vraid_driver_v550b.zip
Unzip the download. Look for "drvdisk". There is a txtsetup.oem
and three folders in there. If the two disks are connected to
a PCI card with VT6421, the array has been "created", then copy
the contents of drvdisk to a floppy, such that txtsetup.oem is
at the top level of the floppy.
Either floppy can be offered via pressing F6.
Only the driver necessary to complete the install, is needed
at this time. Any other drivers (to handle other data disks that
may be connected to the other controller), can be installed
afterwards.
Paul
Stan said:Yes there is a PCI card. It is a PPA Int'l 1301 2-Port Serial ATA
card. It has one internal and one external port. The internal port has
a stand-alone HDD. Sometimes I connect a stand-alone HDD to the
external port for backing up. That all seems to work when operated
normally.
(Except if I Boot, then connect the external HDD, and then shut down
forgetting to remove the external HDD first, the computer
automatically restarts.)
The two physical drives that make up the RAID 0 array are cabled to
the motherboard.
The RAID 0 array is an existing array. I have been booting off it for
at least two years.
I downloaded this since the RAID array is cabled to the motherboard. I
compared versions of driver files that I have and found this.
17/04/2005 -- M5289.sys -- 52K -- v5.0.3.0 -- current in \drivers\
12/01/2004 -- M5289.sys -- 51K -- v5.0.2.9 -- motherboard disk XP
12/01/2004 -- M5289.sys -- 69K -- v5.0.2.9 -- motherboard disk XPA64
12/23/2005 -- M5288.sys -- 206K - v6.2.1.8 -- old download for XP
12/23/2005 -- M5288.sys -- 282K - v6.2.1.8 -- old download for XPA64
12/23/2005 -- M5288.sys -- 210K - v6.2.1.8 -- in zip above, for XP
12/23/2005 -- M5288.sys -- 288K - v6.2.1.8 -- in zip above, for XPA64
Perhaps I have the wrong driver file installed. Is it reasonable to
change from the M5289.sys to an 5288.sys? If so, should it be the one
for XP or XPA64? My CPU is an AMD Athion 64 3700.
Since I do not have a RAID array cabled to that card, is there a
reason for having this driver? In fact, shouldn't I uninstall the
existing VIA RAID driver?
Stan Hilliard
I thought your objective was to repair WinXP ?
You don't need to torture the VT6421 or its connected disk. If you wish,
you could disconnect the data cable between the VT6421 and connected
disk, for safety. But only if you think the installer CD will have
an unnatural attraction to that disk. I would disconnect the cable
from the PCI card end. That should be enough.
Asrock has a floppy download for ULI RAID. This is probably the same
as you have on a floppy right now.
http://www.asrock.com/mb/download.asp?Model=939Dual-SATA2
"SATA RAID Driver (For system to read from floppy diskette during Windows installation)
475.13KB
You can click their link, or try this link. This is what I downloaded
for a look.
( ftp://174.142.97.10/drivers/ULi/SATA/Floppy_AA.zip )
Copy the whole thing to a floppy.
The txtsetup.oem makes
mention of m1589. So that should match what you claim to have.
m1589 is also mentioned in the Abit KU8 manual, so that is
Abit's word on it as well.
*******
I tested my WinXP installer CD just before writing this.
During the very start of the CD boot sequence, there is an option
to press F6. It only flashes on the screen for a second, so
you have to be watching for it. And it doesn't react immediately
to the pressing of F6 either.
Later, you get a chance to press "s" and offer a driver. I prepared my
floppy for a test device in my computer, but Windows decided it
already had a driver.
But, if I didn't press F6, it would not
automatically recognize my card. (I used a SCSI PCI card and
SCSI disk, as a "stranger" hardware test case.) So even though
Windows XP appears to have a driver for my card, I still had
to press F6, and the "s", and a little later, it showed me
the partition with WinXP on it. Without the F6 charade, it
wouldn't find the partition on its own.
In your case, you'd press F6 early (it'll flash a message at
the bottom of the screen, and you might see that). Press "s" when
prompted. With the floppy in there, it should find m1589.
(The i386 folder has all three m158x devices in it, and the
INF down there, appears to apply the correct one for you.
So no need to get out the worry beads just yet.)
If it works, you should be seeing your partition to repair,
just like I was shown the partition on my old 9GB SCSI drive.
Paul
I thought your objective was to repair WinXP ?
You don't need to torture the VT6421 or its connected disk. If you wish,
you could disconnect the data cable between the VT6421 and connected
disk, for safety. But only if you think the installer CD will have
an unnatural attraction to that disk. I would disconnect the cable
from the PCI card end. That should be enough.
I left it connected.
Asrock has a floppy download for ULI RAID. This is probably the same
as you have on a floppy right now.
http://www.asrock.com/mb/download.asp?Model=939Dual-SATA2
"SATA RAID Driver (For system to read from floppy diskette during Windows installation)
475.13KB
You can click their link, or try this link. This is what I downloaded
for a look.
( ftp://174.142.97.10/drivers/ULi/SATA/Floppy_AA.zip )
Copy the whole thing to a floppy.
I made the floppy.
The txtsetup.oem makes
mention of m1589. So that should match what you claim to have.
m1589 is also mentioned in the Abit KU8 manual, so that is
Abit's word on it as well.
*******
I tested my WinXP installer CD just before writing this.
During the very start of the CD boot sequence, there is an option
to press F6. It only flashes on the screen for a second, so
you have to be watching for it. And it doesn't react immediately
to the pressing of F6 either.
Later, you get a chance to press "s" and offer a driver. I prepared my
floppy for a test device in my computer, but Windows decided it
already had a driver.
I pressed "s" and setup highlighted the SATA/RAID driver. [enter]
On the next cycle I pressed "s" again, but this time it said it
already had a driver. [enter] The screen was frozen.
Rebooted to a normal startup. With explorer,
system32\drivers\m5289.sys was the old one:
07/04/2005 -- 52K -- v3.0.6.0.
and not the larger one from on the floppy.
Rebooted from setup CD. It again took F6, "s" one time. [enter] Setup
displayed the three partitions on the RAID array. The only options
were "set up XP on the selected item", "Create a partition", and
"delete a partition". There was no "R" option. I pushed [F3] to quit.
Stan Hilliard
But, if I didn't press F6, it would not
automatically recognize my card. (I used a SCSI PCI card and
SCSI disk, as a "stranger" hardware test case.) So even though
Windows XP appears to have a driver for my card, I still had
to press F6, and the "s", and a little later, it showed me
the partition with WinXP on it. Without the F6 charade, it
wouldn't find the partition on its own.
In your case, you'd press F6 early (it'll flash a message at
the bottom of the screen, and you might see that). Press "s" when
prompted. With the floppy in there, it should find m1589.
(The i386 folder has all three m158x devices in it, and the
INF down there, appears to apply the correct one for you.
So no need to get out the worry beads just yet.)
If it works, you should be seeing your partition to repair,
just like I was shown the partition on my old 9GB SCSI drive.
Paul
I have another problem that might be related to this one. My virus
scanner program, F-Prot, has for the last week been generating false
positives and wrongfully (I think) quarantining the files. Many have
been driver files -- those that I recently downloaded here, and ULi
and nvidia install files that I downloaded a long time ago to a HDD
where I keep downloaded applications and utilities. It even removed
some files that I recently installed from an old ABIT guru utility
disk that came with the KU8 motherboard. I am discussing the false
positives here:
https://forum.f-prot.com/index.php/topic,1598.0.html
I think that problem needs to be solved before I can run the repair of
XP. Perhaps if I can fix the wrongful quarantine problem I won't need
to repair XP.
Stan Hilliard
Stan said:I pressed "s" and setup highlighted the SATA/RAID driver. [enter]
On the next cycle I pressed "s" again, but this time it said it
already had a driver. [enter] The screen was frozen.
Rebooted to a normal startup. With explorer,
system32\drivers\m5289.sys was the old one:
07/04/2005 -- 52K -- v3.0.6.0.
and not the larger one from on the floppy.
Rebooted from setup CD. It again took F6, "s" one time. [enter] Setup
displayed the three partitions on the RAID array. The only options
were "set up XP on the selected item", "Create a partition", and
"delete a partition". There was no "R" option. I pushed [F3] to quit.
Stan Hilliard
I have another problem that might be related to this one. My virus
scanner program, F-Prot, has for the last week been generating false
positives and wrongfully (I think) quarantining the files. Many have
been driver files -- those that I recently downloaded here, and ULi
and nvidia install files that I downloaded a long time ago to a HDD
where I keep downloaded applications and utilities. It even removed
some files that I recently installed from an old ABIT guru utility
disk that came with the KU8 motherboard. I am discussing the false
positives here:
https://forum.f-prot.com/index.php/topic,1598.0.html
I think that problem needs to be solved before I can run the repair of
XP. Perhaps if I can fix the wrongful quarantine problem I won't need
to repair XP.
Stan Hilliard
I also discuss the quarantine problem in a thread that I started on
this newsgroup on 10/3/09 at 2:29 AM, "What if virus ..."
Stan Hilliard