Disk partitioning size

[Daave]

Thanks, JS. It seems like you and John John have demonstrated that
Randem's tests were flawed. (Surprise, surprise.) Therefore, his
conclusions are erroneous, and his advice can be disregarded.

Finished the test, computer reboots without any problems!

For anyone interested I have included my step by step
testing.

Step by Step:
Installed 160GB WD IDE drive
Installed Windows XP Pro
(SP3 Included, single 149GB NTFS Partition)
Installed Motherboard drivers
Installed Network chip drivers
Turned off Automatic Updates
Downloaded Installed COMODO Firewall/AV
Ran AV scan
Download and installed TweakUi
Turned off "Auto Play" on DVD drive
Downloaded Installed NVIDIA video card drivers
Password protected user account
Changed screen resolution
Changed Windows Explorer to "Detail" and show hidden files.

Checked C: partition properties.
Decimal values
Used = 6.04GB
Free = 153.99GB
Capacity = 160.03GB

Started task of filling up the drive with files and folders
1) Used previous burned DVD media to copy file to new folder on hard
drive. 2) Checked "Disk Defragmenter", no defrag required, analysis
shows only a very
small number of fragmented files, everything is packed tight.
3) Activated Windows XP.
4) Created a "Restore Point"
5) Disabled AV and Firewall
6) Ran Windows Update - Custom Option
(Installed latest version of WGA)
7) Installed all "Critical Updates" except for IE7.
8) Updates installed, reboot required.
9) Install .NET Framework 3.5 SP1 optional update.
10) Copied from DVD to new folders bunch of files.
11) Repeatedly copied contents existing folders to newly created
folders to begin filling up the hard drive. Rebooted the computer a
couple of times during this process (both cold and warm reboots)
12) Cool Boot with 135GB Decimal (125GB Binary) used drive space, no
problems.
13) Disk Defragmenter analysis showed no files or clusters in use
beyond 135GB.
14) Copied a single file .ISO from DVD (2.6GB Decimal / 2.43 Binary)
file from DVD drive
to hard disk. this puts the used drive space past the 137 GB barrier
(137.621GB).
15) Warm or Cold boot without any problems.
16) One final test, added another 2.6GB file to hard drive. Warm and
Cold reboot without any problems.

The world is not flat...

To test:

1 - Copy files or folders to large hard disk till it reaches past
137GB 2 - Reboot

Something that simple even you guys can follow it. I have given the
solution to this problem that many have used to fix the problem. But
you guys still tell the world the world is flat... I guess this
problem must be in the other people's minds who have this problem
and have had it fixed. Please tell this user he was imagining his
hard disk crash
http://www.hardwareanalysis.com/content/topic/19004/?o=400#556461
BTW: Here are the articles that MS has posted and the ONLY error
they have fixed. Show me anywhere in these documents where it states
that MS has fixed this particular problem.

List of Fixes in Windows XP by Service Pack

SP1 - SP1a - http://support.microsoft.com/kb/324720
SP2 - http://support.microsoft.com/kb/811113
SP3 - http://support.microsoft.com/kb/946480/

Corrupted Large Hard Disk Fix from Hibernation

http://support.microsoft.com/default.aspx?scid=kb;[LN];331958


--
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

I'll wait up for this too. But, don't hold your breath.

JS wrote:
OK, tell me what to test.
I can setup my test PC for XP or Vista
Give me the steps to perform
(in ordered sequence).
and I'll run the test.

I have a spare 160GB drive, will that do?

--
JS
http:/www.pagestart.com


Whatever, you LACK of testing abilities shines very brightly
here. All you
can do is attempt to verbally tear down others withh no evidence
what-so-ever. It's a simple test why can't you perform it? Or is
that very
evident?

--
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



I'm sure your "tests" are equally as substantive and valid as
Twayne's (alleged) "tests" on registry cleaners ("speeding up
the system"). I'll
leave it at that. LOL.

Randem wrote:
All it take is a simple test... but some how you guys can't
seem to do
that... hmmmm.

--
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



Yeah, I think so!

John John (MVP) wrote:
There are tons of Windows XP OEM installation that were
shipped out on
large drives and none of them are failing because of problems
with 48-bit LBA addressing! I don't care what you say the
facts and experience of others simply do not support your
claims. Computer manufacturers have been shipping XP
installations on 160GB and 250GB
hard drives for many years now and users have been installing
retail
versions on large drives for as many years and your assertions
simply
do
not bear out. If what you say were true there would have been
*millions* of complaints about this and the problem would be
front page
news and discussed all over the place. I have seen many, many
Windows
XP installations on large hard drives filed to near capacity
and none
have succumbed to the 137GB 28-bit LBA barrier, this problem
was addressed with SP1 and your information is out of date

John

Randem wrote:
It has been tested in SP2 and SP3 with ALL updates applied so
there
is
certainly no mistake... It is very easy to replicate.

 

[Bill in Co.]

Next up on the list is the (alleged by some) "improvement in system speed"
obtained by using registry cleaners! LOL.

Thanks, JS. It seems like you and John John have demonstrated that
Randem's tests were flawed. (Surprise, surprise.) Therefore, his
conclusions are erroneous, and his advice can be disregarded.

Finished the test, computer reboots without any problems!

For anyone interested I have included my step by step
testing.

Step by Step:
Installed 160GB WD IDE drive
Installed Windows XP Pro
(SP3 Included, single 149GB NTFS Partition)
Installed Motherboard drivers
Installed Network chip drivers
Turned off Automatic Updates
Downloaded Installed COMODO Firewall/AV
Ran AV scan
Download and installed TweakUi
Turned off "Auto Play" on DVD drive
Downloaded Installed NVIDIA video card drivers
Password protected user account
Changed screen resolution
Changed Windows Explorer to "Detail" and show hidden files.

