System Restore and other problems

So what happens if you repair the registry using the command
SCANREG /FIX
from a command prompt such as Start | Run.. On completion of the repair the
system will reboot. Can you now create a system restore checkpoints?

I does sound though as if you may have also trashed the restore archive and
its control files so I would also recommend that you clear the C:\RESTORE
folder from DOS as follows:
a) Boot to DOS using a floppy. Do NOT choose "Minimal Boot" from the menu
when booting from a floppy but rather choose "Start computer with (or without)
CD-ROM support" otherwise the ATTRIB command will not be available.
b) At the DOS A:\ prompt, type:

ATTRIB -H -S -R C:\_RESTORE
and then
REN C:\_RESTORE OLDREST

c) Remove the floppy
d) Reboot your PC
e) Delete the folder C:\OLDREST
f) Check that an automatic system restore checkpoint was created.
g) Finally adjust the space allocated to the restore folder:
System | Performance | File System | Hard Disk and adjust the restore slider
to your preferred setting. A figure of 200MB is normally more than adequate
for day to day use allowing perhaps a week of checkpoints to be available
although increasing this to perhaps 400MB for a few days during periods of
large installs such Microsoft Office is advisable.
--
Mike Maltby MS-MVP



om wrote:

Thanks Mike. UPnP is now removed and unwanted dial-ups
stopped.

I'm now ready for a voyage of discovery... to find out if
my System Restore can be restored. Are you willing to play?

Some history of the problem and attempts to fix it...

This may be relevant (?) - Nine months ago I couldn't
enter Windows, no safe mode, only DOS available on
startup. A local 'expert' reinstalled the hard drive by
copying it, he said. So my pc has a hidden partition,
containing my original personal files, that isn't listed
(or, apparently, identified) by Windows. Certainly, I have
listed something like half the memory available than
before, now 128MB RAM 46% free. SR worked before this
incident. But I don't know precisely when SR went duff -
it is only called up when it's needed.

The responses I get from SR are as follows:
Restore my computer to an earlier time currently no
restore points available.
Create a restore point System Restore is not able to
create a Restore Point. Please restart the computer and
run System Restore again.

Restarting always results in a repeat of the above.

Data appears to be being logged. C:\_RESTORE\LOGS contains
3 files: lastsfp.dat, vxdalt1.log and vxdsfp.log, the last
two of 1025 KBytes, all of today's date. ...\ARCHIVES
contains BKUPVXDLASTLOG files of 1025 KB up to today's
date. ...\TEMP contains many .CPY files up to today's date.
...\SFP folder is empty.

C:\WINDOWS\SYSTEM\RESTORE contains statemgr.exe and
stmgr.exe, amongst other files. Stmgr.exe is also on C:
drive (I copied it to one or other folder in a vain
gesture).

I have tried to fix SR previously... by removing H,S,R
attributes in DOS and renaming... but the automatic
replacement folder delivered the same problem, as above.

Any ideas for a solution are most welcome from all.
-Jeremy Stanford

-----Original Message-----
(thanks, Mike)
--
Noel Paton (MS-MVP 2002-2004, Win9x)


Hi Noel,
I think its your turn on recommendations for restoring
System Restore

The problem is that no restore points can be created.

I have tried both Mike's recommendations previously
[thanks Mike], namely a) SCANREG /FIX and b) deleting the
existing c:\_RESTORE folder using DOS. For good measure
have now tried both again - but the problem is unchanged.

I found after replacing _RESTORE folder that disk space
for SR was at max., I reset it to 317MB, rebooted, but
still no restore points are being created.

Perhaps there is something available on my original WIN ME
CD to restore SR to working order??? I would like any
advice on this.

-Jeremy Stanford

N.B.Below is pasted a copy of yesterday's descriptive post
[Jeremy Stanford - June 11 6:22PM]

Some history of the problem and attempts to fix it...

