Jump to content

frnak42

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

About frnak42

frnak42's Achievements

0

Reputation

  1. yeah, the problem is only when no ati card is present, otherwise all works great. And I do a force reboot after every driver just to be on the safe side. Frnak
  2. Oh for sure the 5.1s are gonna be my drivers of choice, especially since ATI realeses drivers every other week, I'll just wait for the 5.3s. One last thing, my email to ATI is on it's way and when the 5.3s will come out I will post again to let you guys know if the issue has been resolved Frnak
  3. No I am not, but I'm actually running under winPE which is kinda different but the general guidelines are the same. I simply run the setup file /k under the oemrunonce section. I never had that problem before, as previous driver versions (5.1 and under) would just not install themselves if no ATI card was present. I run both the ATI and nVidia setups upon every installation I do, but they have been smart enough to simply not install if no compatible card was found, except for the catalyst 5.2 that is. Frnak
  4. hmmm yeah, it would seem I forgot to mention one detail. It does work perfectly well with ATI based cards, but if no ATI card is present, then the setup seems to hang. Most people probably don't care, but for those of us building a one cd fits all kinda solution will be somewhat p***ed. Frnak
  5. Just so you guys know, the 5.2s are out, but it seems there is a bug in the setup file. When the /k command is used, the setup starts but never stops, so it never gets to the next step unless you kill the setup process. At least that is what I've seen on an asus P4C800-E-DX and an MSI FX5600XT. Could be the issue is hardware related and not something you'll encouter all the time, but since this this board has been quite useful to me I figured you guys deserved the heads up. Frnak
×
×
  • Create New...