Checked C: partition properties.
Decimal values
Used = 6.04GB
Free = 153.99GB
Capacity = 160.03GB

Started task of filling up the drive with files and folders
1) Used previous burned DVD media to copy file to new folder on hard
drive. 2) Checked "Disk Defragmenter", no defrag required, analysis
shows only a very
small number of fragmented files, everything is packed tight.
3) Activated Windows XP.
4) Created a "Restore Point"
5) Disabled AV and Firewall
6) Ran Windows Update - Custom Option
(Installed latest version of WGA)
7) Installed all "Critical Updates" except for IE7.
8) Updates installed, reboot required.
9) Install .NET Framework 3.5 SP1 optional update.
10) Copied from DVD to new folders bunch of files.
11) Repeatedly copied contents existing folders to newly created
folders to begin filling up the hard drive. Rebooted the computer a
couple of times during this process (both cold and warm reboots)
12) Cool Boot with 135GB Decimal (125GB Binary) used drive space, no
problems.
13) Disk Defragmenter analysis showed no files or clusters in use
beyond 135GB.
14) Copied a single file .ISO from DVD (2.6GB Decimal / 2.43 Binary)
file from DVD drive
to hard disk. this puts the used drive space past the 137 GB barrier
(137.621GB).
15) Warm or Cold boot without any problems.
16) One final test, added another 2.6GB file to hard drive. Warm and
Cold reboot without any problems.

The world is not flat...

To test:

1 - Copy files or folders to large hard disk till it reaches past
137GB 2 - Reboot

Something that simple even you guys can follow it. I have given the
solution to this problem that many have used to fix the problem. But
you guys still tell the world the world is flat... I guess this
problem must be in the other people's minds who have this problem
and have had it fixed. Please tell this user he was imagining his
hard disk crash
http://www.hardwareanalysis.com/content/topic/19004/?o=400#556461
BTW: Here are the articles that MS has posted and the ONLY error
they have fixed. Show me anywhere in these documents where it states
that MS has fixed this particular problem.

List of Fixes in Windows XP by Service Pack

SP1 - SP1a - http://support.microsoft.com/kb/324720
SP2 - http://support.microsoft.com/kb/811113
SP3 - http://support.microsoft.com/kb/946480/

Corrupted Large Hard Disk Fix from Hibernation

http://support.microsoft.com/default.aspx?scid=kb;[LN];331958


--
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



I'll wait up for this too. But, don't hold your breath.

JS wrote:
OK, tell me what to test.
I can setup my test PC for XP or Vista
Give me the steps to perform
(in ordered sequence).
and I'll run the test.

I have a spare 160GB drive, will that do?

--
JS
http:/www.pagestart.com


Whatever, you LACK of testing abilities shines very brightly
here. All you
can do is attempt to verbally tear down others withh no evidence
what-so-ever. It's a simple test why can't you perform it? Or is
that very
evident?

--
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



I'm sure your "tests" are equally as substantive and valid as
Twayne's (alleged) "tests" on registry cleaners ("speeding up
the system"). I'll
leave it at that. LOL.

Randem wrote:
All it take is a simple test... but some how you guys can't
seem to do
that... hmmmm.

--
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



Yeah, I think so!

John John (MVP) wrote:
There are tons of Windows XP OEM installation that were
shipped out on
large drives and none of them are failing because of problems
with 48-bit LBA addressing! I don't care what you say the
facts and experience of others simply do not support your
claims. Computer manufacturers have been shipping XP
installations on 160GB and 250GB
hard drives for many years now and users have been installing
retail
versions on large drives for as many years and your assertions
simply
do
not bear out. If what you say were true there would have been
*millions* of complaints about this and the problem would be
front page
news and discussed all over the place. I have seen many, many
Windows
XP installations on large hard drives filed to near capacity
and none
have succumbed to the 137GB 28-bit LBA barrier, this problem
was addressed with SP1 and your information is out of date

John

Randem wrote:
It has been tested in SP2 and SP3 with ALL updates applied so
there
is
certainly no mistake... It is very easy to replicate.

 

[Joe Grover]

I just had to reload a box last week for that. The guy said, "So I
installed this registry cleaner..." and I just told him to give me the
machine.

Next up on the list is the (alleged by some) "improvement in system speed"
obtained by using registry cleaners! LOL.

Thanks, JS. It seems like you and John John have demonstrated that
Randem's tests were flawed. (Surprise, surprise.) Therefore, his
conclusions are erroneous, and his advice can be disregarded.

Finished the test, computer reboots without any problems!

For anyone interested I have included my step by step
testing.

Step by Step:
Installed 160GB WD IDE drive
Installed Windows XP Pro
(SP3 Included, single 149GB NTFS Partition)
Installed Motherboard drivers
Installed Network chip drivers
Turned off Automatic Updates
Downloaded Installed COMODO Firewall/AV
Ran AV scan
Download and installed TweakUi
Turned off "Auto Play" on DVD drive
Downloaded Installed NVIDIA video card drivers
Password protected user account
Changed screen resolution
Changed Windows Explorer to "Detail" and show hidden files.

Checked C: partition properties.
Decimal values
Used = 6.04GB
Free = 153.99GB
Capacity = 160.03GB

