Tweet
Afternoon all,
Big problems here with my G400 32Mb, dual head, drivers are 5.15
G400 160Mb ram
GA-5AX mobo
Win95 OSR2
Generic PCI NIC
SBPro Generic rockwell modem
It installs fine and OpenGL and DirectX look like they behave correctly and the old 1.01 Final Reality demo runs fine, BUT _all_ scores are VERY low (lower than a Voodoo 2 + Millenium II combo).
When ever I run HalfLife, QuakeIII Test, they all run slowly at first, then just die. Typically between 5 seconds and a few minutes. No GPFs, no mess, no lock ups, they just die. On top of that AvP produces massive screen corruption (lots of white
blocks when text and foreground stuff should be).
After poking around the resources for the G400 I noticed that ALL the memory ranges used are also assigned to the PCI-to-PCI bridge, all three block of memory. I've tried to reassign the memory ranges to above and below the PCI-to-PCI bridge, but every time i'm greeted with either a frozen machine at some point in the bootup process, or if it boots, a corrupted pallet and icons that are either in silhouette or just plain wrong.
changing AGP aperture, musmastering, AGP 1x or 2x, screen resolution makes no difference.
When I reinstall either/both the drivers for the PCI bridge or the G400 they always choose totally overlapping memory ranges.
My question is: is this memory range sharing between the G400 and the PCI bridge stuff supposed to happen?
Ideas people?
robert.
--
Robert Hodkinson, SF nut and a Render-head. www.geocities.com/SoHo/Coffeehouse/5939
reply email is bag.it@cableol.co.uk
Big problems here with my G400 32Mb, dual head, drivers are 5.15
G400 160Mb ram
GA-5AX mobo
Win95 OSR2
Generic PCI NIC
SBPro Generic rockwell modem
It installs fine and OpenGL and DirectX look like they behave correctly and the old 1.01 Final Reality demo runs fine, BUT _all_ scores are VERY low (lower than a Voodoo 2 + Millenium II combo).
When ever I run HalfLife, QuakeIII Test, they all run slowly at first, then just die. Typically between 5 seconds and a few minutes. No GPFs, no mess, no lock ups, they just die. On top of that AvP produces massive screen corruption (lots of white
blocks when text and foreground stuff should be).
After poking around the resources for the G400 I noticed that ALL the memory ranges used are also assigned to the PCI-to-PCI bridge, all three block of memory. I've tried to reassign the memory ranges to above and below the PCI-to-PCI bridge, but every time i'm greeted with either a frozen machine at some point in the bootup process, or if it boots, a corrupted pallet and icons that are either in silhouette or just plain wrong.
changing AGP aperture, musmastering, AGP 1x or 2x, screen resolution makes no difference.
When I reinstall either/both the drivers for the PCI bridge or the G400 they always choose totally overlapping memory ranges.
My question is: is this memory range sharing between the G400 and the PCI bridge stuff supposed to happen?
Ideas people?
robert.
--
Robert Hodkinson, SF nut and a Render-head. www.geocities.com/SoHo/Coffeehouse/5939
reply email is bag.it@cableol.co.uk
Comment