Anyone figured out how to make Win2k give up more than 45 m
This is a discussion about Anyone figured out how to make Win2k give up more than 45 m in the Windows Games category; In win98 my g400 32 meg has about 94 megs of texture memory when i have the apeture ste to 128 in the bio but in win2k it never goes over 45 megs which subsequently will not allow me to run the 64 meg texture test in 3dmark2000.
In win98 my g400 32 meg has about 94 megs of texture memory when i have the apeture ste to 128 in the bio but in win2k it never goes over 45 megs which subsequently will not allow me to run the 64 meg texture test in 3dmark2000. I have tried all the dx8 betas but see no differece. 3dmark2000 says its either Matrox or win2ks fault. Matrox says they find nothing wrong with their drivers so I guess it must be win2k. Anyone have any ideas on this?
------------------
Celeron 300a@464 on a Abit BH6 Rev 1.01, 192 Pc100, Matrox G400 32 SH,
SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other
odds and ends
------------------
Celeron 300a@464 on a Abit BH6 Rev 1.01, 192 Pc100, Matrox G400 32 SH,
SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other
odds and ends
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Sep 3
Sep 13
0
2 minutes
Responses to this topic
With my G400 in Windows 2000 when it got to the 64m test it said that it could not run it because I did not have enough memory. When I stuck in a 3D Prophet 2 GTS 64m (Geforce 2 GTS with 64m of vram) I would get a BSOD as soon as the texture loading bar gets all the way to the right. IT'S A DRIVER PROBLEM.
OP
Still no one?
------------------
Celeron 300a@464 on a Abit BH6 Rev 1.01, 192 Pc100, Matrox G400 32 SH,
SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other
odds and ends
------------------
Celeron 300a@464 on a Abit BH6 Rev 1.01, 192 Pc100, Matrox G400 32 SH,
SBlive Value, Supra Express 56i ISA, all running on Win2k pro with other
odds and ends
Hmmm, I did further testing awhile back. Install DX8 build 146 would make 3Dmark 2000 v1.1 crash alot. So I put DX7 back on and replace the DX7 ddraw.dll with the DX8 Build 146 ddraw.dll. Instead of 0.1fps in the 64m test I got 50something fps in the 64m test.
So try replacing the dx7 ddraw.dll with the dx8 ddraw.dll
So try replacing the dx7 ddraw.dll with the dx8 ddraw.dll
