runonce

mmarable, You can throw the custom winntbbu.exe file in the system32 folder (for your unattended install) and use the winnt32.exe file to check and see what it will look like full screen. You will not get the progress bar or windows XP information but you can see how most of your customizations will look and if it is not compatible you will get an error message. This will save you from having to run and install to see what your custom winntbbu will look like.

Eagle00789, I get it it now thanks so much.

Eagle, I don't understand. Sorry. Adding to the DB works great now. Thanks.

Sesshoumaru, I am having the same problem. The SP2 ntoskrnl.exe has been changed and it effects the color palet causing the nasty color of the boot screen you discribed. I had use BootEditor, which was was easy and worked great, but it does not work with the SP2 ntoskrnl. There has been some instructions on this site and others regarding using a HEX editor to change the values that are causing the problem but I have had no luck doing this. Info on editing XP SP2 boot screen Boot screens on WindowsXP SP2, Palette color correction Edit the Boot Logo & Boot Logo Palette in Windows XP Hopefully, someone will come up with a remedy to easily change the XP2 boot screen once they have had a chance to play with it for awhile. It would be great if BootEditor could be adjusted to work with the SP2 ntoskrnl but I do not think it is being supported any longer. Good Luck

Eagle, "Is it possible to add other Program Paths to the drop down menu?", you mean, add your own paths?? (Yes!) when I use Edit/Add to Database I get an error message tblPrograms:Cannot modigy a read only dataset. Is there a way for the user to add additional program info to this program." this should be solved in 2111. (I am still getting this error with 2111.) is there a way to add registry commands for the app being installed to the RunOnceEx though this Program" Waht do you mean with that?? (What I was taking about is the command in line 3 below. Will the program enter the REGEDIT/S parameter or is that line for the reg tweak something we will have to add to the RunOnceEx bat file after your programs makes the application program entrys only.) REG ADD %KEY%\010 /VE /D "Alcohol 120" /f REG ADD %KEY%\010 /V 1 /D "%systemdrive%\install\alcohol\setup.exe /qn" /f REG ADD %KEY%\010 /V 2 /D "REGEDIT /S %systemdrive%\install\alcohol\register.reg" /f Thanks for all your hard work. This is an excellent app.

Eagle, Just installed 2111. When I use the Database Update feature it sticks on the update sceen where it says Determinig the Update Possibilities. It notes my version but not the online version and the cancel button is not accessible.

eagle, Just started playing with this prog, very cool. I have a few questions: Is it possible to add other Program Paths to the drop down menu? Also, when I use Edit/Add to Database I get an error message tblPrograms:Cannot modigy a read only dataset. Is there a way for the user to add additional program info to this program. Lastly, is there a way to add registry commands for the app being installed to the RunOnceEx though this Program Great Prog. Thanks

Here are two of my Setup Screens. Let me know what you think. If anyone is interested in them let me know and I will be happy to send them to you.

I placed mine in the $oem$/$1/Install folder. It doesn't matter that much where you place it as long as you call it from the correct location in your winnt.sif file in the guirunonce section. I place all my batches in the same directory, except for my cleanup batch.

Custom Boot Screen SUCCESS Thanks to all for your help. I solved the problem by using my own kernal and Boot Editor to insert a new main bmp and remove the Pro overlay. It then worked its magic and wala a functional custom boot screen in my Unattended install CD. How Sweet It Is :excited: :beer: Thanks again go out to everyone for all the guides and help.

My unattaned install worked fine until I attempted to use the custom Boot Screen.My Unattended Install consists of an Slipstreamed SP1A into my original XP Pro. therefore I assumed I should use the SP1 ntoskrnl.exe. Last night I used Resource Hacker to check the original ntoskrnl.exe in my Unattended install and it indicates it is File/Prod #: 5.1.2600.1151, which I though is the Non SP1 Boot Screen. Instead of using the SP1 ntoskrnl.exe should I be using the non SP1 ntoskrnl.exe. (Added: I tried usng the non Sp1 boot screen and it put me in a reboot loop after the boot screen appeared.) How do I determine if I am using a Mlti Processor kernal? Thanks

Using the directions in this thread I installed a SP1 Boot screen I obtained from ThemeXP. The install using VPC goes well and the custom Boot Screen is present after the restart but after the desktop loads the OS shuts down and restarts. This continues after each time the system restarts. I used two different premade ntoskrnl.exe files from ThemeXP and renamed them accordingly with the same results. I used the following code in my BootLog.cmd file bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1 bootcfg /Timeout 0 Any ideas what I may be doing wrong.

Geckotek, I thought so, but I just wanted to make sure. Thanks for the correction as well.

b0r3d, In your guide to creat a custom Boot Screen you mention making a BootLogo.cmd containing the following: bootcfg /RAW /A / Kernel=OEMKrnl.exe /ID 1 bootcfg /Timeout 0 and calling it from GuiRunOnce. [GUIRunOnce] bootlogo.cmd Can you tell me where I should place the Bootlog.cmd file, and in GuiRunOnce when the BootLogo.cmd is call do I have to indicate a location such as %systemdrive%/install/bootlogo.cmd so it knows where I placed the bootlogo.cmd file??? Great help guide. Thanks