Device Manager, no Monitors branch

  • Thread starter Thread starter Roger R
  • Start date Start date
Re: Device Manager, no Monitors branch


"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
news:k8q1q3l6n26fpsvu0cluu72mv0h75c8qtg@4ax.com...
> On Wed, 30 Jan 2008 12:59:15 -0500, "MEB" <meb@not here@hotmail.com>
> put finger to keyboard and composed:
>
>> You mentioned Powerstrip as a potential, but how about DCCtest to see if
>>the card and monitor are communicating?
>>http://www.entechtaiwan.com/util/legacy.shtm
>
> Sounds good to me.

and it was good too.

DDC test appears to display the correct information.

DDC test Report:

DDC status:
Video BIOS: Video Bios reports support for DDC.
Monitor: DDC1/2B supported (less than 2 sec transfer time)

Model identifiers:
Manufacturer - Hansol Electronics
Model ID - HSL06AD
Serial No -xxx
manufac _ date
EDID ver - 1.02

Display perameters:
Video type - Analogue(0.7 V)
Image size 320 x 240 mmm (17 ")
Max H freq - 63 khz
max V freq - at least 100 Hz
max resolution - 1800 x 1008 (est)

Power management:
Standby - tick
suspend - tick
Off - tick

Gamma:
2.26

Timing descriptions:
GTF support - n/a
List of display resolutions:
640 x 480 at 60 Hz
640 x 480 at 75 Hz
640 x 480 at 85 Hz
720 x 400 at 70 Hz -VGA
800 x 600 at 75 Hz
800 x 600 at 85 Hz
1024 x 768 at 75 Hz
720 x 405 at 84 Hz
640 x 480 at 100 Hz
800 x 600 at 100 Hz
1024 x 768 at 85 Hz
1280 x 1024 at 60Hz

The above report suggest the Monitor is talking to the computer and
reporting the correct data in its Eprom.

Roger R
 
Re: Device Manager, no Monitors branch

Okay, just trying to collate potential issues and answers.

--

MEB
http://peoplescounsel.orgfree.com
_________


"Roger R" <d-e-c-o-d-e-r@clara.co.uk> wrote in message
news:1201784873.56849.0@demeter.uk.clara.net...
|
| "MEB" <meb@not here@hotmail.com> wrote in message
| news:u5UgLPJYIHA.1532@TK2MSFTNGP04.phx.gbl...
| > Ah glad you brought that to my attention, I remember that
| > thread/discussion
| > though I did not recognize the poster or problem.
|
|
| You appear to be suggesting I am connected to that poster.
| I am not.
|
|
| > Apparently PowerStrip was not used to pull the info per that thread and
| > the
| > suggestions at that time..
| > Perhaps this time your help will be accepted.
|
| The problem with Power Strip is that though it is small enough to be
| transferred by floppy and appears to install ok it does not run.
|
| 'DCC test' you propose in your supplementary reply to Franc Zabkar works
OK
| and I have commented on the results in response to your post recommending
| it.
|
| Roger R
|
|
 
Re: Device Manager, no Monitors branch



"Roger R" <d-e-c-o-d-e-r@clara.co.uk> wrote in message
news:1201785920.57229.0@demeter.uk.clara.net...
|
| "Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
| news:k8q1q3l6n26fpsvu0cluu72mv0h75c8qtg@4ax.com...
| > On Wed, 30 Jan 2008 12:59:15 -0500, "MEB" <meb@not here@hotmail.com>
| > put finger to keyboard and composed:
| >
| >> You mentioned Powerstrip as a potential, but how about DCCtest to see
if
| >>the card and monitor are communicating?
| >>http://www.entechtaiwan.com/util/legacy.shtm
| >
| > Sounds good to me.
|
| and it was good too.
|
| DDC test appears to display the correct information.
|
| DDC test Report:
|
| DDC status:
| Video BIOS: Video Bios reports support for DDC.
| Monitor: DDC1/2B supported (less than 2 sec transfer time)
|
| Model identifiers:
| Manufacturer - Hansol Electronics
| Model ID - HSL06AD
| Serial No -xxx
| manufac _ date
| EDID ver - 1.02
|
| Display perameters:
| Video type - Analogue(0.7 V)
| Image size 320 x 240 mmm (17 ")
| Max H freq - 63 khz
| max V freq - at least 100 Hz
| max resolution - 1800 x 1008 (est)
|
| Power management:
| Standby - tick
| suspend - tick
| Off - tick
|
| Gamma:
| 2.26
|
| Timing descriptions:
| GTF support - n/a
| List of display resolutions:
| 640 x 480 at 60 Hz
| 640 x 480 at 75 Hz
| 640 x 480 at 85 Hz
| 720 x 400 at 70 Hz -VGA
| 800 x 600 at 75 Hz
| 800 x 600 at 85 Hz
| 1024 x 768 at 75 Hz
| 720 x 405 at 84 Hz
| 640 x 480 at 100 Hz
| 800 x 600 at 100 Hz
| 1024 x 768 at 85 Hz
| 1280 x 1024 at 60Hz
|
| The above report suggest the Monitor is talking to the computer and
| reporting the correct data in its Eprom.
|
| Roger R
|

Okay then, I'll modify my original suggestions and checks to include
downloading one of the nVidia cleanup tools to COMPLETELY remove any old
settings.
nVidia has always required {in 9X} an absolutely clean registry [of
adapters and settings] to properly install. Also, as previously indicated,
you MUST have the default VGA display. IF the driver was the 81 version or
above, then you will need to do additional manual cleanup/checking before
attempting a re-install.

After running the cleanup tool, use something like RegSeeker to search the
registry for any that might have been missed. Check the Shared DLL key as
well for references to nv** dlls and folders. Also check the INF directory
for old nVidia references/INFS. you may find nvagp.inf or nvaml.inf,
manually remove them
Again, the default monitor and adapter MUST be there PRIOR to installing
nVidia driver. The issue is, the default monitor will not be installed until
starting in Normal Mode, so completely "default the system" and try to
restart in Normal Mode BEFORE attempting to install the nVidia driver.
One issue that MAY cause a problem is OpenGL. Might check the registry for
entries for that and post what is found.

As another issue: if there was some special INF or installer application
for your display, you will need to re-install/run such. I generally prefer
to do this before installation of nVidia drivers, though some will not
install without adapter support so do whatever is required.

--

MEB
http://peoplescounsel.orgfree.com
_________
 
Re: Device Manager, no Monitors branch

On Thu, 31 Jan 2008 12:57:29 -0000, "Roger R"
<d-e-c-o-d-e-r@clara.co.uk> put finger to keyboard and composed:

>"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
>news:f0enp3t79fufgv9579f3ud79199sop19vk@4ax.com...
>>
>> The Vendor and Device IDs belong to the NVidia graphics adapter but
>> HSL06AD appears to be the model identifier for your monitor (HanSoL
>> C776).
>
>Yes, the monitor is indeed a C766.

>> Tilicharger le pilote http://www.hansol-uk.com/support/drivers.html
>
>I am unable to get any 'driver' or inf file from the above link.

I found a universal Fijitsu "driver" set here:
http://members.driverguide.com/driver/detail.php?driverid=34015

It's basically just a universal INF file. I suspect the Fujitsu C776
may be the same monitor as yours.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.
 
Re: Device Manager, no Monitors branch

"Roger R" <d-e-c-o-d-e-r@clara.co.uk> wrote in message news:1201780474.55257.0@demeter.uk.clara.net...
> news:1201269898.24447.0@proxy00.news.clara.net...
> > WIN98SE on Desktop.
> > Running only in Safe Mode.
> > Device Manager has no 'Monitors' branch.
> > So I can't install a monitor.
> > How can this be restored?
>
> Make sure your display adapter is configured properly. Start
> the computer in DOS or open a DOS box and type the
> following five lines. The name and manufacturer of the display
> adapter should appear at the right side of the screen. If this
> doesn't match what is shown in Device Manager, you will
> need to download and install the correct drivers for the adapter.
> If you want help with this, please repost with the information.
> Please note that the characters in line two are zeroes.
>
> debug
> dc000:0
> d
> d
> Q
>
> Almost a week later I've been able to do the above...
>
> Under dc000:0 =
> U.~.K7400.L.w.V1
> DEO ......I...IB
> M VGA Compatible
> ........10/18/02
> ................
> ..}.............
> ................
> PMIDj.m.........
>
> Under d =
> ...7..NV....0.a.
> ...........y......
> ....P...q(Kk.k.v
> sv.v....N........
> ..A.kH1.'.....v
> .............J.P
> .....V.Y......1.
> 1....>.T.\..1.1.1
>
> under d (2) =
> ....PCIR..q.....
> ....~.......GF4M
> X440-SE VGA BIOS
> ................
> ................
> ................
> ............Ver
> sion 4.17.00.61V
>
> (number of multiple dots in lines may not be accurate)

Looks like an Aopen. See
http://download.aopen.com.tw/userdownload_List.aspx?RecNo=8345&Model=GF4MX440SE-V64(A4)

Ben
 
Re: Device Manager, no Monitors branch



"Roger R" <d-e-c-o-d-e-r@clara.co.uk> wrote in message
news:1202341606.28766.0@damia.uk.clara.net...
|
| "MEB" <meb@not here@hotmail.com> wrote in message
| news:%23kJtG9DZIHA.536@TK2MSFTNGP06.phx.gbl...
| >
| > Okay then, I'll modify my original suggestions and checks to include
| > downloading one of the nVidia cleanup tools to COMPLETELY remove any old
| > settings.
| > nVidia has always required {in 9X} an absolutely clean registry [of
| > adapters and settings] to properly install. Also, as previously
indicated,
| > you MUST have the default VGA display. IF the driver was the 81 version
or
| > above, then you will need to do additional manual cleanup/checking
before
| > attempting a re-install.
| >
| > After running the cleanup tool, use something like RegSeeker to search
the
| > registry for any that might have been missed. Check the Shared DLL key
as
| > well for references to nv** dlls and folders. Also check the INF
directory
| > for old nVidia references/INFS. you may find nvagp.inf or nvaml.inf,
| > manually remove them
| > Again, the default monitor and adapter MUST be there PRIOR to installing
| > nVidia driver. The issue is, the default monitor will not be installed
| > until
| > starting in Normal Mode, so completely "default the system" and try to
| > restart in Normal Mode BEFORE attempting to install the nVidia driver.
| > One issue that MAY cause a problem is OpenGL. Might check the registry
for
| > entries for that and post what is found.
| >
| > As another issue: if there was some special INF or installer
application
| > for your display, you will need to re-install/run such. I generally
prefer
| > to do this before installation of nVidia drivers, though some will not
| > install without adapter support so do whatever is required.
| >
|
| Thanks for your detailed advice.
| Some success.
| The Monitors branch in Device Manager has now re-appeared.
|
| The root of the problem appears to have been the NVIDIA Forceware.
|
| In another group I'd previously raised a problem of Windows stalling
| on loading with the message:
| 'Windows protection error, you need to restart your computer'
| The message re-appered if the computer was restarted, the only solution
| being to hold down the control key during bootup and select 'Safemode'.
|
| In response to that situation 'Glen Ventura' had questioned the graphics
| card drivers, but I had been assertive they ok as they were the latest
| drivers 81.98 and were correctly (and recently) installed.
| They were correctly installed but appear to be the trouble.

Okay, Glen was likely dead-on, we've discussed nVidia issue before in this
group.
Though I am once again using the 81.98 drivers, I have had issues with them
in the past. For some reason the drivers seem to get corrupted occasionally,
and in my case, I have never gotten the 81 drivers to uninstall properly,
always having to manually remove them.

|
| The NVIDIA USA site has a FAQ on the Windows protection error.
| FAQ Answer ID 40.
| 'Windows Protection Error or Windows hangs during startup after installing
| NVIDIA Forceware unified display drivers.'
| This describes various motherboard incompatibilities for earlier boards
and
| other possible BIOS issues.
|
| The article has a link to recommended motherboard BIOS settings, (the
| resulting page is in Spanish) but appears to be in English as Answer ID
805.
|
| Checking the list against my BIOS, and found all ok except:
| Video BIOS Shadowing: Disable. Mine was set to 'Enable'.
| Changed to 'Disable' but have no idea if that made any difference.

It may, and is what is generally recommended. Older video cards like the
nVidia128 needed that but the newer generally don't.

|
| Then set about removing the 81.98 drivers by clicking remove in Device
| Manager.
| At this stage I haven't removed the NVIDIA drivers completely as you
| described, but can't easily find the NVIDIA removal utility.
| Found guru3d site, but have not got the remove tool yet.

That's one of the tools, try that one.

|
| Also removed the drivers for the Firewire IEEE 1394 for good measure.
| Restated Windows and it wanted the firewire drivers first which went ok.
| Then it wanted the drivers for the graphics card and it decided to
install:
| Standard PCI Graphics Adaptor (VGA)

EXCELLENT. It has to be installed before you can successfully install the
nVidia driver..

|
| Restarted Windows, but still problems with protection error and no monitor
| branch.

Right, when the default PCI installed, it indicated the nVidia driver was
NOT properly installed, though the registry still held entries for the
nVidia driver.

|
| Then in Control panel uninstall NVIDIA Display Manager.

Really, it actually uninstalled or did it error out?

|
| Restart computer and this time starts normally (but in 640 X 480) but with
| all device drivers loaded.
| (things in system tray)
| Look in Device Manager - still no monitor branch
| In Control panel click Display, click all the tabs in turn.
| In settings unable to change resolution.
|
| Go back to Device Manager and, lo and behold, Monitors branch appears.
| This branch identifies monitor correctly as C776 (standard monitor types).

Weird, slow refresh times, but at least there will be the default and
monitor branch. The issue likely remains with some errant nVidia entries and
possible some left over files. Use the cleanup tool, and check with whatever
registry tool you use, for nVidia entries. Then do the previously posted
check for old nVidia files. Cleanup as best you can before attempting a
re-install. Run back through the older posts in this discussion for other
tihngs to check. Also, while in the BIOS, did you make sure everything was
setup properly?

*AND Do these additional things though before attempting the install*:

1. To save potential issues, run - Find New Harware - and see if anything
needs installed/re-installed.

2. Try to save the registry and copy that to another folder. Look in
C:\WINDOWS\SYSBCKUP {or whatever your configuration is} for the date and
time stamp of the proper rb00*.cab.

3. Boot to Safe Mode, check for ghost/improper drivers, remove any found.
If found and removed, restart, and go back to the beginning of this list.

4. Boot to DOS, delete the win386.swp file in Windows folder.

5. Restart in Normal Mode. Check Device Manager again, and make sure
everything is as it should be. Reboot one more time to Normal Mode and
install your driver.

|
| So that's where I am now:
| Windows starts normally but is stuck at 640 x 480 probably because I
haven't
| installed correct drivers for the card (AGP)

And that's all you will get until you install the adapter driver...

|
| And I haven't yet run any utility to completely remove the old NVIDIA
81.98
| drivers, or checked out the registry for NVIDIA entries. Do you think it
| is still worth the hassle of doing this?

Don't try a re-install without do that.... you likely will be having
difficulties otherwise... you can do both or just search the registry, just
make sure you get it all.

|
| I'm not out of the woods yet but there is now light at the end of the
| tunnel.
| I think I'll go back to the old NVIDIA drivers that are on the disk that
| came in the box with the card. They worked ok, what do you think?
|
| Roger R
|
|

Potentially, but first, open the CD/disk installer [with an unzip program
if necessary] and check the INF file for the version. The 77.72 driver
un-installs [meaning proper registry entries] and was a fairly stable driver
[some clipping issues and other anomalies on certain cards]. DirectX. 9.0c
works well with it..

You should find something like this:

[version]
DriverVer = 06/15/2005, 7.7.7.2
LayoutFile=layout.inf

Then again, sometimes the manufacturer tweaked one of nVidia's drivers
specifically for the card it was sent with, and that driver may be the best
to use if the manufacturer didn't provide any updates.. the nVidia provided
drivers are, after all, just generic.

Let us know how it works out...

--

MEB
http://peoplescounsel.orgfree.com
_________
 
Re: Device Manager, no Monitors branch


"MEB" <meb@not here@hotmail.com> wrote in message
news:%23kJtG9DZIHA.536@TK2MSFTNGP06.phx.gbl...
>
> Okay then, I'll modify my original suggestions and checks to include
> downloading one of the nVidia cleanup tools to COMPLETELY remove any old
> settings.
> nVidia has always required {in 9X} an absolutely clean registry [of
> adapters and settings] to properly install. Also, as previously indicated,
> you MUST have the default VGA display. IF the driver was the 81 version or
> above, then you will need to do additional manual cleanup/checking before
> attempting a re-install.
>
> After running the cleanup tool, use something like RegSeeker to search the
> registry for any that might have been missed. Check the Shared DLL key as
> well for references to nv** dlls and folders. Also check the INF directory
> for old nVidia references/INFS. you may find nvagp.inf or nvaml.inf,
> manually remove them
> Again, the default monitor and adapter MUST be there PRIOR to installing
> nVidia driver. The issue is, the default monitor will not be installed
> until
> starting in Normal Mode, so completely "default the system" and try to
> restart in Normal Mode BEFORE attempting to install the nVidia driver.
> One issue that MAY cause a problem is OpenGL. Might check the registry for
> entries for that and post what is found.
>
> As another issue: if there was some special INF or installer application
> for your display, you will need to re-install/run such. I generally prefer
> to do this before installation of nVidia drivers, though some will not
> install without adapter support so do whatever is required.
>

Thanks for your detailed advice.
Some success.
The Monitors branch in Device Manager has now re-appeared.

The root of the problem appears to have been the NVIDIA Forceware.

In another group I'd previously raised a problem of Windows stalling
on loading with the message:
'Windows protection error, you need to restart your computer'
The message re-appered if the computer was restarted, the only solution
being to hold down the control key during bootup and select 'Safemode'.

In response to that situation 'Glen Ventura' had questioned the graphics
card drivers, but I had been assertive they ok as they were the latest
drivers 81.98 and were correctly (and recently) installed.
They were correctly installed but appear to be the trouble.

The NVIDIA USA site has a FAQ on the Windows protection error.
FAQ Answer ID 40.
'Windows Protection Error or Windows hangs during startup after installing
NVIDIA Forceware unified display drivers.'
This describes various motherboard incompatibilities for earlier boards and
other possible BIOS issues.

The article has a link to recommended motherboard BIOS settings, (the
resulting page is in Spanish) but appears to be in English as Answer ID 805.

Checking the list against my BIOS, and found all ok except:
Video BIOS Shadowing: Disable. Mine was set to 'Enable'.
Changed to 'Disable' but have no idea if that made any difference.

Then set about removing the 81.98 drivers by clicking remove in Device
Manager.
At this stage I haven't removed the NVIDIA drivers completely as you
described, but can't easily find the NVIDIA removal utility.
Found guru3d site, but have not got the remove tool yet.

Also removed the drivers for the Firewire IEEE 1394 for good measure.
Restated Windows and it wanted the firewire drivers first which went ok.
Then it wanted the drivers for the graphics card and it decided to install:
Standard PCI Graphics Adaptor (VGA)

Restarted Windows, but still problems with protection error and no monitor
branch.

Then in Control panel uninstall NVIDIA Display Manager.

Restart computer and this time starts normally (but in 640 X 480) but with
all device drivers loaded.
(things in system tray)
Look in Device Manager - still no monitor branch
In Control panel click Display, click all the tabs in turn.
In settings unable to change resolution.

Go back to Device Manager and, lo and behold, Monitors branch appears.
This branch identifies monitor correctly as C776 (standard monitor types).

So that's where I am now:
Windows starts normally but is stuck at 640 x 480 probably because I haven't
installed correct drivers for the card (AGP)

And I haven't yet run any utility to completely remove the old NVIDIA 81.98
drivers, or checked out the registry for NVIDIA entries. Do you think it
is still worth the hassle of doing this?

I'm not out of the woods yet but there is now light at the end of the
tunnel.
I think I'll go back to the old NVIDIA drivers that are on the disk that
came in the box with the card. They worked ok, what do you think?

Roger R
 
Re: Device Manager, no Monitors branch

Roger R wrote:
> And I haven't yet run any utility to completely remove the old NVIDIA
> 81.98 drivers, or checked out the registry for NVIDIA entries. Do
> you think it is still worth the hassle of doing this?
>
> I'm not out of the woods yet but there is now light at the end of the
> tunnel.
> I think I'll go back to the old NVIDIA drivers that are on the disk
> that came in the box with the card. They worked ok, what do you
> think?
>
> Roger R
Uninstall all old Nvidia drivers and then use the Nvidia special uninstall
program to get rid of the rest.
Now,after rebooting the required number of times, install the Nvidia drivers
of your choice.
PS: Also make sure any other mfg vid drivers from possibly another vid card
or an onboard vid card are also deleted.
 
Re: Device Manager, no Monitors branch

"Roger R" <d-e-c-o-d-e-r@clara.co.uk> wrote in message
news:1202341606.28766.0@damia.uk.clara.net...
>
> "MEB" <meb@not here@hotmail.com> wrote in message
> news:%23kJtG9DZIHA.536@TK2MSFTNGP06.phx.gbl...
>>
>> Okay then, I'll modify my original suggestions and checks to include
>> downloading one of the nVidia cleanup tools to COMPLETELY remove any old
>> settings.
>> nVidia has always required {in 9X} an absolutely clean registry [of
>> adapters and settings] to properly install. Also, as previously indicated,
>> you MUST have the default VGA display. IF the driver was the 81 version or
>> above, then you will need to do additional manual cleanup/checking before
>> attempting a re-install.
>>
>> After running the cleanup tool, use something like RegSeeker to search the
>> registry for any that might have been missed. Check the Shared DLL key as
>> well for references to nv** dlls and folders. Also check the INF directory
>> for old nVidia references/INFS. you may find nvagp.inf or nvaml.inf,
>> manually remove them
>> Again, the default monitor and adapter MUST be there PRIOR to installing
>> nVidia driver. The issue is, the default monitor will not be installed
>> until
>> starting in Normal Mode, so completely "default the system" and try to
>> restart in Normal Mode BEFORE attempting to install the nVidia driver.
>> One issue that MAY cause a problem is OpenGL. Might check the registry for
>> entries for that and post what is found.
>>
>> As another issue: if there was some special INF or installer application
>> for your display, you will need to re-install/run such. I generally prefer
>> to do this before installation of nVidia drivers, though some will not
>> install without adapter support so do whatever is required.
>>
>
> Thanks for your detailed advice.
> Some success.
> The Monitors branch in Device Manager has now re-appeared.
>
> The root of the problem appears to have been the NVIDIA Forceware.
>
> In another group I'd previously raised a problem of Windows stalling
> on loading with the message:
> 'Windows protection error, you need to restart your computer'
> The message re-appered if the computer was restarted, the only solution
> being to hold down the control key during bootup and select 'Safemode'.
>
> In response to that situation 'Glen Ventura' had questioned the graphics
> card drivers, but I had been assertive they ok as they were the latest
> drivers 81.98 and were correctly (and recently) installed.
> They were correctly installed but appear to be the trouble.
>
> The NVIDIA USA site has a FAQ on the Windows protection error.
> FAQ Answer ID 40.
> 'Windows Protection Error or Windows hangs during startup after installing
> NVIDIA Forceware unified display drivers.'
> This describes various motherboard incompatibilities for earlier boards and
> other possible BIOS issues.
>
> The article has a link to recommended motherboard BIOS settings, (the
> resulting page is in Spanish) but appears to be in English as Answer ID 805.
>
> Checking the list against my BIOS, and found all ok except:
> Video BIOS Shadowing: Disable. Mine was set to 'Enable'.
> Changed to 'Disable' but have no idea if that made any difference.
>
> Then set about removing the 81.98 drivers by clicking remove in Device
> Manager.
> At this stage I haven't removed the NVIDIA drivers completely as you
> described, but can't easily find the NVIDIA removal utility.
> Found guru3d site, but have not got the remove tool yet.
>
> Also removed the drivers for the Firewire IEEE 1394 for good measure.
> Restated Windows and it wanted the firewire drivers first which went ok.
> Then it wanted the drivers for the graphics card and it decided to install:
> Standard PCI Graphics Adaptor (VGA)
>
> Restarted Windows, but still problems with protection error and no monitor
> branch.
>
> Then in Control panel uninstall NVIDIA Display Manager.
>
> Restart computer and this time starts normally (but in 640 X 480) but with
> all device drivers loaded.
> (things in system tray)
> Look in Device Manager - still no monitor branch
> In Control panel click Display, click all the tabs in turn.
> In settings unable to change resolution.
>
> Go back to Device Manager and, lo and behold, Monitors branch appears.
> This branch identifies monitor correctly as C776 (standard monitor types).
>
> So that's where I am now:
> Windows starts normally but is stuck at 640 x 480 probably because I haven't
> installed correct drivers for the card (AGP)
>
> And I haven't yet run any utility to completely remove the old NVIDIA 81.98
> drivers, or checked out the registry for NVIDIA entries. Do you think it
> is still worth the hassle of doing this?
>
> I'm not out of the woods yet but there is now light at the end of the tunnel.
> I think I'll go back to the old NVIDIA drivers that are on the disk that
> came in the box with the card. They worked ok, what do you think?

There is a tool at the Guru3D site:
Guru3D - Driver Sweeper
http://www.guru3d.com/index.php?page=driversweeper

I don't know if it works on Win98....the page states it is "fully tested on Windows
2000, XP and Vista" but does not indicate if it works on earlier systems. All you
can do is try.

Before running this or any removal tool, uninstall the drivers and any other
nVidia-related items via Add/Remove Programs.

After you have gotten the drivers and utilities removed, reboot and then install the
drivers from the disc that came with the card.
--
Glen Ventura, MS MVP Windows, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm
 
Re: Device Manager, no Monitors branch



"Roger R" <d-e-c-o-d-e-r@clara.co.uk> wrote in message
news:1202567374.87471.0@iris.uk.clara.net...
|
| "MEB" <meb@not here@hotmail.com> wrote in message
| news:%23JUmIdUaIHA.6140@TK2MSFTNGP02.phx.gbl...
| > | Then in Control panel uninstall NVIDIA Display Manager.
| > Really, it actually uninstalled or did it error out?
|
| No that uninstalled ok, but that refers to the Display Manager desktop
| software.
| The NVIDIA Display Driver did red error out. It still remains.

Yeah, that's what it generally does. Leaves too many entries and files
supposedly to load.

|
| > Let us know how it works out...
|
| Report Saturday 09 Feb 08
|
| Installed Guru3d.
| Notes say only works in Win 2000 and XP, but go ahead anyway - even when
| asked if I'm really really sure I want to proceed.
|
| In Driver Sweeper window move NVIDIA Display to 'remove' window and
activate
| sweep.
| Blue band goes across bottom of application window.
| View log: deleted folder (\NVIDIA)
| So this did not appear to find anything else.
| ----
|
| RegSweeper:
|
| Nothing much appeared to happen and nothing was indicated to be removed.
|
| Registry (using regedit)
| HKCR> A lot of entries listed here, but are presumably just listing
possible
| types.
| A lot of :
| NvCpl.xxxxx
| NVdmcpl.xxxx
| single entry for nView.profile\shell\open\command
| data:"rundll32.exe nview.dll,nViewCmd loadprofile shell"%1""
|
| HKLM\Software\NVIDIA Corporation
| data: Default (value not set)
|
| Searching for: NVIDIA:
| HKU\.DEFAULT\installLocationsMRU
| Data: (amongst others) c "E:\NVIDIA\"
| f "C:WINDOWS\SYSTEM\NvInst"
|
| HKU\.DEFAULT\Software\MartS\TotalUnistall data: LastAppRunPath
|
| Searching for: Nv**, or nv**
| no results
| ----
|
| Using CCleaner:
| Registry:
| C:\WINDOWS\SYSTEM\nview.dll,18 (HKCR\nview profile\default icon)
| the following in HKCR\CLSID\
| ActiveX\COM Issue InProcServer32\C:\WINDOWS\SYSTEM\NVCPL.DLL
| ActiveX\COM Issue InProcServer32\C:\WINDOWS\SYSTEM\NVCPL.DLL
| ActiveX\COM Issue InProcServer32\C:\WINDOWS\SYSTEM\NVCPL.DLL
| ActiveX\COM Issue InProcServer32\C:\WINDOWS\SYSTEM\NVCPL.DLL
| each of the above with different data keys.
| HKLM\Software\NVIDIA Corporation (as noted in regedit above)
|
| The above all cleaned. (backed up)
|
| In applications:
| NVIDIA Display Driver (red error out)
|
| after this shutdown for restart:
| fatal exception error on closedown.

Yeah that first shutdown/restart generally gives that error, or depending
upon the system, it occurs during the uninstallation.

IF you're sure you removed all of the entries [though the MRU can be left]
then it should also have removed any Start Menu entires and Control Panel
entries. Reading further below I see that you still have it showing so
something was missed

| ----------------
|
| Started normally.
| backup registry
|
| Forced scan for hardware:
| Followed instruction as in MS article 317187 (Rerun hardware detection)
| It scanned for hardware, asked for nothing, and then restarted.
|
| Checked Device manger - no yellow question marks or other warnings
| -------------
| Checking Device manger for duplicate entries when in in Safemode
| Display adaptors has only one single entry :
| Standard PCI Graphics Adaptor (VGA) (as previously noted)
|
| Monitors:
| Plug and Play Monitor
| -------------------------
|
| Re- the Disk that came originally with the card:
|
| > Potentially, but first, open the CD/disk installer [with an unzip
program
| > if necessary] and check the INF file for the version. The 77.72 driver
| > You should find something like this:
| > [version]
| > DriverVer = 06/15/2005, 7.7.7.2
| > LayoutFile=layout.inf
| >
| --------------
| On disk that came with the card
|
| Not sure where I'm looking here, but under
| NVIDIA the following are listed:
| 5X00
| WIN2K_XP
| WIN9X_ME In .inf file: driver ver 3.0.8.2
| WINNT4
| 6X00
| WIN2K_XP
| WIN9X_ME In .inf file:driver ver 3.0.8.2
| WINNT4
| 7X00
| WIN2K_XP
| WIN9X_ME In .inf file:driver ver 4.1.0.4
| WINNT4
| 7228
| WIN2K_XP
| WIN9X_ME In .inf file:driver ver 4.1.0.4
| 7300
| WIN2K_XP
| WIN9X_ME In .inf file:driver ver 4.1.0.4
|
| Which of those are relevant I don't know. The correct files are found on
| installation without having to choose any of the above.

Hmm, by the version indications those appear to be from the Detonator
Series. [3.37 - 03-22-99; 3.53 version 10-15-99; 3.68 12-30-99;
4.12.01.0522 - 05/18/00
What are the actual file dates?

So did I miss whether you verified that adapter as the AOpen 440 as was
identified/suggested ?

|
| If they are the files versions do seem quite old - nowhere near your ver
7,
| so perhaps i should download something like 7.7.7.2 from somewhere, I
think
| guru3d has library of all the NVIDIA driver files, but as noted before
| perhaps the best route is to install the original drivers from the disk
and
| then update
| later?

With a card that old, I suppose the first thing we should also do, is
verify that the adapter's fan is still working, is it? If not or it never
had one then the card MAY be having some additional issues with occasional
video waivering or other like flickers and such, or even video lockup, which
indicate partial eletromigration/degradation within the adapter chip.

If none is occurring then try the original drivers to test the card... you
may not notice the issue in 2d [standard Windows] though certainly in video
or 3d applications.

| --------------------
|
| In conclusion, evrything appears ok except I'm stuck with the NVIDIA
Display
| drivers in Control panel >Add/Remove software that can't be shifted.
| Attempts at removal result in Red error out using all methods tried so
far.

If the driver still shows in Device Manager you still have traces left in
the registry. Though you used some good tools and even regedit apparently,
something was missed. Had you successfully removed all the registry entries
then it wouldn't apear in Device Manager or Uninstall Programs.
And did you do the search in your Windows folder for files named nv*.* ? I'm
thinking that the INF file is still in the INF folder. Does the INF folder
still contain the nv3disp.inf, nvagp.inf, or nvaml1.inf? If so remove it.

|
| In your opinion would I be better off buying an ATI type card for a fresh
| start?
| An inexpensive card would do, I'm not using it for gaming, just ordinary
| windows apps, and video on screen. Could you recommend anything?
|
| Roger R
|
| Supplementary Data:
| Mainboard is: ASUS A7V 133 employing chipset VIA Apollo KT133A
| AGP 2.0 spec for 4X, 2X and 1X
|

If your card showed any signs indicating potential degradation, then
replace it. You indicate no gaming, but the video issues require at least a
capable card so yes an ATI would be a good replacement. Your AGP 2.0 will
make it potentially difficult to find one, so if you can't, try a PCI based
card if you need to replace the adapter.

--

MEB
http://peoplescounsel.orgfree.com
_________
 
Re: Device Manager, no Monitors branch


"MEB" <meb@not here@hotmail.com> wrote in message
news:%23JUmIdUaIHA.6140@TK2MSFTNGP02.phx.gbl...
> | Then in Control panel uninstall NVIDIA Display Manager.
> Really, it actually uninstalled or did it error out?

No that uninstalled ok, but that refers to the Display Manager desktop
software.
The NVIDIA Display Driver did red error out. It still remains.

> Let us know how it works out...

Report Saturday 09 Feb 08

Installed Guru3d.
Notes say only works in Win 2000 and XP, but go ahead anyway - even when
asked if I'm really really sure I want to proceed.

In Driver Sweeper window move NVIDIA Display to 'remove' window and activate
sweep.
Blue band goes across bottom of application window.
View log: deleted folder (\NVIDIA)
So this did not appear to find anything else.
----

RegSweeper:

Nothing much appeared to happen and nothing was indicated to be removed.

Registry (using regedit)
HKCR> A lot of entries listed here, but are presumably just listing possible
types.
A lot of :
NvCpl.xxxxx
NVdmcpl.xxxx
single entry for nView.profile\shell\open\command
data:"rundll32.exe nview.dll,nViewCmd loadprofile shell"%1""

HKLM\Software\NVIDIA Corporation
data: Default (value not set)

Searching for: NVIDIA:
HKU\.DEFAULT\installLocationsMRU
Data: (amongst others) c "E:\NVIDIA\"
f "C:WINDOWS\SYSTEM\NvInst"

HKU\.DEFAULT\Software\MartS\TotalUnistall data: LastAppRunPath

Searching for: Nv**, or nv**
no results
----

Using CCleaner:
Registry:
C:\WINDOWS\SYSTEM\nview.dll,18 (HKCR\nview profile\default icon)
the following in HKCR\CLSID\
ActiveX\COM Issue InProcServer32\C:\WINDOWS\SYSTEM\NVCPL.DLL
ActiveX\COM Issue InProcServer32\C:\WINDOWS\SYSTEM\NVCPL.DLL
ActiveX\COM Issue InProcServer32\C:\WINDOWS\SYSTEM\NVCPL.DLL
ActiveX\COM Issue InProcServer32\C:\WINDOWS\SYSTEM\NVCPL.DLL
each of the above with different data keys.
HKLM\Software\NVIDIA Corporation (as noted in regedit above)

The above all cleaned. (backed up)

In applications:
NVIDIA Display Driver (red error out)

after this shutdown for restart:
fatal exception error on closedown.
----------------

Started normally.
backup registry

Forced scan for hardware:
Followed instruction as in MS article 317187 (Rerun hardware detection)
It scanned for hardware, asked for nothing, and then restarted.

Checked Device manger - no yellow question marks or other warnings
-------------
Checking Device manger for duplicate entries when in in Safemode
Display adaptors has only one single entry :
Standard PCI Graphics Adaptor (VGA) (as previously noted)

Monitors:
Plug and Play Monitor
-------------------------

Re- the Disk that came originally with the card:

> Potentially, but first, open the CD/disk installer [with an unzip program
> if necessary] and check the INF file for the version. The 77.72 driver
> You should find something like this:
> [version]
> DriverVer = 06/15/2005, 7.7.7.2
> LayoutFile=layout.inf
>
--------------
On disk that came with the card

Not sure where I'm looking here, but under
NVIDIA the following are listed:
5X00
WIN2K_XP
WIN9X_ME In .inf file: driver ver 3.0.8.2
WINNT4
6X00
WIN2K_XP
WIN9X_ME In .inf file:driver ver 3.0.8.2
WINNT4
7X00
WIN2K_XP
WIN9X_ME In .inf file:driver ver 4.1.0.4
WINNT4
7228
WIN2K_XP
WIN9X_ME In .inf file:driver ver 4.1.0.4
7300
WIN2K_XP
WIN9X_ME In .inf file:driver ver 4.1.0.4

Which of those are relevant I don't know. The correct files are found on
installation without having to choose any of the above.

If they are the files versions do seem quite old - nowhere near your ver 7,
so perhaps i should download something like 7.7.7.2 from somewhere, I think
guru3d has library of all the NVIDIA driver files, but as noted before
perhaps the best route is to install the original drivers from the disk and
then update
later?
--------------------

In conclusion, evrything appears ok except I'm stuck with the NVIDIA Display
drivers in Control panel >Add/Remove software that can't be shifted.
Attempts at removal result in Red error out using all methods tried so far.

In your opinion would I be better off buying an ATI type card for a fresh
start?
An inexpensive card would do, I'm not using it for gaming, just ordinary
windows apps, and video on screen. Could you recommend anything?

Roger R

Supplementary Data:
Mainboard is: ASUS A7V 133 employing chipset VIA Apollo KT133A
AGP 2.0 spec for 4X, 2X and 1X
 
Re: Device Manager, no Monitors branch

Roger R wrote:
[snip}
> In your opinion would I be better off buying an ATI type card for a
> fresh start?
> An inexpensive card would do, I'm not using it for gaming, just
> ordinary windows apps, and video on screen. Could you recommend
> anything?
>
> Roger R
>
> Supplementary Data:
> Mainboard is: ASUS A7V 133 employing chipset VIA Apollo KT133A
> AGP 2.0 spec for 4X, 2X and 1X

Try this link for more info and how to use Detonator Destroyer.
It is really supposed to work great.
Yes, it is free.
http://www.guru3d.com/detonator-destroyer/
 
Re: Device Manager, no Monitors branch

Buffalo wrote:
> Roger R wrote:
> [snip}
>> In your opinion would I be better off buying an ATI type card for a
>> fresh start?
>> An inexpensive card would do, I'm not using it for gaming, just
>> ordinary windows apps, and video on screen. Could you recommend
>> anything?
>>
>> Roger R
>>
>> Supplementary Data:
>> Mainboard is: ASUS A7V 133 employing chipset VIA Apollo KT133A
>> AGP 2.0 spec for 4X, 2X and 1X
>
> Try this link for more info and how to use Detonator Destroyer.
> It is really supposed to work great.
> Yes, it is free.
> http://www.guru3d.com/detonator-destroyer/

You could also try Drive Cleaner Pro located here:
http://downloads.guru3d.com/download.php?det=745
but Detonator Destroyer has a strong following for its effectiveness.

BTW, there are plenty of old ATI vid cards available through Pricewatch.com
, among other places.
Almost any card, even a 9200 or 9250 should be just fine. One 64mb card is
only around $20.00.
However, your present card should be just fine if it is not damaged.
 
Re: Device Manager, no Monitors branch


"Roger R" <d-e-c-o-d-e-r@clara.co.uk> wrote in message
news:1202755122.58933.0@iris.uk.clara.net...
|
| "MEB" <meb@not here@hotmail.com> wrote in message
| news:uh0fOm7aIHA.4172@TK2MSFTNGP02.phx.gbl...
| In response to your comments, first a bit about the Nvidia driver files,
| then
| further down the page more about the Nvidia driver files that remain
| installed in Windows\System.
|
| Starting with the Nvidia drivers.
| Referring to the driver files on the CD disk that came with the adaptor:
|
| > Hmm, by the version indications those appear to be from the Detonator
| > Series. [3.37 - 03-22-99; 3.53 version 10-15-99; 3.68 12-30-99;
| > 4.12.01.0522 - 05/18/00
| No I don't recognise those.
|
| Looking again at the disk, Contents.txt has the following:
| For my adaptor card (not an AGP8X) the drivers are the 7X00 series:
| Cut and pasted from the document:
| 7100M4-NVIDIA GeFORCE4MX440,
| <WIN9X_ME> Windows 95/98/ME drivers.(V41.04W)
| The actual NVAML.INF under the 7X00, win98 heading has data:
| DriverVer = 10/25/2002, 4.1.0.4
|
| Now,
| It happens I saved the complete Windows inf file dated 25 Jan 08.
| (I'm a bit puzzled because the 81.98 drivers were downloaded on 09Dec07
and
| I believed I installed shortly after, but could be mistaken.)
| Never the less, this .inf contains the following:
| nvaml.inf: Inf file ver3.0 Driver ver 4.1.0.4. dated 10/25/2002
|
| This accords with the on the original disk, but I can't understand why the
| .inf was not updated when the 81.98 drivers were installed.

The drivers and infs will not be overwritten if they are newer [date] or
already installed. That's why you must completely remove all old files,
registry entries, and everything related to the previous nVidia driver, and
why people have created those third party removers. At one time, even the
forums and support on nVidia would recommend using those uninstallers.

6.31 - 09-20-00- Detonator Series
Your driver ???
61.76 - 07-12-04 - Forceware Series
77.72 - 06-15-05- Forceware
81.98 - 12-10-05 - Forceware

|
| I thought there was somewhere on the windows system that kept a record of
| the various hardware changes, but if there is, I can't now discover it.

Perhaps you're thinking of the hardware txt file or system.1st, or the info
displayed via MSINFO showing hardware and driver changes.

|
| -----
| > So did I miss whether you verified that adapter as the AOpen 440 as was
| > identified/suggested ?
|
| No, not confirmed, the card is not branded AOpen or anything as Posh.
| It was an inexpensive white box branded as 'Sparkle'.
| http://www.sparkle.com.tw
|
| On that site, under APG cards they don't specifically list the GeForce4
| MX440, only the GeForce2 MX400.
| Never the less, following the GeForce2 MX400 link:
| Under 'driver downloads' for the above they have driver 77.72 for win9X.
| I downloaded that. (the http link returns no file found, but ftp
connection
| enables download of the 19 MB ZIP file : 77.72_win9x_international.)
|
| When unzipped the readme file has the following title:
| NVIDIA Display Drivers for Windows 9x, version 4.14.10.7772, 06/15/2005
| 1. List of supported adaptors, GeForce4 MX440 is amongst them.
| 2. List of files (No nvagp.inf as stated but NVAML.inf instead)
| 3. Installation instructions.
| 4. Uninstallation instructions ( use add\remove in Control Panel)
| 5. Control Freak panel access instructions.
|
| File NVAML.inf : DriverVer = 06/15/2005, 7.7.7.2
|
| This would be the version on which you commented favourably,
| so i think I'll have a go at installing that.
| (Does that type have name? Forceware or detonator or something..?)
|
| > With a card that old, I suppose the first thing we should also do, is
| > verify that the adapter's fan is still working, is it? If not or it
never
| > had one then the card MAY be having some additional issues...
|
| The card never had a fan, but there has not been any flickering, or, as
far
| as I know, any video lockups.
|
| -------------
| Now about the Nvidia files remaining in Windows:
|
| > | In conclusion, everything appears ok except I'm stuck with the NVIDIA
| > Display
| > | drivers in Control panel >Add/Remove software that can't be shifted.
| > | Attempts at removal result in Red error out using all methods tried so
| > far.
| >
| > And did you do the search in your Windows folder for files named nv*.* ?
| > I'm
| > thinking that the INF file is still in the INF folder. Does the INF
folder
| > still contain the nv3disp.inf, nvagp.inf, or nvaml1.inf? If so remove
it.
|
| My thoughts were obviously focussed elsewhere, so i missed that.
| nvaml.inf is present. (assume nvaml1 is a typo)
| The nvaml.inf (ver 3) data: Driver ver: 8.1.9.8 12/10/2005

Actually it wasn't a typo, that's how some of the older drivers provided
the nvaml file. Regardless, it is the file necessary to remove or Windows
will install SOME of the 81.98 intenationalized settings upon Windows
startup. Its not worth your effort to check, bu you may have a mis-matched
registry and files.

Okay, here's something that I also do when servicing older computers, if I
don't manually clean the slots and adapters [additional cost], I at least
remove the hold down screw and carefully rock the card in the slot to ensure
any corrosion [moisture in the air ALWAYS creates corrosion, smoke and you
have a dilectric barrier] is scraped away.

|
| As you suspected the Windows folder still contained the whole Nvidia
driver
| application in Windows\System\Nvinst\.
| The Windows search for nv*.* files produced 146 files,
| Located as follows:
|
| In: WINDOWS\SYSTEM
| nvuDisp.exe
| NVDisp.nvu
| nvapps.xml
| nvwddi.dll
| nvwimg.dll
| nvwdmcpl.dll
| Folder: NvInst
| No other nv types
|
| In WINDOWS\SYSTEM\NvInst\
| 136 files:
| Comprising: (.dll's and .hlp files omitted)
| keystone.exe
| nvsvc.exe
| nvuDisp.exe
| nwiz.exe
| nvaml.inf
| nvapps.xml
| nvcore.vxd
| nvmini.vxd
| vgartd.vxd
| NVDisp.nvu
| default.tvp

The above, in conjunction with the nvaml.inf file indicates you are using
the international version. Likely you have dozens of help files and other in
various language formats, making up the bulk of the found files.
Unless your system is not English then a warning: there may come a time
when your help screens and warning screens may pop-up in some foriegn
language when using the Internation version. If you have an English language
version of Windows, make the effort to download English only nVidia driver.

|
| In WINDOWS\APPLOG\
| Nvudisp.lgc
| ---------------

That's from taskmon, monitoring loading sequence and other for the
driver//files/application.

|
| All the above should simply be deleted and registry rechecked?
| ..worried about adverse consequence because of the appearance of the red
| error when trying to remove these using the Windows uninstaller.
|
| ------------
| Conclusion:
| Remove these remaining traces of the Nvidia installation and install the
| 77.72 drivers.
|
| Roger R
|
| Supplementary Data:
| Mainboard is: ASUS A7V 133 employing chipset VIA Apollo KT133A
| AGP 2.0 spec for 4X, 2X and 1X
|

The simple answer is Yes remove them all.

There are significant enough changes between the older 77.72 and the newer
81.98 files to cause problems.

Now here's a potential issue which may have occurred:

IF you failed to completely uninstall the other driver before installing
the 81.98 driver, then that may have caused your problem with the 81.98
driver.
Try the 77.72 driver, if it suits your purposes then stay there, OR, since
you now know how to rid yourself of the old drivers, completely remove the
77.72 driver [its uninstaller works, though still cleanup] and re-try the
81.98 sometime in the future.
Once either is installed, re-run the DirectX installer for the version on
your system [if you have it]. Check with MSINFO > Tools > DirectX, or type
dxdiag in the RUN box. If that doesn't work try dxinfo. NOTE: both had
updates which should be applied.


BTW it appears your card is specifically supported in the 77.72:
NVIDIA&DEV_0173.DeviceDesc="NVIDIA GeForce4 MX 440-SE"
> under d (2) =
> ....PCIR..q.....
> ....~.......GF4M
> X440-SE VGA BIOS
> ................


--

MEB
http://peoplescounsel.orgfree.com
_________
 
Re: Device Manager, no Monitors branch


"MEB" <meb@not here@hotmail.com> wrote in message
news:uh0fOm7aIHA.4172@TK2MSFTNGP02.phx.gbl...
In response to your comments, first a bit about the Nvidia driver files,
then
further down the page more about the Nvidia driver files that remain
installed in Windows\System.

Starting with the Nvidia drivers.
Referring to the driver files on the CD disk that came with the adaptor:

> Hmm, by the version indications those appear to be from the Detonator
> Series. [3.37 - 03-22-99; 3.53 version 10-15-99; 3.68 12-30-99;
> 4.12.01.0522 - 05/18/00
No I don't recognise those.

Looking again at the disk, Contents.txt has the following:
For my adaptor card (not an AGP8X) the drivers are the 7X00 series:
Cut and pasted from the document:
7100M4-NVIDIA GeFORCE4MX440,
<WIN9X_ME> Windows 95/98/ME drivers.(V41.04W)
The actual NVAML.INF under the 7X00, win98 heading has data:
DriverVer = 10/25/2002, 4.1.0.4

Now,
It happens I saved the complete Windows inf file dated 25 Jan 08.
(I'm a bit puzzled because the 81.98 drivers were downloaded on 09Dec07 and
I believed I installed shortly after, but could be mistaken.)
Never the less, this .inf contains the following:
nvaml.inf: Inf file ver3.0 Driver ver 4.1.0.4. dated 10/25/2002

This accords with the on the original disk, but I can't understand why the
..inf was not updated when the 81.98 drivers were installed.

I thought there was somewhere on the windows system that kept a record of
the various hardware changes, but if there is, I can't now discover it.

-----
> So did I miss whether you verified that adapter as the AOpen 440 as was
> identified/suggested ?

No, not confirmed, the card is not branded AOpen or anything as Posh.
It was an inexpensive white box branded as 'Sparkle'.
http://www.sparkle.com.tw

On that site, under APG cards they don't specifically list the GeForce4
MX440, only the GeForce2 MX400.
Never the less, following the GeForce2 MX400 link:
Under 'driver downloads' for the above they have driver 77.72 for win9X.
I downloaded that. (the http link returns no file found, but ftp connection
enables download of the 19 MB ZIP file : 77.72_win9x_international.)

When unzipped the readme file has the following title:
NVIDIA Display Drivers for Windows 9x, version 4.14.10.7772, 06/15/2005
1. List of supported adaptors, GeForce4 MX440 is amongst them.
2. List of files (No nvagp.inf as stated but NVAML.inf instead)
3. Installation instructions.
4. Uninstallation instructions ( use add\remove in Control Panel)
5. Control Freak panel access instructions.

File NVAML.inf : DriverVer = 06/15/2005, 7.7.7.2

This would be the version on which you commented favourably,
so i think I'll have a go at installing that.
(Does that type have name? Forceware or detonator or something..?)

> With a card that old, I suppose the first thing we should also do, is
> verify that the adapter's fan is still working, is it? If not or it never
> had one then the card MAY be having some additional issues...

The card never had a fan, but there has not been any flickering, or, as far
as I know, any video lockups.

-------------
Now about the Nvidia files remaining in Windows:

> | In conclusion, everything appears ok except I'm stuck with the NVIDIA
> Display
> | drivers in Control panel >Add/Remove software that can't be shifted.
> | Attempts at removal result in Red error out using all methods tried so
> far.
>
> And did you do the search in your Windows folder for files named nv*.* ?
> I'm
> thinking that the INF file is still in the INF folder. Does the INF folder
> still contain the nv3disp.inf, nvagp.inf, or nvaml1.inf? If so remove it.

My thoughts were obviously focussed elsewhere, so i missed that.
nvaml.inf is present. (assume nvaml1 is a typo)
The nvaml.inf (ver 3) data: Driver ver: 8.1.9.8 12/10/2005

As you suspected the Windows folder still contained the whole Nvidia driver
application in Windows\System\Nvinst\.
The Windows search for nv*.* files produced 146 files,
Located as follows:

In: WINDOWS\SYSTEM
nvuDisp.exe
NVDisp.nvu
nvapps.xml
nvwddi.dll
nvwimg.dll
nvwdmcpl.dll
Folder: NvInst
No other nv types

In WINDOWS\SYSTEM\NvInst\
136 files:
Comprising: (.dll's and .hlp files omitted)
keystone.exe
nvsvc.exe
nvuDisp.exe
nwiz.exe
nvaml.inf
nvapps.xml
nvcore.vxd
nvmini.vxd
vgartd.vxd
NVDisp.nvu
default.tvp

In WINDOWS\APPLOG\
Nvudisp.lgc
---------------

All the above should simply be deleted and registry rechecked?
...worried about adverse consequence because of the appearance of the red
error when trying to remove these using the Windows uninstaller.

------------
Conclusion:
Remove these remaining traces of the Nvidia installation and install the
77.72 drivers.

Roger R

Supplementary Data:
Mainboard is: ASUS A7V 133 employing chipset VIA Apollo KT133A
AGP 2.0 spec for 4X, 2X and 1X
 
Re: Device Manager, no Monitors branch


Okay, put both messages together

"Roger R" <d-e-c-o-d-e-r@clara.co.uk> wrote in message
news:1202846154.4902.0@proxy01.news.clara.net...
|
| "MEB" <meb@not here@hotmail.com> wrote in message
| news:eug1o5TbIHA.2268@TK2MSFTNGP02.phx.gbl...
| >BTW it appears your card is specifically supported in the 77.72:
| > NVIDIA&DEV_0173.DeviceDesc="NVIDIA GeForce4 MX 440-SE"
| >> under d (2) =
| >> ....PCIR..q.....
| >> ....~.......GF4M
| >> X440-SE VGA BIOS
| >> ................
|
| Problems are -more or less -resolved and the system is now running in
normal
| start up with 1024 x 768 display.
|
| Details:
| Followed your instructions and deleted all the NVIDIA folders and files
| wherever located.
| Ran Reg sweep again and removed all NVIDIA entries.
| I was confident everything was removed.
| Checked Device Manager for duplicate or spurious entries -none.
| Monitor is P&P listed as C776
| Re-started two or three times.
| Saved copy of registry to My Documents at this point.
|
| Meanwhile went to Guru3d and downloaded NVIDIA drivers:
| Ver 77.72 for win98, english version.
| Installed these drivers.
| All ok.
|
| Adaptor card is now listed in Device Manager as:
| GeForce4 MX440

Great, you've got it now...

|
| Notice on restart detection of additional hardware, monitor.
| In Device Manager there are now two monitors:
| C776
| Default Monitor.
|
| Remove Default Monitor.
| Restart but Default Monitor is restored.

Don't worry about that Default Monitor entry, leave it alone for now. The
Default is because there is no specific INF, and the other is from the
PlugnPray that nVidia found.

|
| This adaptor card supports two monitors. Is this second monitor appearing
| because the card expects to find two?
| Or is it because the .inf for the card is not right.
| I don't have an .inf for it, as its P&P should that matter?

A true INF would help, but the "PlugnPray" was supposed to use the
interaction between the monitor chip, adapter chip, and the OS and provide
the necessary functions. Key word is supposed....


There are a couple of settings that you might want to check in the nVidia
Settngs. Generally the defaults will work, particularly as your not gaming,
though if you find issues with video, then 3dGuru is your "friend" for
checking those settings.

|
| Been along the road of getting an .inf file, but it seems to come down to
| paying for one.
| Its not the money, the sum involved is small, but I don't have the
| mechanisms to pay by the methods they insist on.

Monitor6.inf contains:

[Hansol]
%Mazellan17px%=Mazellan17px, Monitor\HSLA605
%Mazellan15ax%=Mazellan15ax, Monitor\HSL05DD
%Mazellan14px%=Mazellan14px, Monitor\HSL0579
%Mazellan400A%=Mazellan400A, Monitor\HSL057A
%Mazellan700A%=Mazellan700A, Monitor\HSL06A6
%Mazellan17ax%=Mazellan17ax, Monitor\HSL06A6
%Mazellan700P%=Mazellan700P, Monitor\HSL06A5
%Mazellan500P%=Mazellan500P, Monitor\HSL05DE
%Mazellan500A%=Mazellan500A, Monitor\HSL05DD
%Mazellan400P%=Mazellan400P, Monitor\HSL0579

; -------------- Hansol
[Mazellan17px]
DelReg=DEL_CURRENT_REG
AddReg=Mazellan17px.AddReg, 1600, DPMS

[Mazellan15ax]
DelReg=DEL_CURRENT_REG
AddReg=Mazellan15ax.AddReg, 1024, DPMS

[Mazellan14px]
DelReg=DEL_CURRENT_REG
AddReg=Mazellan14px.AddReg, 1024, DPMS

[Mazellan400A]
DelReg=DEL_CURRENT_REG
AddReg=Mazellan400A.AddReg, 1024, DPMS

[Mazellan500P]
DelReg=Del_Current_Reg
AddReg=Mazellan500P.Add, 1280, DPMS

[Mazellan17ax]
DelReg=DEL_CURRENT_REG
AddReg=Mazellan17ax.Add, 1280, DPMS

[Mazellan700P]
DelReg=DEL_CURRENT_REG
AddReg=Mazellan700P.Add, 1600, DPMS

[Mazellan700A]
DelReg=DEL_CURRENT_REG
AddReg=Mazellan700A.Add, 1280, DPMS

[Mazellan500A]
DelReg=DEL_CURRENT_REG
AddReg=Mazellan500A.Add, 1024, DPMS

[Mazellan400P]
DelReg=DEL_CURRENT_REG
AddReg=Mazellan400P.Add, 1024, DPMS

; -------------- Hansol
[Mazellan17px.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-85.0,50.0-120.0,+,+"
HKR,,ICMProfile,1,9

[Mazellan15ax.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-120.0,+,+"
HKR,,ICMProfile,1,9

[Mazellan14px.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-120.0,+,+"
HKR,,ICMProfile,1,9

[Mazellan400A.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-50.0,50.0-120.0,-,-"
HKR,,ICMProfile,1,9

[Mazellan700A.Add]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-120.0,-,-"
HKR,,ICMProfile,1,9

[Mazellan500P.Add]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-120.0,-,-"
HKR,,ICMProfile,1,9

[Mazellan17ax.Add]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-120.0,-,-"
HKR,,ICMProfile,1,9

[Mazellan700P.Add]
HKR,"MODES\1600,1200",Mode1,,"30.0-85.0,50.0-120.0,+,+"
HKR,,ICMProfile,1,9

[Mazellan500A.Add]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-120.0,+,+"
HKR,,ICMProfile,1,9

[Mazellan400P.Add]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-120.0,+,+"
HKR,,ICMProfile,1,9

; User visible strings
;-------------------------------------------------
[Strings]
MS="Microsoft"

Hansol="Hansol Electronics"
Mazellan14px="Hansol Electronics Mazellan14px"
Mazellan15ax="Hansol Electronics Mazellan15ax"
Mazellan17px="Hansol Electronics Mazellan17px"
Mazellan400A="Hansol Electronics Mazellan400A"
Mazellan700A="Hansol Electronics Mazellan700A"
Mazellan500P="Hansol Electronics Mazellan500P"
Mazellan17ax="Hansol Electronics Mazellan17ax"
Mazellan700P="Hansol Electronics Mazellan700P"
Mazellan500A="Hansol Electronics Mazellan500A"
Mazellan400P="Hansol Electronics Mazellan400P"

Franc found:
> [ Hansol C776 ]
>
> Propriitis du moniteur:
> Nom du moniteur Hansol C776
> Identification du moniteur HSL06AD
> Modhle C776
> Type de moniteur 17" CRT
> Date de fabrication Semaine 48 / 2000
> Numiro de sirie YESN054206
> Taille d'affichage maximale visible 32 cm x 24 cm (15.7")
> Ratio d'aspect de l'image 4:3
> Friquence horizontale 30 - 72 KHz
> Friquence verticale 50 - 160 Hz
> Risolution maximale 1280 x 1024
> Gamma 2.26
> Gestion du mode DPMS Standby, Suspend, Active-Off
>
> Modes vidio giris:
> 640 x 480 140 Hz
> 800 x 600 110 Hz
> 1024 x 768 85 Hz
> 1152 x 864 75 Hz
> 1280 x 1024 65 Hz
>

So perhaps one of our gurus would just create an INF for you, all the
information is available.


| --------
|
| DirectX:
| Version: 6.1a (4.06.03.0518)

AAAAKKK, the driver you have installed is DX8.0+

|
| Don't know if this needs upgrading- to 9 or something, but how to upgrade
| it?

http://www.microsoft.com/downloads/details.aspx?FamilyID=4846c891-d45d-4122-8230-69f3e5ecdede -
DX 8.1 - require genuine check
If it fails, while still online/connected to that site, go to
C:\WINDOWS\Temporary Internet Files and click GenuineCheck.exe, paste the
results to the webpage.

9.0c can be found on the windowsupdates site in the catalog or on Microsoft.
http://www.microsoft.com/downloads/...38-db71-4c1b-bc6a-9b6652cd92a3&displaylang=en -
web installer for 9.0c - also genuine check

Got any gaming magazine CDs or have a friend/relative/other which has one?
Generally they have a DX version on them somewhere.


| MS update site doesn't seem very helpful.
| MS update site already checked this machine today and I downloaded a
| security patch, but no mention of updates for DirectX.

Well DX6 isn't even remotely current.

|
| Typed dxdiag in Run box
| Tabs produced following results:
| DirectX files: No problems found
| DX Media Files: no problems found
| DirectX drivers: no problems found
| Display 1:
| Direct Draw Acceleration enabled. All test functions ok.
| Direct 3D: Initially acceleration enabled but when test run
| saw rotating coloured cube ok, but next test Hardware Acceleration
Rendering
| causes it to crash out.

The card itself likely supports DX7 [possibly 8] natively, though I haven't
checked that, so DX6 isn't going to provide the proper functioning. If at
all possible upgrade to at least DX7 if not 8.1 or 9.0c [though that's more
for the 81.98 driver].

| Re run test after restart: same result.
| DirectX Features pane Direct3D: No acceleration available and
| 'Disable' button remains greyed out.
| However after each computer restart the Direct 3D Acceleration is again
| enabled.
| Display 2:
| As display 1

Right, the card natively supports hardware acceleration so that's going to
be the default.

|
| Sound tests : all ok
| ------------------
|
| Other unrelated issues encountered when restoring normal operation.
|
| Problem (resolved) with network card.
| Not detected - no light on RJ45 panel.
| Run: Force Hardware Re-detection. ref MS 317187
| Still Not detected.
| Remove card, restart and re-install network card software.
| Shutdown and reinstall card.
| Restart - network functioning normally.

Okay, so the various manipulations of the registry OR during those errors
you were having, the netcard decided to give you another headache.
But its fixed, check another one off.

|
| Problem with antivirus -needs reinstallation.
| That done and up dated.

Not unusual, check another one off.

|
| Enable normal start up in msconfig.
| Normal shutdown.
| --------------
| Roger R
|
|

AND THE CORRECTION
| A couple of errors in my post:
|
| I wrote:
| > Notice on restart detection of additional hardware, monitor.
| > In Device Manager there are now two monitors:
| > C776
| > Default Monitor.
|
| This happened before the NVIDIA drivers installed so not due to them.
|
|
| > Or is it because the .inf for the card is not right.
| > I don't have an .inf for it, as its P&P should that matter?
|
| Of course it is the Monitor not the adaptor card that I don't have the
..inf
| file.
|
| Sorry about that.
|
| Roger R


Roger, it seems you're about done, save for the INF and DirectX. At
minimum, upgrade DirectX.

--

MEB
http://peoplescounsel.orgfree.com
_________
 
Re: Device Manager, no Monitors branch


"MEB" <meb@not here@hotmail.com> wrote in message
news:eug1o5TbIHA.2268@TK2MSFTNGP02.phx.gbl...
>BTW it appears your card is specifically supported in the 77.72:
> NVIDIA&DEV_0173.DeviceDesc="NVIDIA GeForce4 MX 440-SE"
>> under d (2) =
>> ....PCIR..q.....
>> ....~.......GF4M
>> X440-SE VGA BIOS
>> ................

Problems are -more or less -resolved and the system is now running in normal
start up with 1024 x 768 display.

Details:
Followed your instructions and deleted all the NVIDIA folders and files
wherever located.
Ran Reg sweep again and removed all NVIDIA entries.
I was confident everything was removed.
Checked Device Manager for duplicate or spurious entries -none.
Monitor is P&P listed as C776
Re-started two or three times.
Saved copy of registry to My Documents at this point.

Meanwhile went to Guru3d and downloaded NVIDIA drivers:
Ver 77.72 for win98, english version.
Installed these drivers.
All ok.

Adaptor card is now listed in Device Manager as:
GeForce4 MX440

Notice on restart detection of additional hardware, monitor.
In Device Manager there are now two monitors:
C776
Default Monitor.

Remove Default Monitor.
Restart but Default Monitor is restored.

This adaptor card supports two monitors. Is this second monitor appearing
because the card expects to find two?
Or is it because the .inf for the card is not right.
I don't have an .inf for it, as its P&P should that matter?

Been along the road of getting an .inf file, but it seems to come down to
paying for one.
Its not the money, the sum involved is small, but I don't have the
mechanisms to pay by the methods they insist on.
--------

DirectX:
Version: 6.1a (4.06.03.0518)

Don't know if this needs upgrading- to 9 or something, but how to upgrade
it?
MS update site doesn't seem very helpful.
MS update site already checked this machine today and I downloaded a
security patch, but no mention of updates for DirectX.

Typed dxdiag in Run box
Tabs produced following results:
DirectX files: No problems found
DX Media Files: no problems found
DirectX drivers: no problems found
Display 1:
Direct Draw Acceleration enabled. All test functions ok.
Direct 3D: Initially acceleration enabled but when test run
saw rotating coloured cube ok, but next test Hardware Acceleration Rendering
causes it to crash out.
Re run test after restart: same result.
DirectX Features pane Direct3D: No acceleration available and
'Disable' button remains greyed out.
However after each computer restart the Direct 3D Acceleration is again
enabled.
Display 2:
As display 1

Sound tests : all ok
------------------

Other unrelated issues encountered when restoring normal operation.

Problem (resolved) with network card.
Not detected - no light on RJ45 panel.
Run: Force Hardware Re-detection. ref MS 317187
Still Not detected.
Remove card, restart and re-install network card software.
Shutdown and reinstall card.
Restart - network functioning normally.

Problem with antivirus -needs reinstallation.
That done and up dated.

Enable normal start up in msconfig.
Normal shutdown.
--------------
Roger R
 
Re: Device Manager, no Monitors branch

"Roger R" <d-e-c-o-d-e-r@clara.co.uk> wrote in message
news:1202846154.4902.0@proxy01.news.clara.net...

A couple of errors in my post:

I wrote:
> Notice on restart detection of additional hardware, monitor.
> In Device Manager there are now two monitors:
> C776
> Default Monitor.

This happened before the NVIDIA drivers installed so not due to them.


> Or is it because the .inf for the card is not right.
> I don't have an .inf for it, as its P&P should that matter?

Of course it is the Monitor not the adaptor card that I don't have the .inf
file.

Sorry about that.

Roger R
 
Re: Device Manager, no Monitors branch


"MEB" <meb@not here@hotmail.com> wrote in message
news:uW%2337CgbIHA.5892@TK2MSFTNGP06.phx.gbl...
Thanks for detailing all the monitor info, I hope you were able to cut and
paste didn't have to type all that.

> | DirectX:
> | Version: 6.1a (4.06.03.0518)
>
> AAAAKKK, the driver you have installed is DX8.0+

Followed the link and downloaded DirectX 8.1.
Installed and it passes all its test fine.
So that is sorted.

> Roger, it seems you're about done, ..

Yes everything working normally now - Great.

I'd like to take this opportunity to thank all those who contributed to
solving this problem, incl Glen Ventura, Franc Zabkar and especially
yourself for the considerable effort put into your comprehensive replies.
Very much appreciated.

Roger R
UK
 
Re: Device Manager, no Monitors branch



"Roger R" <d-e-c-o-d-e-r@clara.co.uk> wrote in message
news:1202928815.31293.0@proxy00.news.clara.net...
|
| "MEB" <meb@not here@hotmail.com> wrote in message
| news:uW%2337CgbIHA.5892@TK2MSFTNGP06.phx.gbl...
| Thanks for detailing all the monitor info, I hope you were able to cut and
| paste didn't have to type all that.
|
| > | DirectX:
| > | Version: 6.1a (4.06.03.0518)
| >
| > AAAAKKK, the driver you have installed is DX8.0+
|
| Followed the link and downloaded DirectX 8.1.
| Installed and it passes all its test fine.
| So that is sorted.
|
| > Roger, it seems you're about done, ..
|
| Yes everything working normally now - Great.
|
| I'd like to take this opportunity to thank all those who contributed to
| solving this problem, incl Glen Ventura, Franc Zabkar and especially
| yourself for the considerable effort put into your comprehensive replies.
| Very much appreciated.
|
| Roger R
| UK
|

Thanks for responding with the results, and thanks for recognizing the
effort that we all [the group] try to put into solving the issues we are
presented with, and it does [at times, as this did] take multiple areas
addressed.

Good luck and make us your newsgroup for any future issues which might need
resolved. There are a lot who wait in the background for questions related
to their areas of knowledge...

--

MEB
http://peoplescounsel.orgfree.com
_________
 
Back
Top