system doesnt boot up

I'd need to imagine that using the recovery console would work out just fine.. Umm.. Let's see..

-Boot off of Windows 2000 CD (Might need to enable booting off of CD in BIOS)

-To repair a Windows 2000 installation, press R.

-To repair a Windows 2000 installation by using the recovery console, press C

-Don't forget to access the Recovery console you will need to Press R, and then C. You'll see.

This should fix you up. The recovery console will allow you to delete the BootSkin directory, but odds are that won't fix your problem. But, worth the initial effort.

If that don't work then just use the Repair function instead of Recovery console. I'm 99% sure that will resolve your issue if it is just a simple conflict.

If still having issues you could probably replace the NTOSKRNL.EXE that resides in your Windows System32 directory via the Recovery console... Could be the BootSkin corrupted that file, but no point in assuming the worse.

If nothing you do solves your problem consider the above and view this link as provided by Microsoft for instructions to replace system files via Recovery Console and replace that NTOSKRNL.EXE with the original one.Link

Wow, that's a mouthful. Damn 12 years experience with Windows installation, customization and repair. Any other Windows based questions you might have I'm always available for support.

Boot off a Windows CD and remove \windows\system32\drivers\vidstub.sys.

No, it's not a reinstall as far as i know, but i haven't had to do it so i can't explain it. i do know that when i bought my computer and was playing with it, there was an option to make a bootdisk. maybe Laoran will come back and see this and explain it. Since he also mentions booting off the cd in his first step. You might also bump your other thread on this and see if Nakor responds.

so you're saying when you first turn on your machine, when it does the count down (prior to booting up) pressing F8 doesn't work? From what I've read elsewhere, when the very first screen comes up, press F8 - sometimes repeatedly real fast.

so you're saying when you first turn on your machine, when it does the count down (prior to booting up) pressing F8 doesn't work? From what I've read elsewhere, when the very first screen comes up, press F8 - sometimes repeatedly real fast.

It appears he's able to access the boot options menu per his post.
As he states

i tried everything: running in safe mode, last known config, by dos prompt...

But doesn't matter. I doubt he'll have any problems Sir Bichur after using our methods above, good thing you mentioned the vidstub.sys file because I normally forget to. Between the recovery console, repairing the installation, replacing NTOSKRNL.EXE and replacing vidstub.sys suggestions, if that don't fix the issue then he will need to reinstall Windows entirely would be my guess from experience. Which reinstalling the OS always sucks but at least it's a good last resort option that will fix your issue for sure. Unless you have a hardware conflict of some type and need to replace something. Welcome to "fun with windows" 101.

So that is why my laptop didn't want to boot...thanks bichur.

good thing you mentioned the vidstub.sys file because I normally forget to.

I only mentioned it because Nakor brought it up in ghawar's earlier post. If you keep a watch (i got no computer skills, so I really can't help) keep in mind if ghawar posts through the stardock forums, you won't see the reply here, you'll have to go there: Link but at least our login from here works there

I only mentioned it because Nakor brought it up in ghawar's earlier post. If you keep a watch (i got no computer skills, so I really can't help) keep in mind if ghawar posts through the stardock forums, you won't see the reply here, you'll have to go there: Link but at least our login from here works there

You know, honestly Sir Bichur I have never even visited the Stardock forums. Perhaps, I'll have to check them out as well and see if I can lend a hand or two there as well sometimes.

Thanks for checking out the Stardock forums!!(Laoran)

Yeah, im having the same problems with Vista. Ive tried all of the things above but none work. It says the \Windows\System32\Drivers\vidstub.sys is corrupt or missing. Error code 0x0000229. Ive tried safe mode, last good config, and trying to repair it with the Vista CD.

And YES i do realize that it never said it was compatible with Vista but I didnt imagine that just installing the software would F*** it up that bad either.

Im fearing the biggest possibility that im going to have to reinstall Vista. So if anyone else has any recommendations please tell me.

You installed and ran Bootskins in Vista?

no, it would be more like installed and tried to run Bootskin in Vista

I don't think the Vista CD will repair since it's not a core Windows file

Have you tried booting into safe mode and deleting it?

I have the same problem - tried Bootskins in Vista without even thinking it wouldn't work. The machine won't come up in any mode - not even safe mode. AND, unfortunately this is a demo/test machine so I don't have access to the Windows/Recovery disks.

Any suggestions while I wait for the vendor to send me some?

If you can't even get into safe mode a format might be the only possibilty.

If you are somehow able to find your way into safe mode delete the vidstub.sys file out of the

c:\windows\system32\drivers

Boot process never got far enough to get to safe mode. I had to do a complete re-install from the Vista CD, and then reload all my drivers.

Brian, you are haveing a time of it aren't you.  :NOTSURE: 

I don't believe in doing anything half-way!  

  

I mean, I'm not the type to 'play it safe' when trying to get things to work. Being an MIS type, I'm used to making sure I break things first so I can do whatever I need to do to prevent them from breaking when I hand them off to users.

I understand now, someone who gets to break computers for a living.   

Exactly! And I've done it enough times that it doesn't bother me when it happens! If it doesn't break, I'm not trying hard enough.

There is a utility you can burn to a CD and boot off of called BartPE that lets you access your Windows filesystem and delete vidstub.sys

coolie - I'll track it down. I know myself well enough that I'll crash it again for sure.

Thank you!!!

The forums are the place to come with questions, someone will have the answer.   

If you get really jammed up please let us know at support@stardock.com. We like to pass everything on to the devs so that we can avoid troulbes whenever possible.

darn... add me to the club.
i hate it when i cant see if a program is going to work (or not) under certain versions of windows.
it would be nice if the programs actually consider the OS they are going to work on.

i love the stardock concept and even with this minor annoyance i will continue to use it but that bootskin sthingy gets ... the boot...real hard.

if you look for tools to remove the vidstub.sys (just go to %windows%\system32\drivers\ and delete it) you can go here for bootable NTFS toolsNTFS bootable recovery floppy (convert it to run from CD)

ofcourse you need to build it before you have problems (and test boot from CD/DVD before thinking it is OK) or.... you need another computer... but that would be obvious LOL)

Take care and have fun

This is the most interesting thread and came up #1 in a Google search. I installed Bootskin, selected one that comes with it then powered down. Later I powered on and my startup would not continue. I got the very same message : "\Windows\System32\Drivers\vidstub.sys is corrupt or missing. Error code 0x0000229."

Everyone suggests deleting vidstub. sys but what is that driver? Will Bootskin fail without it. I'm guessing it is not a Microsoft file?

I just hate deleting something before knowing what it controls.

My version of Vista is Home Premium and I have not installed SP1 yet.