Windows "Registry Configuration Error"

"PCR" wrote in message ...
"Darren Harris" wrote in message
om...
| "PCR" wrote in message
...
| That is not a good sign, that BIOS won't hold a setting. Are you
sure
| you are clicking "Save settings & Exit"? Is it only Boot Order that
| won't hold? Considering those warnings of Jeff Richards in my prior
post
| (which others have said as well), it might be best to solve that
BIOS
| problem before writing to the hard drive. What are it's settings
| regarding the hard drive? Does the clock seem to be set properly in
| DOS...?...
|
| DOS? When I hear DOS, my mind goes blank. It seems

Seems?

| that nothing in
| BIOS can be changed without it going back to what it was when the PC
| re-boots.'
|
| I think I figured out the BIOS, but changing the boot sequence
| affected nothing.

That could mean two things: (1) You could not change it, or (2) You did
change it, but still got the same error message.

I do not find your language to be precise... "seems" & "affected
nothing".

I don't understand what that meant. Nevertheless, I figured out how to
change the boot sequence, but it has had no affect at all on my
problems.("Affected nothing").

| I still get the "Invalid System Disk" message and
| nothing further than that. The hard drives are set to "AUTO".

I would think "AUTO" is fine. I suppose "AUTO" would give you the best
possible setting. What are the other choices besides AUTO?

I'm not even going to go through the trouble of hookinghe system
anymore.

| (1) Boot to Command Prompt Only, by holding CTRL as you boot to get
the
| Startup Menu, if it isn't already enabled at "START, Run, MSConfig,
| Advanced button".
| (2) Enter "TIME", no quotes. (Then, ENTER, to exit w/o changing.)
| (3) Turn off the computer.
|
| Was the time wrong in DOS?.. Better replace the CMOS battery, then.
|
|
| C:\time/?
| Displays or sets the system time.
|
| TIME [time]
|
| Type TIME with no parameters to display the current time setting and
a
| prompt for a new one. Press ENTER to keep the same time.
|
| C:\time
| Current time is 6:54:27.68p
| Enter new time:
|
| I had already replaced the CMOS battery recently. The PC had
| deteriorated to the point that All I'd get was a black screen when I
| powered up. But after the battery change, I'm back to all the other
| garbage I'm going through. Anyway, I reset the clock and it seems to
| keep in CMOS.

Seems? Anyhow, if the clock holds it's time at a DOS screen, then I must
think CMOS is getting power enough to hold ALL it's settings. Is it, or
isn't it?

