Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by strotee76

  1. Download DPs_BASE, it's where you'll find DPs_BASE.exe.

    Within the application, click on Settings -> Location, click on Browse and point it to your XP source folder.

    More options will become available once it locates the i386 folder. Let me know when you get this far and I can be more detailed. (sorry, not in front of my system, but it's pretty easy once you do it a few times)

  2. While using nLite, do you choose the last option? I don't have nLite open right this second but I believe it's Bootable ISO. So you do whatever you want nLite to do (remove components, automated install, slipstream hotfixes, etc) and after it's done and says something about if the installation grew or shrunk, what happens? It should give you an option to create a bootable ISO that you can then either use nLite or a 3rd party burning app to burn to CD. Just ensure the BIOS on the computer has the 1st boot device as the CD as opposed to the hard drive.

    Also, it's a good idea to look into virtualization software such as VirtualBox, VMWare, etc; this will save you a lot of coasters and frustration. Ask if you have questions.

  3. Regardless of the fact that the hotfix he wants to install is integrated or is an addon

    You're wrong, he did ask for it to be integrated. I was at least being forthcoming and saying that installing the hotfix upon first startup is not technically being properly integrated into the source as jeromerocks originally requested:

    I want to integrate a hotfix into the unattended setup (his exact words)

    (Keep It Simple Stupid) Sometimes, the best solution is to avoid fancy, schmancy batch scripts, etc etc and just burn two versions, that is one option. If you want to spend the time to create the script, tweak it, tweak it some more, test it on many systems, then be my guest, that's also another option. I was offering a pseudo-code approach to the problem. True, I wasn't giving you an exact recipe of how to do it but I figured it'd at least give you something to consider.

    Others can chime in with their opinions or thoughts, I'm merely one person who offered ideas while not chastising others for trying.


    Batch Scripting

  4. Common sense solution: Create two CD's? What's the price of CD-R these days (especially if you buy a 50/100 pack)? 5 cents? 10 cents?

    Just burn two copies. Copy A (integrated version) Copy B (non-integrated version)

    Or, you can create a batch file that prompts you at first startup whether or not to silently install the hotfix. But, technically, that's not integrated into the source, more like an add-on.

  5. I used to be in your shoes.

    Couple options:

    1) You have to use the WMP11 slipstreamer before nLite. To my knowledge, there's no way to merge the two programs and get "tweaked" settings.

    2) Take the EXE of the WMP11 slipstreamer and place it into the nLite Program Files folder and (unfortunately) get the "vanilla" version of WMP11. Just drag the WMP11 installation EXE into the Hotfix section and nLite will piggyback off the newly copied WMP11 slipstreamer EXE. I hope this makes sense.

    3) I've stopped using WMP11 slipstreamer to integrate WMP11 into my own XP source. I've started to use an All-In-One update package that includes WMP11, IE7, DirectX updated files, and post SP3 patches. As expected, just drag it into the Hotfix section. It might be overkill for your needs but you can find it here:

    Onepiece's EN-US Windows XP Post-SP3 All-in-One Update Pack (updated very frequently)

    Of course, test it a virtual environment before wasting a CD.

  6. You should be able to disable unattended by either deleting or renaming the file, WINNT.SIF.

    1. Just open a command window (Start --> Run --> "cmd").

    2. Peruse to your i386 folder in your XP source files.

    3. Type in "ren winnt.sif winnt.old"

    4. The installation will no longer be unattended.

  7. I would start with a clean XP source now that you are using 1.48.

    winntbbu.dll is the file that gets deleted to create the "classic" look during setup; there's a chance a file got corrupted with your XP source.

    So, copy all the files from a virgin XP disc into a temp directory, point nLite to that folder, and see if that's any better.

  8. What does this have to do with nLite?

    But to answer your question, a 6x DVD-ROM reads at the equivalent of a 54x CD-ROM, so a 16x DVD-ROM would absolutely kill any CD-ROM known to mankind.

  9. You can't remove IE7 and WMP11 if you integrated it into the installation files; you'll have to start over with a clean source.

    If by chance IE7 and WMP11 are separate add-ons, then you might be able to remove them from svpack.in_.

    To expand svpack.in_, do this:

    1. Open a command line (cmd)

    2. Change directories to the i386 folder

    3. type "expand svpack.in_ svpack.inf"

    4. make your changes to svpack.inf, save it

    5. type "makecab svpack.inf"

    6. type "del svpack.inf"

  10. First, forget SP2, it's history, SP3 is the new sheriff in town.

    Yes, you can slipstream SP3, then IE7, then WMP11. I'm running it now. Take a gold copy of XP (pre-SP1), slipstream SP3, then integrate IE7/WMP11, crack open a beer, turn on the Sox game, install and live happily ever after. :thumbup

  11. "I am an advanced user"

    If so, then you should read manuals, forums, etc before trusting a new program to perform work on the Windows directory.

    "What everyone fails to notice it that nLite shouldn't allow you to use it wrong."

    That's about the same as a razor blade manufacturer trying to ensure you can't cut someone's throat with it. nLite is a tool, much like a gun. Both very dangerous if used improperly.

    "I wanted to warn the developer of the flaw..."

    What flaw? nLite is programmed to look for an i386 folder, you just happened to point it to c:\windows which happend to have an i386 folder (blame your OEM, not nLite). I think part of the problem is your slight misunderstanding of the phrase "Windows installation files" and the "Windows folder". All in all, this entire thread is much ado about nothing.

    I know nuhi is a nice guy who wants to appease the situation but please do more research before making threads demanding someone's head on a pike. All of us on this board respect nuhi and his efforts he has put into the program so we get very defensive when someone claiming our beloved nLite broke someone's XP only to find out it was more of a misunderstanding with a new user. Good luck.

  12. This thread is amusing to say the least. Here we have one poster claiming one thing and everyone else claiming another. Statistically speaking, who do you think is correct?

    I think we can all agree that nLite is for advanced users. Nuhi should spend his time adding features/eradicating bugs and not id1ot-proofing (not pointed to anyone in particular) the software so my mother can use it. I (along with a lot of people on this board) have made 100’s of nLite installations (virtual or not); it’s a science to make a reliable nLite’d installation disc. I save 2 or 3 presets that I use on every installation of Windows (saves time, makes installations universal) along with an ISO of a virgin copy of XP (extract, dump it into its own folder on the desktop, point nLite to that folder and let it do its magic).

    This isn’t the first time someone new to nLite posts something along the lines of “help me restore XXXXX” or “omg, it destroyed my installation”. I remember when I first started tinkering with nLite, those were some rough, frustrating days/weeks. I promise, you WILL fail at least one installation of Windows after it was nLite’d. The entire process is entirely too complex to remember all the intricate details involved with making it not completely worthless. There’s a fine line between removing too much and removing too little. Use virtualization software (VMWare, VirtualBox, etc).

    Above all, have patience. Rome wasn’t built over night, nor will your“perfect” Windows installation.

  • Create New...