View Single Post
  #17  
Old April 19th 05, 01:52 AM
Mart
external usenet poster
 
Posts: n/a
Default

Assuming that - as you alluded in a previous reply - you really do have
on-board video, then as Rick has stated in his post "There should be another
setting somewhere where you can disable the on-board if you want to."

What does your User Manual say on this subject?

If you are not sure what hardware is connected to your PC, then try running
Belkin Advisor (freeware) from :-
http://www.belarc.com/free_download.html

It will give an audit of your PC which includes a section on your Display
hardware.

Just a thought, in your original post you said "After installing a (MadDog)
Nvidia GeForce MX4000 PCI graphics card" Just what were you using before
you installed your new graphics card - and did you remove and/or disable the
old one?

Mart


"TheRealFastlane" wrote in message
...
Disable is NOT an option, choices in CMOS for graphics adapter are PCI
or AGP. There is no AGP slot and selecting AGP requires a CMOS reset
to restart the machine. I have since installed a 3DFX Voodoo3/2000 PCI
adapter which has resolved the Diablo2 latency problem and removes the
Nvidia S-video plug and I continue to get the new hardware found (PCI
vga-compatible adapter) on restart. Mulling over your suggestion of
must be disabled (I agree), I removed the Intel 82810 system &
graphics controller fron the systems devices list, restart, found new
hardare, cancel, and the 82xxx is back in dev mgr. disabled it,
restarted, found new hardware. If I let windows search for a driver it
finds none then lists it as unknown device in dev mgr with a yellow
question mark.
Thanks

On Sat, 9 Apr 2005 08:11:57 +0100, "Mart"
wrote:
Until or unless you confirm that you have DISABLED the on-board graphics
in
the BIOS, the rest of your posting is irrelevant. It's no use just
'uninstalling' it in Device Manager - it MUST be disabled in the BIOS!!!
Otherwise you are wasting both you own time and our time.

If you are not sure how to do this, then either RTFM (Read The Flipping
Manual - polite version!) or take your PC to a local repair shop and get
them to check it for you.

Mart


"fastlane" wrote in message
news
Following is definitely graphics related but no way (yet)
to determine if related to 2nd device innstalled.
A couple of weeks ago I discovered a major problem with
Diablo2, the right side of display would blink as well
as the bottom (an obverse L). I had installed the latest
drivers from the reseller however' there are later drives
available from Nvidia so I installed them and it fixed the
blinking problem but I still cannot play online because of
some latency/lag problem (ping=4K+ at times in game)
which has nothing to do with my ISP, comm soft/hardware etc
BECAUSE I just installed D2 on an inferior Dell machine,
used the same modem, ISP, everything but mobo and graphics
and my game connection is normal.

On Thu, 7 Apr 2005 03:37:03 -0700, TheRealFastlane
wrote:

Both are an annoyance, the 2nd monitor is installed and enabled in dev
mgr,
the PCI vga grahpics I have disabled and dont understand as the only
connected PCI device is the Nvidia which has vga/svga, dvi and S ports
(dont
know if its in or out).

"Mike M" wrote:

What exactly are the problems you are experiencing? Rather than
disabling
the second connection each time you boot what happens if you simply
ignore
the second monitor which is probably the s-video port on your graphics
card? Whilst I don't have an nVidia card I have ATI cards on my PCs
that
have multiple connectors supporting multiple monitors and once
installed
have no further problems.
--
Mike Maltby MS-MVP



TheRealFastlane wrote:

Major Annoyance
After installing a (MadDog) Nvidia GeForce MX4000 PCI graphics card
in my 6735 Pavilion (latest drivers installed), at every restart, I
get new hardware detected and windows insists on installing a
default monitor AND a PCI VGA-compatible display adapter in addition
to the installed NEC monitor and Nvidia card. The only way around
this so far is to let it install these devices then disable them in
device manager.
Thanks






-- Keyboard not detected
Press F1 to continue