If you do have 2 graphics cards now i think it wont work because you have to have a crossfire-compatible motherboard and i dont think and old radeon 7000 has that.
i might be wrong but im pretty sure that 2 graphics cards cant go crossfire like that especially with one soo old
No mate, I know Crossfire is impossible in my situation, I just want to have a third monitor working independently of the other two, even it worked in 256 @ 800x600 I'd be happy.
you don't need drivers for standard vga. it seems the video card is working but windows is refusing to use it. have you tried switching the bios to make the pci adapter the primary/startup adapter?
I focused on that since it's something I've dealt with before. It's a simple matter to get the latest Intel motherboard chipset drivers but some don't get the connection from that to the error.
If we could get that installed then it's crossed off the list and we look deeper at card to driver support issues like you are doing.
that's an issue with the ati drivers, not necessarily the motherboard drivers. the 8.x catalyst drivers do not support the radeon 7000 so that error from when he was trying to apply those drivers to that card.
The motherboard drivers tell the drivers how to do that. It's a small step along the way.
(with an unsigned driver 6.14.10.6517) and it's even configurable in Catalylst Control.
The I2C error is still appearing in even viewer but is not halting or restarting the system which makes me think it was the other error that was doing that. I do have 2 instance of a new error related to ati2mtag:
Event Type: Error
Event Source: ati2mtag
Event Category: CPLIB
Event ID: 52249
Date: 04/08/2008
Time: 17:30:02
User: N/A
Computer: KERBEROS
Description:
CPLIB :: Initialization - Failed to load the library
Data:
0000: 00 00 00 00 01 00 5a 00 ......Z.
0008: 33 00 00 00 19 cc 00 c0 3....Ì.À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
but this is causing no issue with the operations of the system.
in safe mode are you? if so, try it in regular mode.
I just had the one. The ATi driver gets swiched off anyway once in safe mode and you're left with basic functionality.
It altered nothing apart from showing the post and BIOS screens in the third monitor but once it booted into windows the primary display adapter (the HD2400) took over. The properties of the "VGA Compatible" remained unchanged.
http://64.233.169.104/search?q=cache:EIwArxdnnocJ:www.motherboardpoint.com/t159512-ati2mtag-gives-blue-screens.html+ati2mtag+i2c&hl=en&ct=clnk&cd=4&gl=us&client=mozilla
I'd like to see that Intel driver installed then you may have to repeat the above chore of driver (hell) testing.
Many thanks to you Bob and those who helped a distraught Irishman with his problem.
I'm gonna quit while I'm ahead with 2 working graphics cards and let those non-intrusive event errors alone.
Many thanks again.
| Forum legend: | |
| Locked thread | |
| Moderator | |
![]() |
CNET staff |
![]() |
Samsung staff |
| Norton Authorized Support team | |
| AVG staff | |
| Windows Outreach team | |
![]() |
Dell staff |
| Intel staff | |