When I said that the clock "seems to keep in CMOS", that meant that
after I set the clock, and rebooted the time was still correct.(That
of course doesn't mean ituld be correct a week from then).

| I loaded BIOS defaults in CMOS, and I see no changes.(Except that I
| now have a 464 processor instead of a 450).

Do you see a change or don't you? Anyhow, I don't know what to make of
464 vrs. 450. My BIOS has no such thing.

I said that "I see no changes". *Except* for the processor which is
listed as a 464mhz now instead of 450mhz.

| When I attempt to boot to Command Prompt Only, by holding down CTRL.
| when I power on,I get the Memory count-up, BIOS version screen, drives
| shown, and then it's back to the "Invalid System Disk" message. :-(

Well, a possible fix is "SYS C:", as in my first post. There are
warnings in it. I think, as BIOS is set to Auto & as you get a DIR
listing, very probably it is worth a try. If you decide to try it, do so
in that portion of this thread.

I'll skip it. There is too much to read about and learn(again), and
I've sp far wasted at least 50 man-hours on this for nothing.

| I have another motherboard. Perhaps I should try the rest of the
| hardware with it. It'll be a pain because I have a hard enough time
| trying to figure out where each wire goes in the system the way it
| is.(Sigh).

If you change MB's, you will need to worry over VMM32.vxd, which is
monolithic file containing low-level drivers.

So I guess it's time to throw the PC in the trash and try get the info
off of one of the drives("C") some other way.

Thanks.

Darren Harris
Staten Island, New York.

"Darren Harris" wrote in message
om...
| "PCR" wrote in message
...
| "Darren Harris" wrote in message
| om...
| | "PCR" wrote in message
| ...
| | That is not a good sign, that BIOS won't hold a setting. Are you
| sure
| | you are clicking "Save settings & Exit"? Is it only Boot Order
that
| | won't hold? Considering those warnings of Jeff Richards in my
prior
| post
| | (which others have said as well), it might be best to solve that
| BIOS
| | problem before writing to the hard drive. What are it's settings
| | regarding the hard drive? Does the clock seem to be set properly
in
| | DOS...?...
| |
| | DOS? When I hear DOS, my mind goes blank. It seems
|
| Seems?
|
| | that nothing in
| | BIOS can be changed without it going back to what it was when the
PC
| | re-boots.'
| |
| | I think I figured out the BIOS, but changing the boot sequence
| | affected nothing.
|
| That could mean two things: (1) You could not change it, or (2) You
did
| change it, but still got the same error message.
|
| I do not find your language to be precise... "seems" & "affected
| nothing".
|
| I don't understand what that meant. Nevertheless, I figured out how to
| change the boot sequence, but it has had no affect at all on my
| problems.("Affected nothing").

Huh? I thought surely you had perished, possibly of XP-poisoning. OK,
fine, your boot order is fine, then! I can't recall what the original
problem is, though.

|
| | I still get the "Invalid System Disk" message and
| | nothing further than that. The hard drives are set to "AUTO".

Ah! OK, that's it, the problem.

|
| I would think "AUTO" is fine. I suppose "AUTO" would give you the
best
| possible setting. What are the other choices besides AUTO?
|
| I'm not even going to go through the trouble of hookinghe system
| anymore.

Well, AUTO should be fine.

|
| | (1) Boot to Command Prompt Only, by holding CTRL as you boot to
get
| the
| | Startup Menu, if it isn't already enabled at "START, Run,
MSConfig,
| | Advanced button".
| | (2) Enter "TIME", no quotes. (Then, ENTER, to exit w/o
changing.)
| | (3) Turn off the computer.
| |
| | Was the time wrong in DOS?.. Better replace the CMOS battery,
then.
| |
| |
| | C:\time/?
| | Displays or sets the system time.
| |
| | TIME [time]
| |
| | Type TIME with no parameters to display the current time setting
and
| a
| | prompt for a new one. Press ENTER to keep the same time.
| |
| | C:\time
| | Current time is 6:54:27.68p
| | Enter new time:
| |
| | I had already replaced the CMOS battery recently. The PC had
| | deteriorated to the point that All I'd get was a black screen when
I
| | powered up. But after the battery change, I'm back to all the
other
| | garbage I'm going through. Anyway, I reset the clock and it seems
to
| | keep in CMOS.
|
| Seems? Anyhow, if the clock holds it's time at a DOS screen, then I
must
| think CMOS is getting power enough to hold ALL it's settings. Is it,
or
| isn't it?
|
| When I said that the clock "seems to keep in CMOS", that meant that
| after I set the clock, and rebooted the time was still correct.(That
| of course doesn't mean ituld be correct a week from then).

If the battery were bad, a reboot would lose the time setting. Best to
look at it at DOS, though, as something in the Startup Group of Windows
might kill the setting. If it goes bad after sitting in Windows a while,
then something in Windows is doing it. The CMOS battery only controls
time when the computer is off (or is in DOS, I guess). Once Windows is
started, Windows or something in the Startup Group is doing it.

You have proven the CMOS battery is good. Also, the AUTO setting should
be fine, AFAI can think.

|
| | I loaded BIOS defaults in CMOS, and I see no changes.(Except that
I
| | now have a 464 processor instead of a 450).
|
| Do you see a change or don't you? Anyhow, I don't know what to make
of
| 464 vrs. 450. My BIOS has no such thing.
|
| I said that "I see no changes". *Except* for the processor which is
| listed as a 464mhz now instead of 450mhz.

I know; I know. Uhhh, I guess I was being a tad over-critical for some
unknown reason.

|
| | When I attempt to boot to Command Prompt Only, by holding down
CTRL.
| | when I power on,I get the Memory count-up, BIOS version screen,
drives
| | shown, and then it's back to the "Invalid System Disk" message.
:-(
|
| Well, a possible fix is "SYS C:", as in my first post. There are
| warnings in it. I think, as BIOS is set to Auto & as you get a DIR
| listing, very probably it is worth a try. If you decide to try it,
do so
| in that portion of this thread.
|
| I'll skip it. There is too much to read about and learn(again), and
| I've sp far wasted at least 50 man-hours on this for nothing.

Well, it took me many, many months before I would ever "SYS C:" or even
"FDISK /Status", myself. "SYS C:" is the proscribed fix for your
condition, as can be seen in the Readme.txt of any Startup Diskette...

....Quote of Startup Diskette Readme...............
If you encounter any of these error messages while
running Setup:

* Invalid System Disk
* Incorrect MS-DOS Version
* Missing or Corrupted Command.com
* Compression Driver errors

It is likely that your computer's startup drive may
need updated system files. You can use the SYS command
to copy the needed files to your computer.

NOTE: If you are currently loading compression software,
you will need to know your host drive letter. This is
typically H. If you are not loading any compression
software, then you will need to SYS your C drive.
......End quote of Startup Diskette Readme..........

You MUST have the proper Diskette, though, one that matches your OS. If
Win98SE, then use one made in Win98SE-- or get the right one from...
http://www.bootdisk.com/
Also, don't forget those other warnings! If you've already written to
this hard drive since the problem began, well... might as well do the
SYS C:. The damage has already been done, IF it were going to happen
from the write.

|
| | I have another motherboard. Perhaps I should try the rest of the
| | hardware with it. It'll be a pain because I have a hard enough
time
| | trying to figure out where each wire goes in the system the way it
| | is.(Sigh).
|
| If you change MB's, you will need to worry over VMM32.vxd, which is
| monolithic file containing low-level drivers.
|
| So I guess it's time to throw the PC in the trash and try get the info
| off of one of the drives("C") some other way.

Maybe. Well, why not get a second hard drive, & fresh install to it.
Then, attach this as Slave, & see what you can read?

|
| Thanks.
|
| Darren Harris
| Staten Island, New York.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

Well, it took me many, many months before I would ever "SYS C:" or even
"FDISK /Status", myself. "SYS C:" is the proscribed fix for your
condition, as can be seen in the Readme.txt of any Startup Diskette...

...Quote of Startup Diskette Readme...............
If you encounter any of these error messages while
running Setup:

* Invalid System Disk
* Incorrect MS-DOS Version
* Missing or Corrupted Command.com
* Compression Driver errors

It is likely that your computer's startup drive may
need updated system files. You can use the SYS command
to copy the needed files to your computer.

NOTE: If you are currently loading compression software,
you will need to know your host drive letter. This is
typically H. If you are not loading any compression
software, then you will need to SYS your C drive.
.....End quote of Startup Diskette Readme..........

You MUST have the proper Diskette, though, one that matches your OS. If
Win98SE, then use one made in Win98SE-- or get the right one from...
http://www.bootdisk.com/
Also, don't forget those other warnings! If you've already written to
this hard drive since the problem began, well... might as well do the
SYS C:. The damage has already been done, IF it were going to happen
from the write.

|
| | I have another motherboard. Perhaps I should try the rest of the
| | hardware with it. It'll be a pain because I have a hard enough
time
| | trying to figure out where each wire goes in the system the way it
| | is.(Sigh).
|
| If you change MB's, you will need to worry over VMM32.vxd, which is
| monolithic file containing low-level drivers.
|
| So I guess it's time to throw the PC in the trash and try get the info
| off of one of the drives("C") some other way.

Maybe. Well, why not get a second hard drive, & fresh install to it.
Then, attach this as Slave, & see what you can read?

Well I do have some 9gig drives. But it doesn't seem that he problem
is the drive since I diconnected my "C" and made my "D" the primary by
itself. That didn't help at all.

Anyway, I haven't written to my hard drive since this problem started,
because I can't get that far.(I don't know if the system writes to it
though).

And after "Load BIOS Defaults" changed my processor to a 464mhz, I
went back in CMOS and changed the CPU host clock from 103 to 100. That
brought the processor back down from 464mhz to 450mhz.

In CMOS I tried "Load BIOS Defaults" again. The only other change it
seemed to make was set the memory count-up to continuous.(It will
cycle indefinitely). I now have to press ESC to get past that.(Yeah, I
know I really shouldn't be messing with things I have no knowledge of,
but I have run out of options).

I did tried booting with a Windows 98 boot disk(downloaded from
http://www.bootdisk.com/, and instead of "Invalid System Disk", I get
Disk I/O error". So I can try "SYS C:" or anything else until I
resolve this.(Perhaps I should try changing the floppy drive first).

I guess it comes down to swaping and switching hardware. (Including
trying another motherboard). Now I have to worry what
software(drivers) I'll need.(What's VMM32.vxd?).

Darren Harris
Staten Island, New York.

"Darren Harris" wrote in message
m...
| Well, it took me many, many months before I would ever "SYS C:" or
even
| "FDISK /Status", myself. "SYS C:" is the proscribed fix for your
| condition, as can be seen in the Readme.txt of any Startup
Diskette...
|
| ...Quote of Startup Diskette Readme...............
| If you encounter any of these error messages while
| running Setup:
|
| * Invalid System Disk
| * Incorrect MS-DOS Version
| * Missing or Corrupted Command.com
| * Compression Driver errors
|
| It is likely that your computer's startup drive may
| need updated system files. You can use the SYS command
| to copy the needed files to your computer.
|
| NOTE: If you are currently loading compression software,
| you will need to know your host drive letter. This is
| typically H. If you are not loading any compression
| software, then you will need to SYS your C drive.
| .....End quote of Startup Diskette Readme..........
|
| You MUST have the proper Diskette, though, one that matches your OS.
If
| Win98SE, then use one made in Win98SE-- or get the right one from...
| http://www.bootdisk.com/
| Also, don't forget those other warnings! If you've already written
to
| this hard drive since the problem began, well... might as well do
the
| SYS C:. The damage has already been done, IF it were going to happen
| from the write.
|
| |
| | | I have another motherboard. Perhaps I should try the rest of
the
| | | hardware with it. It'll be a pain because I have a hard enough
| time
| | | trying to figure out where each wire goes in the system the
way it
| | | is.(Sigh).
| |
| | If you change MB's, you will need to worry over VMM32.vxd, which
is
| | monolithic file containing low-level drivers.
| |
| | So I guess it's time to throw the PC in the trash and try get the
info
| | off of one of the drives("C") some other way.
|
| Maybe. Well, why not get a second hard drive, & fresh install to it.
| Then, attach this as Slave, & see what you can read?
|
| Well I do have some 9gig drives. But it doesn't seem that he problem
| is the drive since I diconnected my "C" and made my "D" the primary by
| itself. That didn't help at all.

Did you get the jumper right, either Master or "Master alone on cable",
as WD sometimes wants to be? Did you move it on the cable to where C:\
was, probably farthest from the MB?

|
| Anyway, I haven't written to my hard drive since this problem started,
| because I can't get that far.(I don't know if the system writes to it
| though).

Writing to the hard drive should not be done, when the geometry is bad.
That is the "caution" against SYS C:, (although no such caution does
appear in the Readme of a Startup Diskette).

|
| And after "Load BIOS Defaults" changed my processor to a 464mhz, I
| went back in CMOS and changed the CPU host clock from 103 to 100. That
| brought the processor back down from 464mhz to 450mhz.
|
| In CMOS I tried "Load BIOS Defaults" again. The only other change it
| seemed to make was set the memory count-up to continuous.(It will
| cycle indefinitely). I now have to press ESC to get past that.(Yeah, I
| know I really shouldn't be messing with things I have no knowledge of,
| but I have run out of options).

Well, go back in, & change it back.

|
| I did tried booting with a Windows 98 boot disk(downloaded from
| http://www.bootdisk.com/, and instead of "Invalid System Disk", I get
| Disk I/O error".

When does "Disk I/O error" show up? Are you sure it is speaking of C:?
Did you try "DIR C:"? Perhaps try...
http://cquirke.mvps.org/9x/
....for an idea/two.

| So I can try "SYS C:" or anything else until I
| resolve this.(Perhaps I should try changing the floppy drive first).
|
| I guess it comes down to swaping and switching hardware. (Including
| trying another motherboard). Now I have to worry what
| software(drivers) I'll need.(What's VMM32.vxd?).

VMM32.vxd is a monolithic driver file created only by installing
Windows, though an over-install will do. It is machine specific &
contains low-level drivers for components such as the MB itself.

|
| Darren Harris
| Staten Island, New York.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

| Well I do have some 9gig drives. But it doesn't seem that he problem
| is the drive since I diconnected my "C" and made my "D" the primary by
| itself. That didn't help at all.

Did you get the jumper right, either Master or "Master alone on cable",
as WD sometimes wants to be? Did you move it on the cable to where C:\
was, probably farthest from the MB?

I tried every combination. And I know that the master or a single hard
drive is always supposed to be at the end of the cable.

|
| Anyway, I haven't written to my hard drive since this problem started,
| because I can't get that far.(I don't know if the system writes to it
| though).