This may be relevant (?) - Nine months ago I couldn't
enter Windows, no safe mode, only DOS available on
startup. A local 'expert' reinstalled the hard drive by
copying it, he said. So my pc has a hidden partition,
containing my original personal files, that isn't listed
(or, apparently, identified) by Windows. Certainly, I have
listed something like half the memory available than
before, now 128MB RAM 46% free. SR worked before this
incident. But I don't know precisely when SR went duff -
it is only called up when it's needed.

The responses I get from SR are as follows:
Restore my computer to an earlier time currently no
restore points available.
Create a restore point System Restore is not able to
create a Restore Point. Please restart the computer and
run System Restore again.

Restarting always results in a repeat of the above.

Data appears to be being logged. C:\_RESTORE\LOGS contains
3 files: lastsfp.dat, vxdalt1.log and vxdsfp.log, the last
two of 1025 KBytes, all of today's date. ...\ARCHIVES
contains BKUPVXDLASTLOG files of 1025 KB up to today's
date. ...\TEMP contains many .CPY files up to today's date.
.....\SFP folder is empty.

C:\WINDOWS\SYSTEM\RESTORE contains statemgr.exe and
stmgr.exe, amongst other files. Stmgr.exe is also on C:
drive (I copied it to one or other folder in a vain
gesture).

I have tried to fix SR previously... by removing H,S,R
attributes in DOS and renaming... but the automatic
replacement folder delivered the same problem, as above.

Any ideas for a solution are most welcome from all.
-Jeremy Stanford

Try this - see if it forces a first restore point....
Start | Run enter

C:\WINDOWS\SYSTEM\Restore\rstrui.exe /makefirstrestorepoint

(Note - the above should all be one line starting at C: and ending at the
't', and is case-sensitive)


In Registry, check the following item -
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\VxDMon
i
n the RH pane

"StaticVxD"="*VxDMon"
"LogDir"="c:\\_RESTORE\\LOGS"
"TempDir"="c:\\_RESTORE\\TEMP"
"VxdDat"="C:\\_RESTORE\\VxDMon.dat"
"VxdCfg"="C:\\_RESTORE\\VxDMon.cfg"
"SystemFileProtection"="Y"
"SystemRestore"="Y"
"FirstRun"="N"

Is there anything else there?




--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
or
http://www.microsoft.com/presspass/f.../Mar27pmvp.asp

"Jeremy Stanford" wrote in message
...
-----Original Message-----
(thanks, Mike)
--
Noel Paton (MS-MVP 2002-2004, Win9x)


Hi Noel,
I think its your turn on recommendations for restoring
System Restore

The problem is that no restore points can be created.

I have tried both Mike's recommendations previously
[thanks Mike], namely a) SCANREG /FIX and b) deleting the
existing c:\_RESTORE folder using DOS. For good measure
have now tried both again - but the problem is unchanged.

I found after replacing _RESTORE folder that disk space
for SR was at max., I reset it to 317MB, rebooted, but
still no restore points are being created.

Perhaps there is something available on my original WIN ME
CD to restore SR to working order??? I would like any
advice on this.

-Jeremy Stanford

N.B.Below is pasted a copy of yesterday's descriptive post
[Jeremy Stanford - June 11 6:22PM]

Some history of the problem and attempts to fix it...

This may be relevant (?) - Nine months ago I couldn't
enter Windows, no safe mode, only DOS available on
startup. A local 'expert' reinstalled the hard drive by
copying it, he said. So my pc has a hidden partition,
containing my original personal files, that isn't listed
(or, apparently, identified) by Windows. Certainly, I have
listed something like half the memory available than
before, now 128MB RAM 46% free. SR worked before this
incident. But I don't know precisely when SR went duff -
it is only called up when it's needed.

The responses I get from SR are as follows:
Restore my computer to an earlier time currently no
restore points available.
Create a restore point System Restore is not able to
create a Restore Point. Please restart the computer and
run System Restore again.

Restarting always results in a repeat of the above.

