johnhc

I have found several discussions of changing the GUI setup screen background color but none for x64. At one time in the long past, I found a way to do this but cannot rediscover it and have forgotten. It seems like it was not too bad. I let it go when the results did not look too good. NLite allows blue or black, but I would like to try some more interesting colors. Can some one point me in the right direction? Thanks, John.

I have found some discussions on changing the background color of the text mode setup screen. These are all for 32 bit XP. I have looked at my x64 file, smss.exe (both of them) with a resource editor and can make little sense of them. Can anyone explain to me how to accomplish this on x64? Thanks much, John.

arpharazon, yours is indeed a puzzling problem. Here is an experiment to try. Remove almost everything from nLite - no SP2, no drivers, not updates, no tweaks, no component removals. Essentially just burn an ISO from your XP x64 CD and see if that works. If you get the BSOD and Automatic Reboot, try hitting F8 and see if you can go into Safe Mode. If you can, then turn off the Automatic Reboot and reboot. Post you BSOD error code. Did you check the MD5 of your SP2? Please let us know what you learn. I kinda wish you had not told me about your TuneUp Utilities problem. I am using it but not the defragger. Have fun, John.

Kels, when I get a new WPI, I install my Windows options, User options and Config file in the WPIScrpits folder. I then edit the api.js file and remove the // on the sound line. I replace the Evil_Vista theme with my own. The only change here is a 'Windows Post-Install Wizard' in the header (wpi.htm file) that you helped me with a long time ago. I have attached my nLite Last Session. If you want me to run your experiment, please let me know what conditions (theme change?) Thanks, John.

I wanted to use the HAL9000 install screen, but the only methods I could find were for 32 bit XP and not 64 bit. The two DLLs are quite different, so I had to experiment. Here is what I found. I DLed HAL9000 and opened it in Explorer Suite (CFF) (supports x64) and saved Bitmaps 103, 104, 105, 109, 185, 186, 187, 188, and Strings 1-5. I then did a Replace of these Bitmaps and Strings in my WINNTBBU.DLL (Version 5.2.3790.1830). I also used a null string (720x450, why that size I do not remember) to replace 100-102. It looked fine except the progress bar was green. I also found a post on modifying this in 32 bit XP. Using the hex editor in Explorer Suite (CFF), I looked at my DLL and it was very different. I did a search for h'079E0500', the green color in the stock progress bar. Fortunately there was only one hit, at h'2A01'. I changed this to h'51000000', the dark red in HAL9000. The first time I failed to update the PE header and Checksum using the Rebuilder function. It worked fine and looks great. Enjoy, John.

SilverArrow, I am not familiar with the -S switch. What does it do, what are you doing, and what is your reference to i386\Update? I suggest you decide what tools you are going to use, then stick with that set. NLite can do everything for you and altering your source before you run nLite can only lead to grief. RyanVM update packs can be placed in the nLite hot fix area. Please make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

hellbringer616, with so little information, I can only guess. And my guess is yes. There is a sticky above that discusses nVidia drivers. If you are installing on a SATA and/or RAID, then the answer is absolutely. You can install other drivers after install. Please make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

eh3, I see nothing in the winnt.sif that would bother me. What we really need to see is your Last Session, so, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. It would also be really nice if you would edit your topic title and make it more descriptive so others can find it better. You can do this by editing your first post. Enjoy, John.

arpharazon, perhaps I am wrong about this if you have never had to use text mode drivers. Are you installing on a SATA drive? Have you installed on this machine on a SATA drive before? I guess by your reply, that you did not build this machine, but store bought it? Please let me know. Enjoy, John.

arpharazon, you need text mode drivers for your SATA controller. Please post a link to your MB driver page. Enjoy, John.

arpharazon, I, too, am confused about the AMD reference on my SP2. I'll have to check into that. The SP is the same and you should check the length in bytes against mine and the MD5. I use HashTab, but there are many free hash checkers available. You should also check the MD5 for nLite installer (see web site.) If you have SATA HDD, then you must install text mode drivers and you have not via nLite. Did you use F6 for this? If so, you must disable OEM Preinstall - see help (? in circle) in the Unattended section, General tag next to the OEM Preinstall pull down. Let me hear, John.

Xistic, I am glad you are running. I, too, don't know what caused your problem. Perhaps disabling NetBT caused this problem also. Thanks for reporting your result and if your rerun nLite, not disabling NetBT, please let us know if your problem does not recur. Thanks, John.

arpharazon, I agree - WHAT? I see nothing in your Last Session that should lead to a BSOD. What is the displayed error code? When everything is lined up properly, you should get NO error messages at all from nLite. If you are getting compatibility messages on your hot fixes, then they are not for XP x64. You should only include hot fixes that MS released after SP2. Kurt_Aust has a great list. Are your sure you are starting with a fresh copy of your source and integrating one SP (SP2?) Are you installing on a RAID and/or SATA connected HDD? You have no text mode drivers. Are you installing on HW or a virtual system? Please check the particulars on your copy of SP2. Name: AMD64-en-windowsserver2003.windowsxp-kb914961-sp2-x64-enu_7f8e909c52d23ac8b5dbfd73f1f12d3ee0fe794c.exe Size: 350 MB (367,964,016 bytes) MD5: 46D05CE174437A224C8A77047D010AE9 The SHA-1 is the hex at the end of the name. Please let me hear, John.

esau, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

