johnhc

furballi,you still have the same problems after the install as at the start of this topic? The Last Session indicates you have .NET 2.0 not 3. I don't know that this makes any difference, but earlier you said you had installed .NET 3.0. I see nothing in your Last Session that should cause this problem. Have you tried any testing on a virtual system (VirtualBox or VMware Server, both free)? Enjoy, John.

ulysse34, what are these things? HotfixingReports HotCatCleanup D:\DVD\Windows XP KBs\Post XP SP3 KBs\WindowsXP-MSCompPackV1-x86.exe D:\DVD\Windows XP KBs\Post XP SP3 KBs\rootsupd.exeI have not seen these before. Are all your hot fixes in date order? That is, are to oldest hot fixes first in the list and the newest last? Enjoy, John

cmmcnamara, I am surprised no one has answered. I don't know for sure, but I suspect when you select all the .inf files your will get all the code that comes along with it. I plan on installing an ATI Catalyst driver when I get some hardware and I expect CCC to come along (I will DL the package with CCC). If it does not work that way, I'll solve that problem at that time. Today I am doing all my testing on VMware Server which can't test driver installation. I hope AMD releases a processor soon that I want. Enjoy, John.

Teebird, EH??!! Are you using nLite? How did you make a DVD from two CDs? If you want some help, you need to tell us what you are doing. Please attach (not paste) your Last Session.ini (if you are running nLite). Enjoy, John.

justibus, thanks. The bootcfg command also looks promising. I am looking at several options now. Thanks much, John.

ricktendo64, you are correct, it needs to be done during setup, but I am looking for a more flexible method than asking you to make me an AddOn each time I want to try something different. Thanks much, John. jaclaz, thanks for the link. It has possibilities. I will look at at it more. Thanks, John.

patman99, please attach (not paste) your Last Session.ini. Make sure you always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Enjoy, John.

Inferi0r, I think the answer to your last question is replace the : (colon) with - (dash). I also would like to know the answers to your remaining questions. Anyone? Enjoy, John.

DennyMK, I tried to modify my NTOSKRNL.exe with a resource editor and when I rebooted, the new boot screen flashed for a few seconds, looking like the good quality image I used. Then the screen went black and the new boot image reappeared, but this time the color was wrong and the quality was poor. I then DL the trial version of TuneUp and used it with the same image and it looks great. I open the TUKernel.exe with the resource editor and the bit maps are not altered. I then did a new install (format) of my ISO (on VMware Server). After the install, I copied the TUKernel.exe into the System32 folder and changed the boot.ini as LordWarlock suggested and it looked great. In this case TuneUp is not installed and any files left around are gone. I also opened NTOSKRNL.exe, that TuneUp had altered, with my resource editor and could find no changes. I am really curious how the image is placed in TUKernel.exe and what changes are made to NTOSKRNL.exe. Do you have any ideas to share with me? I am running XP x64. Does your 32 bit TUKernel.exe appear to have had its bit maps altered by TuneUp? Thanks to you and LordWarlock for teaching me some more about Windows. Enjoy, John.

Thanks, DennyMK. I saw that but it does not address the issue of changing boot.ini before installation. John.

Avi956, yes it works fine. Slipstream SP3 first, then include IE7 and WMP11 into your hot fix list before the updates to these. You need to have Boooggy's WMP11 Slipstreamer installed on your computer (see these forums). Be sure to always start with a clean copy of your files/folders, do all your work in one nLite session and integrate only one SP. Enjoy, John.

furballi, yep. Look in the folder C:\Program Files (x86)\nLite\Presets, and open the newest Preset (on your XP x64 system). Then attach that to the post. Thanks, John.

furballi, that Last Session.ini still says your are running nLite under a 32 bit Vista. Enjoy, John.

ricktendo64, thanks but I am hoping there is a method which will allow me to practice and experiment. It looks like to me that the bootin.ini gets created during install and it may not be possible to modify it directly. Hopefully, the ingredients are in some file I can modify at pre-install. Things like the partition would probably be left to the install process. Thanks again, John.

Can I modify boot.ini via nLite or another pre-install process? Thanks, John.

skytalk, please run the experiment I requested. I understand results may not be useful, but we will learn something. Also please post a screen shot of Windows Explorer view of the folder iaahci.inf. There are probably both text mode and regular drivers for SATA. Thanks, John.

toeagle5, to see the error, try tapping F8 during boot. You should get a screen with lots of options. Select the option to not automatically restart on error. When you do a reboot, the BSOD should stay on the screen so you can read it. Please post the Stop code and error description. Also please attach (not paste) your Last Session.ini. Makes sure you always start with a fresh copy of your CD files/folders, do all you work in one nLite session and integrate only one SP. Enjoy, John.

skytalk, please try it without any drivers added. It looks like to me you have set all the drivers as text mode drivers. Are there really that many? I suspect, at this time, that this is a false error. Make sure to always start with a fresh copy of your CD files/folders, do all you work in one nLite session and integrate only one SP. Also, in the future, please only attach your Last Session.ini. Let us know if it works with no drivers integrated. Enjoy, John.

phaolo, make sure you always start with a fresh copy of your CD files/folders, do all you work in one nLite session and integrate only one SP. Please let us know if you discover how the Printer Sharing disappeared. Thanks for the Services number meanings. Enjoy, John.

ulysse34, please attach (not paste) your Last Session.ini. Make sure you always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Enjoy, John.

furballi, If you want us to help, you need to give us some more detail, including your Last Session.ini. Enjoy, John.

freeheart4sale, don't know. Please attach (not paste) your Last Session.ini. Be sure to always start with a fresh copy of your CD files/folders, do all you work in one nLite session and integrate only one SP. Enjoy, John.

tcostin, please attach (not paste) your Last Session.ini. Be 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. You should place hot fixes to IE7 after IE7 in your hot fix list. How did you do it "at the same time"? All hot fixes should integrate except KB956391, which must be integrated later. You can use the RunOnce exit to do this - use switches /Passive /NoRestart to achieve a silent install. I don't know why your other one failed. Please post a screen shot of your error. Enjoy, John.

shaheen, ricktendo64 is correct, you need only the latest SP you want to integrate. If your CD has no SP, then you need only SP3. On a running system you do need to install SP1 before SP3. Be sure to always start with a fresh copy of your CD files/folders and do all you work in one nLite session. Please attach (no paste) your Last Session.ini. Enjoy, John.

furballi, I see you are running nLite under 32 bit Vista. This is probably not going to work. You can try running nLite in compatibility mode. Go to nLite.exe in where programs are in Vista (C:\Programs\nLite on my XP x64) and right click-select Properties-click Compatibility tab-check 'Run this program in compatibility.....' and select a mode that seems best, perhaps XP SP2. I don't have a Vista machine to look at now. If you don't slipstream an SP, it is possible it will work, but I suspect it will not - worth a try. Your best bet is to find a machine running XP x64. Enjoy, John.