Data appears to be being logged. C:\_RESTORE\LOGS contains
3 files: lastsfp.dat, vxdalt1.log and vxdsfp.log, the last
two of 1025 KBytes, all of today's date. ...\ARCHIVES
contains BKUPVXDLASTLOG files of 1025 KB up to today's
date. ...\TEMP contains many .CPY files up to today's date.
....\SFP folder is empty.

C:\WINDOWS\SYSTEM\RESTORE contains statemgr.exe and
stmgr.exe, amongst other files. Stmgr.exe is also on C:
drive (I copied it to one or other folder in a vain
gesture).

I have tried to fix SR previously... by removing H,S,R
attributes in DOS and renaming... but the automatic
replacement folder delivered the same problem, as above.

Any ideas for a solution are most welcome from all.
-Jeremy Stanford

OK, done that. I copied the registry entry before, and
after, running the rstrui.exe action. Registry entries
before and after remained identical. [I tried SR again,
but still no restore points, or after restart.]

This was the registry entry :
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\V
xDMon]
"StaticVxD"="*VxDMon"
"LogDir"="c:\\_RESTORE\\LOGS"
"TempDir"="c:\\_RESTORE\\TEMP"
"VxdDat"="C:\\_RESTORE\\VxDMon.dat"
"VxdCfg"="C:\\_RESTORE\\VxDMon.cfg"
"SystemFileProtection"="Y"
"SystemRestore"="Y"
"FirstRun"="N"
"OOBEInProgress"="Y"

Note the final entry, which was constant. My research
tells me, variously, that an OOBE is an
OutOfBodyExperience, an OutOfBoxExperience to enhance user
satisfaction, or a program associated with Win XP which
starts setup wizards on a new pc (which mine isn't, but it
has had a retread).

So I deleted the OOBE entry from the registry and, on
reboot, experienced an OOBodyE myself. SR window says: New
restore point 12 June 2004 19:35 new.

So PROBLEM SOLVED by understanding the registry. Many
thanks.

The only niggling problem I have remaining is a message on
startup about my NVidia display driver:
RUNDLL
Error in C:\windows\system\NvCpl.dll
Missing entry NVStartup

AFAIK display functions are working fine. Registry entries
at HKLM\Software\Microsoft\Windows\Current version\Run,
include :
NvCplDaemon "RUNDLL32.EXE
C:\WINDOWS\SYSTEM\NvCpl.dll,NvStartup"

This same entry is correctly ticked in System
Configuration Utility | Startup.

So I don't know what RUNDLL thinks the problem is - or
whether I can just ignore it.
-Jeremy Stanford

-----Original Message-----
Try this - see if it forces a first restore point....
Start | Run enter

C:\WINDOWS\SYSTEM\Restore\rstrui.exe /makefirstrestorepoi
nt

(Note - the above should all be one line starting at C:
and ending at the
't', and is case-sensitive)


In Registry, check the following item -

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\Vx
DMon
i
n the RH pane

"StaticVxD"="*VxDMon"
"LogDir"="c:\\_RESTORE\\LOGS"
"TempDir"="c:\\_RESTORE\\TEMP"
"VxdDat"="C:\\_RESTORE\\VxDMon.dat"
"VxdCfg"="C:\\_RESTORE\\VxDMon.cfg"
"SystemFileProtection"="Y"
"SystemRestore"="Y"
"FirstRun"="N"

Is there anything else there?




--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post
messages to NG's
or
http://www.microsoft.com/presspass/f...2001/Mar01/Mar
27pmvp.asp

"Jeremy Stanford"
wrote in message
...
-----Original Message-----
(thanks, Mike)
--
Noel Paton (MS-MVP 2002-2004, Win9x)


Hi Noel,
I think its your turn on recommendations for restoring
System Restore

The problem is that no restore points can be created.

I have tried both Mike's recommendations previously
[thanks Mike], namely a) SCANREG /FIX and b) deleting
the
existing c:\_RESTORE folder using DOS. For good measure
have now tried both again - but the problem is
unchanged.

