jlwater

My bad, I had read this EULA prior to installing, that's what I get for trusting Google to do my homework. I should have read the updated during the install. Thanks johnhc for your help, but it looks like I'll need to find another solution.

jlwater, I suggest you go to the various vendor's web sites, DL the drivers for your HW and integrate them using nLite. That way you get only the drivers you really need and you get the latest copies of them. I have not asked before, but what is the normaliz.dll problem? Enjoy, John. Agreed that would be ideal, unfortunately my employer uses several different hardware configurations, as well as some cannibalized mutts. Having the full suite of driverpacks seems to be the best solution. The Normaliz.dll problem is documented here http://forum.driverpacks.net/viewtopic.php?id=1563 and there is a solution on the third post of the thread.

I was afraid of that. And you were right so far, it was definitely something to do with driverpacks; the base nLite image with just the normaliz.dll fix worked fine. Now the trick is finding out what in driverpacks is screwing me up!

Yep, just redid the disk. Used nLite to make all my changes, then right before making the ISO, I do the $$ folder addition in the above link to make sure normaliz.dll isn't a problem, then slipstream in the driverpacks, and finally make the ISO. Got the same msobshel.htm error, which kills the install. Edit: also the ISO installs flawlessly on VBox.

I'm fairly certain that I've started with a fresh XP folder each time. The updates are all the hotfixes and such I could find on the Update Catalog since SP3 was released. I slipped the driverpacks using Driverpacks Base right before the ISO was created. The ISO tested on VB worked except that it came up with this error: http://forum.driverpacks.net/viewtopic.php?id=1563 The solution posted by Ed2007 in post #3 solved my problem on VB, but obviously now there's this obstacle. I'm going to make a new ISO now to guarantee that I'm doing Ed2007's solution before I slip the driverpacks.

Hi, I'm making a SP3 Unattended disk. I'm using nLite to create the ISO and slipstreaming in pretty much everything possible from DriverPacks. I tested the ISO on VirtualBox with no errors, but after I burned the disk and attempted my install, I ran into this problem. The most recent discussions of this problem seem to date to 2006 in regard to KB912945, which is not included in my hotfixes. re: Any ideas?

Hi all, I'm taking my first crack at an unattended install and I was looking at the MSFN tutorial for creating a disc using nLite. When I browse to the source folder for nLite, nLite detects the source files as being SP3. Since I want my disc to be SP3, is it still necessary to use the SP integration step in the tutorial? Thanks, j