johnhc

VectorX, How are you burning the disk? If you are using burning SW (such as Nero), did you specify the boot sector? I suggest that you use nLite to burn the disk. Enjoy, John.

vrapp, In general, you cannot nLite a source that has already been nLited. The results, as can be seen by reading these forums, are usually bizarre errors and problems. So, yes your should start with a fresh copy of the original CD. If this post looks familiar, it is because I copied most of it from another post. Multiple nLiteing of a source seems to be one of the most common problems seen in these forums. Enjoy, John.

kevluck, In general, you cannot nLite a source that has already been nLited. The results, as can be seen by reading these forums, are usually bizarre errors and problems. I suspect you were just lucky to get a working CD out of the bargain (although missing some items). So, yes your should start with a fresh copy of the original CD. Enjoy, John.

whftherb, Don't know what you missed, but don't know much at all about what you are doing. What OS are you using to run nLite? What version of nLite are you using? Are you sure the source has not been nLited before? Do you have the BIOS set properly to boot from the CD? Have you tried putting the CD into a running system and see if it auto starts? You can cancel out of this. How did you burn your CD - nLite or burning SW (like Nero)? If you used burning SW, perhaps you did not get the tight boot sector written. nLite works fine in burning disks. In order to see the repair option you will have to run the Unattended section and select Prompt Repair under Unattended Mode. I assume you are testing on hardware. I suggest you consider using VirtualPC or VirtualBox to test your ISO (assuming you are running 32 bit OS). Please attach (not paste) your LastSession.ini. With this information, people here might have a chance to help you. Enjoy, John.

*John*, Here. Enjoy, John.

icnocop, I am getting a headache just trying to sort the combinations of 32/64/XP/2003! Here is what I think: You need to use a 64 bit OS to create a 64 bit OS ISO You may get away with creating a 32 bit ISO on a 64 bit OS if you select XP Compatibility Mode for nLite.exe You should be able to create Win 2003 ISOs on XP and vice versa, if the first two above are met From what I have seen on these forums, when something fundamental is wrong, many really strange errors are thrown You must start with a fresh (not nLited before) source. Please notice that this is what I think, based on my experience and what I have seen in these forums. I suggest you get a virtual system for your testing. If you will be running 64 bit OSs, I recommend VMware Server. It is free but huge. Get this Processor Check tool to make sure your CPU is 64 VM capable. Enjoy, John.

Yantoo, You have my sympathy - I don't understand it either. There are a number of hits in these forums on the error (using first line for search). They may not apply, but you should look anyway. The root of the error is toward the bottom (6th from). It is saying there is probably corrupt memory. I would suggest you run MemTest86 for a few hours. If you are not familiar, see Google for the program and instructions. Enjoy, John.

Skreekins, I don't see anything obvious. Hopefully some else will. I suggest you try one or two things. Install one of he virtual systems I mentioned before and/or remove everything but your hot fix and see if that works. Be sure to start with a fresh copy of your original CD. After something works, start adding items till it fails. This is where a virtual system comes in handy because you can write an ISO with nLite (to a file) and boot your VM from that, never burning a disk. Enjoy, John.

*John*, It has been reported in this forum that it does not work unless you use Compatibility Mode. You should be able to find the thread via a search. Enjoy, John.

icnocop, I notice your OS (on the left of your posts) says XP x64. Are you nLiteing a 32 or 64 bit version of Win 2003? Are you able to try nLite under the same OS as you are building? I would also suggest you start with a fresh copy of your CD and use nLite to integrate only SP2 and see if that works. I certainly don't know what effect a command line slipstreamed source has on nLite. Enjoy, John.

Skreekins, You need to attach (not paste) your LastSession.ini so we can see what your settings are. Are you using a fresh (not nLited before) source when you run nLite? Are you testing on hardware of a virtual system, such as VirtualPC or VirtualBox? - highly recommended. What OS are you running nLite under? My only suggestion at this time is to simplify. That is, try a build with just the the fresh source, the SATA drivers and see it that works, then add SP3 (using fresh source), etc. Enjoy, John.

fuzytwitch, Google gets many hits on 'repeated activation windows XP'. I looked, briefly, and they seem to revolve around the hardware information sent to MS to validate your copy. Look in your System Event Log and see if you are getting errors logged at the time of you activation request window. Please attach (not paste) the LastSession.ini. What OS did you do the nLite build under? Did you start with a fresh copy of the source (not nLited before)? There are also many hits in this forum for eeePC. I suggest you look to see what others have experienced. I think most here have 'bit of a time line'. Enjoy, John.

