Tweet
Yes, yes, but you (we?) should keep the generic "VIA chipset sucks" comments out of this thread, as this is about a real driver problem in 5.3 drivers for G200. We shuold not bury the real problem under the garbage.
Again, for myself this problem was the first one I could not sort out myself, it is so predictable and happens so often, there was no behaviour like that in the previous version of the drivers for G200, the only conclusion is that the drivers are flawed.
Could it be true that the Matrox guys were in a hurry with the new version, and did not have time to fully test all platform combinations? They just may have left in some code that simply can not work on MVP3 chipsets.
But, as said, this should be easy to fix. If they do not have the kit there in Canada themselves, someone should at least send them the information in the blue screen. (Can not do it myself, the G200 machine just moved).
M.
------------------
Athlon500/MSI6167/64M(!)/10GIBM/6GSamsung/1GSCSI IBM/AHA2940/CL2xDVD/FastMM2+MJPEG/HPPSScanner/HPPSPrinter/G400DH32M/ZIP100SCSI/Mitsumi2xCD-R/Samsung17GL/MX300/AKA Electric Classic
Again, for myself this problem was the first one I could not sort out myself, it is so predictable and happens so often, there was no behaviour like that in the previous version of the drivers for G200, the only conclusion is that the drivers are flawed.
Could it be true that the Matrox guys were in a hurry with the new version, and did not have time to fully test all platform combinations? They just may have left in some code that simply can not work on MVP3 chipsets.
But, as said, this should be easy to fix. If they do not have the kit there in Canada themselves, someone should at least send them the information in the blue screen. (Can not do it myself, the G200 machine just moved).
M.
------------------
Athlon500/MSI6167/64M(!)/10GIBM/6GSamsung/1GSCSI IBM/AHA2940/CL2xDVD/FastMM2+MJPEG/HPPSScanner/HPPSPrinter/G400DH32M/ZIP100SCSI/Mitsumi2xCD-R/Samsung17GL/MX300/AKA Electric Classic
Comment