Archived from groups: microsoft.public.win2000.general (
More info?)
After the install you can apply the reghack in this article.
48-Bit LBA Support for ATAPI Disk Drives in Windows 2000
http://support.microsoft.com/?id=305098
These articles may help.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q154690
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q159865
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q262448
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"ThePoet" <ThePoet@discussions.microsoft.com> wrote in message
news:270A3F02-FC77-4BFD-A9DD-C29B6AA1866D@microsoft.com...
|I have installed WIn2000 Server SP4, clean install on new system, NOT yet
| connected to network. As its a server, I did a basic install, then
installed
| mother board drivers a few days later, and I let system burn in, to see if
| there are any problems.
|
| The Mother board is a Asus P4V8X-X with an Intel P4 2.8, drives , 2 x 160
| gig maxtors. ( tested Maxtor drives, with MaxBlast before and after
| installing OS, and drives passed all tests. (although test does not see
| partition on second drive, even though it is partitioned and formatted and
| working fine) all other tests pass ( loop test, so passed many times )
|
| The drivers are the "VIa PT800/P4X533 series" drivers.
|
| I have 2 event ID's that I can not figure out. Both related to Hard drive
&
| Controller, as follows
| 1)
| Source Disk
| Category None
| Event ID 11
|
| The driver detected a controller error on \device\harddisk0\DRO
|
| 2)
| Source ATAPI
| Category None
| Event ID 5
|
| A parity error was detected on\device\IDE\IDEPORT0
|
|
| Microsoft says that the most likely cause is a bad cable, and I changed
but
| this appears not to be the problem. I couldn't find any more info on these
| event ID's.
|
| As for the system, it will re-boot itself, but only about every 2 to 4
days.
| As the system so far is stand alone, and never connected to a network or
| internet, it can not be a virus.
|
| Anyone have any ideas the best way to trouble shoot this. The only thing I
| can think of , is the actual motherboard drivers.
|