nLite causing BSOD during XP install?

[thestickman]

hi there.

i have been lurking these forums for some time now, and unfortunately am unable to find the remedy to this problem.

the last time i slipstreamed and created an unattended install winXPpro SP2 was a few months ago with nLite v1.35 and encountered no problems whatsoever.

since then i have lost that unattended installation and with the latest release of SP3 i was wanting to make an unattended winXPpro SP3 installation. so i went and downloaded the current version of nLite 1.45 and went ahead with the same processes of slipstreaming and integrating addons etc. to my installation.

every cd i have made so far has resulted in the BSOD directly after the initial driver loading stage of the winXP setup.

initially i thought it may have been corruption in some of the addons or possibly BSTDriverPacks i was integrating, and/or also modifying the components and settings in windows itself, so i eliminated that from the next slipstream alltogether and kept it completely clean, slipstreaming ONLY SP3.

still receiving the BSOD i thought it may have been a corrupted SP3, so i re-downloaded the pack and low and behold the same error occured.

i tested further by slipstremaing cleanly SP2 only, and low and behold, still encounterd the BSOD,

regardless of whether i have slipstreamed SP2 or SP3 using the current nLite v1.45 i encounter this BSOD error.

i have also re-downloaded and re-installed nLite incase it was corrupted and STILL encountering the BSOD.

so going from being able to at least make an unattended SP2 install with addons and drivers etc., i cant even do that much with the current version of nLite.

the winXPpro SP2 source installation cd i am using works flawelessly so this is obviously not the issue.

i am just wondering if there is something i may be doing wrong considering it used to work flawlessly prior to updating to the newest nLite. also is anybody else encountering this particular problem?

any suggestions are greatly welcome.

cheers, marty

sorry i forgot to mention the exact problem is....

*** STOP 0x0000007B (0xF795E524, 0xC0000034, 0x00000000, 0x00000000)

Edited April 13, 2008 by thestickman

[cluberti]

What controller is your boot drive attached to? The 7B stop is common around here when the driver for your RAID or SATA controller isn't integrated properly (STOP 0x7B = Inaccessible boot device).

[thestickman]

hi cluberti, thanks for the quick response.

im using an abit nf7-s nForce2 mainboard with Sil3112 SATA controller.

my OS hard drive is on the IDE0 channel, and have 2 data hard drives filling the remaining SATA controller.

hope that helps...

[cluberti]

If you haven't already, you might want to read this thread.

[thestickman]

no that post doesnt help much cluberti but thanks for ur efforts anyway

im sorry to see theres no easy fix for this issue.

the fact that the unattended install USED to work with all types of modifications, be it service pack slipstream, driverpack integration, addons, or even removal of components, and NOW does not accept even a service pack update which has very little to do with my SATA drives as im not installing the OS on the SATA controlled hard drives baffles me. why is it a clean version of winxp installs flawlessly but a service pack updated winxp doesnt?

the point for me is that i am not even the least bit computer savvy and now i have to really get into the nitty gritty of customizing certain files etc. to suit my pc. not only is this extremely inconvenient for me and my lack of "coding" knowledge if u can even call it that, but the fact that it doesnt do all these things automatically anymore means theres definitely something wrong. id prefer it to just be the way it used to be, a point n click modified, universally usable unattended nLite install cd.

i might look into it further when i find some time and patience haha.

cheers, marty

[thestickman]

problem solved!

due to late night fatigue i hadnt noticed that the nLite website provided the v1.3.5 installer.

all my issues were resolved as soon as i installed it