Started task of filling up the drive with files and folders
1) Used previous burned DVD media to copy file to new folder on hard
drive. 2) Checked "Disk Defragmenter", no defrag required, analysis
shows only a very
small number of fragmented files, everything is packed tight.
3) Activated Windows XP.
4) Created a "Restore Point"
5) Disabled AV and Firewall
6) Ran Windows Update - Custom Option
(Installed latest version of WGA)
7) Installed all "Critical Updates" except for IE7.
8) Updates installed, reboot required.
9) Install .NET Framework 3.5 SP1 optional update.
10) Copied from DVD to new folders bunch of files.
11) Repeatedly copied contents existing folders to newly created
folders to begin filling up the hard drive. Rebooted the computer a
couple of times during this process (both cold and warm reboots)
12) Cool Boot with 135GB Decimal (125GB Binary) used drive space, no
problems.
13) Disk Defragmenter analysis showed no files or clusters in use
beyond 135GB.
14) Copied a single file .ISO from DVD (2.6GB Decimal / 2.43 Binary)
file from DVD drive
to hard disk. this puts the used drive space past the 137 GB barrier
(137.621GB).
15) Warm or Cold boot without any problems.
16) One final test, added another 2.6GB file to hard drive. Warm and
Cold reboot without any problems.


The world is not flat...

To test:

1 - Copy files or folders to large hard disk till it reaches past
137GB 2 - Reboot

Something that simple even you guys can follow it. I have given the
solution to this problem that many have used to fix the problem. But
you guys still tell the world the world is flat... I guess this
problem must be in the other people's minds who have this problem
and have had it fixed. Please tell this user he was imagining his
hard disk crash
http://www.hardwareanalysis.com/content/topic/19004/?o=400#556461
BTW: Here are the articles that MS has posted and the ONLY error
they have fixed. Show me anywhere in these documents where it states
that MS has fixed this particular problem.

List of Fixes in Windows XP by Service Pack

SP1 - SP1a - http://support.microsoft.com/kb/324720
SP2 - http://support.microsoft.com/kb/811113
SP3 - http://support.microsoft.com/kb/946480/

Corrupted Large Hard Disk Fix from Hibernation

http://support.microsoft.com/default.aspx?scid=kb;[LN];331958


--
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



I'll wait up for this too. But, don't hold your breath.

JS wrote:
OK, tell me what to test.
I can setup my test PC for XP or Vista
Give me the steps to perform
(in ordered sequence).
and I'll run the test.

I have a spare 160GB drive, will that do?

--
JS
http:/www.pagestart.com


Whatever, you LACK of testing abilities shines very brightly
here. All you
can do is attempt to verbally tear down others withh no evidence
what-so-ever. It's a simple test why can't you perform it? Or is
that very
evident?

--
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



I'm sure your "tests" are equally as substantive and valid as
Twayne's (alleged) "tests" on registry cleaners ("speeding up
the system"). I'll
leave it at that. LOL.

Randem wrote:
All it take is a simple test... but some how you guys can't
seem to do
that... hmmmm.

--
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



Yeah, I think so!

John John (MVP) wrote:
There are tons of Windows XP OEM installation that were
shipped out on
large drives and none of them are failing because of problems
with 48-bit LBA addressing! I don't care what you say the
facts and experience of others simply do not support your
claims. Computer manufacturers have been shipping XP
installations on 160GB and 250GB
hard drives for many years now and users have been installing
retail
versions on large drives for as many years and your assertions
simply
do
not bear out. If what you say were true there would have been
*millions* of complaints about this and the problem would be
front page
news and discussed all over the place. I have seen many, many
Windows
XP installations on large hard drives filed to near capacity
and none
have succumbed to the 137GB 28-bit LBA barrier, this problem
was addressed with SP1 and your information is out of date

John

Randem wrote:
It has been tested in SP2 and SP3 with ALL updates applied so
there
is
certainly no mistake... It is very easy to replicate.

 

[Randem]

Funny, now go back to compare the iso's you copied that put you over the
137gb size see if it is equal in contents to the original. When you find
that out copy that file back onto the HD while windows is running. Courious,
did you also copy the files to the HD while windows was not running then
boot the HD?

And it is not at all surprising that the test that was accepted was one that
matches what you want it to be and all else is bogus. Hmmm, that sounds
familiar. You have no real evidence of either test but you tout one over the
other without even performing it yourself even though people all over are
complaining about this problem and MS's Fixboot or any other MS reconized
solution works but mine does.... EXPLAIN THAT AWAY! That is something you
cannot control. Ask the users that the solution has fix the problem or are
you afraid the answer may not be what you want it to be.

More people with this unresolved error that my solution has fixed. The
internet is covered with this issue with no MS solution. I guess that they
have imagined it also...
http://www.hardwareanalysis.com/content/topic/19004/?o=400

--
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

Next up on the list is the (alleged by some) "improvement in system speed"
obtained by using registry cleaners! LOL.

Thanks, JS. It seems like you and John John have demonstrated that
Randem's tests were flawed. (Surprise, surprise.) Therefore, his
conclusions are erroneous, and his advice can be disregarded.

Finished the test, computer reboots without any problems!

For anyone interested I have included my step by step
testing.

Step by Step:
Installed 160GB WD IDE drive
Installed Windows XP Pro
(SP3 Included, single 149GB NTFS Partition)
Installed Motherboard drivers
Installed Network chip drivers
Turned off Automatic Updates
Downloaded Installed COMODO Firewall/AV
Ran AV scan
Download and installed TweakUi
Turned off "Auto Play" on DVD drive
Downloaded Installed NVIDIA video card drivers
Password protected user account
Changed screen resolution
Changed Windows Explorer to "Detail" and show hidden files.

Checked C: partition properties.
Decimal values
Used = 6.04GB
Free = 153.99GB
Capacity = 160.03GB

