After nLite is done with the modifications, replace the original registry entries in the hivesft,inf file. As a workaround you can temporarily copy the time zone registry entries from another update pack and replace them in the hivesft.inf file.
This is a known issue: for some reason the updated time zone registry entries in the post-sp4 update pack in hivesft.inf cause nlite to crash (an unresolved bug in nLite). There is no "readme" file included, so I'm not sure if this exe file should be slipstreamed into the installation files using nLite, or if it is intended to be run as a stand alone update after the setup (with USP4-v3.1b only). The package includes a new file called "WindowsXP-SP4EOS-Rollup.exe", and extracts into a directory named "Update Rollup for Live Installations". Last night I D/L again the newest package from Harkaz Google drive. I have tried this on both machines (currently running XP SP4) with the same results. I tried using the "slipstream.bat" routine both while nLite was still active and had just updated the Service Pack, and after shutting nLite down. However, after I extract the zip and use "slipstream.bat" to modify this install directory then nLite will no longer open the files for further use.Īt this point, nLite throws a dialog box at me saying "Unhandled exception has occured.
I have created a directory for the install files, and then used nLite to add the USP4-v3.1b service pack, and this seems to work just fine. I have been attempting to create the install ISO with nLite once again, but for some reason I am not able to integrate the May19 updates as I have done in the past. Soon, I will be replacing the MB on my office machine, so I will need to do a complete re-install of XP. On a separate machine I was doing a fresh install, so I slipstreamed this file into the installation files (of XP Pro SP3), and then used "Slipstream.bat" to update those install files again with the "PostSP4-May19" package. On my office machine I already had a SP3 install, so I simply double clicked the file to update. I have 2 machines currently running a version of the SP4 update.
0 kommentar(er)
