Help!

How do I stop my main XP Pro workstation from continuing its endless Chkdsk
H: /f (clean results) Chkdsk C: (clean results) -> auto-reboot cycle

The cycle began with actual corrupton on both volumes (I blame BitTorrent
for causing/exacerbating this corruption).
I scheduled a boot-time chkdsk /f for both C: and H: volumes (with a full
surface check).
Thr first time through, it did fix quite a number of issues on each.
WHen it was done with C: (the second drive it did), it auto-rebooted, and
rolled right back into the chkdsk process again.
Now, the workstation is stuck in this boot-chkdsk-boot-chkdsk-boot... loop.

Is there an out short of creating some sort of arcane Windows pre-install
boot-up CD to let me back into my workstation/registry?
These chkdsk's seem to launch so early in the boot process that there are
none of the usual boot-time options seem to be presented to me.

any ideas welcome.

Hello,

Registry damaged? See http://support.microsoft.com/kb/316506

Regards,
Singapore Computer Home Repair Service
http://www.bootstrike.com/ComputerService/
Video Conversion VHS Video8 Hi8 Digital8 MiniDv MicroMv
http://www.bootstrike.com/VHSVideoConvert/
"MarkB_GrndP" <mburns_08109> wrote in message
news:4901
[..]

Singapore,

Sorry - the info in that KB article (nor in any of the others linked to it)
does not help.
There is currently not any means of gaining any control of the computer at
this point.
My only options during boot-up are upon hitting F8, to make any of the
alternate boot-up selections, but they *ALL* get hung up by falling back into
the Chkdsk/f process ...which ends in a spontaneous reboot immediately
following the successful, error-free time-consuimg 5(6 actually)-pass
chkdsk/f-ing of C:.
Trust me, I've tried all the options (safe mode -command prompt seemed to
hang up after loading the drivers list, but the HDD activity lights seemed to
refelct that the chkdsk was still happening, just not displaying).

I have constructed a BartPE disk in an attempt to gain enough control of the
system to hack the registry erntries which are controlling the autoChk's
Chkdsk/f settings and stop them from running.

Why the successful completion of a chkdsk/f that fixed problems, and several
subsequent passes with no errors/fixes have not successfully reset these
registry entries as they are supposed to - is another question to be explored
after I finally do regain control of the workstation.

- GrandPaMark (Ye Olde IT Geezer)

"Singapore Computer Service" wrote:
[..]