I have Driver and Windows Update Concerns

[The Lone Programmer]

I am not too new to nLite, but I still have some concerns.

1> Say I wanted to just integrate a ton of drivers into my XP ISO. Would it slow down the computer I install it on or cause any kind of errors if the computer doesn't contain hardware for the drivers I added?

2> Say I have a Windows XP disc, but it is not a first generation disc. Meaning it has various updates on it. Am I going to experience problems if I integrate RyanVM's update package into my installation?

3> Say I have installed RyanVM's update package June06 version into my installation disc. Would I encounter problems if I later installed RyanVM's update package October06 on top of it?

I would really like to just add a crapload of drivers to this disc, but I don't want to run into any complications. I would also like to take the easy way out and just add updates onto a disc without problems as well.

Please let me know the answers to my three questions.

Thanks,

The Lone Programmer

[RyanVM]

2> Say I have a Windows XP disc, but it is not a first generation disc. Meaning it has various updates on it. Am I going to experience problems if I integrate RyanVM's update package into my installation?

Possibly, though my pack is somewhat smart enough to remove some superseded updates present on a CD (though I periodically trim the list). You're best off starting over fresh.

3> Say I have installed RyanVM's update package June06 version into my installation disc. Would I encounter problems if I later installed RyanVM's update package October06 on top of it?

Hint: Read the changelog on my site

[The Lone Programmer]

I looked at your change log. It looks as though you are having unneccessary hotfixes removed. Not quite sure though.

You said that you periodically trim the list. What do you mean by that? You are skipping out on some of the updates?

What about drivers. Would I be safe just going crazy with adding drivers? What if I added a driver, but a month later added a newer version of the same driver. Would that mess things up or would the installation be smart enough to install only the new one?

Thanks,

The Lone Programmer

[RyanVM]

The point of the changelog was that version 2.1.0 clearly says that it cannot be integrated over previous versions. Now when did that version come out? That should answer your June question.

I trim the list of fixes that are automatically removed from time to time.

I can't speak for drivers, sorry.

[The Lone Programmer]

Thanks for clearing that up for me.

[nuhi]

Drivers may slow down only the detection phase, you can add plenty but there is some limit, don't know exact. Anyway try with all you need and post here if you encouter any issues.

[The Lone Programmer]

Detection phase? I am unfamiliar with what you mean by that.

I do have another question on top of this one.

How come when I try to make a WinPE cd using Windows PE or Bart PE I get driver errors after I've used nLite to integrate drivers. When I boot the ISO's I make with Windows PE and Bart PE in my virtual machine, it will always fail to find the .sys file of the driver. Does that mean I didn't properly integrate the driver?

When I use UBCD4Win I get an nLite.inf error when it boots up. I have no clue how to fix that. The same error happens when I add the Windows Skin plugin for BartPE. What is the deal?

Thanks,

The Lone Programmer

[nuhi]

Detection phase is the part of setup where it detects your hardware, first GUI boot during install.

BartPE modification isn't generic I'm afraid, I had to copy my RAID sys file as well after making WinPE.

So when you see which file is missing go into the pre-bart installation folder and copy what you need into appropriate folder in WinPE...for example SATA/RAID sys file is going into System32\Drivers folder...don't add anything else if you are just making WinPE.