johnhc

Thanks cluberti. I looked at the key you pointed to and the value is ?:\pagefile.sys. Thanks, John.

cluberti, I really hate to ask questions since I am clearly not qualified to use your script - I am not knowledgeable enough. I have run it on my VM (VMware Player running W7 Ultimate x64, host XP x64). I always get "No paging file found." I do have a System managed paging file, currently 1024 MB. After some looking and research, it seems to me that the following code is returning nothing. Should this work on 64 bit machines? Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_PageFileSetting",,48)Thanks much, John.

cluberti, thanks much! I will give it a try on my next install. Thanks, John.

MOBO, also attach your txtsetup.sif, but be sure there is no private data in it. Also attach the txtsetup.sif from the original CD. Where did your source CD come from? Have you run nLite more than once against the same source? Enjoy, John.

Is it possible to set the PageFile size during install? In XP x64, I used PageFileConfig.vbs to set it out of GUIRunOnce. W7 does not have a PageFileConfig.vbs file and I cannot find an equivalent. The AutoUnattend.xml does offer a Size and Path for Windows PE. Thanks, John.

david.nchly, I don't really have an answer for you (certainly not the 'best'), but I will relate the method I learned from Kurt_Aust (used in his great guide for XP x64). Build an ISO with the components you want (including latest SP, IE8 and WMP11, if you want), install it on a VM and go to Windows Updates and use that list to select list of updates. There are Update Packs (mainly RyanVM) for XP and XP x64, but I do not know if there are for W2003. I use VMware Player for my test virtual system - it is free. VMware Server (at EOL), VirtualPC and VirtualBox are also free. Enjoy, John.

lm411, Windows updates certainly change all kinds of system files and I suppose some are protected by SFC. I really don't know how SFC goes about its job and have never used it. I would think that your Windows installation would not contain any system files that are not on your nLite created CD unless you have managed to restore some removed components. By "multiple runs" of nLite, I mean to copy your CD files/folders, run nLite to apply hot fixes, run nLite to remove components, run nLite to apply Unattended parameters, etc - each in a separate run. This will get you in deep you know what. I always recommend that a fresh copy of the CD files/folders be made then nLite is run executing all the Tasks that you want to do. It is OK to apply an SP, then quit and continue later. It is also OK to complete your nLite run, then come back and create an ISO or burn a CD. But probably most other sequences will cause a problem. Enjoy, John.

Phenixer, are you in a business environment? The nLite license only permits personal, not any kind of business use. Please see the license agreement. Applying IE8 and MP11 updates to Windows that contains neither can cause many and strange symptoms. I have no experience with Deployment Toolkit, so can't tell you what effect it would have. In general, I recommend to do all their work with nLite and no other SW. Mixing various programs to process the source can definitely cause problems. NLite expects to see an unaltered copy of Windows to start. Deployment Toolkit may expect the same thing. Are you using WinPE? The more you tell us the better chance we have of figuring out what the problems are. BTW, you should get no errors running nLite or installing. If you do, then something is wrong and needs to be corrected. Enjoy, John.

I think you two are in the wrong Forum. Please try here. Enjoy, John.

Phenixer, the Hot Fix feature is neither buggy nor unuseful. It works great, in fact. There are some updates that do not integrate in nLite and that may be your problem. Since I run XP x64, I am not aware of specific XP updates. I also suggest you look at RyanVm Forum for an Update Pack in French - saves a lot of trouble and easy to use if there is one in French. It looks like you have done nothing but add updates. Is this true, or have you run nLite more than once against the same source? You should always start with a fresh copy of your CD files/folders and run nLite only once doing all you work in that one session. Please, in the future, attach (not paste) your Last Session as requested in the BOLD RED letters at the top. Enjoy, John.

VonBiggenBurgh, you need to buy a CD/key combo or a key that goes with your existing CD. A Retail key will not work on an OEM CD, vice versa and etc. Enjoy, John.

