S
Steve Goodman
Thanks to Windows Media Player 9's incomplete set of codecs, I had a
complete set of installables handy. I'd installed them on my own Win 2000
machine, and when my wife encountered an 'unknown codec' issue, I installed
them onto her machine. At the end of the Indeo codec install, however, I
noted an error not being able to complete the install, saying that the
target file was corrupt. Okay fine, before rebooting I scheduled a CHKDSK/F
to occur (via the "do you want to schedule" response it gives), and
restarted the machine.
At that point, the PC failed to get to the F8 screen (ah, so reminiscent of
OS/2!) and just locked altogether. Repeated boots bring the same
non-result. Having made an ERD for both our PCs after the install of SP4, I
whipped it out and attempted to do a Repair via Fast option, after rebooting
yet again, with the CD present. Since my wife's boot drive is an ATA-100 I
had the diskette handy with the drivers for it - Win 2000's base install
doesn't recognize Promise (at least!) ATA-100 drives unless one has that
diskette ready with the F6/S stuff at the beginning of setup. Needless to
say this is the LAST time I use an ATA-100 drive for a boot device! It just
seems like SCSI with bad makeup on.
The Setup disk check went on, apparently taking some time between 25-26%,
then going on until it hit 96%, and at that point I got the prompt:
Setup cannot copy the file: speech.dll
To retry, press ENTER.
If you are installing from a CD, make sure the
Windows 2000 CD is in the CD-ROM drive.
I guess I don't need to tell you that hitting Enter brought nothing but the
above error message back. It apparently didn't find speech.dll on the CD,
and besides cancelling Setup, the only option was to Skip the file with Esc.
Thinking, "What the heck is speech.dll for anyway?" I decided to Skip. Next
I got the same "cannot copy the file" message over and over, and had to
choose Skip File with Esc (no alternative in sight), with the following
files:
spchtel.dll
vcmd.exe
vcauto.tlb
vtxauto.tlb
vcmshl.dll
speech.hlp
speech.cnt
Xlisten.dll
Xvoice.dll
Xcommand.dll
Vdict.dll
VText.dll
XTel.dll
WrapSAPI.dll
mstask.ini
It would appear that the majority of these items above are somehow
voice-command related. There's nothing like ViaVoice or any of that stuff
on this system, and none of the codecs installed had anything to do with
voice recognition, to say the least.
Setup cannot restore the registry. The Emergency Repair disk or the hard
disk containing Windows 2000 may be damaged. Press ENTER to continue the
repair process.
When rebooting is performed after pressing Enter, the system goes through
what looks like regular bootup, until it gets to the "press any key to boot
from CD", whereupon it jumps right to the F8 screen briefly, and then the
following causes a screen scroll-up, printing to screen through the existing
text and baseline:
Windows 2000 could not start because the following file is missing or
corrupt:
\WINNT\SYSTEM32\CONFIG\SYSTEMced startup options for Windows 2000, press F8.
You can attempt to repair this file by starting Windows 2000
Setup using the original Setup floppy disk or CD-ROM.
Select 'r' at the first screen to start repair.
I don't need to tell you that the 'ced startup options...' stuff was there
before the error message popped up.
I found the sole reference to the above error message on the KB, which was
quite helpful in creating a kind of boot disk - but of course once the boot
disk goes past its own Starting Windows 2000 screen, it comes up with the
same error message about \WINNT\SYSTEM32\CONFIG\SYSTEM - and so I tried
booting off CD again, to attempt a Console repair session. CHKDSK/P had to
be used, as /F isn't an option. No errors apparently. I CHDIR'ed down to
find there IS NO SYSTEM folder/directory under \WINNT\SYSTEM32\CONFIG - so
what's up with that? Bootup brought the same error as above. I have no
desire to run setup from scratch, as it destroys all settings - most likely
including anything installed into and under the \WINNT directory. That's
pretty stupid if you ask me.
The last item on the file list above, mstask.ini, troubles me immensely. I
can't find any references to THAT on the KB either. Of course there's no
registry tool I can find to run in a Console session, unless I'm just
missing it.
I'd appreciate hearing suggestions as to how to bring this one back from the
undead. Halloween's too far away. Thanks in advance.
complete set of installables handy. I'd installed them on my own Win 2000
machine, and when my wife encountered an 'unknown codec' issue, I installed
them onto her machine. At the end of the Indeo codec install, however, I
noted an error not being able to complete the install, saying that the
target file was corrupt. Okay fine, before rebooting I scheduled a CHKDSK/F
to occur (via the "do you want to schedule" response it gives), and
restarted the machine.
At that point, the PC failed to get to the F8 screen (ah, so reminiscent of
OS/2!) and just locked altogether. Repeated boots bring the same
non-result. Having made an ERD for both our PCs after the install of SP4, I
whipped it out and attempted to do a Repair via Fast option, after rebooting
yet again, with the CD present. Since my wife's boot drive is an ATA-100 I
had the diskette handy with the drivers for it - Win 2000's base install
doesn't recognize Promise (at least!) ATA-100 drives unless one has that
diskette ready with the F6/S stuff at the beginning of setup. Needless to
say this is the LAST time I use an ATA-100 drive for a boot device! It just
seems like SCSI with bad makeup on.
The Setup disk check went on, apparently taking some time between 25-26%,
then going on until it hit 96%, and at that point I got the prompt:
Setup cannot copy the file: speech.dll
To retry, press ENTER.
If you are installing from a CD, make sure the
Windows 2000 CD is in the CD-ROM drive.
I guess I don't need to tell you that hitting Enter brought nothing but the
above error message back. It apparently didn't find speech.dll on the CD,
and besides cancelling Setup, the only option was to Skip the file with Esc.
Thinking, "What the heck is speech.dll for anyway?" I decided to Skip. Next
I got the same "cannot copy the file" message over and over, and had to
choose Skip File with Esc (no alternative in sight), with the following
files:
spchtel.dll
vcmd.exe
vcauto.tlb
vtxauto.tlb
vcmshl.dll
speech.hlp
speech.cnt
Xlisten.dll
Xvoice.dll
Xcommand.dll
Vdict.dll
VText.dll
XTel.dll
WrapSAPI.dll
mstask.ini
It would appear that the majority of these items above are somehow
voice-command related. There's nothing like ViaVoice or any of that stuff
on this system, and none of the codecs installed had anything to do with
voice recognition, to say the least.
Setup cannot restore the registry. The Emergency Repair disk or the hard
disk containing Windows 2000 may be damaged. Press ENTER to continue the
repair process.
When rebooting is performed after pressing Enter, the system goes through
what looks like regular bootup, until it gets to the "press any key to boot
from CD", whereupon it jumps right to the F8 screen briefly, and then the
following causes a screen scroll-up, printing to screen through the existing
text and baseline:
Windows 2000 could not start because the following file is missing or
corrupt:
\WINNT\SYSTEM32\CONFIG\SYSTEMced startup options for Windows 2000, press F8.
You can attempt to repair this file by starting Windows 2000
Setup using the original Setup floppy disk or CD-ROM.
Select 'r' at the first screen to start repair.
I don't need to tell you that the 'ced startup options...' stuff was there
before the error message popped up.
I found the sole reference to the above error message on the KB, which was
quite helpful in creating a kind of boot disk - but of course once the boot
disk goes past its own Starting Windows 2000 screen, it comes up with the
same error message about \WINNT\SYSTEM32\CONFIG\SYSTEM - and so I tried
booting off CD again, to attempt a Console repair session. CHKDSK/P had to
be used, as /F isn't an option. No errors apparently. I CHDIR'ed down to
find there IS NO SYSTEM folder/directory under \WINNT\SYSTEM32\CONFIG - so
what's up with that? Bootup brought the same error as above. I have no
desire to run setup from scratch, as it destroys all settings - most likely
including anything installed into and under the \WINNT directory. That's
pretty stupid if you ask me.
The last item on the file list above, mstask.ini, troubles me immensely. I
can't find any references to THAT on the KB either. Of course there's no
registry tool I can find to run in a Console session, unless I'm just
missing it.
I'd appreciate hearing suggestions as to how to bring this one back from the
undead. Halloween's too far away. Thanks in advance.