Started task of filling up the drive with files and folders
1) Used previous burned DVD media to copy file to new folder on hard
drive. 2) Checked "Disk Defragmenter", no defrag required, analysis
shows only a very
small number of fragmented files, everything is packed tight.
3) Activated Windows XP.
4) Created a "Restore Point"
5) Disabled AV and Firewall
6) Ran Windows Update - Custom Option
(Installed latest version of WGA)
7) Installed all "Critical Updates" except for IE7.
8) Updates installed, reboot required.
9) Install .NET Framework 3.5 SP1 optional update.
10) Copied from DVD to new folders bunch of files.
11) Repeatedly copied contents existing folders to newly created
folders to begin filling up the hard drive. Rebooted the computer a
couple of times during this process (both cold and warm reboots)
12) Cool Boot with 135GB Decimal (125GB Binary) used drive space, no
problems.
13) Disk Defragmenter analysis showed no files or clusters in use
beyond 135GB.
14) Copied a single file .ISO from DVD (2.6GB Decimal / 2.43 Binary)
file from DVD drive
to hard disk. this puts the used drive space past the 137 GB barrier
(137.621GB).
15) Warm or Cold boot without any problems.
16) One final test, added another 2.6GB file to hard drive. Warm and
Cold reboot without any problems.


The world is not flat...

To test:

1 - Copy files or folders to large hard disk till it reaches past
137GB 2 - Reboot

Something that simple even you guys can follow it. I have given the
solution to this problem that many have used to fix the problem. But
you guys still tell the world the world is flat... I guess this
problem must be in the other people's minds who have this problem
and have had it fixed. Please tell this user he was imagining his
hard disk crash
http://www.hardwareanalysis.com/content/topic/19004/?o=400#556461
BTW: Here are the articles that MS has posted and the ONLY error
they have fixed. Show me anywhere in these documents where it states
that MS has fixed this particular problem.

List of Fixes in Windows XP by Service Pack

SP1 - SP1a - http://support.microsoft.com/kb/324720
SP2 - http://support.microsoft.com/kb/811113
SP3 - http://support.microsoft.com/kb/946480/

Corrupted Large Hard Disk Fix from Hibernation

http://support.microsoft.com/default.aspx?scid=kb;[LN];331958


--
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



I'll wait up for this too. But, don't hold your breath.

JS wrote:
OK, tell me what to test.
I can setup my test PC for XP or Vista
Give me the steps to perform
(in ordered sequence).
and I'll run the test.

I have a spare 160GB drive, will that do?

--
JS
http:/www.pagestart.com


Whatever, you LACK of testing abilities shines very brightly
here. All you
can do is attempt to verbally tear down others withh no evidence
what-so-ever. It's a simple test why can't you perform it? Or is
that very
evident?

--
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



I'm sure your "tests" are equally as substantive and valid as
Twayne's (alleged) "tests" on registry cleaners ("speeding up
the system"). I'll
leave it at that. LOL.

Randem wrote:
All it take is a simple test... but some how you guys can't
seem to do
that... hmmmm.

--
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



Yeah, I think so!

John John (MVP) wrote:
There are tons of Windows XP OEM installation that were
shipped out on
large drives and none of them are failing because of problems
with 48-bit LBA addressing! I don't care what you say the
facts and experience of others simply do not support your
claims. Computer manufacturers have been shipping XP
installations on 160GB and 250GB
hard drives for many years now and users have been installing
retail
versions on large drives for as many years and your assertions
simply
do
not bear out. If what you say were true there would have been
*millions* of complaints about this and the problem would be
front page
news and discussed all over the place. I have seen many, many
Windows
XP installations on large hard drives filed to near capacity
and none
have succumbed to the 137GB 28-bit LBA barrier, this problem
was addressed with SP1 and your information is out of date

John

Randem wrote:
It has been tested in SP2 and SP3 with ALL updates applied so
there
is
certainly no mistake... It is very easy to replicate.

 

[Randem]

I am interested in your test to find out why it differs from mine if you are
interested in discussing this in a professional manner without all the
hyperbole of the others.

You copied 1 file, I copied a whole nested folder structure. In my test the
file system structure gets corrupted and has to be recreated and this is why
Windows will not boot. I will try this both ways with a few other test along
with 1 file crosing the boundry and multiple folders crossing.

Could you do a compare of the file that crosses the boundry to see if it the
same as the original?



--
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

Finished the test, computer reboots without any problems!

For anyone interested I have included my step by step
testing.

Step by Step:
Installed 160GB WD IDE drive
Installed Windows XP Pro
(SP3 Included, single 149GB NTFS Partition)
Installed Motherboard drivers
Installed Network chip drivers
Turned off Automatic Updates
Downloaded Installed COMODO Firewall/AV
Ran AV scan
Download and installed TweakUi
Turned off "Auto Play" on DVD drive
Downloaded Installed NVIDIA video card drivers
Password protected user account
Changed screen resolution
Changed Windows Explorer to "Detail" and show hidden files.

Checked C: partition properties.
Decimal values
Used = 6.04GB
Free = 153.99GB
Capacity = 160.03GB

Started task of filling up the drive with files and folders
1) Used previous burned DVD media to copy file to new folder on hard
drive.
2) Checked "Disk Defragmenter", no defrag required, analysis shows only a
very
small number of fragmented files, everything is packed tight.
3) Activated Windows XP.
4) Created a "Restore Point"
5) Disabled AV and Firewall
6) Ran Windows Update - Custom Option
(Installed latest version of WGA)
7) Installed all "Critical Updates" except for IE7.
8) Updates installed, reboot required.
9) Install .NET Framework 3.5 SP1 optional update.
10) Copied from DVD to new folders bunch of files.
11) Repeatedly copied contents existing folders to newly created folders
to begin filling up the hard drive. Rebooted the computer a couple of
times
during this process (both cold and warm reboots)
12) Cool Boot with 135GB Decimal (125GB Binary) used drive space, no
problems.
13) Disk Defragmenter analysis showed no files or clusters in use beyond
135GB.
14) Copied a single file .ISO from DVD (2.6GB Decimal / 2.43 Binary) file
from DVD drive
to hard disk. this puts the used drive space past the 137 GB barrier
(137.621GB).
15) Warm or Cold boot without any problems.
16) One final test, added another 2.6GB file to hard drive. Warm and Cold
reboot without any problems.

