C
CJT
Peter said:So, why do you use Win2K?
I believe XPSP1/2003 does not have that (particular) problem.
Why trade one set of problems for another?
Peter said:So, why do you use Win2K?
I believe XPSP1/2003 does not have that (particular) problem.
Why trade one set of problems for another?
Peter said:[...]
BTW, all this got fixed as soon as I entered the Registry
parameter, EnableBigLba, following Microsoft's KB report;
after rebooting my machine, the drive, with no partitions
whatsoever, got correctly reported as 186GB (thanks again
Peter, for the pointer!)
So, why do you use Win2K?
I believe XPSP1/2003 does not have that (particular) problem.
At the risk of turning this into an endless flamewar
Let's say that Win2K was the last thing I got from Microsoft
before my mind crossed the "I'm absolutely fed up" threshold.
That, plus the fact that Windows XP has not given me any
reasons to make me trust it -- you only hear horror story
after horror story; compound stupidity service pack after
service pack... Yes, I know that those horror stories one
hear contain only a given fraction of truth in them...
True that many of those horror stories apply mainly to the
very initial release, and many of those problems have been
fixed. But still...
True also that the fact that the very only thing I use from
Microsoft is the OS alone is an advantage; I have never in
my life executed the Internet Explorer (really, not a single
time! -- on my machine, that is), and it's been more than
seven years since the last time I used MS Office... So that
should get me covered on the security front.
Peter said:While it reduces your vulnerability, it does not eliminate it completely.
Eric Gisin said:That is a serious bug in Win2K. I don't think Microsoft acknowledges it.
If there are no parts, then Disk Manager reports the size from drive
identification. This is limited to 137GB if the BIOS reports that.
If partitions extend beyond the above size, Windows uses it and corrupts the
disk, often overwritting the beginning (MBR, boot, FAT).
Peter said:[...]
BTW, all this got fixed as soon as I entered the Registry
parameter, EnableBigLba, following Microsoft's KB report;
after rebooting my machine, the drive, with no partitions
whatsoever, got correctly reported as 186GB (thanks again
Peter, for the pointer!)
So, why do you use Win2K?
I believe XPSP1/2003 does not have that (particular) problem.
At the risk of turning this into an endless flamewar
Let's say that Win2K was the last thing I got from Microsoft
before my mind crossed the "I'm absolutely fed up" threshold.
That, plus the fact that Windows XP has not given me any
reasons to make me trust it -- you only hear horror story
after horror story; compound stupidity service pack after
service pack... Yes, I know that those horror stories one
hear contain only a given fraction of truth in them...
True that many of those horror stories apply mainly to the
very initial release, and many of those problems have been
fixed. But still...
True also that the fact that the very only thing I use from
Microsoft is the OS alone is an advantage; I have never in
my life executed the Internet Explorer (really, not a single
time! -- on my machine, that is), and it's been more than
seven years since the last time I used MS Office... So that
should get me covered on the security front.
Carlos
Folkert Rienstra said:if the BIOS reports that.
Does this mean that Disk Manager, like Fdisk, still relies on the BIOS?
Don't be stupid. Win NT has always gotten logical CHS from the BIOS.Folkert Rienstra said:Well Eric, does Disk Manager, like Fdisk, still rely on the BIOS or does it not?
Eric Gisin said:Don't be stupid.
Win NT has always gotten logical CHS from the BIOS.