tsures20, You need to give us more information. Please attach (not paste) your LastSession.ini. What kind of disk do you have - OEM, Retail, Recovery, etc? Have you nlited the source more than once? You must always use a fresh (not nLited before) source. What does mean? If there is an error, please post a screen shot. Are you testing under a virtual system (eg, VirtualPC or VirtualBox) - good idea, BTW?Curiosity question: why are you not integrating SP3? Enjoy, John.

oao, I DLed nLite 1.4.9.1 from all four of the options in the nLite site and all had the correct MD5. I suggest you need to determine what the error is concerning your machine. Perhaps PM nuhi, asking about you problem. Enjoy, John.

oao, It looks like you have a bad DL. I have attached a screen shot of my Hashes for nLite 1.4.9.1. You have no need for the archive, so delete that. The size (not size on disk) should be: 2.54 MB (2,665,796 bytes). Check this against the properties of your nLite installer. To use HashTab, you highlight and copy the MD5 from the nLite site, then paste into 'Hash Comparison:' area of the properties on the DLed file. See my attached shot. Notice the big green check to the left, if you do yours, you will see a big red x. Why the hashes for the two files are the same tells me you DL the same file twice, or whatever error you are getting is killing the files the exact same way. Look at the size of the installer. BTW, I do not see where you say you DLed from the nLite site. When you get a good DL (hashes agree), then try your install again. Perhaps, again, it is your security SW. Good luck, John.

oao, Is your Windows up to date? You need to check the MD5 hash before you continue (I use HashTab, see Google). Did you DL from the nLite site? John

mehanna, This error code shows up many times in Google and in these forums. Please search for a solution. Do you have .NET Framework 2.0 or higher installed? If you need more help, please supply such information as OS and nLite versions, .NET version, etc. Enjoy, John.

asheenlevrai, I suspect the problem is in the CD. Perhaps you could post a screen shot of the files on the disk. Explore the CD and take a screen shot. What do you mean by ? What does UniGE mean? Is this a VLK (Volume License Key) CD? Can you do an install with the original CD? Does it install in an unattended (silent) mode?The LastSession.ini is the Preset file containing all you nLite inputs that is written to your source folder by nLite. We don't need it at this time since you said a simple nLiteing of the source with only SP3 does not work. I suspect you have a much more fundamental problem - perhaps a CD that is already prepared as an unattended install disk. Enjoy, John.

asheenlevrai, I have not looked at your instructions but have some suggestions. You must always start with a fresh set of the CD files (not nLited before). I copied my CD into a folder and always copy this to a new folder before I start nLite. Have you tried just your source and SP3? Do you use a virtual system to test? I recommend VirtualPC or VirtualBox. I have used neither since I am running XP x64 and use VMware Server. It is huge compared to the other two. You can check in these forums for comments/recommendations on the two. Do you have a retail CD or an OEM CD? Is your CD a 'recovery" CD from your computer manufacturer. If so, tell us which company? Some people report problems with nLiteing some 'recovery' CDs. Please attach (not paste) your LastSession.ini. Enjoy, John.

oao, NS7 - NetScape 7? Do you have a DL accelerator? If so, turn it off and try again. Perhaps your security SW is interfering with the DL and/or the install. Did you check the MD5 after DL, if not re-DL and check the MD5. Is nLite or the installer set to run in 16 bit compatibility mode? What error do you get on the IE6 DL? Are you DLing from the nLite site, if not DL again from the nLite site and check the MD5. Enjoy, John

awpd, Your router should have settings that allow placing restrictions by MAC address. So, you should be able to block Internet access for the single computer on your LAN while still having access to other computers on your LAN. See your router manual and then sign on to the router and set the access restrictions. Enjoy, John.

awpd, How about simply unplugging your modem? I don't have a LAN but when I want to run with no Internet activity, I pull the power from the modem. You can also unplug the Ethernet cable between the modem and router. It is OK to hot plug/unplug Ethernet cables. Enjoy, john.

You guys should give this site a look: Viper. Enjoy, John.

DerekBaker, Go into The Unattended section and click the question mark next to the Unattended pull down list. Basically you can only see the Repair option if you don't do a completely silent/automatic install (my interpretation). Enjoy, John.

DerekBaker, Your question puzzles me. Why would a partition with a valid Windows installation not allow a Repair? Seems like this is exactly when a Repair is appropriate. However, whether the Repair option would appear is dependent on what you specified in the Unattended section. Please attach (not paste) your LastSession.ini so we can take a look at it. Have you nLited a source that has been nLited before? You must always use a fresh source that has not been nLited before. Have you tried your ISO on a virtual system? You might want to look into VirtualPC or VirtualBox to test your ISO before you go to hardware. Note that your driver install will not be tested. I am not familiar with the term AHCI. Google tells me it refers to SATA connection. Have you properly enabled the option in your BIOS? Enjoy, John.