msobshel.htm problem

[jlwater]

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?

Edited August 25, 2010 by jlwater

[cluberti]

Moved.

[johnhc]

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?

jlwater, thanks for the Last Session.ini. Have you run nLite more than once against the same source files/folders? You should always start with a fresh copy of your CD files/folders and run nLite only once doing all your work. Where did your updates (the list, that is) come from? How did you slip the driver packs? Did you test the exact same ISO on VB as the one you installed on your HW? Enjoy, John.

[jlwater]

jlwater, thanks for the Last Session.ini. Have you run nLite more than once against the same source files/folders? You should always start with a fresh copy of your CD files/folders and run nLite only once doing all your work. Where did your updates (the list, that is) come from? How did you slip the driver packs? Did you test the exact same ISO on VB as the one you installed on your HW? Enjoy, John.

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.

[jlwater]

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.

Edited August 9, 2010 by jlwater

[johnhc]

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.

jlwater, I would suggest you will need to do some experiments. Are you installing to a RAID or SATA drive? If so, you must integrate your driver for it. Otherwise, you really don't have to have drivers to get going. So, integrate, using nLite, any drivers you need for a RAID and/or SATA, then skip the driver pack all together. Since the problem occurs on HW and not VM, then it may have to do with a driver, perhaps the video driver. My personal opinion is that using something like driver packs is asking for trouble. Mixing programs (nLite, driver pack integrator etc) confuses the issue and makes it near impossible to determine where the fault is. After you run this experiment, if it fails, then run again with no updates ( and no driver packs). Start each experiment with a fresh copy of your CD files/folders. Please attach your Last Session with each experiment. Enjoy, John.

[jlwater]

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!

[johnhc]

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!

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.

[jlwater]

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!

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.

[Sp0iLedBrAt]

my employer uses several different hardware configurations

Please read the nLite EULA. It is for personal, non-commercial use only.

[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.

[johnhc]

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, you are welcome. Sorry that we ran into this so late in the game. At the bottom of this page is a link to the Unattended Guide. You can do most of what nLite does directly with tools MS provides in XP. It is not as easy to use and, of course, not automatic. If the Driver Packs allow business use, then you can go that way. I should point out however that using these free tools in a business environment can be problematic. In the case of nLite, nuhi (author/owner) has not been active here in over a year. Enjoy, John.