lm411, I see you select several Tasks but have no input for them - Hot Fixes, Drivers. Did you run nLite more than once against the same source? You should always start with a fresh copy of your files/folders and run nLite only once doing all your work. Multiple runs is asking for strange problems. I suggest you do some research here on running SFC (again, why are you running it?) after nLite - seems like I remember others inquiring about this. BTW, the Tweak "Explorer-Launch folder windows in a separate process" exposes a Windows bug, but has nothing to do with your problem. Right now, I do not see a path to get you back without starting over. Enjoy, John.

lm411, you need to attach your Last Session, as requested above in BOLD RED letters. Your first mistake, I see, is slipping SP2 and SP3. You only need SP3. Some here will disagree with me but you certainly don't need SP2. Requirements are different with a running system than at install time. I do not know what is stopping SFC from running - maybe the Last Session will help. Why are you running it? Enjoy, John.

VonBiggenBurgh, yes SP3 has all prior fixes and it is the only one needed. I doubt Sousemouse really took 46 attempts. Using a VM, always starting with a fresh copy of your CD files/folders and running nLite only one time you should have a running system quickly. Enjoy, John.

Sousemouse, Ponch gotcha on the Recycle Bin. For the warning message, please post a screen shot of the warning message and the User tab of the nLite Unattended Task. Also attach your Last Session_U.ini, but first remove all private data such as the CD key. I trust you have not run nLite more than once against the same source. Enjoy, John.

Sousemouse, you have opened your own thread. This is unnecessary. Please do not double post and stick with your thread. John.

VonBiggenBurgh, these types of things cannot be discussed here. Please see the Forum rules at the top right. So, you definitely need to buy a key. I would suggest you buy a current XP OEM version. OEM versions can be installed on only one computer. If you want to move your installation over time to multiple PCs, then you will need a Retail copy. Bought Windows will probably have a CD and with the key. The last time I looked, newegg.com still had copies. Without a valid copy of Windows and a legal key we cannot help you here. If you buy the latest, then you will have SP3, but if you start with an earlier copy, you will need to integrate only SP3, no matter what level the CD is. I suggest you look into Update Packs. They contain all the updates from SP3 and can be placed into the nLite Hot Fix section. Please see the RaynVM forums. Don't know what language you want to install, so consider that. I do highly recommend a virtual system for testing. VirtualPC, VirtualBox and VMware Player are all free. Until you install on HW, you will not need to burn a CD/DVD, simply make an ISO and install it into your VM. VMs will not test your drivers, but do a great job otherwise. Enjoy, John.

b-man, probably not, but please attach your Last Session and we'll take a look. Enjoy, John.

onksssss, allen2 is probably correct, so please attach your txtsetup.sif file, or just attach the code around the [WinntDirectories]. Please make sure it does not contain any private information. I suspect you have run nLite more than once against the same source. Please attach your Last Session.ini file as requested above in BOLD RED letters above. Where did your source CD come from? Did you have any errors copying your CD to a folder? Please look at your System Log and see if there are any CDROM Bad Sector errors around the time that the copy was done. Enjoy, John.

chetan, you are welcome. Glad you are running. Enjoy, John.

chetan, please attach your latest Last Session.ini and answer my remaining questions. Enjoy, John.

ItaloEvil, are you saying you are not running nLite? Were you able to read my last reply? Please answer all my questions. Have you installed .NET 3.5? Enjoy, John. ItaloEvil, stai dicendo che non stai eseguendo nLite? Sei riuscito a leggere la mia ultima replica? Si prega di rispondere a tutte le mie domande. Avete installato. NET 3.5? Godetevi, John.

chetan, you need to learn to do your own research. Google knows everything, almost! Here is a link to HashTab. It will add a tab to your Properties dialog. So, to use it you right click the file, go to Properties and select the File Hashes tab and compare the MD5 to the one supplied with the Update Pack. You did not answer any of my questions in my last reply. Please do so. Enjoy, John.

