registry help,please!

Um, you got a "critical update notice from Microsoft"? On Win98? How did you get
this notification...email or what? Win98 has been out of support for some time, and
Microsoft has not produced any critical updates for it in almost two years.
--
Glen Ventura, MS MVP Windows, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm


"JS" wrote in message
...
When I clicked on "view updates" I got a page fault msg. that had something about
"ddhelp",then I got the blue screen.After that, I am not sure, I may have tried to
reboot.

"Gary S. Terhune" none wrote in message
...
"POW"? Froze the screen? Rebooted itself? Died altogether as if the cord was
pulled?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
Ok, Gary, I think I have been skipping around a little.
1. my machine will not start normally.
2.I can only go to option #5"command prompt only"(shift-f5)
3.when I run scanreg, I get the msg thats says"you do not have extended memory
driver"
4.I got a critical update notice from MS and got online(dialup) and when I
clicked on "view updates" POW!
Is that better? I have made some other posts that may help or confuse further.
We'll get this done!
Thanks,
Jim
"Gary S. Terhune" none wrote in message
...
OK, now I need to make sure what's what:

Your machine won't start normally, or will it?

When you currently start, without a floppy boot disk, you get an option
"Command Prompt Only" and no other option? Or is that just the one that's
highlighted? Or are you simply trying to run SCANREG?

Is it only when you get the Command Prompt and run SCANREG that you get the
memory errors?

Do you know what made your machine crashing the first place? Does it do it
often?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
ok guys, I am a little confused on the order of things that I am supposed to
do.
I did scanreg and it told me about the himem and extended memory driver.
I have made a boot disk,(although I am not sure what to do with it and when.)
I did the edit c:config.sys thing in the blue screen(C:config.sys on top) I
added the "device" line here.
When I did the alt-f-s , a search thing came up.I didnt know what to do then,
so I esc and did alt f-x and it said it was saved.
I use the reset button to restart and nothing is different.Still comes up in
the setup with command prompt only highlighted.
I am pretty good on the step-by-step concept, so if you can tell me what to do
next, I would appreciate it.
Thanks for your help,
Jim

