Ati X1000 series secondary display problem

  • Thread starter Thread starter tararot2
  • Start date Start date
T

tararot2

I've just build an XPe SP2 image that works perfect with the previous
generation of Ati cards: One display, two displays, Direct3D
applications, etc. But when I plug in something in the second monitor
connector the system freezes completely. I'm using Shuttle XPC SB83G5
and SB87G5. Everything works ok with the SB83G5 but fails with the
SB87G5. I've tried with different graphics card: Club3D X1600XT,
Club3DX1600Pro, Sapphire X1600, X1300 and always the same.
I have no idea of where to look for.
I appreciate any help, thanks.
 
I think you are a shemale!
Well that was random.
....and that's an odd one too. Are you installing the drivers for these
ATI cards or using components?
 
Hi Adora,
we install the drivers not components.
Maybe you can guide us to find the sld components of latest ati drivers.
 
Oriol said:
Hi Adora,
we install the drivers not components.
Maybe you can guide us to find the sld components of latest ati drivers.
Afraid I never got it working satisfactorily, so I install catalyst just
after FBA. We did have some second screen issues on one unit that were
resolved by a BIOS update. Possible that's your issue... I've never seen
anything quite like that, though. Does it do the same thing under Pro?
 
Everything works fine under Pro. I agree that maybe is a BIOS problem
because there isn't much difference between Shuttle SB83G5 and SB87G5.
But I didn't find an update for this BIOS...


Adora Belle Dearheart ha escrit:
 
Everything works fine under Pro. I agree that maybe is a BIOS problem
because there isn't much difference between Shuttle SB83G5 and SB87G5.
But I didn't find an update for this BIOS...
OK - if it's working OK under Pro, it's time to find the differences.
Are you perhaps using custom drivers in some places under XPe that you
aren't using under XPPro, or vice cersa? For example, I recently had an
issue with a unit on which the USB was disabled whenever we changed the
sound settings to 'no sounds' rather than 'windows default', and it
turned out to be because we were using the supplied motherboard drivers
whereas on Pro we were using the standard microsoft all-purpose ones.
 
Back
Top