memoryinmotion

I'm using the original purchased DVD - which is not visibly damaged. Unfortunately, I don't have access to TechNet or MSDN at this time. As I was closing up the shop tonight, I noticed something off: I usually turn off all the lights so I can see if I've forgotten to turn off speakers and monitors. I noticed that the keyboard numlock was still lit on this machine that had been turned off for some time. I've only seen this on older systems with blown capacitors and/or bad power supplies. I've made a note to check the motherboard tomorrow.

That makes sense - and I was heading down that road. However, I have 2x 2 GB sticks with room for two more. Also, Memtest86 checks fine after at least 4 hours. The PSU is a Zumax 400W powering little more than a 350 IDE drive and the Video Card. I've loaded XP on this thing about six hours ago, and it's running flawlessly. What else should I be looking at? Keeping XP (which would be my first thought) is not an option since the individual that owns it needs it to link to a Linksys Media Extender, which requires the Vista operating system... which is the impetus for this problem. Try Windows in safe mode - does it hang there? If not, then it's a driver issue for sure. No, it doesn't hang in Safe Mode - so I'm looking hard at the video driver. However, There seems to be nothing I can do to make this card work, and it's supposed to be compatible with Vista. Using it's native drivers, or the drivers that came with Vista cause the same problem. I would suspect the card is bad if it didn't run fine under XP.

That makes sense - and I was heading down that road. However, I have 2x 2 GB sticks with room for two more. Also, Memtest86 checks fine after at least 4 hours. The PSU is a Zumax 400W powering little more than a 350 IDE drive and the Video Card. I've loaded XP on this thing about six hours ago, and it's running flawlessly. What else should I be looking at? Keeping XP (which would be my first thought) is not an option since the individual that owns it needs it to link to a Linksys Media Extender, which requires the Vista operating system... which is the impetus for this problem.

First the Hardware: MSI K9A2 Neo with 4 GB Logic RAM AMD Athlon 6000 ATI All in Wonder 600 Series Video I can't count how many times I've tried this in the last 14 hours. It freezes during installation, it freezes while finalizing the installation, it freezes when it finally gets installed just sitting there doing nothing. It froze while installing the MSI Driver disk, then it finished the system drivers on reboot... then it froze while installing Flash. Reboot again, installed Flash successfully, then it froze sitting on the desktop doing nothing. The lockups are completely random. No blue screens or errors. What the hell is going on? I've NEVER had such issues with Vista. BTW - this is a clean install, beginning with a wiped drive (WipeDrive, Level 2 - DoD standard). No other hardware is in place.

Is there any way to "slipstream" new chipset drivers on to an old drive? New system: MSI K9A2 Neo with an AMD Athlon 64 x2 6000+ Old system: Asus A7V400 - MX with an AMD Sempron Single core (No exact specs yet.) This would be a great timesaver if possible.

SOLVED! Thank you, John! I had NOT been using a fresh source after all - and rectifying that solved the issue. Also solves the question of why it works in one environment and not the other - accessing different sources on different networks. Ah-HAH! Thanks so much. MiM

I have not been starting with a fresh source, however yesterday (when I involved a third machine) - that was indeed a fresh source and had the same problem. I'm using 1.4.9 now, and had been using 1.4.7 before. I had used several versions along the way, but not with any regularity. 1.4.7 worked the best on the machine that I'm not having any trouble with - and I believe I'm still using 1.4.7 on that machine. I'm not using virtual systems. I haven't checked the MD5, but I'm downloading them direct from nliteos.com, and not a third party. LAST_SESSION.INI

Just to be clear - I do not have Vista installed on the computers in question. One is running XP Home SP3, and the other is running SP2... and I've tried a third computer since writing this... also with SP2... also producing .iso's that bomb at the product key. I have NOT tried manual slipstreaming yet, but I did not have to manually slipstream SP3 on the machine that does work, so that didn't occur to me.

It's driving me crazy. I've been using nLite forever now without a problem. The only difference is the box with which I use it. If I create a CD on the original box, it works just fine. If I use a different box (both are XP, both using the same XP CD and SP3 File), CD's created on the second box have the "Invalid Key" error. I have been hunting around for a week now, and only see this error related to slipstreaming SP3 under Vista. This is not the case here - neither machine has ever been installed with Vista. Just using the simplest unattended configuration, I'm getting an "Invalid Product ID" message from a CD created under XP. Both are custom-built, non-proprietary boxes with retail versions of XP installed - and from which the CDs are being made. Any clues?