I found after replacing _RESTORE folder that disk space
for SR was at max., I reset it to 317MB, rebooted, but
still no restore points are being created.

Perhaps there is something available on my original WIN
ME
CD to restore SR to working order??? I would like any
advice on this.

-Jeremy Stanford

N.B.Below is pasted a copy of yesterday's descriptive
post
[Jeremy Stanford - June 11 6:22PM]

Some history of the problem and attempts to fix it...

This may be relevant (?) - Nine months ago I couldn't
enter Windows, no safe mode, only DOS available on
startup. A local 'expert' reinstalled the hard drive by
copying it, he said. So my pc has a hidden partition,
containing my original personal files, that isn't listed
(or, apparently, identified) by Windows. Certainly, I
have
listed something like half the memory available than
before, now 128MB RAM 46% free. SR worked before this
incident. But I don't know precisely when SR went duff -
it is only called up when it's needed.

The responses I get from SR are as follows:
Restore my computer to an earlier time currently no
restore points available.
Create a restore point System Restore is not able to
create a Restore Point. Please restart the computer and
run System Restore again.

Restarting always results in a repeat of the above.

Data appears to be being logged. C:\_RESTORE\LOGS
contains
3 files: lastsfp.dat, vxdalt1.log and vxdsfp.log, the
last
two of 1025 KBytes, all of today's date. ...\ARCHIVES
contains BKUPVXDLASTLOG files of 1025 KB up to today's
date. ...\TEMP contains many .CPY files up to today's
date.
....\SFP folder is empty.

C:\WINDOWS\SYSTEM\RESTORE contains statemgr.exe and
stmgr.exe, amongst other files. Stmgr.exe is also on C:
drive (I copied it to one or other folder in a vain
gesture).

I have tried to fix SR previously... by removing H,S,R
attributes in DOS and renaming... but the automatic
replacement folder delivered the same problem, as above.

Any ideas for a solution are most welcome from all.
-Jeremy Stanford




.

The presence of the OOBEInProgress value suggests that your reinstall of the
operating system did not complete correctly as this should have been deleted
once the system install completed.
--
Mike Maltby MS-MVP



Jeremy Stanford wrote:

OK, done that. I copied the registry entry before, and
after, running the rstrui.exe action. Registry entries
before and after remained identical. [I tried SR again,
but still no restore points, or after restart.]

This was the registry entry :
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\V
xDMon]
"StaticVxD"="*VxDMon"
"LogDir"="c:\\_RESTORE\\LOGS"
"TempDir"="c:\\_RESTORE\\TEMP"
"VxdDat"="C:\\_RESTORE\\VxDMon.dat"
"VxdCfg"="C:\\_RESTORE\\VxDMon.cfg"
"SystemFileProtection"="Y"
"SystemRestore"="Y"
"FirstRun"="N"
"OOBEInProgress"="Y"

Note the final entry, which was constant. My research
tells me, variously, that an OOBE is an
OutOfBodyExperience, an OutOfBoxExperience to enhance user
satisfaction, or a program associated with Win XP which
starts setup wizards on a new pc (which mine isn't, but it
has had a retread).

So I deleted the OOBE entry from the registry and, on
reboot, experienced an OOBodyE myself. SR window says: New
restore point 12 June 2004 19:35 new.

So PROBLEM SOLVED by understanding the registry. Many
thanks.

The only niggling problem I have remaining is a message on
startup about my NVidia display driver:
RUNDLL
Error in C:\windows\system\NvCpl.dll
Missing entry NVStartup

AFAIK display functions are working fine. Registry entries
at HKLM\Software\Microsoft\Windows\Current version\Run,
include :
NvCplDaemon "RUNDLL32.EXE
C:\WINDOWS\SYSTEM\NvCpl.dll,NvStartup"

This same entry is correctly ticked in System
Configuration Utility | Startup.

So I don't know what RUNDLL thinks the problem is - or
whether I can just ignore it.
-Jeremy Stanford