chetan, MD5 is a hash code. It is used to verify that a DL has not had an error which corrupted the data. You use a hash generator to check the code when it is given by the DL site. The site you linked to provided the MD5 code, so you should check it. I use HashTab, but there are myriad free ones available via Google search. What is your original source CD? Does it contain SP3? If not, you need to add it (using nLite), but you must do this running nLite under XP, not Vista or W7. You should always start with a fresh copy of your CD file/folders. Never run nLite against a source folder that has had nLite run against it before. Enjoy, John.

ItaloEvil, here is a quote from Kurt_Aust's thread on doing XP x64 installs. I think it applies to XP also. If you have not installed the earlier .NET (3.5), then you need to do that and the SPs that go with it. I attach my Programs list from my W7 (comes with .NET 3.5) install. You can see .NET 4 installed. Do you not see it in your Add/Remove list? My .log file looks just like yours, so I think that error has nothing to do with your problem. So we have as much information as possible, please provide the following information: Attach (not paste) your Last Session.ini file. Paste the code (batch file, if used) that you are using to install .NET 4. A screen shot of your Add/Remove list around .NET. Screen shots of any error messages you are getting. Enjoy, John. The .Net 4.0 installer, unlike the .Net 3.5 one, is NOT cumulative, it only installs the additional components that comprise .Net 4.0. Hence on Windows Vista and earlier you will need to install .Net 3.5 sp1 (.Net 3.5 is already included in Windows 7). Personally I wouldn't bother with .Net 4.0 for now as it will be a while (as noted in the guide) before we see applications using it in the wild, it was 2 years after the release of .Net 3.5 before I came across an application using it (most rely on .Net 2.0 only). I probably would have waited longer to add .Net 4.0 in the (forlorn) hope that a fully updated .Net 2.0 through .Net 4.0 installer would be released, but .Net 4.0 had already been mentioned by Trance-Energy in the guide. ItaloEvil, ecco una citazione da filo Kurt_Aust sulla facendo XP x64 installazioni. Penso che essa si applica anche a XP. Se non avete installato il precedente. NET (3.5), allora avete bisogno di farlo e la SP che l'accompagnano. Allego la mia lista programmi dal mio W7 (fornito con. NET 3.5) di installazione. Si può vedere. NET 4 installato. Non lo vedo nei tuoi Aggiungi / Rimuovi lista? Il mio. File di log sembra proprio come il vostro, quindi penso che l'errore non ha nulla a che fare con il vostro problema. Così abbiamo quante più informazioni possibile, fornire le seguenti informazioni: • Applicare (non incolla) il file di ultima Session.ini. • Incollare il codice (file batch, se utilizzato) che si sta utilizzando per l'installazione. NET 4. • Una schermata del vostro Aggiungi / Rimuovi lista intorno. NET. • Le schermate di eventuali messaggi di errore hai trovato. Godetevi, John. L'. NET 4.0 di installazione, a differenza del. Net 3.5 uno, non è cumulabile, viene installato solo i componenti aggiuntivi che comprendono. Net 4.0. Quindi su Windows Vista e versioni precedenti è necessario installare. NET 3.5 SP1 (. Net 3.5 è già incluso in Windows 7). Personalmente non preoccupatevi di. NET 4.0 per ora in quanto sarà un po '(come indicato nella guida) prima di vedere applicazioni che utilizzano in natura, è stato due anni dopo il rilascio di. Net 3.5, prima mi sono imbattuto in un'applicazione che utilizza (la maggior parte fare affidamento. Net 2.0). Probabilmente avrei aspettato più da aggiungere. NET 4.0 nella (vana) speranza che una completamente aggiornata. NET 2.0 tramite. NET 4.0 installer sarebbe stato rilasciato, ma. NET 4.0 era già stato citato da Trance-Energia nella guida. EDIT: Forgot to attach my screen shot.