johnhc

Nlite_, Did you start with a fresh (not nLited before) copy of your source? This is the kind of weird problem that occurs when a source is nLited more than once. Good luck, John

Nlite_, Sorry, I think the answer is no. There are a number of topics in this forum about restoring removed components. Search here and see what is possible. Good luck, John.

memoryinmotion, You are welcome! Glad it is a go. Enjoy, John

adambaumil, Have you tried to boot into Safe Mode (hit F8)? If you can get into Safe Mode, go into My Computer Properties and turn off Automatically Restart. The next reboot should then halt with a BSOD and the error code. If you are using a real machine (not virtual) and have an AMD processor there is a problem with SP3 that causes a continuous reboot. Let us know what you learn. The MS fix is here. Good luck, John.

memoryinmotion, Are you always starting with a fresh source (not nLited before)? Perhaps you should attach (not paste) your LastSession.ini. Are you using a virtual system to test your ISOs? What versions of nLite worked and did not work? Did you check the MD5 on the DLs? xophe, MrZoSo reports here that if you use Compatibility mode of XP SP2 Compatibility, you can make good ISOs for XP in Vista. Good luck and enjoy, John.

HowdyDoody, I have not used VirtualPC, so I don't know exactly what is next, but you should be able to create a Virtual Machine. Read the manual and play with it or maybe someone with experience will offer to help. I also don't know what Primary Slave is. On the Create Bootable ISO in the upper left area is a Mode pull down. It has Direct Burn option. If you are using VirtualPC you should be able to create an ISO file and boot (install) directly from that. To learn a little about VirtualPC, I suggest that you create an ISO from your fresh source containing only the OS and maybe SP3. Then install this on your Virtual Machine defined in VirtualPC. Allocate at least 512 MB memory and 4 GB of HDD. I have not had any failures during installs of the ISOs I have built, so I don't what what error you are talking about. Enjoy, John

Kurt, MrZoSo, in this post says he just set nLite to Compatibility Mode of XP SP2 Compatibility and it worked (XP x64 ISO created under Vista). Enjoy, John.

LoBa, I think the first thing I would suggest is that you put the four services you have removed back and see what happens. If that fixes it, then experiment to see which one is causing the problem. One of them seems to have to do with Win Updates. I also would definitely go to the latest version of nLite. Be sure to start with a fresh source (not nLited before). Enjoy, John.

HowdyDoody, Have you tried using the CD writer built into nLite (Create Bootable ISO step)? It has an erase function also. I have used it without a problem. You don't need to create an ISO file. I think you should not be afraid of using a virtual system. I use VMware Server (only support XP x64 at the time) and have had no problem. Look at these forums concerning VirtualPC and VirtualBox. What kind of SP3 problems are you afraid of having? I installed it on an old machine of mine running XP Pro (32 bit) with no problems. My son had a problem concerning AMD CPU, but there is a MS fix for that. Again many people in these forums have installed SP3. Perhaps someone can help. In the long run you will need it for security reasons. Good luck and let us know how it goes. John.

HowdyDoody, Are you nLiteing a source that has already been nLited? You should always start with fresh source. I copied my CD contents to a folder and make a copy before I start nLite. Curious - why are you not adding SP3? You should consider a virtual system (VirtualPC, VirtualBox, etc) to test on and prevent making all those coasters. Are you using re-writable CDs? If so, are you erasing them before you re-write them? What OS are you running nLite under? Enjoy, John

RamGuy, I have my XP Pro x64 set to 3070 MB/3070 MB (min/max) and it is exactly that size to the byte (3070*1024*1024). How did you set it? Have you rebooted? Your sidebar says Vista, but your question says Win XP. Which is it and if XP which version? What does this have to do with nLite? Enjoy, John. Edit: Look at this Topic for more information about page files. What is your memory size?

Thanks, Kurt...I too am seeing double. TranceEnergy PMed me that it did work for him, but he had to use the fixmbr (fix master boot record) command to get the boot device back. There have been a number of people asking about this in the nLite Forum. Thanks, John.