Great - at least that's one problem out of the way!

As to your rundll problem, my first inclination is to go with the 'easy hit'
Reboot to Safe Mode
Open Device Manager
Remove ALL Display Adapters
Remove ALL Monitors
Reboot to Normal Mode - Windows will reinstall the required drivers -
hopefully curing your problem.



--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
or
http://www.microsoft.com/presspass/f.../Mar27pmvp.asp

"Jeremy Stanford" wrote in message
...
OK, done that. I copied the registry entry before, and
after, running the rstrui.exe action. Registry entries
before and after remained identical. [I tried SR again,
but still no restore points, or after restart.]

This was the registry entry :
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\V
xDMon]
"StaticVxD"="*VxDMon"
"LogDir"="c:\\_RESTORE\\LOGS"
"TempDir"="c:\\_RESTORE\\TEMP"
"VxdDat"="C:\\_RESTORE\\VxDMon.dat"
"VxdCfg"="C:\\_RESTORE\\VxDMon.cfg"
"SystemFileProtection"="Y"
"SystemRestore"="Y"
"FirstRun"="N"
"OOBEInProgress"="Y"

Note the final entry, which was constant. My research
tells me, variously, that an OOBE is an
OutOfBodyExperience, an OutOfBoxExperience to enhance user
satisfaction, or a program associated with Win XP which
starts setup wizards on a new pc (which mine isn't, but it
has had a retread).

So I deleted the OOBE entry from the registry and, on
reboot, experienced an OOBodyE myself. SR window says: New
restore point 12 June 2004 19:35 new.

So PROBLEM SOLVED by understanding the registry. Many
thanks.

The only niggling problem I have remaining is a message on
startup about my NVidia display driver:
RUNDLL
Error in C:\windows\system\NvCpl.dll
Missing entry NVStartup

AFAIK display functions are working fine. Registry entries
at HKLM\Software\Microsoft\Windows\Current version\Run,
include :
NvCplDaemon "RUNDLL32.EXE
C:\WINDOWS\SYSTEM\NvCpl.dll,NvStartup"

This same entry is correctly ticked in System
Configuration Utility | Startup.

So I don't know what RUNDLL thinks the problem is - or
whether I can just ignore it.
-Jeremy Stanford

-----Original Message-----
Try this - see if it forces a first restore point....
Start | Run enter

C:\WINDOWS\SYSTEM\Restore\rstrui.exe /makefirstrestorepoi
nt

(Note - the above should all be one line starting at C:
and ending at the
't', and is case-sensitive)


In Registry, check the following item -

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\Vx
DMon
i
n the RH pane

"StaticVxD"="*VxDMon"
"LogDir"="c:\\_RESTORE\\LOGS"
"TempDir"="c:\\_RESTORE\\TEMP"
"VxdDat"="C:\\_RESTORE\\VxDMon.dat"
"VxdCfg"="C:\\_RESTORE\\VxDMon.cfg"
"SystemFileProtection"="Y"
"SystemRestore"="Y"
"FirstRun"="N"

Is there anything else there?




--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post
messages to NG's
or
http://www.microsoft.com/presspass/f...2001/Mar01/Mar
27pmvp.asp

"Jeremy Stanford"
wrote in message
...
-----Original Message-----
(thanks, Mike)
--
Noel Paton (MS-MVP 2002-2004, Win9x)


Hi Noel,
I think its your turn on recommendations for restoring
System Restore

The problem is that no restore points can be created.

I have tried both Mike's recommendations previously
[thanks Mike], namely a) SCANREG /FIX and b) deleting
the
existing c:\_RESTORE folder using DOS. For good measure
have now tried both again - but the problem is
unchanged.

I found after replacing _RESTORE folder that disk space
for SR was at max., I reset it to 317MB, rebooted, but
still no restore points are being created.

Perhaps there is something available on my original WIN
ME
CD to restore SR to working order??? I would like any
advice on this.

