Chkdsk Error

Ever since installing bootskin and flyakite osx i have had CHKDSK refuse to show any data while it is running, i have removed bootskin and its registry entries after un-install and decided to run CHKDSK on next reboot on C: so pc restarts as normal, i enter boot password and the almighty apple screen appears, it dissapears and the HDD's ACCESS light constanty stays on and the monitor is blank, it is on, just no picture, graphics card cable is in correctly, and CHKDSK is running because if i set it to start, and keep hitting escape, it would exit as normal and windows would boot, people have said to me to edit the .ini file (bootloader) and remove /noguiboot /bootlogo, but THEY ARENT EVEN THERE! (i assume this is because bootskin is no longer installed)

Please help! i would like to see whats happening with chkdsk as my MFT has a error in BITMAP section.

Error given to me in cmd with chkdsk is below

CHKDSK Discovered free space marked as allocated in the volume BITMAP.

Windows Found problems with the file system.

Run CHKDSK with the /F switch to fix these errors.

and as i said, i did this, system needed to reboot cos drive was IN USE and then when chkdsk was running, screen is BLANK!

HELP PLEASE! DONT WANNA HAVE TO WIPE OS! DONT HAVE ANOTHER HDD TO BACKUP NEEDED WORK FILES!

EDIT: Problem was solved! I had to uninstall flyakite osx (yes, everything) and then reboot, and reinstall BUT without installing the osx boot screen (apple logo) and now chkdsk runs with me being able to see whats going on

#528763

BTW I had same problem but with "easier" solution: just let chkdsk run without you beeing able to see what it does. Whenever the Windows login screen finally appears, it means chkdsk has done all the job.

Another option is to edit boot ini file, and remove the /kernel kernel_name switch. This is with BootSkin or similar ones, I recall Flyakite let's you decide to use that or the boot.bmp technique, but I'm not sure.

#528781

BTW I had same problem but with "easier" solution: just let chkdsk run without you beeing able to see what it does. Whenever the Windows login screen finally appears, it means chkdsk has done all the job.

Another option is to edit boot ini file, and remove the /kernel kernel_name switch. This is with BootSkin or similar ones, I recall Flyakite let's you decide to use that or the boot.bmp technique, but I'm not sure.

Ah well I still got a problem now...

CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows found problems with the file system.

Run CHKDSK with the /F (fix) option to correct these.

Help? I,ve ran CHKDSK at startup 5 times now :'(

#528782

Mmm... try going the UI way instead:

Go to "My computer" folder, right click the hard disk, click Properties, click Tools, click "Check now" under error checking (the section with Scandisk icon) check/enable all options and click Start. It will tell you it needs to reboot. Let it do so.

After reboot your file system should be clean and working just fine.

Do you have any other operative system installed? More exactly I mean Linux / *BSD / Mac OS X with ntfs-3g driver? maybe FreeDOS with NTFS with write access enabled?

#528784

Mmm... try going the UI way instead:
Go to "My computer" folder, right click the hard disk, click Properties, click Tools, click "Check now" under error checking (the section with Scandisk icon) check/enable all options and click Start. It will tell you it needs to reboot. Let it do so.
After reboot your file system should be clean and working just fine.
Do you have any other operative system installed? More exactly I mean Linux / *BSD / Mac OS X with ntfs-3g driver? maybe FreeDOS with NTFS with write access enabled?

I have windows XP with flyakite osx installed, no other OS's present, im thinkin the FS (file system) error has come from where vista used a secret partition we removed (vista was the OS installed when we got pc, secret partition contained drivers, etc)

#528785