Re: Disk partitioning size

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Yes, and just because you have a large HD does not mean you have filled
it... So those sorts of problems would never surface until then and for some
NEVER...

--
Randem Systems
Your Installation Specialist
The Top Inno Setup Script Generator
http://www.randem.com/innoscript.html
Disk Read Error Press Ctl+Alt+Del to Restart
http://www.randem.com/discus/messages/9402/9406.html?1236319938



"Bill in Co." <not_really_here@xxxxxxxxxxxxx> wrote in message
news:%23iFc0wAvJHA.2376@xxxxxxxxxxxxxxxxxxxxxxx
And that happened YEARS ago.

Randem wrote:
Really, How would people find out that it was broken? The regular users
generally did not have HD's that were larger than 120GB So they could not
report it for it never affected them until after they got HD bigger than
137GB

--
Randem Systems
Your Installation Specialist
The Top Inno Setup Script Generator
http://www.randem.com/innoscript.html
Disk Read Error Press Ctl+Alt+Del to Restart
http://www.randem.com/discus/messages/9402/9406.html?1236319938



"John John (MVP)" <audetweld@xxxxxxxxxxx> wrote in message
news:eg2zuy9uJHA.4648@xxxxxxxxxxxxxxxxxxxxxxx
What the heck are you mumbling about now? SP1 included the 48-bit LBA
fix
(as released the Windows XP ATAPI driver had no 48-bit LBA support and
was
incapable of handling large LBA disks). It was very quickly discovered
that the 48-bit LBA fix supplied in SP1 caused problems when the machine
was put into hibernation or when the machine crashed and wrote a memory
dump file. So about 4 months after the release of SP1 a fix was
released
to fix the SP1 48-bit LBA ATAPI driver so that it could handle memory
dumps and hibernation.

I don't see the what the release date of SP1 has to do with anything, it
is a well known fact that the initial SP1 48-bit LBA driver had a bug
that
was later repaired. What is it that you don't understand? SP1 broke
what? The non existent 48-bit LBA support in the original Windows XP
release? Anyway, I'm done with this thread, you need to update your
knowledge and keep up with the developments in the field, you are at
least
6 years behind with this 28-bit 137GB LBA information, an eternity in
the
IT world!

Good luck with your endeavours!

John

Randem wrote:
So you are saying that SP1 broke XP? SInce XP was released in October
of
2001, from October 2001 to January 22, 2003 is quite a long time....




.

Relevant Pages

  • Re: Disk partitioning size
    ... (as released the Windows XP ATAPI driver had no 48-bit LBA support and was ... incapable of handling large LBA disks). ... So about 4 months after the release of SP1 a fix was released ...
    (microsoft.public.windowsxp.general)
  • Re: Disk partitioning size
    ... Randem Systems ... incapable of handling large LBA disks). ... that the 48-bit LBA fix supplied in SP1 caused problems when the machine ... So about 4 months after the release of SP1 a fix was released ...
    (microsoft.public.windowsxp.general)
  • Re: Windows XP SP1 BUG?
    ... theso insert the cd & do a upgrade will fix this? ... what about un installing ... sp1 will that work i will try it tells me a few programs may not run if i do ... up on the recovery console and went through the "upgrade install". ...
    (microsoft.public.windowsxp.security_admin)
  • Re: .oft templates / signature problem
    ... I didn't say it would fix the problem. ... I said OL2003 SP1 has the same ... behavior and registry value as OL2002 SP3+hotfix. ...
    (microsoft.public.outlook.general)
  • Re: 1005/DSRESTOR error after SP1
    ... I have seen this error on each and every SBS that was upgraded to SP1. ... have also seen that after some reboots it can be gone. ... Simply ignore this error for now, there will be a fix later, although I ...
    (microsoft.public.windows.server.sbs)