Writing to the hard drive should not be done, when the geometry is bad.
That is the "caution" against SYS C:, (although no such caution does
appear in the Readme of a Startup Diskette).

Well, like I mentioned, I cannot get to my desktop, so there is no way
for me to write to any drive.

| And after "Load BIOS Defaults" changed my processor to a 464mhz, I
| went back in CMOS and changed the CPU host clock from 103 to 100. That
| brought the processor back down from 464mhz to 450mhz.
|
| In CMOS I tried "Load BIOS Defaults" again. The only other change it
| seemed to make was set the memory count-up to continuous.(It will
| cycle indefinitely). I now have to press ESC to get past that.(Yeah, I
| know I really shouldn't be messing with things I have no knowledge of,
| but I have run out of options).

Well, go back in, & change it back.

There is nothing to change back. The only option is, "LOAD BIOS
DEFAULT" is a singular option. There is nothing that says anything
like "return to previous".

| I did tried booting with a Windows 98 boot disk(downloaded from
| http://www.bootdisk.com/, and instead of "Invalid System Disk", I get
| Disk I/O error".

When does "Disk I/O error" show up? Are you sure it is speaking of C:?

No. That of course would be referring to my floppy drive, which is the
first drive accessed.

After the very first screen that gives you the memory count-up, along
with the other system info like what drive is on what SCSI ID, I get
the "Disk I/O error" when the Windows 98 boot disk is in the floppy
drive. Or I get "Invalid system disk" "Replace disk, and then press
any key" when there is nothing in the floppy drive.

Did you try "DIR C:"? Perhaps try...
http://cquirke.mvps.org/9x/
...for an idea/two.

Like I said, I cannot get far enough into the system to use any of
those commands.

| So I can try "SYS C:" or anything else until I
| resolve this.(Perhaps I should try changing the floppy drive first).
|
| I guess it comes down to swaping and switching hardware. (Including
| trying another motherboard). Now I have to worry what
| software(drivers) I'll need.(What's VMM32.vxd?).