xbxjunkie, I hope someone will answer for absolutely sure if it is OK to use Vista to create an XP ISO. I think it is probably OK it they are both 32 or both 64 bit OSs. You should be creating a boot-able ISO. Why not try the disk writer built into nLite. It has always worked for me on both CDs and DVDs. A better idea is a virtual system such as VirtualBox (Sun), VirtualPC (MS) or VMware Server (all free). I use VMware Server because at the time it was the only one to support XP x64 guest (I'm using XP x64 host and guests). The first two are much smaller than the last, about 10 to 1. You should also be able to just write an ISO file with nLite and connect it to the VM and quit burning disks. You could also use re-writable CDs or DVDs (this was my first solution until I found out about the ISO file). Once things are working on a VM then go back to real HW. Note that the Sata drivers will not be tested in the VM environment. Good luck, John

jmacknmo, I have looked at but not tried any recommendations from this Viper site but give it a try. Google will probably yield more ideas as will searching these forums. Enjoy, John.

David McMahon, First, I suggest you slow down and stop opening multiple New Topics. One is plenty until you get off the ground. By slow down, I suggest you do an nLite with nothing but your original source (clean, not nLited!), add SP3 in Service Packs and the WMP11 file I pointed to as the ONLY Hot Fix. Try building and installing this. Your virtual machine should have at least 512 MB of memory and 4 GB of HDD. I have not used VirtualBox but it looks like it is running out of resources. This small step for man, is useful to help you understand the nLite process and become confident with the sequences. I don't understand what you are doing with WMP11 Slipstreamer (and Booogy's site) but you don't need to do anything with WMP11 except to put the file I point to in as a Hot Fix and nLite will recognize it and call Booogy's WMP11 Slipstreamer for the integration. You will see the window open and run the integration. When you are completely successful with this exercise, then you can proceed at your own pace. It is fun to learn this stuff but frustrating trying to learn it all at once. Try it! Here is the top of my Hot Fixes list from my Last Session. Notice I am running XP x64, so the names of the files are different: [Hotfixes] C:\Slipstream\Slipstream Components\nLite_AddOns\Kels_QuickLaunch_x64.cab C:\Slipstream\Slipstream Components\WMP11\wmp11-windowsxp-x64-enu.exe C:\Slipstream\Slipstream Components\WMP11 Hot Fixes\WindowsMedia11-KB929399-v2-x64-INTL.exe C:\Slipstream\Slipstream Components\WMP11 Hot Fixes\WindowsMedia11-KB936782-x64-ENU.exe C:\Slipstream\Slipstream Components\WMP11 Hot Fixes\WindowsMedia11-KB939683-x64-ENU.exe C:\Slipstream\Slipstream Components\WMP11 Hot Fixes\WindowsMedia11-KB941569-x64-ENU.exe C:\Slipstream\Slipstream Components\Update_Hotfix\Hotfix\020-IE7-WindowsServer2003-x64-enu.exe After this works, do a Windows Update (from your VM) and note the updates it recommends. Enjoy, John.

David McMahon, here is WMP11. I just went to Windows Download Center and typed WMP11. You can find the .Net source you want the same way but I don't know anything about the Silent thingy. Enjoy, John.

Lqdwax, What OS are you running - Vista? I have seen several people having WPI CD problems with Vista. Please search this forum. BTW, the latest version is 7.1.0 (maybe a typo)? Unless you turned it off, there should be a WPI log file in your root directory. I forgot the name format and don't having any on this machine but take a look (for me C:\) it should be obvious. This seems like a strange path for a config file. Why is it in the root directory? Is this a name you created (rb_config)? Is this file in your WPI folder or your root? I don't have one of these files on my system anywhere including WPI.Good luck, John.

mscals, I see nothing obvious. It is really a minimum nLite process. The one question I have is are you trying to integrate SP3 into a source that already has SP3? You need to start with a fresh copy of your source each nLite session. I copied my CD contents into a folder and make a copy of this folder before I start nLite. Are you using a virtual system to test? If not, please consider VirtualBox (Sun), VirtualPC (MS) or VMware Server. They are all free. I use VMware Server because it was the only one at the time to support XP x64 (which I run). It is much larger than the other two (perhaps 10 times) so consider the others first. I have used neither, but you should be able to get some advice in these forums. Enjoy, John.

mrZoSo, I may be wrong about having to use XP vs Vista for nLite but I think you must use a 64 bit OS. See this post - the red at the top. It also has some good information and links for building XP x64 ISOs. Enjoy, John.

Kurt, Does it work OK to run nLite on a Vista 64 bit OS to create an ISO for XP x64? Thanks, John.

Kurt, Does it work OK to run nLite on a Vista 64 bit OS to create an ISO for XP x64? Thanks, John.

David McMahon, nLite 1.4.9 has WMP11 Slipstreamer built in - just add WMP11 as a hot fix. There are at least three free virtual systems available to test your ISOs. I use VMware Server because it was the only one to support XP x64. Sun has VirtualBox and MS has VirtualPC. I have not used these two but they are much much smaller than Vmware Server (something like 40 MB vs 400 MB). I suggest you try one of the smaller. More opinions can be found in these forums. One thing to be careful about is do not nLite a source that has been nLited before. I copied my CD into a folder and then make a copy before I start nLite to create an ISO. Spend some time looking at questions and answers in these forums including looking at WPI to install your user programs after Windows is installed. Do a little at a time such as your source + SP3, then test on your virtual system to get used to all pieces. Enjoy, John.

mscals, We need to know more of what you are doing. Please attach (not paste) your LastSession.ini file. Thanks, John.

mrZoSo, I think your problem is not running nLite on an XP x64 system. Any other OS will give you trouble. I looked at my txtsetup.sif file (in AMD64 folder) and is a large (500 KB) text file. It has lots of data on disk names, file names and much much more. Try nLite on XP x64. Good luck, John.

jmbattle, I am glad you determined what the BSOD problem was! I specify 512MB for my VM memory size. When I first started running VMware Server, I got the Stop 50 error, but mine turned out to be a hardware problem corrected by a slight increase in core voltage. Enjoy, John.