--
JS
http:/www.pagestart.com

The world is not flat...

To test:

1 - Copy files or folders to large hard disk till it reaches past 137GB

2 - Reboot

Something that simple even you guys can follow it. I have given the
solution to this problem that many have used to fix the problem. But you
guys still tell the world the world is flat... I guess this problem must
be in the other people's minds who have this problem and have had it
fixed. Please tell this user he was imagining his hard disk crash
http://www.hardwareanalysis.com/content/topic/19004/?o=400#556461


BTW: Here are the articles that MS has posted and the ONLY error they
have fixed. Show me anywhere in these documents where it states that MS
has fixed this particular problem.

List of Fixes in Windows XP by Service Pack

SP1 - SP1a - http://support.microsoft.com/kb/324720
SP2 - http://support.microsoft.com/kb/811113
SP3 - http://support.microsoft.com/kb/946480/

Corrupted Large Hard Disk Fix from Hibernation

http://support.microsoft.com/default.aspx?scid=kb;[LN];331958


--
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

I'll wait up for this too. But, don't hold your breath.

JS wrote:
OK, tell me what to test.
I can setup my test PC for XP or Vista
Give me the steps to perform
(in ordered sequence).
and I'll run the test.

I have a spare 160GB drive, will that do?

--
JS
http:/www.pagestart.com


Whatever, you LACK of testing abilities shines very brightly here. All
you
can do is attempt to verbally tear down others withh no evidence
what-so-ever. It's a simple test why can't you perform it? Or is that
very
evident?

--
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



I'm sure your "tests" are equally as substantive and valid as
Twayne's
(alleged) "tests" on registry cleaners ("speeding up the system").
I'll
leave it at that. LOL.

Randem wrote:
All it take is a simple test... but some how you guys can't seem to
do
that... hmmmm.

--
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



Yeah, I think so!

John John (MVP) wrote:
There are tons of Windows XP OEM installation that were shipped
out on
large drives and none of them are failing because of problems with
48-bit LBA addressing! I don't care what you say the facts and
experience of others simply do not support your claims. Computer
manufacturers have been shipping XP installations on 160GB and
250GB
hard drives for many years now and users have been installing
retail
versions on large drives for as many years and your assertions
simply
do
not bear out. If what you say were true there would have been
*millions* of complaints about this and the problem would be front
page
news and discussed all over the place. I have seen many, many
Windows
XP installations on large hard drives filed to near capacity and
none
have succumbed to the 137GB 28-bit LBA barrier, this problem was
addressed with SP1 and your information is out of date

John

Randem wrote:
It has been tested in SP2 and SP3 with ALL updates applied so
there
is
certainly no mistake... It is very easy to replicate.

 

[JS]

1) All files where copied to the hard drive while windows was running.

2) I will verify the .ISO on the hard drive matches the source as you
requested.

3) "And it is not at all surprising that the test that was accepted was one
that
matches what you want it to be and all else is bogus. "

My answer that statement is: "I had no predetermined outcome in mind
when I conducted this test, it was performed out of curiosity."

Each and every step is detailed in my previous post for your review.
This took a significant amount of "my" time to perform and document.
It was conducted by me and no one else. I did not refute your claim
but merely stated my results and resent your implication of bias.

--
JS
http:/www.pagestart.com

Funny, now go back to compare the iso's you copied that put you over the
137gb size see if it is equal in contents to the original. When you find
that out copy that file back onto the HD while windows is running.
Courious, did you also copy the files to the HD while windows was not
running then boot the HD?

And it is not at all surprising that the test that was accepted was one
that matches what you want it to be and all else is bogus. Hmmm, that
sounds familiar. You have no real evidence of either test but you tout one
over the other without even performing it yourself even though people all
over are complaining about this problem and MS's Fixboot or any other MS
reconized solution works but mine does.... EXPLAIN THAT AWAY! That is
something you cannot control. Ask the users that the solution has fix the
problem or are you afraid the answer may not be what you want it to be.

More people with this unresolved error that my solution has fixed. The
internet is covered with this issue with no MS solution. I guess that they
have imagined it also...
http://www.hardwareanalysis.com/content/topic/19004/?o=400

--
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

Next up on the list is the (alleged by some) "improvement in system
speed" obtained by using registry cleaners! LOL.

Thanks, JS. It seems like you and John John have demonstrated that
Randem's tests were flawed. (Surprise, surprise.) Therefore, his
conclusions are erroneous, and his advice can be disregarded.


JS wrote:
Finished the test, computer reboots without any problems!

For anyone interested I have included my step by step
testing.

Step by Step:
Installed 160GB WD IDE drive
Installed Windows XP Pro
(SP3 Included, single 149GB NTFS Partition)
Installed Motherboard drivers
Installed Network chip drivers
Turned off Automatic Updates
Downloaded Installed COMODO Firewall/AV
Ran AV scan
Download and installed TweakUi
Turned off "Auto Play" on DVD drive
Downloaded Installed NVIDIA video card drivers
Password protected user account
Changed screen resolution
Changed Windows Explorer to "Detail" and show hidden files.

Checked C: partition properties.
Decimal values
Used = 6.04GB
Free = 153.99GB
Capacity = 160.03GB

