It's my belief, that somethere there is a one-file plugin that sets up the EnableBigLBA with RVMI, that a noob can slip into a clean set of original source files. Noobs don’t want to maintain multiple sets of original sources. It's hard enough already.
to summarize the above
#1 red2k proposes to replace SETUREG.HIV with a 69K file ... he doesn’t say, but as noob I’m guessing this would modify the original source before running nLite or ryansVM Integrator. That means two sets of original source files. As noob ... I don’t want to change a setup file after slipping because I don’t know if RVMI or nLite or some patch didn’t already add something critical.
#9 Oleg_II proposes the reg file solution, which works in hfslip, but not in RVMI or nLite (HFSLIP demands it's own file structure, which, for someone who was not part of its evolution, is quixotic and totally unforgiving). He mentions the test executable from 48bitlba.com, but that won’t slipstream in RVMI or nLite, or run batch unattended. Maxtor and Seagate have executables to set 48bit lba which might work in runonce.
#15 fdv proposes opening HIVESFT.INF and doing a cut and paste. I don’t trust myself with a one-time cut-and-paste for setting up hdds. I just want to integrate an addon or inf patch file.
#18 os2fan2 proposes a batch file to modify setupreg.hiv. In #43 he explains that setupreg.hiv is in effect the registry during text mode setup. (good info ... thanks!) There is a link to an expanded HIVEFIX.INF by os2fan2 with all kinds of bonus tweaks. The 2nd line of the batch says “You need to also fix the file txtsetup.sif to get this to run.” He doesn’t say how. That’s a full stop for a noob like me. In #21 Tomcat says the expanded version produced a BSOD.
#39 Kelsenellenelvian explains how to setup the 48-bit batch by os2fan2.
I’m guessing that hivefix.inf can be tweaned before or after integration ... as long as it’s before system installation.
(aside ... this would apply to installation into very large partitions ... problem is M$ programmed setup installers to fling directories (potentially containing files that need to be frequently accessed) across the full span of the install partition. New directories are randomly placed so as to fill the entire freespace of the partition, and then they are made unmovable for FAT32 systems. The installer is programmed to expand the system into all available free space, even if it causes fragmentation of the page file. I have to assume that MS engineers must understand the technology of their profits. This is not normal fragmentation. It is random seek banging that will slow down a FAT32 system and accelerate the crash of a hdd, since directories that are installed into the farthest reaches of a partition cannot be defragged or compacted back into the rest of the files at the top of a partition. Because the setup installer is programmed to fill all available partiton space with flung directories, I’d suggest that the setup installer be restrained to smallest partition reasonably possible ... 5G leaves 2g for pagefile, 2 gig for files, 1 gig for defragging and for temp expansions and contractions. The partition can be expanded after MS setup installers are gone.
Net result, after reading the above, hopefully most noobs aren't going to setup systems on partitions that cross the 128g barrier ... if they want to use a large partition and fast trash their new hdd, then, the hivefix.inf is probably an important one ... I don't know about the text mode OS, but after install, a large hdd in 2k without the 48bit reg setting will screw up the system, even if the hdd is never accessed, read, or written to. 2k needs to make drive letter asignments, and when there is a large hdd in a system which is not 48bit enabled, the process that tries to make the driver letter assignments gets stuck in some kind of loop when it studies the big one ... so I would assume the same problem might exist in the OS used by text mode setup as well ...?)
There is a solution in nLite, but (IMHO) it’s not easy or intuitive to find. We want EnableLBA support for our system HDDs. Open nLite, go to the Tweaks page, then open the “Explorer” section (not My Computer, not Performance, not Devices, not Management, ...) then wade into all the bubblegum and display tweaks for Explorer (to a noob, Explorer is mostly about bubblegum and display) ... inquire into the ninth tweak, which is labeled “Large Partition Support” (hmmm.... what's that? ... Unlike other options in this setting, this one is not some bubblegum tweak about Explorer display options. It's not labeled, EnableBigLBA support, or 48-bit HDD support, or Large Harddrives > 128g, ...) . Large Partition support enables a large HDD, even if you don't use "large partitions."
After 12 years, and thousands of posts, I still haven't found a simple one-file plugin for RVMI (or nLite) which will set the EnableBigLBA
admittedly there already is one, but it’s Gurglemeyer’s 120meg SP51. At the moment, that’s the smallest one-file plugin that will set a simple reg entry in nLite or RVMI!
(oh, humble me!) I don’t have a VM yet to test this on, but I did find an inf file for XP that might (!) possibly (!) work (untested!) as a small one-file plugin for RVMI and nLite... it’s from KB303013 for XP but should work in 2k
open a text file called 48bitLBA.inf
add the following code
In RyanVM Integrator, add this file into the addons section of RyansVM integrator, or in nLite, add the file to the Hotfixes, Addon, Update Packs page.
OMG! Finally, after twelve years, and thousands of posts, is there now finally a one-file one-step go-solution plugin to EnableBigLBA for noobs ... just integrate and go.
I don’t have a VM to test this on at the moment ... I ventured off onto this part of my learning curve trying to build a machine to build a machine with, etc. I want to get a bootUSB working before I try mounting the learning curve for a VM, so maybe someone with a VM could test and confirm before me?
Edited by Molecule, 27 September 2012 - 01:51 PM.
can the platonic solids be constructed by gaussian modulation of rotational action, rotational action itself being an artifact of intersection of two sphaeric actions--the tetrahedron for example