|"I also tried the Dos Version of Seatools, but it wouldn't run properly for some reason. I think it was because of the GUI, I couldn't move the mouse, and had to operate with the keyboard only."|
Nothing you said indicates there's anything wrong with SeaTools.
That program,and many, if not all, other Dos bootable ones, cannot recognize a USB mouse. It will recognize a PS/2 mouse or, probably, a Serial mouse, (or a "combo" mouse that is designed to be, and has the circuits so it can be, used with either a USB or PS/2 connection, with a simple USB to PS/2 adapter).
However, Seatools is so simple to use, using a keyboard with it is no problem.
Type H (or click on H if the mouse works) for more info.
"It still ran the tests, but when it completed, I couldn't figure out how to check if the test completed successfully or not. "
If it is successful, a line indicating it was is added right after the LBA line - e.g. for the long test
"Read Scan Passed on (date) @ (time)"
However, if the drive has one or more SMART errors, I don't know if that will appear.
"Also, I couldn't find an option in my BIOS to disable the "IDE compatible mode" for the SATA HD's. "
The mode the SATA controller(s) is(are) set to in the bios Setup has NOTHING to do with your problem!
I gather from the info in your posts this computer is a desktop computer and it may be a Gateway model, but it may be very helpful if you supplied which MODEL it is. That's often on a label on the outside of a brand name system's case, or may be determined on the brand name's web site.
- if it is a brand name system in most cases the brand did not make the mboard - it was made by a major mboard manufacturer and supplied to the brand name builder and is either identical to amodel made by the mboard manufacturer, or an OEM only model supplied only to brand name builders, with a bios version on it made by, or for, the brand name builder.
- or - if it is a generic system
In either case, the mboard model and possibly it's brand is often printed in obvious larger characters on the surface of the mboard, often between slots or in the middle of the mboard - if you see such a model number and/or brand on the mboard, tell us what you see.
If it's a brand name system, what you see in the brand name's bios version may be very similar or quite different from what is seen in the mboard manufacturer's bios version for a mboard that is identical to a mboard manufacturer's model .
If it is a generic system, or if the mboard is identical to a mboard manufacturer's model, the bios Setup settings info is often in the mboard manufacturer's manual for the model, and if so we can look at that and (may) see what you see.
The settings in the mboard's bios regarding the mode only apply if the WD drive is connected to a header for the main chipset's SATA chipset - some mboards have an additonal SATA controller chipset e.g. JMBxxxx - the settings in the bios often don't apply to that, and don't apply if the WD drive is connected to a controller card in a slot.
It isn't necessarily called IDE compatibilty mode in the bios. It may be called Compatibilty mode, or IDE mode, or EIDE mode, or ATA mode, or similar.
SATA mode is a.k.a. AHCI mode.
You usually find the setting for IDE compatibilty mode, or whatever it's called, in the same place where you can set SATA (or AHCI) mode.
If the the SATA chipset is capable of RAID, you usually find the setting for IDE compatibilty mode, or whatever it's called, in the same place where you can set SATA (or AHCI) or RAID (or AHCI RAID) mode.
"Do you have any other ideas? "
If pci.sys is corrupted, you should be able to delete the existing pci.sys on the WD when you boot from the other XP installation, and then copy pci.sys to it, and that should make the WD XP installtion work.
However, it may not actually be pci.sys that is the problem, because sometimes Windows can't tell you directly what the problem is.
Did you you use the correct version of pci.sys??
Apparently you must use the one appropriate for whether or which SP version is supposed to be on the existing XP installation.
I don't have anything other than an existing XP Home installation with SP3 updates installed, so I can't compare pci.sys for the different situations at my place, but I do have a copy of a CD with no SP updates, original CDs with SP2 updates, etc., so I can compare pci.sy_ for the different situations.
The compressed pci.sys is pci.sy_ .
pci.sy_ on an XP Home CD with no SP updates included in it's Properties is 34.7kb, 35,550 bytes (it's in \i386).
pci.sy_ on an XP Home CD with SP2 updates included in it's Properties is 36.3kb, 37,184bytes (it's in \i386).
pci.sy_ on an official Microsoft SP2 upgrade CD in it's Properties is 36.3kb, 37,184bytes - there is only one, so SP2's pci.sys is therefore identical for XP Home, Pro, and MCE.
(I used Winzip to examine the contents of Xpsp2.exe to find that).
pci.sy_ in the official Microsoft SP3 updates download in it's Properties is 37,180 bytes - there is only one, so it's therefore identical for XP Home, Pro, and MCE.
(I used Winzip to examine the contents of WindowsXP-KB936929-SP3.exe to find that).
pci.sys in an XP Home installation with SP3 updates installed in it's Properties is 66.6kb, 68,224bytes
SO - the versions of pci.sys are different depending on whether or which SP updates are on the XP installation.
e.g. if you have updated the XP no SP updates installation by installing SP3 updates, you must use the pci.sy_ from the SP3 updates download, or a copy of pci.sys from another XP installation that has the SP3 updates installed. .
"The SMART status failed due to the "Multi Zone Error Rate" "
Write Error Rate / (a.k.a.)
Multi-Zone Error Rate
The total number of errors when writing a sector.
Not flagged as Critical (orange)
However, when I searched for: Multi Zone Error Rate
some "hits" listed the Multi Zone Error Rate for a particular drive and it's usually 0 (zero).
It could be the WD drive is starting to fail, but it hasn't reached the point yet where other things have been exceeded.
The SMART info has other info in it.
If you're getting high numbers for: reallocated sectors
or any more than only a few :uncorrectable sectors, the WD drive is probably going to fail in a short time.
Sometimes the SMART info shows you the threshold for each value as well as it's present value - the value that should not be exceeded - sometimes it doesn't.
A some of the present values are high, even if they haven't yet exceeded the threshold, that often indicates the drive is starting to fail.
If the WD diagnostics don't show the threshold values........
- I have a freeware utility called dtemp.exe (Drive Temp) that also shows SMART info and it shows the threshold values - however the author is no longer providing it and most links for it on the web are now dead.
- the freeware SpeedFan also has SMART info but I don't know if it shows the threshold values:
- there is often a hardware monitoring software program on the CD that comes with a mboard, or available from the web site in the downloads for the model, you can load in Windows - that often has SMART info in it - it may or may not have the threshold values in it. If you have a brand name system and if you can find which manufacturer made the mboard, the hardware monitoring software program for the same model or a similar OEM only model will work for your mboard.
Another thing that might indicate failure or failure in the near future is the temperature of the drive, and/or of chips on it's logic board. The Dos bootable SeaTools displays the current temp of the drive, if the drive is more recent and has the sensor, and so do the freeware Dtemp.exe and SpeedFan. I have found drives that are failing often have one or more chips that get way too hot - too hot to keep a fingertip on - . whether or not the drive has a temp sensor.
"I think I might just format the partition...nothing seems to be working..
I don't think re-formatting the drive, or deleting the partition(s) then making them again, which partitions and formats in one step, will solve your problem, but Zero filling the drive MIGHT.
However, it could be whatever makes SMART work properly on the drive cannot work properly anymore because something is damaged - firmware or circuitry.
You could try copying all the existing data on the WD drive elsewhere - e.g. in this case it would be preferable to copy just the data including hidden and system files, such as by using XXCOPY /CLONE - then try "Zero filling" or "Low Level Formatting" the drive (which actually Zero fills it), then copy the data back onto the drive.
e.g. To Zero fill the drive with the Dos bootable SeaTools, you press Z, but MAKE SURE you have selected the correct drive (you press D to toggle which physical drive is selected when there is more than one).
"I wasn't aware that XP with no SP does not support HD's above 127 GB. But I didn't notice anything unusual using that XP when it had no SP. "
Actually it's 128gb ( binary) in the bios and in Setup, = 137gb (decimal) manufacturer's size, before the drive has been partitioned and formatted.
If you run Setup from scratch from the XP no updates CD, the max physical drive or partition size XP can recognize is 128gb.
By the way, an XP CD not having SP1 printed on the original CD doesn't necessarily indicate it doesn't have SP1 updates.
An XP CD with SP2 or SP3 updates included has SP2 or SP3 printed on the CD, BUT an XP CD with SP1 updates DOES NOT have SP1 printed on it, at least it doesn't on all the SP1 CDs I've seen. You only know it has SP1 updates included after Setup has finished and you look in System Information.
If your supposedly no SP updates CD actually has SP1 updates, drives> 128gb are recognized properly initially, and XP supports recognizing USB 2.0 controllers. (You may also be able to tell whether it has SP1 updates by looking up the CD's specific volume label.)
If you run the second Repair option from the XP no updates CD, what many call a Repair Install, and I call a Repair Setup, if SP1 or later updates have already been installed on the XP installation, the Repair Setup doesn't touch most of the existing XP installation settings or the files it was updated with, unless they're corrupted or missing, ONLY IF they're on the original CD, so if the > 128gb drive or partition was seen as it's full size previously that doesn't change.
If you installed XP with the no updates CD when there was no drive > 128gb connected, you wouldn't notice anything wrong with the size of drives or partitions detected. If you then upated it with SP1 or later updates, after that when you connect a >128gb drive it's size is recognized properly, if the mboard's bios supports that and the drive (size) detection in the bios is set to Auto or LBA.
You can make yourself a slipstreamed CD, preferably a CD-R for the best possible compatibility with any optical drive, that has the contents of the XP no updates CD with SP2 or SP3 updates integtrated into it, and then you don't need to be concerned about the sizes of drives > 128gb. Also, XP's USB 2.0 support requires SP1 or later updates, and you can integrate SATA controller drivers or other drivers into the slipstreamed CD as well. You use your original Product Key.