Started task of filling up the drive with files and folders
1) Used previous burned DVD media to copy file to new folder on hard
drive. 2) Checked "Disk Defragmenter", no defrag required, analysis
shows only a very
small number of fragmented files, everything is packed tight.
3) Activated Windows XP.
4) Created a "Restore Point"
5) Disabled AV and Firewall
6) Ran Windows Update - Custom Option
(Installed latest version of WGA)
7) Installed all "Critical Updates" except for IE7.
8) Updates installed, reboot required.
9) Install .NET Framework 3.5 SP1 optional update.
10) Copied from DVD to new folders bunch of files.
11) Repeatedly copied contents existing folders to newly created
folders to begin filling up the hard drive. Rebooted the computer a
couple of times during this process (both cold and warm reboots)
12) Cool Boot with 135GB Decimal (125GB Binary) used drive space, no
problems.
13) Disk Defragmenter analysis showed no files or clusters in use
beyond 135GB.
14) Copied a single file .ISO from DVD (2.6GB Decimal / 2.43 Binary)
file from DVD drive
to hard disk. this puts the used drive space past the 137 GB barrier
(137.621GB).
15) Warm or Cold boot without any problems.
16) One final test, added another 2.6GB file to hard drive. Warm and
Cold reboot without any problems.


The world is not flat...

To test:

1 - Copy files or folders to large hard disk till it reaches past
137GB 2 - Reboot

Something that simple even you guys can follow it. I have given the
solution to this problem that many have used to fix the problem. But
you guys still tell the world the world is flat... I guess this
problem must be in the other people's minds who have this problem
and have had it fixed. Please tell this user he was imagining his
hard disk crash
http://www.hardwareanalysis.com/content/topic/19004/?o=400#556461
BTW: Here are the articles that MS has posted and the ONLY error
they have fixed. Show me anywhere in these documents where it states
that MS has fixed this particular problem.

List of Fixes in Windows XP by Service Pack

SP1 - SP1a - http://support.microsoft.com/kb/324720
SP2 - http://support.microsoft.com/kb/811113
SP3 - http://support.microsoft.com/kb/946480/

Corrupted Large Hard Disk Fix from Hibernation

http://support.microsoft.com/default.aspx?scid=kb;[LN];331958


--
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



I'll wait up for this too. But, don't hold your breath.

JS wrote:
OK, tell me what to test.
I can setup my test PC for XP or Vista
Give me the steps to perform
(in ordered sequence).
and I'll run the test.

I have a spare 160GB drive, will that do?

--
JS
http:/www.pagestart.com


Whatever, you LACK of testing abilities shines very brightly
here. All you
can do is attempt to verbally tear down others withh no evidence
what-so-ever. It's a simple test why can't you perform it? Or is
that very
evident?

--
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



I'm sure your "tests" are equally as substantive and valid as
Twayne's (alleged) "tests" on registry cleaners ("speeding up
the system"). I'll
leave it at that. LOL.

Randem wrote:
All it take is a simple test... but some how you guys can't
seem to do
that... hmmmm.

--
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



Yeah, I think so!

John John (MVP) wrote:
There are tons of Windows XP OEM installation that were
shipped out on
large drives and none of them are failing because of problems
with 48-bit LBA addressing! I don't care what you say the
facts and experience of others simply do not support your
claims. Computer manufacturers have been shipping XP
installations on 160GB and 250GB
hard drives for many years now and users have been installing
retail
versions on large drives for as many years and your assertions
simply
do
not bear out. If what you say were true there would have been
*millions* of complaints about this and the problem would be
front page
news and discussed all over the place. I have seen many, many
Windows
XP installations on large hard drives filed to near capacity
and none
have succumbed to the 137GB 28-bit LBA barrier, this problem
was addressed with SP1 and your information is out of date

John

Randem wrote:
It has been tested in SP2 and SP3 with ALL updates applied so
there
is
certainly no mistake... It is very easy to replicate.

 

[Randem]

That "bias" response was not meant for you but for the other guy who instead
of performing any sort of test just states that anything that is not to his
understanding or different from his views are bogus.

Sorry, i that was not clear.

And I thank you for your time.

--
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

1) All files where copied to the hard drive while windows was running.

2) I will verify the .ISO on the hard drive matches the source as you
requested.

3) "And it is not at all surprising that the test that was accepted was
one that
matches what you want it to be and all else is bogus. "

My answer that statement is: "I had no predetermined outcome in mind
when I conducted this test, it was performed out of curiosity."

Each and every step is detailed in my previous post for your review.
This took a significant amount of "my" time to perform and document.
It was conducted by me and no one else. I did not refute your claim
but merely stated my results and resent your implication of bias.

--
JS
http:/www.pagestart.com

Funny, now go back to compare the iso's you copied that put you over the
137gb size see if it is equal in contents to the original. When you find
that out copy that file back onto the HD while windows is running.
Courious, did you also copy the files to the HD while windows was not
running then boot the HD?

And it is not at all surprising that the test that was accepted was one
that matches what you want it to be and all else is bogus. Hmmm, that
sounds familiar. You have no real evidence of either test but you tout
one over the other without even performing it yourself even though people
all over are complaining about this problem and MS's Fixboot or any other
MS reconized solution works but mine does.... EXPLAIN THAT AWAY! That is
something you cannot control. Ask the users that the solution has fix the
problem or are you afraid the answer may not be what you want it to be.

More people with this unresolved error that my solution has fixed. The
internet is covered with this issue with no MS solution. I guess that
they have imagined it also...
http://www.hardwareanalysis.com/content/topic/19004/?o=400

--
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

Next up on the list is the (alleged by some) "improvement in system
speed" obtained by using registry cleaners! LOL.

Daave wrote:
Thanks, JS. It seems like you and John John have demonstrated that
Randem's tests were flawed. (Surprise, surprise.) Therefore, his
conclusions are erroneous, and his advice can be disregarded.


JS wrote:
Finished the test, computer reboots without any problems!

For anyone interested I have included my step by step
testing.