VMM32.vxd is a monolithic driver file created only by installing
Windows, though an over-install will do. It is machine specific &
contains low-level drivers for components such as the MB itself.

It sounds like the only thing to do is get another SCSI system and
plug the "C" drive from the problem system into it so I can get all of
the info I need off of the drive.

Darren Harris
Staten Island, New York.

My BIOS has no such setting as "Continuous RAM test". I can turn on/off
a non-continuous one, though. Look for something like "Quickboot" in a
"Power On Self Test" menu.

Other than that, I guess go on & try attaching the HDD as a Slave. (I
really have nothing else.)


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Darren Harris" wrote in message
om...
| | Well I do have some 9gig drives. But it doesn't seem that he
problem
| | is the drive since I diconnected my "C" and made my "D" the
primary by
| | itself. That didn't help at all.
|
| Did you get the jumper right, either Master or "Master alone on
cable",
| as WD sometimes wants to be? Did you move it on the cable to where
C:\
| was, probably farthest from the MB?
|
| I tried every combination. And I know that the master or a single hard
| drive is always supposed to be at the end of the cable.
|
| |
| | Anyway, I haven't written to my hard drive since this problem
started,
| | because I can't get that far.(I don't know if the system writes to
it
| | though).
|
| Writing to the hard drive should not be done, when the geometry is
bad.
| That is the "caution" against SYS C:, (although no such caution does
| appear in the Readme of a Startup Diskette).
|
| Well, like I mentioned, I cannot get to my desktop, so there is no way
| for me to write to any drive.
|
| | And after "Load BIOS Defaults" changed my processor to a 464mhz, I
| | went back in CMOS and changed the CPU host clock from 103 to 100.
That
| | brought the processor back down from 464mhz to 450mhz.
| |
| | In CMOS I tried "Load BIOS Defaults" again. The only other change
it
| | seemed to make was set the memory count-up to continuous.(It will
| | cycle indefinitely). I now have to press ESC to get past
that.(Yeah, I
| | know I really shouldn't be messing with things I have no knowledge
of,
| | but I have run out of options).
|
| Well, go back in, & change it back.
|
| There is nothing to change back. The only option is, "LOAD BIOS
| DEFAULT" is a singular option. There is nothing that says anything
| like "return to previous".
|
| | I did tried booting with a Windows 98 boot disk(downloaded from
| | http://www.bootdisk.com/, and instead of "Invalid System Disk", I
get
| | Disk I/O error".
|
| When does "Disk I/O error" show up? Are you sure it is speaking of
C:?
|
| No. That of course would be referring to my floppy drive, which is the
| first drive accessed.
|
| After the very first screen that gives you the memory count-up, along
| with the other system info like what drive is on what SCSI ID, I get
| the "Disk I/O error" when the Windows 98 boot disk is in the floppy
| drive. Or I get "Invalid system disk" "Replace disk, and then press
| any key" when there is nothing in the floppy drive.
|
| Did you try "DIR C:"? Perhaps try...
| http://cquirke.mvps.org/9x/
| ...for an idea/two.
|
| Like I said, I cannot get far enough into the system to use any of
| those commands.
|
| | So I can try "SYS C:" or anything else until I
| | resolve this.(Perhaps I should try changing the floppy drive
first).
| |
| | I guess it comes down to swaping and switching hardware.
(Including
| | trying another motherboard). Now I have to worry what
| | software(drivers) I'll need.(What's VMM32.vxd?).
|
| VMM32.vxd is a monolithic driver file created only by installing
| Windows, though an over-install will do. It is machine specific &
| contains low-level drivers for components such as the MB itself.
|
| It sounds like the only thing to do is get another SCSI system and
| plug the "C" drive from the problem system into it so I can get all of
| the info I need off of the drive.
|
| Darren Harris
| Staten Island, New York.

"PCR" wrote in message ...
My BIOS has no such setting as "Continuous RAM test". I can turn on/off
a non-continuous one, though. Look for something like "Quickboot" in a
"Power On Self Test" menu.

Other than that, I guess go on & try attaching the HDD as a Slave. (I
really have nothing else.)

I think the BIOS is corrupt. I don't know what a "Power On Self Test"
is, but it makes no difference because I wouldn't be able to get there
anyway.

Okay, thanks.

Darren Harris
Staten Island, New York.

You are welcome. Good luck.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Darren Harris" wrote in message
om...
| "PCR" wrote in message
...
| My BIOS has no such setting as "Continuous RAM test". I can turn
on/off
| a non-continuous one, though. Look for something like "Quickboot" in
a
| "Power On Self Test" menu.
|
| Other than that, I guess go on & try attaching the HDD as a Slave.
(I
| really have nothing else.)
|
| I think the BIOS is corrupt. I don't know what a "Power On Self Test"
| is, but it makes no difference because I wouldn't be able to get there
| anyway.
|
| Okay, thanks.
|
| Darren Harris
| Staten Island, New York.