johnhc

purkleturkle, I cannot tell you what updates you need/don't need because I run XP x64. I know there is a 'slipstream' AddOn for IE8 from Serby above in the Application Add-Ons sub-forum. There may be others, please search here and maybe on the RyanVM forum. You just place them in the hot fix section and add updates after. The AddOn is slipped into the source and the updates follow. To use your process, you need to include the "slipstream" IE8 and WMP11 and nothing else then install on VM and run Windows Update to see what updates are needed. Enjoy, John

purkleturkle, I suspect it is some or several hot fixes causing the problem. Please do a search here on "Not enough Quota" with the quotes. I did and got several hits, at least one talking about hot fixes. Please notice that both errors are about isass.exe. I see you have some "windowsmedia" hot fixes at the end of your list. Should these be there? I think you will need to sort out your hot fixes and see which belong and which do not. Please let us hear. Enjoy, John.

MutantTractor, yes, running XP under a VM is a good way to get around the problem and several have reported success doing it. Enjoy and please let us hear, John.

purkleturkle, I see you are running nLite under Vista (or W7). This can be a problem, especially if your are integrating a Service Pack. Do you have boooogy's WMP11 Slipstreamer installed on your computer? NLite expects it to be installed. Do you see it running? Where did your error occur? Please post a screen shot of the error message. Enjoy, John.

MutantTractor, by not being an nLite problem, I mean nLite is not adding or removing stuff on its own as you stated in your first post. It may be the fact that you did not run under XP. I need to know some more about source. Where did the original ISO come from? Is it a legal copy of Windows with a valid key? Did you extract it and run nLite against that? When you say "normal ISO under VMWare", you mean the original ISO or some other "normal" ISO? Have you run nLite more than once against the same source folder? Please do try running nLite under XP and let us hear. Enjoy, John.

MutantTractor, I see you are running nLite under Vista (or W7) to create an ISO for XP. This can be a problem, especially if you integrate a Service Pack. Did you consider the link I posted in my first reply? Is the runtime stuff needed for PiFast? Are you sure you have the correct version of PiFast for Windows? I am low on ideas here, except to say I do not think the problem lies with nLite. Please let us know what you find. Enjoy, John.

MutantTractor, please attach your Last Session as requested in the bold RED above. There is lots of information there even if you did not remove anything. I know little about C++, but I suspect you need to include some runtime components, such as this. I suspect nLite has nothing to do with your problem. Enjoy, John.

ner, I am in the process of leaning what I can about W7 and came across this link to the WAIK Guide (about 2.5 MB). I think it is also contained in the WAIK DL. It contains three .chm files including unattend.chm. There is a good explanation of the xml used in the install process. This link has been posted here before, but is very hard to find. Using the unattend.chm and searching on driver or driverpath are good places to start. Hope it is useful to you and others. Enjoy, John

HighFreak1c, I disagree with the wording of the RED note above. I think the Last Session should be attached anytime it is available. Lots on information is there, such as what host you are running nLite under. Sp0iLedBrAt is correct, running nLite under Vista (or W7) to create an ISO for XP is problematical, especially if you integrate an SP. Thanks for your resolution report. Sp0iLedBrAt, I have seen the mention of not placing the source folder on the DeskTop. I do not understand why this would be. Have there been specific threads where problems were eliminated by just moving the folder off the DT? Enjoy, John.

HighFreak1c, we need to see your Last Session, as requested in big bold RED above - please attach it. How did you copy your original CD? Did you copy it into an empty folder and not just into the root directory? Enjoy, John.

bensam56, thanks for your reply. I still do not understand. After your next release (about when?) will I be able to use XP, and if so, do I need WAIK or some part of it? Thanks, John.

broconne, I can't answer you question, but if you will attach your Last Session, as requested in bold RED above, we will take a look. A little searching on Google and in my source folder (XP x64), I find bda.inf and bdasup.sys. These may be the driver and .inf files you are looking for. There may also be more files needed. You will need to look at the .inf and see what is copied. In my folder, the bda.inf is compressed into BDA.IN_ and will need to be expanded (decompressed). The .sys is found in my SP2.cab. Do a search on your source folder for files *bda* and see what you find. Not sure what of them are really needed. BTW, I hope you understand that nLite is for personal use only and cannot be used in a business. Enjoy, John.

b-man, thanks for reporting. Enjoy, John.