Step by Step:
Installed 160GB WD IDE drive
Installed Windows XP Pro
(SP3 Included, single 149GB NTFS Partition)
Installed Motherboard drivers
Installed Network chip drivers
Turned off Automatic Updates
Downloaded Installed COMODO Firewall/AV
Ran AV scan
Download and installed TweakUi
Turned off "Auto Play" on DVD drive
Downloaded Installed NVIDIA video card drivers
Password protected user account
Changed screen resolution
Changed Windows Explorer to "Detail" and show hidden files.

Checked C: partition properties.
Decimal values
Used = 6.04GB
Free = 153.99GB
Capacity = 160.03GB

Started task of filling up the drive with files and folders
1) Used previous burned DVD media to copy file to new folder on hard
drive. 2) Checked "Disk Defragmenter", no defrag required, analysis
shows only a very
small number of fragmented files, everything is packed tight.
3) Activated Windows XP.
4) Created a "Restore Point"
5) Disabled AV and Firewall
6) Ran Windows Update - Custom Option
(Installed latest version of WGA)
7) Installed all "Critical Updates" except for IE7.
8) Updates installed, reboot required.
9) Install .NET Framework 3.5 SP1 optional update.
10) Copied from DVD to new folders bunch of files.
11) Repeatedly copied contents existing folders to newly created
folders to begin filling up the hard drive. Rebooted the computer a
couple of times during this process (both cold and warm reboots)
12) Cool Boot with 135GB Decimal (125GB Binary) used drive space, no
problems.
13) Disk Defragmenter analysis showed no files or clusters in use
beyond 135GB.
14) Copied a single file .ISO from DVD (2.6GB Decimal / 2.43 Binary)
file from DVD drive
to hard disk. this puts the used drive space past the 137 GB barrier
(137.621GB).
15) Warm or Cold boot without any problems.
16) One final test, added another 2.6GB file to hard drive. Warm and
Cold reboot without any problems.


The world is not flat...

To test:

1 - Copy files or folders to large hard disk till it reaches past
137GB 2 - Reboot

Something that simple even you guys can follow it. I have given the
solution to this problem that many have used to fix the problem. But
you guys still tell the world the world is flat... I guess this
problem must be in the other people's minds who have this problem
and have had it fixed. Please tell this user he was imagining his
hard disk crash
http://www.hardwareanalysis.com/content/topic/19004/?o=400#556461
BTW: Here are the articles that MS has posted and the ONLY error
they have fixed. Show me anywhere in these documents where it states
that MS has fixed this particular problem.

List of Fixes in Windows XP by Service Pack

SP1 - SP1a - http://support.microsoft.com/kb/324720
SP2 - http://support.microsoft.com/kb/811113
SP3 - http://support.microsoft.com/kb/946480/

Corrupted Large Hard Disk Fix from Hibernation

http://support.microsoft.com/default.aspx?scid=kb;[LN];331958


--
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



I'll wait up for this too. But, don't hold your breath.

JS wrote:
OK, tell me what to test.
I can setup my test PC for XP or Vista
Give me the steps to perform
(in ordered sequence).
and I'll run the test.

I have a spare 160GB drive, will that do?

--
JS
http:/www.pagestart.com


Whatever, you LACK of testing abilities shines very brightly
here. All you
can do is attempt to verbally tear down others withh no evidence
what-so-ever. It's a simple test why can't you perform it? Or is
that very
evident?

--
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



I'm sure your "tests" are equally as substantive and valid as
Twayne's (alleged) "tests" on registry cleaners ("speeding up
the system"). I'll
leave it at that. LOL.

Randem wrote:
All it take is a simple test... but some how you guys can't
seem to do
that... hmmmm.

--
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



Yeah, I think so!

John John (MVP) wrote:
There are tons of Windows XP OEM installation that were
shipped out on
large drives and none of them are failing because of problems
with 48-bit LBA addressing! I don't care what you say the
facts and experience of others simply do not support your
claims. Computer manufacturers have been shipping XP
installations on 160GB and 250GB
hard drives for many years now and users have been installing
retail
versions on large drives for as many years and your assertions
simply
do
not bear out. If what you say were true there would have been
*millions* of complaints about this and the problem would be
front page
news and discussed all over the place. I have seen many, many
Windows
XP installations on large hard drives filed to near capacity
and none
have succumbed to the 137GB 28-bit LBA barrier, this problem
was addressed with SP1 and your information is out of date

John

Randem wrote:
It has been tested in SP2 and SP3 with ALL updates applied so
there
is
certainly no mistake... It is very easy to replicate.

 

[John John (MVP)]

Yeah, right. Your test failed, screenshots here:
http://profile.imageshack.us/user/johnjohn1

 

[JS]

Sorry about that, my apologies.

By the way the .ISO file (Hash and CRC values) verified
on all three files. The original, the first time it was copied
to the hard drive and the last copy which spans the clusters
before and after the 137GB spot on the hard drive.

--
JS
http:/www.pagestart.com

That "bias" response was not meant for you but for the other guy who
instead of performing any sort of test just states that anything that is
not to his understanding or different from his views are bogus.

Sorry, i that was not clear.

And I thank you for your time.

--
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

1) All files where copied to the hard drive while windows was running.

2) I will verify the .ISO on the hard drive matches the source as you
requested.

3) "And it is not at all surprising that the test that was accepted was
one that
matches what you want it to be and all else is bogus. "

My answer that statement is: "I had no predetermined outcome in mind
when I conducted this test, it was performed out of curiosity."

Each and every step is detailed in my previous post for your review.
This took a significant amount of "my" time to perform and document.
It was conducted by me and no one else. I did not refute your claim
but merely stated my results and resent your implication of bias.

--
JS
http:/www.pagestart.com

Funny, now go back to compare the iso's you copied that put you over the
137gb size see if it is equal in contents to the original. When you find
that out copy that file back onto the HD while windows is running.
Courious, did you also copy the files to the HD while windows was not
running then boot the HD?

