End times prophetic insights, future impending dangers to the US, surviving to the last breath, do well live forever, will there be a new earth, world as we will know it then, conquering lack of faith and fear facing perilous horrendous things yet to be s
malfunctioning on boot-up
Published on May 13, 2005 By Hardryve the Paladin In Stardock Support General
This is my second attempt at using "BootSkin", unfortunate for me it did the same thing it did the last time which is:

BootSkin will boot up but if your using the logon program what takes place is after the bootskin loads...and your waiting for your login skin to boot-up it doesn't my PC's hardrive continues to run without ever getting to the Stardock's LogonStudio, logon screen.

NOTE:

Alternative Versions:
Some drivers and bios makers "break the rules" which can cause BootSkin to not work correctly. If you experience that, you can remove BootSkin by deleting \windows\system32\drivers\vidstub.sys. And then try one these alternative versions:
BootSkin 1.02
BootSkin 1.03


Now I have used the 1.05a - April 2004 version the first time so I thought I would try one of the alternative one's which this time was the 1.03 version. I noticed the warning above and the potential problems that some of the drivers and bios makers can cause so that BootSkin will not work correctly.

Now upon boot-up the program works perfectly, but after it's finished and next would come the logon screen my PC's hardrive gets stuck and continues to run until I have to shut it down manually. Now I would love to use these bootskins, but is there a work around or is this program not compatible with the Stardock's LogonStudio?

Just wondering why this continues to happen with my Operating System which is "Windows XP SP2". I have plenty of ram with a total of 768mb's of ram and enough free space on my hardrive so why is it no one else has this problem?

Comments
on May 13, 2005
or is this program not compatible with the Stardock's LogonStudio?


I run both bootskin and logonstudio with no problems. This is first time I have seen this problem. While waiting for someone who may have answer send an email to Stardock support.