BetaArchive Logo
Navigation Home Screenshots Image Uploader Server Info FTP Servers Wiki Forum RSS Feed Rules Please Donate
UP: 23d, 8h, 14m | CPU: 24% | MEM: 5536MB of 11097MB used
{The community for beta collectors}

Forum rules


Any off topic discussions should go in this forum. Post count is not increased by posting here.
FTP Access status is required to post in this forum. Find out how to get it


Post new topic Reply to topic  [ 6 posts ] 
Author Message
 PostPost subject: Graphics Adaptor not in Driver List        Posted: Sun Jun 03, 2007 8:32 am 
Reply with quote
FTP Access
Offline

Joined
Sat Jun 02, 2007 5:29 pm

Posts
48
Hi, I have been running Longhorn 4053 for a while and everything works except for an irritating graphics problem. After installation, I tried installing my Nvidia graphics drivers for my 7800gtx on Nforce 4 Fatal1ty An8. However it said that setup could not find my graphics adaptor. Sure enough, when I went into the device manager, my graphics adaptor is simply not there! However, when I right click on my desktop and go to properties and then to adaptor, I see that there are 3 driver conflicts with several pci to pci bridges. Here is a copy of the error.

Input/Output Range 03B0 - 03BB used by:
PCI standard PCI-to-PCI bridge
Input/Output Range 03C0 - 03DF used by:
PCI standard PCI-to-PCI bridge
Memory Range 000A0000 - 000BFFFF used by:
PCI standard PCI-to-PCI bridge

And in device manager, there are 4 such Pci to pci bridges that say that they do not have enough free resources to use. Does anyone have any ideas?

Thanks


Top  Profile
 PostPost subject:        Posted: Fri Jun 22, 2007 2:54 am 
Reply with quote
Staff
User avatar
Offline

Joined
Thu Nov 30, 2006 6:10 pm

Posts
2643

Location
Land of The Tea.

Favourite OS
Windows 10 Pro x64
It might be a LongHorn bug.
Report it to Microsoft in 3...2..1.NOW.

_________________
Image
| Personal site - Social links - PC setup | TF2 Game Servers |
Liking traps isn't gay, its not gay if it looks like a girl
I-i-it's n-not as if I wanted to ban you or anything. B-baka. (「・ω・)「


Top  Profile  WWW
 PostPost subject:        Posted: Fri Jun 22, 2007 3:01 am 
Reply with quote
Donator
Offline

Joined
Sat Sep 30, 2006 5:00 pm

Posts
3557
toshua123 wrote:
It might be a LongHorn bug.
Report it to Microsoft in 3...2..1.NOW.

:roll: Please try to make helpful suggestions.


Top  Profile
 PostPost subject:        Posted: Fri Jun 22, 2007 3:11 am 
Reply with quote
Donator
Offline

Joined
Sat Feb 24, 2007 4:14 pm

Posts
6612

Location
United Kingdom

Favourite OS
Server 2012 R2
have you tried extracting the driver using WinRAR and select specific driver, click Have Disk, Browse and navigate to the extracted files. There should be a "nv4_disp.inf" or a similar inf file and select this.

_________________
BuildFeed - the ultimate collaborative NT build list - Windows Longhorn - a look at a defining Microsoft project


Top  Profile  WWW
 PostPost subject:        Posted: Fri Jun 22, 2007 4:13 am 
Reply with quote
Donator
Offline

Joined
Sat Aug 19, 2006 1:25 am

Posts
590

Location
Israel
Is it the PCIe version? If it is, Windows could be detecting it as a bridge. Try removing the bridges (from the device manager), installing nVidia's INFs and rebooting (this might make Windows install the correct drivers).


Top  Profile
 PostPost subject:        Posted: Fri Jun 22, 2007 5:50 am 
Reply with quote
FTP Access
User avatar
Offline

Joined
Sat Mar 17, 2007 2:01 am

Posts
79
I've had this issue before when installing Alcohol 120% on a laptop with an Intel chipset and integrated ATI FireGL graphics. One of alcohol's drivers completely messed up the AGP bus. Uninstalling didn't help, and after a quick look I couldn't find any driver in computer management to remove. I didn't feel like wasting time messing around, so I just used system restore to fix things and never bothered using Alcohol again (after reinstalling it to confirm it as the source of the problem).

If you can't system restore, you might want to try this:

1. Start -> Run -> cmd

2. type:
set DEVMGR_SHOW_DETAILS=1
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt.msc

3. in the Computer Management screen that shows up -> View menu -> Show hidden devices

You now might be able to spot whatever driver is *really* causing the problem.


Top  Profile
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 




Who is online

Users browsing this forum: No registered users and 8 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Jump to:  

All views expressed in these forums are those of the author and do not necessarily represent the views of the BetaArchive site owner.

Powered by phpBB® Forum Software © phpBB Group

Copyright © 2006-2018

 

Sitemap | XML | RSS