J3ph_42

Okay, I realized I had started using a a program called X-Mouse, which makes windows act like act like X in terms of mouse useage (focus follows cursor, single click copy/paste, etc.) Stopping X-Mouse seems to make nlite not crash. If you are curious, I got it here: http://fy.chalmers.se/~appro/nt/TXMouse/

My OS was XP SP2, I just upgraded from the leaked SP3 RTM installer, not a slipstream SP3 install. Next/back is fine. The problem seems to be (from my amateur programming POV) that any time I trigger an OnClick() in a child window (like the file select browser dialog for finding a windows install directory to work from: I can open the dialog, and browse directories, but clicking Open or Cancel will cause the dialog to close, then nlite will die a few seconds later, if I choose a directory that doesn't have an i386 subdirectory, it will pop up a notice window telling me to try again, when I try to dismiss that, nlite freezes, same with the "that's a WORM media, you'll have to choose a working directory on your harddrive to proceed" notification window) My .NET version was 2.0, btw, I tried installing the SP1 release for .NET 2.0, but that didn't help (although the .NET update said it installed properly).

I'm running WinXP SP3. Not sure about the .NET version, it is at least 2.0

I just tried nLite for the first time a few weeks ago when XP SP3 came out, and it worked great. Now, I have come back to it, and if I only use buttons on the main nlite window I am fine, but whenever I click a button in a dialog, nlite crashes. File browser dialogs cause it to simply die, and trying to dismiss error/notification dialogs causes nlite to freeze, forcing me to kill it with task manager. Uninstalling nlite didn't help either. What can I do (other than not use nlite)?