how to get windows 2000 sp4 to have proper lba 48 support?

[cov3rt]

so i've tried to research sources of people trying to get lba 48 working properly on windows 2000, specifically when trying to install with sp4, and i haven't been able to find out what exactly needs to be done and for what purpose. i do not wan't to include or integrated / slipstream unnecessary or excess things, i already have to test blackwingcat's unofficial acpi fix which is part of some package that a user here referenced to, but it's unclear whether this would fix that issue and what other things would need to be done afterwards, as it's something i see have to see after fully updating my system, since not everyone updates their system in the same exact way, i have to take this into account, which is why i mentioned the issue with integrating / slipstreaming stuff may cause conflicting problems and / or may cause me to have to find a workaround that may not be feasible. 

as for the lba 48 issue, some questions involved are getting the setup to detect and create a partition higher than 137 GB ( if possible ), and / or whether the partition can be expanded AFTER installing, and if so, how would this be done. OR be limited to 137 GB partition and call it a day BUT at least have proper working lba 48 for data protection, so that even if the real capacity of the HDD is higher than 137 GB, lets say 160 GB, it still wouldn't have any chance of data corruption, because a specified patch / setting would allow for lba 48 to work "properly" except with limiting the amount of usage space. really, i'm more concerned about a functional system, rather than having a higher capacity drive. 

one solution that was mentioned which is unclear whether it's the only thing that would require for proper lba 48 functioning is simply enabling / setting a registry key in the registry AFTER installing windows 2000 sp4, but what exactly this would do, i haven't gotten a clear understanding of. the link below has a dowload link for the program that checks whether or not you would need to set the key, and if it say's failed, you would click set enablebiglba, but other than this, what else would need to be done, is it as simple as that? 

manual method after installing windows 2000 sp4 - https://web.archive.org/web/20110904131427/http://www.48bitlba.com/enablebiglba.htm

automatic method after installing windows 2000 sp4 - https://web.archive.org/web/20110903033314/http://www.48bitlba.com/enablebiglbatool.htm

there is also another thread which indicates loading of some syssetup file or slipstreaming it perhaps? and another method which indicates the usp 5.1 having the fix, which then would allow for greater than 137 GB formatting during setup? however, this of course would conflict with what i mentioned earlier of using excess / unecessary packages. it seems like adding one file such as the sysetup part would be sufficient, but i haven't found an exact step by step source of how to do so and whether that would be solution for everything, so that the enablebiglba option wouldn't need to be done either? 

here is what i already am including or include in my windows 2000 sp4 installations:

-slipstreamed blackwingcat's amd and intel drivers 

-extended core v16a package ( yet to be tested, but hopefully it doesn't require any changes AFTER os install, and if it does, very minor ), i only came across like two files that are different towards my fully updated systems, and that is the acpi and videoprt.sys i believe, which are modified and / or different after installing one of the other types of unofficial update rollup packages, ( i downloaded from sdfox's files, or whatever that guy's name is ). 

Edited May 14, 2020 by cov3rt

[jaclaz]

I am not sure to understand what you are after.

That's it, the system needs

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters\EnableBigLba

to 1.

Then there may be different ways to implement it, this (using a modified SETUPREG.HIV) is the "best" one in that it is simple and enables BIGLBA also in the TXT setup part:

The batch by os2fan2:

https://msfn.org/board/topic/75713-48-bit-lba-on-win2k-setup/?do=findComment&comment=590337

is one method, but you could also load the hive in regedit and add/modify the key manually or use offline registry editing, etc.

 

 

jaclaz

 

[cov3rt]

8 hours ago, jaclaz said:

I am not sure to understand what you are after.

That's it, the system needs

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters\EnableBigLba

to 1.

Then there may be different ways to implement it, this (using a modified SETUPREG.HIV) is the "best" one in that it is simple and enables BIGLBA also in the TXT setup part:

The batch by os2fan2:

https://msfn.org/board/topic/75713-48-bit-lba-on-win2k-setup/?do=findComment&comment=590337

is one method, but you could also load the hive in regedit and add/modify the key manually or use offline registry editing, etc.

 

 

jaclaz

 

when you say the modified setupreg.hiv also enables biglba in the txt setup part, does that mean that it can allow manually creating partitions larger than 137 GB in setup, or does it just mean that after installing the operating system, the partition then shows up as more than 137 GB if the drive itself is larger than what the setup wizard can create or detect? because if it's only for option 2, then the manual method which i mentioned in "https://web.archive.org/web/20110904131427/http://www.48bitlba.com/enablebiglba.htm" would be more straightforward imo, at least, i haven't been able to find clear and straightforward step by step instructions on how to implement the setupreg.hiv method.

although there are some unanswered stuff / unclear things, for now, i'm just gonna go with the manual method for allowing proper operation of lba 48 on windows 2000 sp4 after installation, as i did come across several threads many many years back where the simple manual method allowed their drives to be detected properly, i think the oldest reference was someone using a 2002 amd motherboard and was able to have their 300 GB hard drive have it's full capacity shown after using the manual method of enablebiglba.