-Jeremy Stanford

N.B.Below is pasted a copy of yesterday's descriptive
post
[Jeremy Stanford - June 11 6:22PM]

Some history of the problem and attempts to fix it...

This may be relevant (?) - Nine months ago I couldn't
enter Windows, no safe mode, only DOS available on
startup. A local 'expert' reinstalled the hard drive by
copying it, he said. So my pc has a hidden partition,
containing my original personal files, that isn't listed
(or, apparently, identified) by Windows. Certainly, I
have
listed something like half the memory available than
before, now 128MB RAM 46% free. SR worked before this
incident. But I don't know precisely when SR went duff -
it is only called up when it's needed.

The responses I get from SR are as follows:
Restore my computer to an earlier time currently no
restore points available.
Create a restore point System Restore is not able to
create a Restore Point. Please restart the computer and
run System Restore again.

Restarting always results in a repeat of the above.

Data appears to be being logged. C:\_RESTORE\LOGS
contains
3 files: lastsfp.dat, vxdalt1.log and vxdsfp.log, the
last
two of 1025 KBytes, all of today's date. ...\ARCHIVES
contains BKUPVXDLASTLOG files of 1025 KB up to today's
date. ...\TEMP contains many .CPY files up to today's
date.
....\SFP folder is empty.

C:\WINDOWS\SYSTEM\RESTORE contains statemgr.exe and
stmgr.exe, amongst other files. Stmgr.exe is also on C:
drive (I copied it to one or other folder in a vain
gesture).

I have tried to fix SR previously... by removing H,S,R
attributes in DOS and renaming... but the automatic
replacement folder delivered the same problem, as above.

Any ideas for a solution are most welcome from all.
-Jeremy Stanford




.

Done as suggested - deleting all Display Adapters and
Monitors. The reinstall took several restarts as Windows
progressively graded up.

Display Adapters now again lists the
NVIDIA RIVA TNT2Model64/Model64Pro, as before. I note it
is dated 20/9/2000.
But Monitors now lists just 1 item: Plug and Play Monitor.
Previously it listed 4 items:
Default Monitor
Dell D10225HE
Plug and Play Monitor
Plug and Play monitor

These 4 were perhaps _available_ for installation? But I'm
surprised I don't now have Default Monitor listed.

Display functions nevertheless seem OK. BUT ... the error
message on startup remains! :
RUNDLL
Error in C:\windows\system\NvCpl.dll
Missing entry NVStartup

During the reinstall in Safe Mode there was a message:
"RUNDLL Error loading c:\Windows\System\NvCpl.dll
A DLL initialization routine failed."

The final stage of reinstallation occurred in Normal not
Safe mode, but with settings at 640x480x16clr.

Not sure what I need to do next ...
Any thoughts please?
-Jeremy Stanford


-----Original Message-----
Great - at least that's one problem out of the way!

As to your rundll problem, my first inclination is to go
with the 'easy hit'
Reboot to Safe Mode
Open Device Manager
Remove ALL Display Adapters
Remove ALL Monitors
Reboot to Normal Mode - Windows will reinstall the
required drivers -
hopefully curing your problem.



--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post
messages to NG's
or
http://www.microsoft.com/presspass/f...2001/Mar01/Mar
27pmvp.asp

Default Monitor should only appear if your monitor is not plug and play.

Your drivers are well out of date - I suggest that you go to nVidia's site
and download more recent ones....
http://www.nvidia.com/object/win9x_56.64
should get you there.
Make sure to follow the installation instructions - they get very picky!g

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
or
http://www.microsoft.com/presspass/f.../Mar27pmvp.asp

"Jeremy Stanford" wrote in message
...
Done as suggested - deleting all Display Adapters and
Monitors. The reinstall took several restarts as Windows
progressively graded up.

Display Adapters now again lists the
NVIDIA RIVA TNT2Model64/Model64Pro, as before. I note it
is dated 20/9/2000.
But Monitors now lists just 1 item: Plug and Play Monitor.
Previously it listed 4 items:
Default Monitor
Dell D10225HE
Plug and Play Monitor
Plug and Play monitor

