There's not much else offer other than what Mike and I have already posted.
You are running out of options regarding getting your current WinMe system
to restore and at least run again (albeit requiring further work), with
scanreg /restore being the last tool in the box.

Regarding options 2 & 3 of scanreg (probably not much use in this case) see
:-
"Changes to the Registry Checker Tool (Scanreg.exe) in Windows Me"
http://support.microsoft.com/kb/273889/en-us

And for Scanreg in general, see :-
"Description of the Windows Registry Checker Tool (Scanreg.exe)"
http://support.microsoft.com/kb/183887/en-us

As for upgrading to XP, you should address that issue to one of the XP
groups. Personally, I would be inclined to concentrate on WinMe until you've
got a good working system (re-install if necessary) - even if that only
means that you proved the rest of your PC (hardware) is functioning
properly, in readiness for a potential XP upgrade. For all we know at this
time, you might well have a virus or malware, or worse still you *might*
even have a failing HDD.

Mart


"JNB" wrote in message
...
I would still like to hear someone weight in on options 2 & 3 of scanReg.
What do they do?.....and on the concept of upgrading to XP. Thanks.

"Mike M" wrote:

If you think system restore is OK then there is no real harm in restoring
an older copy of the registry using scanreg /restore and then running
system restore as SR will replace the old restored version of the
registry
with a copy made at the time the system restore checkpoint was created.
--
Mike Maltby



JNB wrote:

What started all this was when I tried to add new phone numbers to
the list that the dailer was using. That did something and I was
able to use System Restore successfully then...probably about a week
ago. And I'm sure that I've used System Restore several other times
since the date of the .cab files. Anyway, the PC seemed to work fine
except that the dailer was screwed up so I contacted People PC and
they told me to load the new one. I guess I could try getting a new
vsinint.dll.