solidsnake001 solidsnake001

BOOTSKIN PROBLEM? PLZ HELP!

BOOTSKIN PROBLEM? PLZ HELP!

Okay, well I got the bootskin program installed than I go find a bootskin and when I do I download it, and than I double clikc the file and it adds the skin to the list. Okay here comes the problem, when I restart my computer, everything seems to be working but while it goes into the loading boot screen, the computer restart and now I get a messege saying windows did now start correctly, so from the list I choose safe mode and I thought the problem was the bootskin so I uninstall it and than restat my computer and now it is the default windows boot screen. I have downloaded the alternative bootskin downloads 1.02 and 1.03 but still it doesn't work. If anyone knows the problem help plz! Thanks!
8,619 views 42 replies
Reply #27 Top
well i reinstalled BS, loaded my favorite skin from my arcives and did a reboot...

she got to the time when the screen starts...

blinked twice...

loaded the default windows boot screen and continued to load as normal. i guess thats an improvement, i didn't get the choices menu or it knew i would choose last known good gonfig. and went on it's merry way.

i love this BS program... (couldn't resist that)
Reply #28 Top
i just had a thought, service pack 2 changed the boot screen to one that looks like XP PRO with out the product name. someone should check to see the diference and adjust the program acordingly.
Reply #29 Top
someone should check to see the diference and adjust the program acordingly.

Y can't u?
Reply #31 Top
is anyone working on this or has it been swept under the carpet... again..


From above
Maybe is about time to take Bootskin off the back burner.


No current development.
Reply #32 Top
it's to bad, this problem. I have it to. reinstall and everything didn't work. Hope there comes a fix some day.
Reply #34 Top
i realy think they don't care


Not true, the problem is the BIOS tweaks that DEll, Gateway, MDG (in Canada ) etc do when build the system. To make it work for everyone would need everyone to use same BIOS or tweak Bootskin to work with many different BIOS.
Reply #36 Top
then why did it work before service pack 2 and not after when my bios haven't changed in the three years i have had this computer?


There are problems with some chipset video drivers that are shown up with BootSkin. Some only occur with SP2. This is probably not the fault of BootSkin


i have upgraded my video card sence then. i'll try it and let you know


Since there is no current development for Bootskin video chipset upgrade plus SP2 may be your issue.
Reply #37 Top
Cavan1 do you work at stardock?


i hacked the windows boot screen and changed it, just to bad i can't share any of the details, or the screen
Reply #38 Top
Cavan1 do you work at stardock?


No, why ?
Reply #39 Top
i hacked the windows boot screen and changed it, just to bad i can't share any of the details, or the screen


No, why ?


Maybe that's why...?
Reply #40 Top
i was just wondering if your comments ment anythiing, and you gave me the answer i thought was true. and i don't care who knows that i hacked my boot screen i highlighted it for it to be noticed
Reply #41 Top
The strange thing is that I set up my computer again two days ago and even Bootskin worked properly before, Windows XP won't boot with it any more now.

Before re-installing my system, I had Service Pack 2 installed and I have that now, too. The Bios must be the same and there is no change I can think of in comparison to before. What could be the reason that Bootskin worked before, but not any more now? (I used version 1.05a both times.)
Reply #42 Top
Apologies for the bump...

I've got the same problems with BootSkin. v1.05a caused a STOP error, 1.03 and 1.02 froze at a black screen. Bootskin used was XP + Firefox skin (the one with the personified OS characters) and I'm using WinXP SP2. Mobo is Biostar M7VIT Pro and video card is TNT2. Sadly, I think it's a SP2 problem because 1.05a worked when I used Win2K SP4 + Update Rollup 1, though gave me STOP errors when I tried to boot with my JumpDrive inserted into a USB port.

I hope that if any futher work is done I've given enough info to be helpful. I'd much rather not touch my ntoskrnl.exe file if at all possible...