Kels, I am using an AddOn that I wrote (and gave the instructions for in the nLite forum). It runs out f SVCPACK at T-13. Thanks, John. EDIT: Since I posted the above, I have preformed two installs. In the first, WPI started with a white screen which went away and nothing got installed. I rebooted and WPI started with a white screen for a while, then I heard the sound of it starting (I removed the // on the sound line in api.js.) The white screen persisted for awhile, then went away and I could see my desk top. I could see the command prompt window and my installs running, but there was no Installer window and no button in the taskbar. It finish without errors. John.

Xistic, go to Services manager again and set Net Logon to manual and Start it. Did you reboot? If this still fails, open Network Connections (Start) and right click the adapter you are using, then click Properties. In the pull down list select Internet Protocol (TCP/IP), and click properties. This page should say Obtain IP and DNS addresses Automatically. Click Advanced, then the WINS tab. LMHOSTS Lookup should be checked and the NetBIOS Settings should be Default or Enabled - OK out. Disable then enable your connection (right click your adapter.). You can post some screen shots if your still have no joy. Can you get an Internet connection? Good luck, John.

Xistic, I think you may need NetBT (TCP/IP NetBIOS Helper.) Please go into your Services manager (right click My Computer, click Manage, then Services) and set it to Automatic and then click Start. While you are here, make sure the Server service is Started. Then see if you can see the computers on your network. Also you need to remove the tweak "Explorer-Launch folder windows in a separate process." This tweak exposes a Windows bug. To see if it is having any affect now, go into Folder Options (Control Panel) and find this option and uncheck it. Please make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

sidefx88, I have successfully altered (for XP x64) the Hal 9000 billboard (from the site I found here), installed it and it looks great! On the first attempt, I had failed to update the check sum, so had to do it over. I should have known better, since I have been here before. The progress animation is not converted but I am working on it. Thanks much for getting me interested - learning a lot. Thanks, John.

Thanks, Kels for your reply. I am attaching my log when it finally ran. I am not sure what you mean by first drive, but I to have a CD (virtual) in the E: drive. You can be the judge if I have a lot of entries. Thanks much, John. EDIT: Do I still need 'reg delete HKEY_CURRENT_USER\Software\WPI /f'? EDIT2: Yesterday I decided that I was having IE8 problems (with WPI) because it had been installed (T-13), but had not gone through a reboot. So I changed the RUNWPI.INF to call a small .bat that set WPI to run in Registry RunOnce and do a reboot. This worked sometimes. Perhaps it needed to have Windows Explorer to be running (it does for one of my functions), so I removed WPI from the RunOnce and put it into the StartUp folder. It has run every time I've tried it here, but is very strange. Windows Explorer is still not up, but the DeskTop is. I get a white screen, but the installer is running. I open the task manager (and Process Explorer) and observe wmiprvs.exe talking 99% of my CPU. There are actually two of these. One is from SYSTEM and one NETWORK SERVICES. The second one is the one taking all the CPU. They both are called from SVCHOST. I never see WPI main screen, but when the white goes away, I see the installer running. Don't know if any of this helps. Thanks, John.

Sonic, launched from the RUNWPI.INF, by double clicking WPI.hta on the CD or via RunOnce after a reboot. Thanks for replying, John.

I am running XP x64 (under VMware Server) and IE8. Most of the time I start WPI 7.4.0, I get a white screen and it hangs, then goes away. Sometimes it white screens, hangs then the white screen goes away but the installer is running. Really weird. Suggestions? Problem with IE8, x64? Thanks for any help, John.

jdub, in the future, please don't post your Last Session as an image. And best if you remove it - my AV went off on it and called it a malicious site. I also suspect your source. Please post a Windows Explorer screen shot of the CD. Enjoy, John.

tetrapro, your IE7 installer is last, but there are updates to IE7 before. This is a problem. Also you are using an AddOn for IE7 (.cab) which runs at T-13, so the IE7 updates are a real problem. NLite is capable, for a couple of releases now, of integrating the MS installer for IE7. I suggest you DL it from the MS DL Center and place it first in your Hot Fix list - remove the .cab. I would also suggest you check the order of your updates. If you still have a problem, then remove everything in the hot fix section and try again. I also wonder what you mean by You should do everything in one session. Please read my whole previous post. I use nLite to burn a CD or DVD - works fine. Some people report problems with high speeds - slow it down. A virtual system is best for testing (VirtualPC, VirtualBox or VMware Server - all free.) Have fun, John.

frag_68, yes, text mode drivers are distinguished by having a txtsetup.oem file. If you don't have one, then you don't have text mode drivers or the txtsetup.oem is not in the same folder. In some newer driver folders from manufactures there is one txtsetup.oem for all the versions of OS supported. In that case you need to copy txtsetup.oem into the folder you will actually use. Please post a screen shot of a Windows Explorer display of your drivers. Also, please post a link to the MB driver DL site for you model (suggest you get all your drivers here.) Please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

THXMAN, please post a screen shot of the error and, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. To get a program to run on the first startup begs the issue of when the program got installed (RunOnce?.) I think this is going to take some experimenting (a virtual system is really needed here.) Please look here and think about creating a tree to the Start Menu. When the $OEM$ folder is processed, your account will not be set up, but I think you will be able to put a short cut in the AllUser Start Menu. Also look into Windows Post Install (WPI, Forum a couple below this one.) Please do some thinking and let us hear back. Enjoy, John.