simple conflict....I think?

Printable View

September 9th, 2001, 10:40 PM
natb1

simple conflict....I think?

Im building a new system from scratch (components below).
I am experiencing a resource conflict of the Memory usage
type (not I/O Mem). My AGP graphics card insists on sharing
a memory window with my "Standard PCI to PCI Bridge". There
are no acceptable Windows "alternative standard settings".
I can manualy alter this resource for either device (AGP or
PCI to PCI Bridge). However my PC wont boot afterwards. I
have to restore the "use automatic settings" switch.
Windows advises me that I would have to adjust my device
jumpers or utility after attempting a manual fix. I dont
understand that exactly. Is this why they call it
"Plug n Pray"?

The only thing I can think of is a Microsoft article advising
of Windows 95B having limited support of PCI to PCI bridge
(something regarding Aperature size).
However...My MoBo is old to the point of barely being an ATX.
Why would ANY technology on this board have Windows 95B
issues? AT boards have PCI devices...so why is this "bridge"
unique to my MoBo? Or is this REALLY an issue of AGP devices!

Thanks!

MoBo: Shuttle AI61V12A w/latest BIOS, 2X AGP slot, No ISAs,
AMD 751/756 chipset
CPU: AMD Athlon 750 Slot A (no clock tweaks)
RAM: 128MB PNY PC133...Backward Compatible
Video:LeadTek WinFast GeForce2MX AGP
HDD: Maxtor 20 gig
CDROM:40X standard ATAPI

Thats it!....very simple system....Thats why im puzzled? https://forums.windrivers.com/

[This message has been edited by natb1 (edited September 09, 2001).]

[This message has been edited by natb1 (edited September 10, 2001).]
September 11th, 2001, 08:27 PM
Wizard of Duh

Go into Setup and put everything on "Auto", set PnP OS installed? to "Yes". This will let the machine assign resources to all devices automatically, enable PCI steering, and IRQ sharing, which should resolve any conflicts, and allow the machine to boot right up.

------------------
"Yes Ma'am, I do Windows-wish I didn't"
September 12th, 2001, 02:15 AM
Froghead

Bohr's suggestions should work if you make sure you install the PCI Bus mastering for WIN95B. Personally while WIN95B works flawlessly on my P166 system that I'm using right now I wouldn't dream of trying to use it on your system.
You should realize that not one component in your system existed at the time WIN95B came out and you components were designed for WIN98SE and newer. Backwards compatability ain't always so. https://forums.windrivers.com/

------------------
What I know about computers would fill volumes - what I don't know would fill a wharehouse.
September 12th, 2001, 09:57 PM
bohr

Quote:

<font face="Tahoma, Arial, Helvetica, Verdana, Geneva" size="2">Originally posted by Froghead:
Bohr's suggestions should work if you make sure you install the PCI Bus mastering for WIN95B. Personally while WIN95B works flawlessly on my P166 system that I'm using right now I wouldn't dream of trying to use it on your system.
You should realize that not one component in your system existed at the time WIN95B came out and you components were designed for WIN98SE and newer. Backwards compatability ain't always so. https://forums.windrivers.com/

</font>

WWWWWHHHHAAAAATTTTTT???????? https://forums.windrivers.com/ https://forums.windrivers.com/

When or where did I say this Froghead??????
Are you mixing me up for another forum member????
I admit I do alot of suggestions and postings, but I don't recall answering NATB1's question here????

------------------
COMPUTER PROBLEMS!!! IT DOESN'T MATTER IF YOUR COMPUTER HAS A PROBLEM! ALL THAT MATTERS IS THE ROCK IS GOING TO KICK YOUR COMPUTER'S CANDY *** ALL OVER WINDRIVERS DOT COM. CAN YOU SMELLLL WHAT THE ROCK IS COOKING
???????