johnhc

ninjaneo, Have you tried using makecab to convert your uxtheme.dll to uxtheme.DL_ and overwriting the one in the i386 folder? I could find no other copies in my CD copy. Of course there could be more in a .cab file. Seems too easy. Enjoy, John. Edit: I just tried this and it worked! Surprised me! I should point out that I did nothing with nLite but make the ISO (after I copied my modified DLL files to AMD64 folder - I'm running XP x64). Perhaps if nLite was applying an SP or other updates, I may have lost my changes. But it is a start. Enjoy, John.

Kelsenellenelvian, I saw a reference to you in the WinCert forum about Restorator, the program used to modify system resources. It is a non-free version of ResHacker that works on XP x64. Are you, or anyone else for that matter, familiar with it? I see it has a 30 day trial. My question is does it quit working after 30 days or just bug you to death? Paying $95 for a possible one time deal seems unreasonable. I know this is off subject, but I hope people won't mind. Thanks for any help. John.

r00pr3t, HW is hardware. I use VMware Server which is a huge program (latest-575 MB) because I am running XP x64. I suggest you look into VirtualPC (MS) or VirtualBox (Sun). They are both free and I think around 40 MB. You install the program, create a Virtual Machine (VM) - defining virtual HDD size, memory size and attached hardware. You can point the virtual CD/DVD to the ISO file you make with nLite. The VM will use virtual drivers, so it will not test your integrated drivers (leave them in), but should help resolve your network problem. Open a command prompt (Start-Run...-cmd), and type ipconfig. You should see information about your network adapters and connections. Type ping yahoo.com, and you should see the ping requests being sent and received. Error messages would be interesting to see. Good luck, John.

r00pr3t, I looked at your LastSession and see that you have removed some DHCP and DNS stuff. This may be why you can't connect. I suggest you try to build an ISO without removing any services and see if that will work. Leave in all your other nLite parameters. You might go to a command prompt and try to do an ipconfig command and ping to site (yahoo.com) and see what, if anything you get. I assume since you have made 7 coasters, you are using HW to test. You might consider using a virtual system such as VirtualPC or VirtualBox. Then you only have to create an ISO file and boot from there. It won't test your driver integration but is a good test of other aspects of installing and running XP. jmbattle has a good idea with re-writable media to save making coasters. Until I discovered I could use the ISO, I rewrote one DVD+RW maybe 20 times with no problems (just erase before you write a new ISO). Enjoy, John.

phaolo, I also think it is probably a VM problem, but I think you should eliminate the nLite version before you address that. At the boot time you are talking about, VM has no knowledge of SP3 and the only way SP3 should effect your ability to boot is if nLite had problems with integrating it and messed up your ISO. Good luck, John.

phaolo, First, please install the latest nLite and see if that corrects your problem. The VMware log says the floppy is not ready. Why does this matter? You may need to upgrade your VMware also. They just released VMware Server 2.0.0 (free) or you could go over to VirtualPC or VirtualBox (both free) and much much smaller. If I think of anything else, I will comment, but please get the latest nLite. Enjoy, John.

phaolo, I am using VMware Server and am not familiar with what you are using but I suspect it should be OK. I assume you are using nLite to create an ISO. In my VMware experience the optical drive is always listed as CD/DVD and I don't think the ISO knows the difference. Without looking (you should look) I strongly recommend you upgrade to nLite 1.4.9.1. There were some nLite problems early on with SP3. I am running XP x64, so have no SP3 experience. You need to provide more information - the more the better. Please attach (not Paste) your LastSession.ini. Always use a fresh copy of your source files/folders and never nLite a source that has been nLited before. Enjoy, John

r00pr3t, You need to provide more information. Please attach (not paste) your LastSession.ini. What OS are you using and building? Have you nLited your source more than once? What is your source - retail, OEM recovery, etc? Have you just read through these forums to see what kind of problems and answers are found here? Enjoy, John.

abomadi, Are you using a VISTA system to make the XP ISO? If so, have you set nLite.exe to run in XP SP2 Compatibility Mode? Have you nLited the same source more than once? You should always start with a fresh copy of the CD files. What is your XP CD - retail, OEM, recovery, etc? You should attach (not paste) your LastSession.ini. Where did you get the SATA drivers? Did you integrate them as Text Mode? Are you using a virtual system (e.g., VirtualPC or VirtualBox to test? - highly recommended. Enjoy, John

Alien42, I know this is not a direct answer to your question but I suggest you look into WPI (Windows Post Install). It will do all the things you want and is much easier to use. See a couple forums below the nLite forum. Enjoy, John.

lnjr, Sorry, I have run out of suggestions except to attempt to contact nuhi (author of nLite). I suggest you send him a PM with a screen shot of your error and a link to this forum topic. Before you do, I suggest you check the MD5 for nLite also. Nuhi always includes it on his DL page. Please let me know what you learn. John.

BlackLightStar, That error, R6025, shows up many times in a search of these forums. I saw one here in the last few days. I am not familiar with XP (I run XP x64) hot fixes, but those errors, in general, should not occur. Have you nLited the same source more than once? If so, get a fresh copy and start anew. Enjoy, John.

Yantoo, I assume you checked the MD5 for nLite DL also? My only other thought at this time is perhaps your security SW is interfering. You might try turning it all off and see if that helps. When I do this I unplug my modem to prevent bad guys from sneaking in when I am vulnerable. Enjoy, John.

lnjr, After you install HashTab, right click on the hot fix file and select Properties. Go to the Hash tab and you will see the Hashes computed. You can paste the hash - EA16789F6FC1D2523F704E8F9AFBE906 - into the compare line toward the bottom and it will do the compare for you. You will get a green check or red x to the left of the compare line. Do you have any kind of a DL manager or accelerator? Enjoy, John.

lnjr, Please check the MD5 for the IE7 file. Thanks, John.

chbt, It has been reported in this forum that you can nLite an XP ISO under Vista if you set nLite.exe to XP SP2 Compatibility Mode. See here.

lnjr, Why does your IE7 have two .exe levels on it? This must be your problem. Remove one .exe. BTW, you should not attach your LastSession_u.ini files. I suggest you remove them if you can. [Hotfixes] C:\Documents and Settings\lmh\Desktop\IE7-WindowsXP-x86-enu.exe.exe Hope this is it! Good luck, John.

FarmCretin, Interesting looking theme. Where can I find it? Thanks, John. Edit: I would also like to know how to get the devices to appear in the My Computer context menu. I have searched to exhaustion. Thanks again, John.

_Raynor_, I think the way your "[Options]" section looks is correct. The default is "Enabled" and does not add anything to the preset. When you select "Disabled, then the CDPromptRemove is added to the preset. See mine above. The interesting thing is you're not getting a prompt, ever. On the side of your post it says OS: XP Pro x86. Is this what you are testing also? Notice I am running XP x64. Have you nLited your source more than once? You should always start with a fresh copy of you CD files/folders. Enjoy, John.

RonaldoGomez, I suggest you see this thread. Enjoy, John. sardoniks, Please start a new topic and attach (not paste) you LastSession.ini. Thanks, John.

whftherb, I am not familiar with UltraISO. Will it automatically include a boot sector? If you are unsure, use nLite to direct burn the image. I have never had a problem with using nLite to write both CDs and DVDs. I cannot answer your questions about the various files in the image. I think Kelsenellenelvian is talking about when you do the driver integration in nLite for the SATA drivers. The initial install phase is refereed to as text mode since there is no graphics support. When you get the message about 39 minutes to go (refereed to as T-39), Windows has switched to GUI mode. You should not need to push F6 during install. Integrating the text mode drivers should render this unnecessary. Your LastSession.ini looks fine to me. Good luck, John.

lnjr, I use HashTab to check the MD5. When the program is installed, it adds a tab to your properties for a file. Just do a Google on hash and you will see many calculators. HashTab seemed to be the easiest for me. What exactly is your source disk? Retail, OEM, recovery or other? Please attach (not paste) your LastSession.ini. Enjoy, John.

Yantoo, Some more thoughts: Did you check the MD5 on nLite after the DL? I use HashTab and always check the MD5 if available. I DLed dotnetfx.exe, the size is 22.4 MB (23,510,720 bytes) and the MD5 is 93A13358898A54643ADBCA67D1533462. If this is not the .NET 2.0 you DLed, let me know what you used. Otherwise check these numbers against your DL. Enjoy, John.

lnjr, Did you nLite your source more than once? You should always start with a fresh copy of the original CD files/folders. I DLed the update (IE7-WindowsXP-x86-enu.exe) and here is the size and MD5: Check these against yours - perhaps you got a bad DL. Enjoy, John.

jeromerocks, Have you nLited a source that has been nLited before? You should always start with a fresh copy on the original CD data. Many bizarre errors/problems occur when a source is nLited more than once. Enjoy, John. Edit: Does your disk autostart when you put in a running Windows system?