Sign in with
Sign up | Sign in
Your question

Radeon 8500 issue, AMD_MAN?

Tags:
  • Graphics Cards
  • Radeon
  • Graphics
Last response: in Graphics & Displays
Share
February 2, 2002 4:38:23 PM

I think you said somewhere that you build computers... Well you'd probably know more about this than I but here's the problem I came up with. I did a system build a while back on a Asus A7M266 XP1900+ with an OEM R8500. 1GB of ram. Now it seems to me that the amount of ram wouldn't matter beyond 512MB because WinME wouldn't use it (Dual boot OS setup) however the Video card drivers failed on WinME every time. Win2K was fine. Well I got my Radeon 8500 and I had 640MB on a biostar M7MIA. Loaded the drivers, all was well. Three days later I shuck the 128 stick for a 512 and I'm up to a GB with my neighbor and all the sudden I had the same problem in WinME as he does. Pulled it back out, all was fine. So is this a Radeon driver issue or is this a limitation on the OS. I'm thinking it's the latter but is there a workaround so we can keep a whole GB on the system?

Intel is god, cleanroom is life, and the wafers are all that matter.

More about : radeon 8500 issue amd man

February 2, 2002 4:51:46 PM

Hmm, which drivers were you trying to use for WinMe?

AMD technology + Intel technology = Intel/AMD Pentathlon IV; the <b>ULTIMATE</b> PC processor
February 2, 2002 4:59:46 PM

The betas they had two weeks ago on mine that ATI posted late in november and the recommended ones on his three weeks back that were posted october 23rd. Now we're both using the late november betas from the site and I see now there are new ones. Have you had a Video card (any) working fine in WinME on a system with a Gig-o-ram?

Intel is god, cleanroom is life, and the wafers are all that matter.
Related resources
February 2, 2002 6:43:47 PM

Yeah, the older drivers had a 512MB+ RAM issue. The latest betas fix that

AMD technology + Intel technology = Intel/AMD Pentathlon IV; the <b>ULTIMATE</b> PC processor
a b U Graphics card
February 3, 2002 3:09:34 AM

Could also be caused by running out of low level memory! ESPECIALLY if you have cached your Video BIOS!

What's the frequency, Kenneth?
!