Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country

    United States

Posts posted by ImWolf

  1. I have 2 machines currently running a version of the SP4 update. On my office machine I already had a SP3 install, so I simply double clicked the USP4-v3.1b-x86-ENU.exe file to update. 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.

    Soon, I will be replacing the MB on my office machine, so I will need to do a complete re-install of XP. 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. 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. 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.

    At this point, nLite throws a dialog box at me saying "Unhandled exception has occured.....   Length cannot be less than zero.....   Parameter name:length"

    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. I have tried this on both machines (currently running XP SP4) with the same results.

    Last night I D/L again the newest package from Harkaz Google drive. The package includes a new file called "WindowsXP-SP4EOS-Rollup.exe", and extracts into a directory named "Update Rollup for Live Installations". 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). This latest "Rollup" is stamped Dec. 26, 2019.

    Any suggestions?




  2. 47 minutes ago, cc333 said:

    That's normal. It was left that way for compatibility purposes (some programs won't install and/or run if the Service Pack number != 3).


    OK.....  Thanks for the quick reply.

    Is there a way to edit the SP# displayed by "my computer" just for appearances sake without creating compatibility issues?

  • Create New...