OK, Now I'm Livid - Windows 2000 SP4 Trashed Another Large Drive

I just built this AMD box...

MSI K8N Neo4-F Motherboard
AMD Athlon 64 3200+
1GB Crucial Ram
200GB Western Digital HD
EVGA Geforce 256 Video Card

I installed the Windows 2000 SP4, then after about 2 hours of installs
and copying data from my old drive **POW** file copy error! I was
forced to reboot and just like last time Chkdsk went to work trashing
the drive. This time it was an AMD system with a 200GB Western
Digital drive, last time it was an Intel system and a 200GB Maxtor.

I'm desperately trying to figure out what's going on. Are there any
known issues with W2K and large drives?

I did find this link, so I know I'm not the only one that's
experiencing this kind of data loss...

http://groups.google.com/group/micro...05e8ddc83b879b

Any information about how I can prevent this in the future would be
great appreciated.

Thank you,

Cope242

In article <1174957303.548663.149550@e65g2000hsc.googlegroups .com>,
cope242 <waxtrax242@hotmail.com> writes

>I'm desperately trying to figure out what's going on. Are there any
>known issues with W2K and large drives?

Yes! Very well known!

http://www.48bitlba.com/win2k.htm

--
(\__/)
(='.'=) This is Bunny. Copy and paste Bunny into your
(")_(") signature to help him gain world domination.

Previously cope242 <waxtrax242@hotmail.com> wrote:
> I just built this AMD box...

> MSI K8N Neo4-F Motherboard
> AMD Athlon 64 3200+
> 1GB Crucial Ram
> 200GB Western Digital HD
> EVGA Geforce 256 Video Card

> I installed the Windows 2000 SP4, then after about 2 hours of installs
> and copying data from my old drive **POW** file copy error! I was
> forced to reboot and just like last time Chkdsk went to work trashing
> the drive. This time it was an AMD system with a 200GB Western
> Digital drive, last time it was an Intel system and a 200GB Maxtor.

> I'm desperately trying to figure out what's going on. Are there any
> known issues with W2K and large drives?

> I did find this link, so I know I'm not the only one that's
> experiencing this kind of data loss...

> http://groups.google.com/group/micro...05e8ddc83b879b

> Any information about how I can prevent this in the future would be
> great appreciated.

> Thank you,

I don't know about what w2k systems are affected, but some MS OSes
suffer from a 128GB wrap-around bug. The problem here is that the
drivers cannot handle more than said disk-space, but with an
extraordinary degree of incompetence, the disk size is never verified
to be smaller. As a consequence, any write to a sector above the
limit will just be to a sector 128GB nearer to the start of the disk
and will trash anything that is there. In XP this bug was only fixed
in SP2.

Arno

On 26 Mar 2007 18:01:43 -0700 "cope242" <waxtrax242@hotmail.com> wrote in
Message id: <1174957303.548663.149550@e65g2000hsc.googlegroups .com>:

>I just built this AMD box...
>
>MSI K8N Neo4-F Motherboard
>AMD Athlon 64 3200+
>1GB Crucial Ram
>200GB Western Digital HD
>EVGA Geforce 256 Video Card
>
>I installed the Windows 2000 SP4, then after about 2 hours of installs
>and copying data from my old drive **POW** file copy error! I was
>forced to reboot and just like last time Chkdsk went to work trashing
>the drive. This time it was an AMD system with a 200GB Western
>Digital drive, last time it was an Intel system and a 200GB Maxtor.
>
>I'm desperately trying to figure out what's going on. Are there any
>known issues with W2K and large drives?
>
>I did find this link, so I know I'm not the only one that's
>experiencing this kind of data loss...
>
>http://groups.google.com/group/micro...05e8ddc83b879b
>
>Any information about how I can prevent this in the future would be
>great appreciated.

Save the following text to a file, and call it lba48.reg. Then double
click on it and allow it to merge in your registry. I'd recommend you
install Windows on a partition which is less than 137GB initially.

REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\atapi\Parameters]
"EnableBigLba"=dword:00000001

"Mike Tomlinson" <mike@jasper.org.uk> wrote in message news:19furYBfoLCGFwHz@jasper.org.uk
> In article 1174957303.548663.149550@e65g2000hsc.googlegroups. com, cope242 <waxtrax242@hotmail.com> writes
>
> > I'm desperately trying to figure out what's going on. Are there any
> > known issues with W2K and large drives?

> Yes! Very well known!

Yeah right.

>
> http://www.48bitlba.com/win2k.htm

Pity it doesn't say anything about SP4.

"Arno Wagner" <me@privacy.net> wrote in message news:56rtubF29qei0U1@mid.individual.net
> Previously cope242 <waxtrax242@hotmail.com> wrote:
> > I just built this AMD box...
>
> > MSI K8N Neo4-F Motherboard
> > AMD Athlon 64 3200+
> > 1GB Crucial Ram
> > 200GB Western Digital HD
> > EVGA Geforce 256 Video Card
>
> > I installed the Windows 2000 SP4, then after about 2 hours of installs
> > and copying data from my old drive **POW** file copy error! I was
> > forced to reboot and just like last time Chkdsk went to work trashing
> > the drive. This time it was an AMD system with a 200GB Western
> > Digital drive, last time it was an Intel system and a 200GB Maxtor.
>
> > I'm desperately trying to figure out what's going on. Are there any
> > known issues with W2K and large drives?
>
> > I did find this link, so I know I'm not the only one that's
> > experiencing this kind of data loss...
>
> >
http://groups.google.com/group/micro...05e8ddc83b879b
>
> > Any information about how I can prevent this in the future would be
> > great appreciated.
>
> > Thank you,
>
> I don't know about what w2k systems are affected, but some MS OSes
> suffer from a 128GB wrap-around bug.

There is no 128GB "wrap-around bug", babblebot.
There is a 137GB problem.

> The problem here is that the drivers cannot handle more than said disk-space,

> but with an extraordinary degree of incompetence,

Like your's, babblebot?

> the disk size is never verified to be smaller.

Nice explanation babblebot, I see you have got it licked perfectly.
You are in your howmaniest brainfarct now?

> As a consequence, any write to a sector above the limit will just be to a
> sector 128GB nearer to the start of the disk and will trash anything that
> is there.

137GB, babblebot, 137GB. Got it now?

> In XP this bug was only fixed in SP2.

Wrong again.

>
> Arno

In article <46098af3$0$97250$892e7fe2@authen.yellow.readfreen ews.net>,
Folkert Rienstra <see_reply-to@myweb.nl> writes

>Pity it doesn't say anything about SP4.

You're being more than usually dense, Folkert. SP4 includes all
previous service packs. Take your Prozac.

--
(\__/)
(='.'=) This is Bunny. Copy and paste Bunny into your
(")_(") signature to help him gain world domination.

"Folkert Rienstra" <see_reply-to@myweb.nl> schreef in bericht
news:46098af3$1$97250
>>
>> I don't know about what w2k systems are affected, but some MS OSes
>> suffer from a 128GB wrap-around bug.
>
> There is no 128GB "wrap-around bug", babblebot.

Yes, there is ****er. "wrap-around bug" actually pretty much descibes what's
happening.

> There is a 137GB problem.

That's a wrong value and and does not describe the problem. I like the
"128Gb wrap-around bug" better: the value is binary correct and it descibes
consequences of the issue.

--
Joep