The RT 7 Lite site says Server 2003 with SP2 can be used as a host. I am running XP x64 which is based on Server 2003 and has the same version number (5.2.3790). I have DLed RT 7 Lite and installed it on my VM (Vmware Server, running XP x64) with no problems. When I try to run it, it wants to install WAIK and the link leads to WAIK for Windows 7. I assume that it will not install on my XP x64. Is there a way for me to run RT 7 Lite on my XP x64 system? Does it really work on Server 2003 SP2? Thanks, John.

schooluser, as I understand Windows install Setup, drivers are installed during some HW discovery process early in the GUI mode. I know of no way to alter the order, and certainly no way to install an application before certain drivers. The BIOS communicates with Setup to discover the architecture of the HW and does not need drivers as far as I know. My video driver (AIT Catalyst) needs .NET and I install it out of Unattended RunOnce after the Catalyst driver is installed by Setup and have no problems. The video code does not need .NET until you are actually running. If you are having trouble with the smbus driver, tell us where you got it and always attach your Last Session as requested above in big bold RED letters. Enjoy, John.

BandofBrothers, the code 6.1.7600.0 is the same for Vista and W7, so I cannot tell which it is. Are you installing on a SATA drive in AHCI mode or on a RAID? Then you need added text mode drivers, otherwise, not. It is still possible that you will crash with a 07B error. Have you ever tried to install on the HW with no text mode drivers after nLiteing under W7? As I said initially, I cannot predict if making an XP ISO under Vista/W7 will work properly and I don't think I have seen building a 32 bit ISO under 64 bit, but that should probably work. Enjoy, John.

well, i just installed XP on the VM with out the drivers and it worked just fine. Text mode drivers do not get tested in a VM since it does not have access to the real HDDs. Where did you get the 0C2 - VM or HW? Enjoy, John. EDIT: I just checked that you are using Vista x64 to run nLite. Can you use XP - even under VM?

BandofBrothers, if you are getting the error in a VM, then it can't be a text mode driver problem. Are you? Please do look at your *.sys files (you can use Search) and see if any have the same name - if error on HW. Are you? Enjoy, John.

BandofBrothers, there are lots of hits here and on Google. Probably a bad driver. Did you see my question about 32/64 bit? Is the code 0C2? Enjoy, John. EDIT: Just saw your Last Session - was not up when I last replied. I suggest that you determine exactly what HW she has and include only the driver you need. The problem with text mode drivers is that if the driver file (xxx.sys) name is the same in more than one driver set, then the last one that gets there is the one that will be used. You can look at the drivers and see if this is true. Also running nLite under VISTA (or W7) to create an XP ISO is asking for trouble. Sometimes it works and sometimes not - especially when an SP is integrated.

BandofBrothers, do need your Last Session, as noted above in bold RED letters. You did use 32 bit drivers on her machine? What is the BSOD code? Enjoy, John.

TranceEnergy, you don't have a /T parameter for your Reg Add command. Don't you need to specify the key type (REG_SZ)? Enjoy, John.

Creatura, Google has a good translator that I use to translate the parts I need to see. There is a file created by nLite called nLite.inf (compressed into NLITE.IN_) that contains many of the instructions to implement what you ask nLite to do. It uses a routine called nhelper.exe and the last thing is to delete itself. When multiple runs of nLite are made, in some cases, nLite adds items to the end of this file that use nhelper.exe. Since it has been deleted, things don't go so well from here on. Enjoy, John.

Creatura, I tell people to always start with a fresh copy of the CD files/folders and run nLite only one time doing all your work. You can get away with some things (like adding an SP) but not others. I cannot tell which you can and cannot get away with, nor do I think anyone can except nuhi (owner/author) and he has not been seen here in quite some time. You can and should reuse your Last Session (using a fresh copy of source). In the future, please attach your Last Session when you have one and a question. Enjoy, John.

TranceEnergy, are you running your .bat in the nLite GuiRunOnce? If so, %Source% is set when you get control and you don't want to reset it. Enjoy, John.

Heh TranceEnergy, good to hear. I can't make much sense from your sample (mostly lack of knowledge). You did not use %Source% in it, but did you remember that "%Source%=D:\" (D will vary, of course)? That is, the %Source% variable has a trailing \, unlike most environmental variables. Catches many people. Enjoy, John.