johnhc

Slasher, thanks for the Last Session - helps much. You have such broad and myriad problems that I suspect you have run nLite more than once against the same source. I see no hot fixes in your Last Session. Did you not include any or include them in another run? How is your UPS connected to your system - via USB? Do any other USB items work or not work? I have seen none of your symptoms before, but have seen many bizarre and varied symptoms caused by running nLite multiple times against the same source or using some other program to do part of the processing or starting with a source that someone else has run something against. BTW, I assume you are working on your home computer and just mentioned the work computers because they also have UPS setups. Please note that the nLite license only allows personal use and no business use. Here is the important part of my standard inculcation: Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

Rayearth, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

Tralbry, Please notice that the nLite license that you agreed to when you installed it, does not allow business use, only personal use. Enjoy, John.

Thanks, Ponch, I posted it there. John.

Why has the forum begun to require me to login every time I return from leaving the site (reusing the tab)? This just started yesterday (Saturday, 7-11-2009). Thanks, John. EDIT: I am also seeing error messages (Authorization mismatch - please go back and try again. If you have been trying to access a function incorrectly, please use the proper method.) when I try to Preview a Reply.

Why has the forum begun to require me to login every time I return from leaving the site (reusing the tab)? This just started yesterday (Saturday, 7-11-2009). Thanks, John.

Pookey, if you will look at the Help (? in a circle) next to the Unattended Mode pull down of the General tab of the Unattended section, you will see the Prompt Repair mode (last). Enjoy, John.

leozack, the last batch file of yours I looked at used the guts of the AddOn, not the actual AddOn. This is essentially the same as using the MS installers. My comment on 'watching' the long install is - Don't Watch! MS update 963707 can easily be found at the MS DL Center by searching for KB963707. On using Vista to build for XP. Good question. Some have had problems and it is known that integrating an SP does not work. I say give it a try and let us know your experience. Vista 32 or 64 bit, same thoughts. I hope you do know that when you are only changing your batch file or the files it calls, you do not need to run nLite again, except to build an ISO. Enjoy, John.

RRukawa, we are having a very difficult time understanding what you are saying/asking. Perhaps if you post in your native language and you or we can translate it using Google translate. You can usually find attached Last Session by looking for the paper clip on the subject line of the threads. Here is one with several, including mine. Enjoy, John.

Henrique-S, I DLed a bunch of the drivers from the ASUS link you provided and found only two txtsetup.oem files. They were in the SATA mass storage drivers. None of the normal drivers had txtsetup.oem files. Stick with Fernando 1's advice and you will be good to go. Enjoy, John.

Henrique-S, I do not understand why the non-text mode drivers have a txtsetup.oem file in them. They should not. I suspect you have separated the files/folders and left this file behind. All the drivers are placed into the nLite Drivers section. You don't place them in the copied CD source folder, nLite does. You just tell nLite where to find the .inf files. I think you need to play with nLite. I played with it for several days doing one section then another. Yes you can place all the non-text mode drivers together with nLite in the Drivers section. Fernando 1 is the driver expert here, so please do what he suggests and you will be fine. If you still do not understand and still want to use the drivers you have found, please post a link to where you got them and we will tell you how to extract them and make the necessary folders. I do think if you play some you will learn the ropes. Enjoy, John.

