Re: Problem with disk upgrade of Windows XP Pro

From: Dustin Cook (bughunter.dustin_at_gmail.com)
Date: 11/16/05 

Date: 15 Nov 2005 17:09:11 -0800

Kadaitcha Man wrote:

> > Yes, I was. if his original hard disk (the original backup) is still
> > working, I suggested he should clone it again, using a different
> > package. Wasn't that easy to understand?
>
> So, you want him to spend his hard-earned just to score yourself a
> techno-point, uh.

Hmm. No.

> > You know, KM, I'm getting pretty tired of doing your homework for you.
> > Ghost 9 has no problems reading drive image files. Of course, it
> > shouldn't, being as how symantec bought powerquests drive image a few
> > years ago. You knew that, tho right?
>
> BWAHAHAHAHHAAH! And that makes them different packages, does it, snot***?
> You don't just want the poster to fork out cash just to make yourself look
> good, you want him to fork out cash to buy essentially the same program.
> BWAHAHAHAHAHHAAHAH! *** me dead, you're an idiot.

Technically, they are different packages. Different GUI, different
image file layout.

> BWAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA! *PMSL* The OS, you stupid
> shitstain, cannot write to what it cannot address. Large disks are seen by
> XP up to the limit of XP's built-in block addressing parameters. That means,
> *** for fucking brains, if he had a 250GB HDD and restored a 120GB image
> to that 250GB drive, XP would see the 120GB and use it.

And it would trash it. Here:
Note: Failure to install the required service packs and install the
Enable Big LBA patch can result in data loss when accessing the hard
disk beyond 137 Gigabytes. For more information regarding Windows
limitations and the 137 Gigabyte barrier please read Maxtor Knowledge
Base Answer ID 960 and Microsoft Knowledge Base Article 303013.

The drive restoration program is going to let windows access the full
capacity, as it resize s the partition information by default. Windows
will trash the guys data if he isn't running 48bit LBA mode.

> No, Dustbin. I didn't. <SNORT> You fucking gormless techno-idiot. You got
> any supporting evidence for your completely insane claim that "he will need
> to enable 48bit lba, or he WILL trash the new drives data when windows
> writes past the 120gig mark"? Hmmm? You haven't? Oh. Not surprising, really.

Why yes, yes I do.
 Warning Data corruption may occur if either of the following
conditions is true:
· You use this registry value to enable 48-bit LBA support in the
original release version of Windows XP Home Edition or of Windows XP
Professional.
· You install an earlier version of Windows on a disk partition that
was previously created by a 48-bit aware operating system, such as
Windows XP SP1. And that disk partition is equal to or larger than the
current addressable limit of 137 GB.

Now, as I said, if this guy loaded a fresh OEM windows XP even with
sp1, it's not enabled by default. You must set that key, or you WILL
trash the drive data. this only applies if the new hard disk is larger
then 127gigs in size. If so, and he's not running SP2, and doesnt have
the key set, he's going to *** his data by listening to your ignorant
ass.

> > Retard,
> > Dustbin Kook
> > http://boghunter.atspace.org
>
> --
> Dustbin Kook wrote:
> "he will need to enable 48bit lba, or he WILL trash the new drives data when
> windows
> writes past the 120gig mark." BWAHAHAHAHHAHAHA!

And it will. Microsoft even admits it. Without the 48lba mode turned
out, windows begins to write at the beginning of the drive, NOT past
the 127gig mark. The beginning of the drive contains mbr/partition
code, losing it can result in loss of data.

Windows 2000 has the same problem, btw.

Regards,
Dustin Cook
http://bughunter.atspace.org