Hello ! I try with x64 no issues, but with the x86, I got a NTFS drive error with Virtual Box, I need to reinstall ? EDIT : I reboot and is OK
I hope 1.6.3 is the last update, is a powerfull tool I love it I think burn the last custom and make a arcade with
@George King These three files are only used on XP 5.1, they will not appear on XP 5.2 installation. This command will delete the registry entries so XP x64 can boot from winload on UEFI to work properly. I know you have implemented this in the upcoming version, but I wanted to make this post so I can inform others. Spoiler REM Removing unwanted driver files to allow XP to boot properly from UEFI using winload if exist "%TARGET%\Windows\syswow64" ( reg load HKLM\TEMPSYSTEM "%TARGET%\Windows\System32\config\SYSTEM" >nul reg delete "HKLM\TEMPSYSTEM\ControlSet001\Services\cd20xrnt" /f >nul reg delete "HKLM\TEMPSYSTEM\ControlSet001\Services\cbidf" /f >nul reg delete "HKLM\TEMPSYSTEM\ControlSet001\Services\cpqarray" /f >nul reg unload HKLM\TEMPSYSTEM >nul )
Well, I tried these long ago. While I managed to WIM Repack on NT 4.0 and 2000, any earlier NT versions or DOS-based versions are impossible. Because, Windows Setup do not recognize architecture of DOS-based Windows versions. DOS based Windows versions are 16-bit, not 32-bit. If you ask for manually applying via DISM, applied image will not boot and throw out an error about hard drive. Windows NT 3.51 or earlier NT versions are not likely be possible. Because I didn't manage to boot it.
Guys please stop with the equation newer = always better. Actually VBOx messed with XP/2003 installations after 6.1.32 or so, because they changed the routines to map the VHDs The result is that any XP vm created with older versions wont boot at all in the newest releases. Fresh installs should be not affected but still 6.1.26 and earlier should be a safer option
Probably you are too young to remember the FDISK /MBR and SYS C: commands, practically they are the ancestors of bootsect /NTxx /MBR and bcdboot, respectively
I thought I can find modern disk drives for 9x. However, I can agree that you can't install Windows 9x via Win7 + Win10 setup engine. Because Windows Setup does not recognize 16-Bit architecture.
Would be a bit pointless to use a setup infrastructure that is way bigger than the OS meant to be installed. Perhaps Win9x has not the trouble of NTx of having the right HDD controller to be able to boot (that was a huge regression over win9x), nor it has permissions, hard links and other NT goodies. Just zip the installation after the first phase and unzip it in the destination partition, be sure the partition is active, boot from floppy (or CD or USB) do FDISK /mbr and sys C: and you are done. It will boot. Possibly using the 16 bit DOS drivers and showing the truncated filenames (like Progra~1), then you install the correct 32 bit IDE/SCSI driver and your install is ready to the final installation of any other missing driver
In my early days, they were called MWINCH, INIT and SYSGEN, respectively. Plus, don't forget to use a compression program that can back up LFNs. LFNs are only mis-used label or dir entries IIRC, and many DOS-based utilities just drop them, leaving only the tailed shortname.
Never had the pleasure my it history started in 1982 with a Ti99/4a, but my experience with "IBM compatibles" really started in the late days of Win311/early days of Win95, so no VMS, early unixes and even pure DOS for me. Well, my idea was to use win 7/8/10 (or winPE) and 7zip offline. I think that in almost 30 years they learned how fat32 works. But since 1995 I never encountered a single case of such dumb move, W95 was a sort of tornado, in matter of few months things that the past generation of users considered their main tools (like the Norton utilities or Nuts & Bolts) suddenly vanished, and became instantly "retrocomputing"
I was having problems with the previous version, installed VirtualBox-6.1.36-152435-Win, and he did work well they did a change --- looks like …
Yep, but if I remember correctly the similar commands were called this way in VMS then borrowed by CP/M, my memory may fail given I had no direct experience in either the systems. I worked with an Apple II that had a Z80/CP/M card, but I was there as electronic technician, not as IT guy, so I never issued a command, just some buttons pushed.
Update Reports Update Packs x64 i have improved Fixed display of names that do not need multiple patches. I have to change my name KB4470118,KB4493341 are SUPD. (security update) cannot use Update for Windows. UPD in stringing it gives an error as in the leaked file name I have noticed that there are older patches from the old creator too which are corrupted. (the old creator never added it) Added missing Registry in KB4503063 (MSI 4.5). form update.inf Fixed sometimes incorrectly installing files. Certificate Update 2022-08-23 For errors on Server 2003 Windows Media Player 11 can't find a solution at this time. Fixed RVMI and nLite trying to change the build in the file back to Version 2017 I found the terms of use of Addon Server 2003. After you apply the Update Pack, add the IE8 Addon first. followed by Addon Server 2003 If you don't do this, it will give you an Update string for Windows Server 2003. Invalid and still XP Version 2003 I won't be launching right now. I tested it several times to make sure there were no more errors from the previous creator.
Hello, how can you download the onepiece update packs? theres no way to download them from the post to the wincert site wheres linked on the first post in the preparation section.