-= Mancubus =- Posted June 23, 2005 Share Posted June 23, 2005 i have been using this program for a very long time.And i dont have any problems with it.I am running Windows XP w/ Service Pack 2 + 40 of the latest Hotfixes.<{POST_SNAPBACK}>Ok, maybe these were the problems of our exact Windows installations.A quiestion - any way to apply it with the chosen logo unattended? Link to comment Share on other sites More sharing options...
Lost Soul Posted June 27, 2005 Share Posted June 27, 2005 if this is safer then stylexp ill give it a shot ... nice Link to comment Share on other sites More sharing options...
Lost Soul Posted June 28, 2005 Share Posted June 28, 2005 @Astalavistaive installed this program,, the logon studio and the iconpackerim not sure what one of these 3 programs is doing it yet,,but after wpi finishes,, the wincustomize folder pops up that hold the shortcuts for these programs ..any ideals ? does this happen for anybody else ? Link to comment Share on other sites More sharing options...
Thauzar Posted July 30, 2005 Share Posted July 30, 2005 Could there be a little more informations about how to modify this code to fit for any custom bootscreen of our choice? I'm not familiar with WPI nor registries but I guess if I knew what to change I could adapt if for numerous different bootscreens.In fact, here is my real question: how to easily integrate a bootskin custom bootscreen in an unattended CD? This is what I really want to know.Thanks Link to comment Share on other sites More sharing options...
Guest axlemode Posted December 26, 2006 Share Posted December 26, 2006 (edited) @mancubusUnlike other programs that can change the Windows XP boot screens, BootSkin does so in a safe manner. It doesn't patch the Windows XP kernel.Yeah, that's sounds very interesting...Until you encounter with an unability to boot after applying some fresh-new-downloaded cool bootskin. ohmy.gifIt is cured with booting in safe mode and turning back to default boot logo.That happened with me and a lot of people, as I read in forums. sad.gifIt seems, that this tool's got a problem with SP2 (or even SP1), and there wasn't new version for a looooong time. no.giSo, try it with a caution.whistling.gifyou think you knew everything.first, bootskin doesnt patch ntoskrnlsecond, it uses vidstub.sys to load the bootscreen before ntoskrnl loads as a servicethird, if the files are deleted e.g. vidstub.sys or the bootskin.ini is deleted, the vidstub.sys will close thus letting the ntoskrnl show on sturtup.heres a visual\read first before freaking out Edited December 26, 2006 by axlemode Link to comment Share on other sites More sharing options...
S0mE0nesMiNd1 Posted December 26, 2006 Share Posted December 26, 2006 (edited) You registered and bumped a 2 year old post from a banned user to insult someone? Hmmmm Edited December 26, 2006 by S0mE0nesMiNd1 Link to comment Share on other sites More sharing options...
-= Mancubus =- Posted January 5, 2007 Share Posted January 5, 2007 you think you knew everything.first, bootskin doesnt patch ntoskrnlsecond, it uses vidstub.sys to load the bootscreen before ntoskrnl loads as a servicethird, if the files are deleted e.g. vidstub.sys or the bootskin.ini is deleted, the vidstub.sys will close thus letting the ntoskrnl show on sturtup.Where did you see that I told it DOES patch?I know that it doesn't.I warned people because I and my friends REALLY experienced problems after applying some of the bootscreens (not every one, actually). And since this forum filled with, let's say so, not very experienced in recovering windows people, I felt it would worth to warn about it. Link to comment Share on other sites More sharing options...
wan Posted January 5, 2007 Share Posted January 5, 2007 you think you knew everything.first, bootskin doesnt patch ntoskrnlsecond, it uses vidstub.sys to load the bootscreen before ntoskrnl loads as a servicethird, if the files are deleted e.g. vidstub.sys or the bootskin.ini is deleted, the vidstub.sys will close thus letting the ntoskrnl show on sturtup.Where did you see that I told it DOES patch?I know that it doesn't.I warned people because I and my friends REALLY experienced problems after applying some of the bootscreens (not every one, actually). And since this forum filled with, let's say so, not very experienced in recovering windows people, I felt it would worth to warn about it.once to me but after long time of applying some of the boot screen. It not destroyed my window , i just choosed the good setting before the problem occured.. and then i was able to boot and enter my window and after that i was unabled to use the bootscreen again until i install a refresh window again. dont know why. Link to comment Share on other sites More sharing options...
Wesmosis Posted March 27, 2007 Share Posted March 27, 2007 (edited) nice tutorial and nice proggy!but plz, how to apply one of the .bootscreen files unattendedly?I tried but didn't work Edited March 27, 2007 by Wesmosis Link to comment Share on other sites More sharing options...
Wesmosis Posted March 27, 2007 Share Posted March 27, 2007 guyz, what is the final solution for applying your favorite bootskin unattendedly? Link to comment Share on other sites More sharing options...
Wesmosis Posted March 27, 2007 Share Posted March 27, 2007 i tried the the and found the answerand what is the solution dude?! Link to comment Share on other sites More sharing options...
sp00f Posted April 2, 2007 Share Posted April 2, 2007 i tried the the and found the answerand what is the solution dude?!Good question, i was looking for this to Link to comment Share on other sites More sharing options...
TheeBeets Posted September 15, 2007 Share Posted September 15, 2007 I am by no means an expert here but but I think I may have figured it out so here we go!!The process seems quite simple install Bootskin unattendedly and in RunOnceEx run two commandsThe whole process is run with a bootskin.ini file which looks like this[bootSkin]Type=0Name="SpaceXP"Author="aLtgLasS"Description="based on the Wallpaper from Microsoft Plus!"Progressbar=pbar.bmpProgressBarX=258ProgressBarY=353ProgressBarWidth=120Screen=SpaceXP.bmpStep 1"%systemdrive%\Install\Applications\BootSkin\BootSkin105.exe" /fStep 2"%systemdrive%\Install\Applications\spacexp.exe(Winrar SFX Archive extracting bootscreen to "C:\Program Files\Stardock\WinCustomize\BootSkin\skins"Step 3SpaceXp.reg adds this to your registry and hopefully the screen will appearWindows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BootScreen\Parameters]"Enabled"=dword:00000001"DirtyBoot"=dword:00000000"Migrated"=dword:00000001"INIPath"="C:\\Program Files\\Stardock\\WinCustomize\\BootSkin\\Skins\\spacexp\\BootSkin.ini" Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now