These 4 were perhaps _available_ for installation? But I'm
surprised I don't now have Default Monitor listed.

Display functions nevertheless seem OK. BUT ... the error
message on startup remains! :
RUNDLL
Error in C:\windows\system\NvCpl.dll
Missing entry NVStartup

During the reinstall in Safe Mode there was a message:
"RUNDLL Error loading c:\Windows\System\NvCpl.dll
A DLL initialization routine failed."

The final stage of reinstallation occurred in Normal not
Safe mode, but with settings at 640x480x16clr.

Not sure what I need to do next ...
Any thoughts please?
-Jeremy Stanford


-----Original Message-----
Great - at least that's one problem out of the way!

As to your rundll problem, my first inclination is to go
with the 'easy hit'
Reboot to Safe Mode
Open Device Manager
Remove ALL Display Adapters
Remove ALL Monitors
Reboot to Normal Mode - Windows will reinstall the
required drivers -
hopefully curing your problem.



--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post
messages to NG's
or
http://www.microsoft.com/presspass/f...2001/Mar01/Mar
27pmvp.asp

-----Original Message-----

.. . .Your drivers are well out of date - I suggest that
you go to nVidia's site
and download more recent ones....
-- Noel Paton (MS-MVP 2002-2004, Win9x)

The NvCpl.dll problem arose after I did just that ... I
updated the driver about two weeks ago, then I reverted to
the ME CD, now I've reinstalled ...

I'll update again cautiously!

-Jeremy Stanford


"Jeremy Stanford"
wrote in message
...
Done as suggested - deleting all Display Adapters and
Monitors. The reinstall took several restarts as Windows
progressively graded up.

Display Adapters now again lists the
NVIDIA RIVA TNT2Model64/Model64Pro, as before. I note it
is dated 20/9/2000.
But Monitors now lists just 1 item: Plug and Play
Monitor.
Previously it listed 4 items:
Default Monitor
Dell D10225HE
Plug and Play Monitor
Plug and Play monitor

These 4 were perhaps _available_ for installation? But
I'm
surprised I don't now have Default Monitor listed.

Display functions nevertheless seem OK. BUT ... the
error
message on startup remains! :
RUNDLL
Error in C:\windows\system\NvCpl.dll
Missing entry NVStartup

During the reinstall in Safe Mode there was a message:
"RUNDLL Error loading c:\Windows\System\NvCpl.dll
A DLL initialization routine failed."

The final stage of reinstallation occurred in Normal not
Safe mode, but with settings at 640x480x16clr.

Not sure what I need to do next ...
Any thoughts please?
-Jeremy Stanford

Update to my last message [8:59AM]. Device Manager lists
NVidia, as I stated, with date of 20/9/2000 and a file
version of 4.12.01. But Update Driver responds that I'm
using the best driver.
Control Panel now has an individual selection for NVidia
(since my previous update). The NVidia Desktop Manager
panel display gives the file version as 56.64 (i.e. the
latest version).

Add/Remove programs lists 2 Nvidia items: NVIDIA Display
Driver and NVIDIA Windows 95/98/ME Display Drivers.

It seems I do have the latest 54.64 version installed. Is
it possible there is a conflict arising - causing the
Rundll problem - because the previous version was not
removed during my original update 2 weeks ago? (I am
prepared to reinstall 54.64 from the Web if necessary).

-Jeremy Stanford

-----Original Message-----
-----Original Message-----

.. . .Your drivers are well out of date - I suggest that
you go to nVidia's site
and download more recent ones....
-- Noel Paton (MS-MVP 2002-2004, Win9x)

The NvCpl.dll problem arose after I did just that ... I
updated the driver about two weeks ago, then I reverted
to
the ME CD, now I've reinstalled ...

I'll update again cautiously!

-Jeremy Stanford