Henrique-S, I guess we can do this for awhile, but here: A)The folder structure on the machine is your choice, so yes. B)If a folder has multiple .inf files and you want to include them all, then choose multiple. If only one or you do not want all the drivers in a folder, then choose single and select the one you want. C)Windows install has two modes or phases. The first is called text mode (no graphics) and all it does is copy some drivers from the CD to memory and ask you what partition to use and how to format it. Since XP does not have drivers for RAID or SATA attached drives, you must include these. Windows allows pressing F6 to include these drivers, but nLite allows you to place them on the CD (in the NLDRV folder) and automatically load them during text mode. The driver folder for these text mode drivers will contain the txtsetup.oem file. Drivers that are used during running of Windows do not have these txtsetup.oem files. After text mode comes GUI mode (graphics) and this is when the OS is installed and drivers are installed. D)See Above. E)Only one text mode driver for a particular machine is allowed unless several machines have the same RAID or SATA controller. If none of your machines has either SATA or RAID controllers (or you don't use them), then you do not need any text mode drivers. Most current machines have at least SATA controllers and HDDs. F)I leave it around for future reference. I can manually delete it later if I like. More questions? Here is my standard advice when you have a problem: Please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

staples., thanks much for cleaning up your reply and attaching your Last Session. I don't really know enough about your symptoms, but I would be suspicious of removing Internet Explorer and COM+. "999 - sqlstate = im002" gets lots of hits on Google and most seem to have to do with PT running in Administrator account in Vista - perhaps you should take a look. Did you run nLite more than once with the same source? If you can start over, then try not removing IE and COM+. Also take at look at the Black Viper site with respect to the large number of services you have removed. Are you really running SP1 and no updates? My standard inculcation: Please make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

Henrique-S, welcome. The txtsetup.oem is just for the text mode drivers (F6). Unfortunately you cannot place multiple version of these drivers on your CD. For text mode drivers, only the last one that gets there is installed in the text mode on Windows. This is the very first phase on install. So at least the CD will need to be personalized for each machine, if they use different text mode drivers. All the other drivers can be placed in nLite at the same time. The folder structure on the machine you use to run nLite is up to you - whatever works for you is OK. You can place all drivers for all machines in the Drivers section. These drivers are sorted by Windows according to IDs specific to the HW not just the HW type as text mode drivers are. You use the single or multiple driver selection according to whether there are one or more .inf files in a folder. You can always use single and just select each .inf. The delete Option is again up to you. It will delete the NLDRV folder from your Windows folder after the drivers are installed. It might be useful considering that you will have multiple chip set etc drivers. Hope this helps. Enjoy, John.

Spada, I think one thing we do know is that SP integration for XP under Vista (or 7) will not work. Others have reported problems with Vista made XP ISOs. You may be familiar with Unattended installs but here is a link to MSFN's guide. Enjoy, John.

hahahafr, the %Source% variable has a trailing backslash (\), so now you have two. %SYSTEMDRIVE% does not have the trailing backslash, so I would have expected the last command to have worked. Oops, just noticed you have screwed up quotes on the last one. If you have more questions/problems, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

staples, you were not asked to paste your Last Session. Please delete it and attach it (use Browse... and UPLOAD buttons). Thanks, John.

Spada, well, to begin with you have run nLite under Vista to create an XP ISO. That is probably not going to work. Next, you have over 700 drivers (!!!???) and NO text mode drivers - and no hot fixes. Do you not have a RAID or your HDDs on a SATA controller? How did you burn your ISO? If not with nLite, you probably don't have a proper boot sector. Have you run nLite more than once against the same source folder? I think it would help you a lot to spend a few days reading these forums to see the kinds of problems others are having. I'll leave you with my standard inculcation: Please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Thanks for attaching your Last Session - don't need to do that again until your next problem. Enjoy, John.

leozack, you did not answer the questions I asked in my last reply, so I will again suggest that you quit using the 3 in 1 .NET installer and use the real files from MS DL Center. Place them in your batch file as Kurt_Aust shows. If this does not prevent the errors, then remove all the AddOns you have and see if that does. Update KB963707 is not a Firefox update, it is a .NET update (Firefox support) and I suspect MS does not have a method to detect that Firefox is installed on your system. I got the request to install the x64 version of the update on my real machine (never nLited), and I installed it to stop the notifications. The other two updates that were in your nLite hot fix section, but WUD still told you about them, could be some that nLite is unable to integrate. Please do a search in these forums for the KB numbers and see if they are. If so, then place the installers into your batch file as Kurt_Aust does. Are you testing under a virtual system? If not, you should consider one. Enjoy, John.

cmonkedo, I too seem to talk to myself a lot in these forums, just not intentionally. Why in the world do you have 150 updates? Wow, please start by integrating SP3 (am afraid you will need to start over to sort this out), then add the necessary updates. The RyanVM forum has Update Packs that do just that for you. I hope you will also consider a virtual system for testing. VMware Server, VirtualPC and Virtual Box are all free. Please look at the last two first, they are much smaller. Your Last Session reflects that you have removed nothing, so that is not a consideration. I suspect your various updates have stomped on each other. Why the Media Player 6, 9 and 11 updates? Settle on one media player (I use WMP11) and forget the rest. You also must install WMP11, since it is not included, in fact only one is included at one time. NLite now has boooogy's WMP11 Slipstreamer called internally. You just need to install the slipstreamer and place WMP11 installer and updates in the hot fix section. I noticed that some of the AddOns are currently down level - may be a good time to update. But if you do testing on a VM, then leave all of these out, integrate SP3, use the appropriate updates (Update Pack, perhaps), and see if your original problems are gone. Please be sure to follow the other advice in my first reply. Let us know how it is going. Enjoy, John.

cmonkedo, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

staples., your Last Session.ini should be on your install CD, unless you selected the Option not to save it. Enjoy, John.

nik, I see no hot fixes in your Last Session. Have you run nLite more than once against the same source? Google gives many hits on hhctrl.ocx and probably contains the solution - as g-force pointed out. So, make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John. @okto, I think this error is addressed by MS and only an experiment would tell if simply placing hhctrl.ocx in the "keep box" will deal with it. I suspect not. Enjoy, John.

leozack, the Timeout command problem is because XP does not have the command - sorry, I now remember Kurt_Aust talking about that. In W2000, Kurt_Aust uses Ping -n 11 127.0.0.1 > nulI don't understand what this does other than cause some delay. Again, Kurt_Aust thinks it is needed and I just leave it. If your AutoLogon is working, I would leave it as is. I create my real user account, assign a PW and set it to never expire. I leave AutoLogon run always. I have also used boooogy's WMP11 Slipstreamer then run nLite, but since the running of it is integrated into nLite I just place the WMP11 installer and updates in the hot fix section - see my Last Session. I was not correct in suggesting that you could place you copies into the $OEM$ file, since you want to copy the entire I386 folder. I think it would work, but you would need to place two copies into your source folder. I thought disabling OEMPreinstall (which you have) would kill the $OEM$ folder, but it does seem I remember seeing something about AutoLogon and the $OEM$ folder, but can't find it right now. I don't have any help on your errors, except some questions and suggestions. Have you installed ASP.NET from MS? Perhaps the .NET installer you are using is doing something bad. Would you consider my previous suggestion to use the .NET installer and updates from the MS DL Center? For more information on the errors, click on the link provided in the message. I have found some very good information there - and some worthless. I get a rash of errors from an application I install, a couple of warnings about a Print function and a couple of DCOM errors which seem to be common in my system until I install a fix. I assume mine are coming before my batch file gets the fix installed. I get no more errors as time goes by. The * in the password is the indication for blank. Hope this helps, John.

RRukawa, if you mean Last Session.ini files, there are many available already in many posts, both recent and older. If you have a specific need, please search. Enjoy, John.