And it is not at all surprising that the test that was accepted was one
that matches what you want it to be and all else is bogus. Hmmm, that
sounds familiar. You have no real evidence of either test but you tout
one over the other without even performing it yourself even though
people all over are complaining about this problem and MS's Fixboot or
any other MS reconized solution works but mine does.... EXPLAIN THAT
AWAY! That is something you cannot control. Ask the users that the
solution has fix the problem or are you afraid the answer may not be
what you want it to be.

More people with this unresolved error that my solution has fixed. The
internet is covered with this issue with no MS solution. I guess that
they have imagined it also...
http://www.hardwareanalysis.com/content/topic/19004/?o=400

--
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



Next up on the list is the (alleged by some) "improvement in system
speed" obtained by using registry cleaners! LOL.

Daave wrote:
Thanks, JS. It seems like you and John John have demonstrated that
Randem's tests were flawed. (Surprise, surprise.) Therefore, his
conclusions are erroneous, and his advice can be disregarded.


JS wrote:
Finished the test, computer reboots without any problems!

For anyone interested I have included my step by step
testing.

Step by Step:
Installed 160GB WD IDE drive
Installed Windows XP Pro
(SP3 Included, single 149GB NTFS Partition)
Installed Motherboard drivers
Installed Network chip drivers
Turned off Automatic Updates
Downloaded Installed COMODO Firewall/AV
Ran AV scan
Download and installed TweakUi
Turned off "Auto Play" on DVD drive
Downloaded Installed NVIDIA video card drivers
Password protected user account
Changed screen resolution
Changed Windows Explorer to "Detail" and show hidden files.

Checked C: partition properties.
Decimal values
Used = 6.04GB
Free = 153.99GB
Capacity = 160.03GB

Started task of filling up the drive with files and folders
1) Used previous burned DVD media to copy file to new folder on hard
drive. 2) Checked "Disk Defragmenter", no defrag required, analysis
shows only a very
small number of fragmented files, everything is packed tight.
3) Activated Windows XP.
4) Created a "Restore Point"
5) Disabled AV and Firewall
6) Ran Windows Update - Custom Option
(Installed latest version of WGA)
7) Installed all "Critical Updates" except for IE7.
8) Updates installed, reboot required.
9) Install .NET Framework 3.5 SP1 optional update.
10) Copied from DVD to new folders bunch of files.
11) Repeatedly copied contents existing folders to newly created
folders to begin filling up the hard drive. Rebooted the computer a
couple of times during this process (both cold and warm reboots)
12) Cool Boot with 135GB Decimal (125GB Binary) used drive space, no
problems.
13) Disk Defragmenter analysis showed no files or clusters in use
beyond 135GB.
14) Copied a single file .ISO from DVD (2.6GB Decimal / 2.43 Binary)
file from DVD drive
to hard disk. this puts the used drive space past the 137 GB barrier
(137.621GB).
15) Warm or Cold boot without any problems.
16) One final test, added another 2.6GB file to hard drive. Warm and
Cold reboot without any problems.


The world is not flat...

To test:

1 - Copy files or folders to large hard disk till it reaches past
137GB 2 - Reboot

Something that simple even you guys can follow it. I have given the
solution to this problem that many have used to fix the problem. But
you guys still tell the world the world is flat... I guess this
problem must be in the other people's minds who have this problem
and have had it fixed. Please tell this user he was imagining his
hard disk crash
http://www.hardwareanalysis.com/content/topic/19004/?o=400#556461
BTW: Here are the articles that MS has posted and the ONLY error
they have fixed. Show me anywhere in these documents where it states
that MS has fixed this particular problem.

List of Fixes in Windows XP by Service Pack

SP1 - SP1a - http://support.microsoft.com/kb/324720
SP2 - http://support.microsoft.com/kb/811113
SP3 - http://support.microsoft.com/kb/946480/

Corrupted Large Hard Disk Fix from Hibernation

http://support.microsoft.com/default.aspx?scid=kb;[LN];331958


--
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



I'll wait up for this too. But, don't hold your breath.

JS wrote:
OK, tell me what to test.
I can setup my test PC for XP or Vista
Give me the steps to perform
(in ordered sequence).
and I'll run the test.

I have a spare 160GB drive, will that do?

--
JS
http:/www.pagestart.com


Whatever, you LACK of testing abilities shines very brightly
here. All you
can do is attempt to verbally tear down others withh no evidence
what-so-ever. It's a simple test why can't you perform it? Or is
that very
evident?

--
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



I'm sure your "tests" are equally as substantive and valid as
Twayne's (alleged) "tests" on registry cleaners ("speeding up
the system"). I'll
leave it at that. LOL.

Randem wrote:
All it take is a simple test... but some how you guys can't
seem to do
that... hmmmm.

--
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



Yeah, I think so!

John John (MVP) wrote:
There are tons of Windows XP OEM installation that were
shipped out on
large drives and none of them are failing because of problems
with 48-bit LBA addressing! I don't care what you say the
facts and experience of others simply do not support your
claims. Computer manufacturers have been shipping XP
installations on 160GB and 250GB
hard drives for many years now and users have been installing
retail
versions on large drives for as many years and your
assertions
simply
do
not bear out. If what you say were true there would have
been
*millions* of complaints about this and the problem would be
front page
news and discussed all over the place. I have seen many,
many
Windows
XP installations on large hard drives filed to near capacity
and none
have succumbed to the 137GB 28-bit LBA barrier, this problem
was addressed with SP1 and your information is out of date

John

Randem wrote:
It has been tested in SP2 and SP3 with ALL updates applied
so
there
is
certainly no mistake... It is very easy to replicate.