"Gary S. Terhune" none wrote in message
...
CORRECTION: Referring to the following part:
EDIT C:\CONFIG.SYS
(That opens the file for editing. Input the following line
DEVICE=C:\WINDOWS\HIMEM.SYS

Before you can input anything, press END and then ENTER, to get a new line.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"Gary S. Terhune" none wrote in message
...
(Be sure to read all the way through before doing anything.)

Your symptoms point to a possible RAM failure. Suggest you stop right here
and test your RAM using floppy-based tools like, DocMemory from
http://www.simmtester.com/. See here for lots more RAM diagnostic hints:
http://tinyurl.com/2wehd3 If a day's worth of testing doesn't show a
problem, then continue.

"C:\" IS the Command Prompt. The '' character is the Prompt part, the
'C:\' part is the Directory in which the Prompt is set to exist. Unless you
need to change the root directory (C:\), that part of the command is
inherent -- you only HAVE TO input what comes after that, but you CAN input
C:\ to start new commands if you want to.

OK, we'll do it step by step. Each line below that is in ALL CAPS is a
command or data input -- input those lines and press enter at the end of
those lines. (You don't have to use ALL CAPS, it's just a way to help you
read this message.) You do all this from a floppy boot disk, of course.

First, determine if HIMEM.SYS exists in C:\WINDOWS with this command:
DIR C:\WINDOWS\HIMEM.SYS

Do you get an error or do you get file info for HIMEM.SYS? If error, quit
now and report back. We'll go looking for it. But, assuming the file is
where we expect it to be -- it usually is but may be elsewhere in older DOS
and/or WIN95 that have been upgraded, or new but modified 98/98SE systems --
continue with the following:

EDIT C:\CONFIG.SYS
(That opens the file for editing. Input the following line
DEVICE=C:\WINDOWS\HIMEM.SYS

Now, press Alt-F-S to save CONFIG.SYS, then press Alt-F-X to close the file.
Remove the floppy disk and then restart. What happens?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
OK, I got scanreg to work and it says that there is no extended memory
driver. Something about himem.sys
It says to add line to boot drive: device=C:\windows\himem.sys
How do I do this? I have the 98cd, if that helps. Would this be covered on
the MS website? I need this to be fixed by mon.am it is for business.
Thanks,
Jim
"JS" wrote in message
...
So, am I trying to make an extra step by trying to get "command prompt
only" to work? I type scanreg from where it is right now?
I was thinking that I had to start it up first. I don't know what you
mean by "chose backup"?
Thanks Gary,
Jim
"Gary S. Terhune" none wrote in message
...
Yes, the command is SCANREG (all by itself.) Choose backup based upon
date, not filename. I'll let someone else explain the arcania of the
Command Prompt.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
Greetings,
Today, my 98 pc crashed and when I restarted it, it came up in the mode
where you get 5 or so choices, normal, safe mode,etc. The #5 "command
prompt only" was highlighted and I couldn't choose another, and all I
see is the C:\ . What command do I put in to get it started again. I
put in the # 5 and "command prompt only" and got "bad command" on both.
It also said to run scanreg when it gets started. Is "scanreg" the
command I use to start that? Do I need C: only? what are the other two
symbols for? Any other suggestions are appreciated.
Jim

msdos.sys is hidden, need to do an * attrib msdos.sys -r -h -s * from the
DOS prompt...

When done editing re-attrib with * attrib msdos.sys +r +h +s *

--

MEB
http://peoplescounsel.orgfree.com
_________


"Buffalo" wrote in message
...
| JS wrote:
| Ben,
| I am at C:\ and I type in C:\msdos.sys , all I get is a bad command
| or file name. Is that what I was supposed to type in?
| Thanks for your help as well.
| Jim
| MsDos.Sys is just in C:\, just like config.sys and autoexec.bat.
| To bring it up you could try using the Edit command which I believe would
| look like:
| C:\ edit msdos.sys or similar.
|
|

"JS" wrote in message ...
Ben,
I am at C:\ and I type in C:\msdos.sys , all I get is a bad command or
file name. Is that what I was supposed to type in?
Thanks for your help as well.
Jim

Just type "edit c:\msdos.sys", press "Enter" and make sure it looks
something like the following. Use "Page down" to examine the very
end of file as well, since any line that doesn't begin with a semicolon
is probably being processed during bootup. Any line containing
"BootSafe" or "BootMenu" should probably be removed. If the
"c:\msdos.sys" file looks OK, type "dir /a c:\winboot.ini", since
this file can interfere with bootup.

[Paths]
WinDir=C:\WINDOWS
WinBootDir=C:\WINDOWS
HostWinBootDrv=C
[Options]
BOOTGUI=1
;end

Ben

Yes!, believe it or not, or maybe it was some quirk thing, but I got the
standard window on my screen(not email) saying a critical update was
available. It looked official to me! OH NO! Don't tell me!
"glee" wrote in message
...
Um, you got a "critical update notice from Microsoft"? On Win98? How did
you get this notification...email or what? Win98 has been out of support
for some time, and Microsoft has not produced any critical updates for it
in almost two years.
--
Glen Ventura, MS MVP Windows, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm


"JS" wrote in message
...
When I clicked on "view updates" I got a page fault msg. that had
something about "ddhelp",then I got the blue screen.After that, I am not
sure, I may have tried to reboot.

"Gary S. Terhune" none wrote in message
...
"POW"? Froze the screen? Rebooted itself? Died altogether as if the cord
was pulled?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
Ok, Gary, I think I have been skipping around a little.
1. my machine will not start normally.
2.I can only go to option #5"command prompt only"(shift-f5)
3.when I run scanreg, I get the msg thats says"you do not have extended
memory driver"
4.I got a critical update notice from MS and got online(dialup) and
when I clicked on "view updates" POW!
Is that better? I have made some other posts that may help or confuse
further. We'll get this done!
Thanks,
Jim
"Gary S. Terhune" none wrote in message
...
OK, now I need to make sure what's what:

Your machine won't start normally, or will it?

When you currently start, without a floppy boot disk, you get an
option "Command Prompt Only" and no other option? Or is that just the
one that's highlighted? Or are you simply trying to run SCANREG?

Is it only when you get the Command Prompt and run SCANREG that you
get the memory errors?

Do you know what made your machine crashing the first place? Does it
do it often?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
ok guys, I am a little confused on the order of things that I am
supposed to do.
I did scanreg and it told me about the himem and extended memory
driver.
I have made a boot disk,(although I am not sure what to do with it
and when.)
I did the edit c:config.sys thing in the blue screen(C:config.sys on
top) I added the "device" line here.
When I did the alt-f-s , a search thing came up.I didnt know what to
do then, so I esc and did alt f-x and it said it was saved.
I use the reset button to restart and nothing is different.Still
comes up in the setup with command prompt only highlighted.
I am pretty good on the step-by-step concept, so if you can tell me
what to do next, I would appreciate it.
Thanks for your help,
Jim

"Gary S. Terhune" none wrote in message
...
CORRECTION: Referring to the following part:
EDIT C:\CONFIG.SYS
(That opens the file for editing. Input the following line
DEVICE=C:\WINDOWS\HIMEM.SYS

Before you can input anything, press END and then ENTER, to get a
new line.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"Gary S. Terhune" none wrote in message
...
(Be sure to read all the way through before doing anything.)

Your symptoms point to a possible RAM failure. Suggest you stop
right here
and test your RAM using floppy-based tools like, DocMemory from
http://www.simmtester.com/. See here for lots more RAM diagnostic
hints:
http://tinyurl.com/2wehd3 If a day's worth of testing doesn't show
a
problem, then continue.

"C:\" IS the Command Prompt. The '' character is the Prompt part,
the
'C:\' part is the Directory in which the Prompt is set to exist.
Unless you
need to change the root directory (C:\), that part of the command
is
inherent -- you only HAVE TO input what comes after that, but you
CAN input
C:\ to start new commands if you want to.

OK, we'll do it step by step. Each line below that is in ALL CAPS
is a
command or data input -- input those lines and press enter at the
end of
those lines. (You don't have to use ALL CAPS, it's just a way to
help you
read this message.) You do all this from a floppy boot disk, of
course.

First, determine if HIMEM.SYS exists in C:\WINDOWS with this
command:
DIR C:\WINDOWS\HIMEM.SYS

Do you get an error or do you get file info for HIMEM.SYS? If
error, quit
now and report back. We'll go looking for it. But, assuming the
file is
where we expect it to be -- it usually is but may be elsewhere in
older DOS
and/or WIN95 that have been upgraded, or new but modified 98/98SE
systems --
continue with the following:

EDIT C:\CONFIG.SYS
(That opens the file for editing. Input the following line
DEVICE=C:\WINDOWS\HIMEM.SYS

Now, press Alt-F-S to save CONFIG.SYS, then press Alt-F-X to close
the file.
Remove the floppy disk and then restart. What happens?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
OK, I got scanreg to work and it says that there is no extended
memory
driver. Something about himem.sys
It says to add line to boot drive: device=C:\windows\himem.sys
How do I do this? I have the 98cd, if that helps. Would this be
covered on
the MS website? I need this to be fixed by mon.am it is for
business.
Thanks,
Jim
"JS" wrote in message
...
So, am I trying to make an extra step by trying to get "command
prompt
only" to work? I type scanreg from where it is right now?
I was thinking that I had to start it up first. I don't know what
you
mean by "chose backup"?
Thanks Gary,
Jim
"Gary S. Terhune" none wrote in message
...
Yes, the command is SCANREG (all by itself.) Choose backup based
upon
date, not filename. I'll let someone else explain the arcania of
the
Command Prompt.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
Greetings,
Today, my 98 pc crashed and when I restarted it, it came up in
the mode
where you get 5 or so choices, normal, safe mode,etc. The #5
"command
prompt only" was highlighted and I couldn't choose another, and
all I
see is the C:\ . What command do I put in to get it started
again. I
put in the # 5 and "command prompt only" and got "bad command"
on both.
It also said to run scanreg when it gets started. Is "scanreg"
the
command I use to start that? Do I need C: only? what are the
other two
symbols for? Any other suggestions are appreciated.
Jim

Ben,
I got the msdos to come up like you said, and although I really don't know
what I am looking at, it looks very similar to yours. I typed in the dir /a
C:\winboot.ini and it said file not found.
What next?

"Ben Myers" wrote in message
...
"JS" wrote in message
...
Ben,
I am at C:\ and I type in C:\msdos.sys , all I get is a bad command or
file name. Is that what I was supposed to type in?
Thanks for your help as well.
Jim

Just type "edit c:\msdos.sys", press "Enter" and make sure it looks
something like the following. Use "Page down" to examine the very
end of file as well, since any line that doesn't begin with a semicolon
is probably being processed during bootup. Any line containing
"BootSafe" or "BootMenu" should probably be removed. If the
"c:\msdos.sys" file looks OK, type "dir /a c:\winboot.ini", since
this file can interfere with bootup.

[Paths]
WinDir=C:\WINDOWS
WinBootDir=C:\WINDOWS
HostWinBootDrv=C
[Options]
BOOTGUI=1
;end

Ben

OK, I got the alt's to work, and the device line is still there.
I also traded out some of the memory sticks with the same result.

What next, please?

"Gary S. Terhune" none wrote in message
...
Run EDIT CONFIG.SYS command again and see if the DEVICE= line is still
there.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
I did what you said about the config.sys.(I think)
Here is what I did,
from C: I put dir C:\windows\himem.sys
I got a bunch of numbers,date, etc(if you need some of the specifics,let
me know and I will do it again)
Then I wrote edit C:\config.sys and a blue screen with "config.sys" on
top came up.
Here is where I wrote device=C:\windows\himem.sys
Then I hit alt F-S, which I thought you said it would save it, but it
didn't,it brought up a search request. I esc out of that and hit alt-f-x
and then it said it was saved. I then tried to reboot with no luck.


"Gary S. Terhune" none wrote in message
...
OK, typical "crash". Could be memory. Could be, though, that the garbage
is left over a previous run of SCANDISK. I'm running mental scenarios
and my own admittedly faulty memories tell me it's actually common --
cross-linked files fixed but not the accompanying lost clusters.

But that's only one possibility. You need to follow the instructions I
already gave you to edit CONFIG.SYS, make sure where HIMEM.SYS is
located, etc. What are the results?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
When I clicked on "view updates" I got a page fault msg. that had
something about "ddhelp",then I got the blue screen.After that, I am
not sure, I may have tried to reboot.

"Gary S. Terhune" none wrote in message
...
"POW"? Froze the screen? Rebooted itself? Died altogether as if the
cord was pulled?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
Ok, Gary, I think I have been skipping around a little.
1. my machine will not start normally.
2.I can only go to option #5"command prompt only"(shift-f5)
3.when I run scanreg, I get the msg thats says"you do not have
extended memory driver"
4.I got a critical update notice from MS and got online(dialup) and
when I clicked on "view updates" POW!
Is that better? I have made some other posts that may help or confuse
further. We'll get this done!
Thanks,
Jim
"Gary S. Terhune" none wrote in message
...
OK, now I need to make sure what's what:

Your machine won't start normally, or will it?

When you currently start, without a floppy boot disk, you get an
option "Command Prompt Only" and no other option? Or is that just
the one that's highlighted? Or are you simply trying to run SCANREG?

Is it only when you get the Command Prompt and run SCANREG that you
get the memory errors?

Do you know what made your machine crashing the first place? Does it
do it often?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
ok guys, I am a little confused on the order of things that I am
supposed to do.
I did scanreg and it told me about the himem and extended memory
driver.
I have made a boot disk,(although I am not sure what to do with it
and when.)
I did the edit c:config.sys thing in the blue screen(C:config.sys
on top) I added the "device" line here.
When I did the alt-f-s , a search thing came up.I didnt know what
to do then, so I esc and did alt f-x and it said it was saved.
I use the reset button to restart and nothing is different.Still
comes up in the setup with command prompt only highlighted.
I am pretty good on the step-by-step concept, so if you can tell me
what to do next, I would appreciate it.
Thanks for your help,
Jim

"Gary S. Terhune" none wrote in message
...
CORRECTION: Referring to the following part:
EDIT C:\CONFIG.SYS
(That opens the file for editing. Input the following line
DEVICE=C:\WINDOWS\HIMEM.SYS

Before you can input anything, press END and then ENTER, to get a
new line.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"Gary S. Terhune" none wrote in message
...
(Be sure to read all the way through before doing anything.)

Your symptoms point to a possible RAM failure. Suggest you stop
right here
and test your RAM using floppy-based tools like, DocMemory from
http://www.simmtester.com/. See here for lots more RAM diagnostic
hints:
http://tinyurl.com/2wehd3 If a day's worth of testing doesn't
show a
problem, then continue.

"C:\" IS the Command Prompt. The '' character is the Prompt
part, the
'C:\' part is the Directory in which the Prompt is set to exist.
Unless you
need to change the root directory (C:\), that part of the command
is
inherent -- you only HAVE TO input what comes after that, but you
CAN input
C:\ to start new commands if you want to.

OK, we'll do it step by step. Each line below that is in ALL CAPS
is a
command or data input -- input those lines and press enter at the
end of
those lines. (You don't have to use ALL CAPS, it's just a way to
help you
read this message.) You do all this from a floppy boot disk, of
course.

First, determine if HIMEM.SYS exists in C:\WINDOWS with this
command:
DIR C:\WINDOWS\HIMEM.SYS

Do you get an error or do you get file info for HIMEM.SYS? If
error, quit
now and report back. We'll go looking for it. But, assuming the
file is
where we expect it to be -- it usually is but may be elsewhere in
older DOS
and/or WIN95 that have been upgraded, or new but modified 98/98SE
systems --
continue with the following:

EDIT C:\CONFIG.SYS
(That opens the file for editing. Input the following line
DEVICE=C:\WINDOWS\HIMEM.SYS

Now, press Alt-F-S to save CONFIG.SYS, then press Alt-F-X to
close the file.
Remove the floppy disk and then restart. What happens?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
OK, I got scanreg to work and it says that there is no extended
memory
driver. Something about himem.sys
It says to add line to boot drive: device=C:\windows\himem.sys
How do I do this? I have the 98cd, if that helps. Would this be
covered on
the MS website? I need this to be fixed by mon.am it is for
business.
Thanks,
Jim
"JS" wrote in message
...
So, am I trying to make an extra step by trying to get "command
prompt
only" to work? I type scanreg from where it is right now?
I was thinking that I had to start it up first. I don't know
what you
mean by "chose backup"?
Thanks Gary,
Jim
"Gary S. Terhune" none wrote in message
...
Yes, the command is SCANREG (all by itself.) Choose backup
based upon
date, not filename. I'll let someone else explain the arcania
of the
Command Prompt.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
Greetings,
Today, my 98 pc crashed and when I restarted it, it came up
in the mode
where you get 5 or so choices, normal, safe mode,etc. The #5
"command
prompt only" was highlighted and I couldn't choose another,
and all I
see is the C:\ . What command do I put in to get it started
again. I
put in the # 5 and "command prompt only" and got "bad
command" on both.
It also said to run scanreg when it gets started. Is
"scanreg" the
command I use to start that? Do I need C: only? what are the
other two
symbols for? Any other suggestions are appreciated.
Jim

"JS" wrote in message ...
Ben,
I got the msdos to come up like you said, and although I really don't know
what I am looking at, it looks very similar to yours. I typed in the dir /a
C:\winboot.ini and it said file not found.
What next?

Look for lines containing "BootSafe" or "BootMenu". If you find
them, remove them or just put a semicolon in front of them. Be sure
to use "Page down" to check the very end of the file and don't forget to
save the change. If you have trouble modifying the file, try typing
"attrib -r -h -s c:\msdos.sys" at the command prompt.

Ben

Thanks for the suggestion. Is it possible for that update notice originated
from my pc, as I havn't been online with that pc in a while? That's what
making me think that the problem is within my machine rather than a
downloaded bug.
And I am still stuck. I can't get it to boot with a boot disk. Is it wise to
try and reinstall 98 from the cd, knowing I will have to change the bios?
"Buffalo" wrote in message
...
JS wrote:
Yes!, believe it or not, or maybe it was some quirk thing, but I got
the standard window on my screen(not email) saying a critical update
was available. It looked official to me! OH NO! Don't tell me!
"glee" wrote in message
...
Um, you got a "critical update notice from Microsoft"? On Win98?
How did you get this notification...email or what? Win98 has been
out of support for some time, and Microsoft has not produced any
critical updates for it in almost two years.
--
Glen Ventura, MS MVP Windows, A+
If you get into regular Windows, dl, install, update and then run the free
version of SuperAntiSpyware and see if it helps.
It is easy to uninstall SuperAntiSpyware if you want and the free version
works as powerfully as the paid version. The paid version works full time
and updates automatically while the free version is on-demand only and
requires manual updates.
If you still can't get into regular Windows and the others' suggestions
fail, you can dl , onto a CD or DVD, a program called "The Ultimate Boot
Disk" (also free) and use it to boot up and run their anti-virus scan.
If you use this, you may have to go into your BIOS and set the CD-Rom
drive
as the first boot device.

JS wrote:
Yes!, believe it or not, or maybe it was some quirk thing, but I got
the standard window on my screen(not email) saying a critical update
was available. It looked official to me! OH NO! Don't tell me!
"glee" wrote in message
...
Um, you got a "critical update notice from Microsoft"? On Win98?
How did you get this notification...email or what? Win98 has been
out of support for some time, and Microsoft has not produced any
critical updates for it in almost two years.
--
Glen Ventura, MS MVP Windows, A+
If you get into regular Windows, dl, install, update and then run the free
version of SuperAntiSpyware and see if it helps.
It is easy to uninstall SuperAntiSpyware if you want and the free version
works as powerfully as the paid version. The paid version works full time
and updates automatically while the free version is on-demand only and
requires manual updates.
If you still can't get into regular Windows and the others' suggestions
fail, you can dl , onto a CD or DVD, a program called "The Ultimate Boot
Disk" (also free) and use it to boot up and run their anti-virus scan.
If you use this, you may have to go into your BIOS and set the CD-Rom drive
as the first boot device.

Well, we've made fairly certain that it's not hardware, that HIMEM.SYS isn't
missing or messed up... I think you need to follow the track of that
possible intruder for now. To be honest, I'm having one of my periodic
medically derived losses of decent mental faculty and need to bow out of
this diagnosis. I'll jump back in if anything comes up or occurs to me.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
OK, I got the alt's to work, and the device line is still there.
I also traded out some of the memory sticks with the same result.

What next, please?

"Gary S. Terhune" none wrote in message
...
Run EDIT CONFIG.SYS command again and see if the DEVICE= line is still
there.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
I did what you said about the config.sys.(I think)
Here is what I did,
from C: I put dir C:\windows\himem.sys
I got a bunch of numbers,date, etc(if you need some of the specifics,let
me know and I will do it again)
Then I wrote edit C:\config.sys and a blue screen with "config.sys" on
top came up.
Here is where I wrote device=C:\windows\himem.sys
Then I hit alt F-S, which I thought you said it would save it, but it
didn't,it brought up a search request. I esc out of that and hit alt-f-x
and then it said it was saved. I then tried to reboot with no luck.


"Gary S. Terhune" none wrote in message
...
OK, typical "crash". Could be memory. Could be, though, that the
garbage is left over a previous run of SCANDISK. I'm running mental
scenarios and my own admittedly faulty memories tell me it's actually
common -- cross-linked files fixed but not the accompanying lost
clusters.

But that's only one possibility. You need to follow the instructions I
already gave you to edit CONFIG.SYS, make sure where HIMEM.SYS is
located, etc. What are the results?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
When I clicked on "view updates" I got a page fault msg. that had
something about "ddhelp",then I got the blue screen.After that, I am
not sure, I may have tried to reboot.

"Gary S. Terhune" none wrote in message
...
"POW"? Froze the screen? Rebooted itself? Died altogether as if the
cord was pulled?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
Ok, Gary, I think I have been skipping around a little.
1. my machine will not start normally.
2.I can only go to option #5"command prompt only"(shift-f5)
3.when I run scanreg, I get the msg thats says"you do not have
extended memory driver"
4.I got a critical update notice from MS and got online(dialup) and
when I clicked on "view updates" POW!
Is that better? I have made some other posts that may help or
confuse further. We'll get this done!
Thanks,
Jim
"Gary S. Terhune" none wrote in message
...
OK, now I need to make sure what's what:

Your machine won't start normally, or will it?

When you currently start, without a floppy boot disk, you get an
option "Command Prompt Only" and no other option? Or is that just
the one that's highlighted? Or are you simply trying to run
SCANREG?

Is it only when you get the Command Prompt and run SCANREG that you
get the memory errors?

Do you know what made your machine crashing the first place? Does
it do it often?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
ok guys, I am a little confused on the order of things that I am
supposed to do.
I did scanreg and it told me about the himem and extended memory
driver.
I have made a boot disk,(although I am not sure what to do with it
and when.)
I did the edit c:config.sys thing in the blue screen(C:config.sys
on top) I added the "device" line here.
When I did the alt-f-s , a search thing came up.I didnt know what
to do then, so I esc and did alt f-x and it said it was saved.
I use the reset button to restart and nothing is different.Still
comes up in the setup with command prompt only highlighted.
I am pretty good on the step-by-step concept, so if you can tell
me what to do next, I would appreciate it.
Thanks for your help,
Jim

"Gary S. Terhune" none wrote in message
...
CORRECTION: Referring to the following part:
EDIT C:\CONFIG.SYS
(That opens the file for editing. Input the following line
DEVICE=C:\WINDOWS\HIMEM.SYS

Before you can input anything, press END and then ENTER, to get a
new line.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"Gary S. Terhune" none wrote in message
...
(Be sure to read all the way through before doing anything.)

Your symptoms point to a possible RAM failure. Suggest you stop
right here
and test your RAM using floppy-based tools like, DocMemory from
http://www.simmtester.com/. See here for lots more RAM
diagnostic hints:
http://tinyurl.com/2wehd3 If a day's worth of testing doesn't
show a
problem, then continue.

"C:\" IS the Command Prompt. The '' character is the Prompt
part, the
'C:\' part is the Directory in which the Prompt is set to exist.
Unless you
need to change the root directory (C:\), that part of the
command is
inherent -- you only HAVE TO input what comes after that, but
you CAN input
C:\ to start new commands if you want to.

OK, we'll do it step by step. Each line below that is in ALL
CAPS is a
command or data input -- input those lines and press enter at
the end of
those lines. (You don't have to use ALL CAPS, it's just a way to
help you
read this message.) You do all this from a floppy boot disk, of
course.

First, determine if HIMEM.SYS exists in C:\WINDOWS with this
command:
DIR C:\WINDOWS\HIMEM.SYS

Do you get an error or do you get file info for HIMEM.SYS? If
error, quit
now and report back. We'll go looking for it. But, assuming the
file is
where we expect it to be -- it usually is but may be elsewhere
in older DOS
and/or WIN95 that have been upgraded, or new but modified
98/98SE systems --
continue with the following:

EDIT C:\CONFIG.SYS
(That opens the file for editing. Input the following line
DEVICE=C:\WINDOWS\HIMEM.SYS

Now, press Alt-F-S to save CONFIG.SYS, then press Alt-F-X to
close the file.
Remove the floppy disk and then restart. What happens?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
OK, I got scanreg to work and it says that there is no extended
memory
driver. Something about himem.sys
It says to add line to boot drive: device=C:\windows\himem.sys
How do I do this? I have the 98cd, if that helps. Would this be
covered on
the MS website? I need this to be fixed by mon.am it is for
business.
Thanks,
Jim
"JS" wrote in message
...
So, am I trying to make an extra step by trying to get
"command prompt
only" to work? I type scanreg from where it is right now?
I was thinking that I had to start it up first. I don't know
what you
mean by "chose backup"?
Thanks Gary,
Jim
"Gary S. Terhune" none wrote in message
...
Yes, the command is SCANREG (all by itself.) Choose backup
based upon
date, not filename. I'll let someone else explain the arcania
of the
Command Prompt.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"JS" wrote in message
...
Greetings,
Today, my 98 pc crashed and when I restarted it, it came up
in the mode
where you get 5 or so choices, normal, safe mode,etc. The #5
"command
prompt only" was highlighted and I couldn't choose another,
and all I
see is the C:\ . What command do I put in to get it started
again. I
put in the # 5 and "command prompt only" and got "bad
command" on both.
It also said to run scanreg when it gets started. Is
"scanreg" the
command I use to start that? Do I need C: only? what are the
other two
symbols for? Any other suggestions are appreciated.
Jim