If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
System 1:
AMD 1.4 AYJHA-Y factory unlocked @ 1656 with Thermalright SK6 and 7k Delta fan
Epox 8K7A
2x256mb Micron pc-2100 DDR
an AGP port all warmed up and ready to be stuffed full of Parhelia II+
SBLIVE 5.1
Maxtor 40g 7,200 @ ATA-100
IBM 40GB 7,200 @ ATA-100
Pinnacle DV Plus firewire
3Com Hardware Modem
Teac 20/10/40 burner
Antec 350w power supply in a Colorcase 303usb Stainless
Does anybody know how I can hack my own resolution settings in PD 6.14? With 6.06 I used the ResolutionManager w2k to hack a resolution of 1400x1050 into the drivers, ideal for my 19"
But with PD6.14 that's not possible anymore. Perhaps there are some ways doing it by making use of the custom monitor setting files (.mpr files) but I can't find an example of such a file...
Yes, the blend modes are fixed. According to my sources they were fixed shortly after we got into that big spitting war about how broken the OpenGL implementation was... but of course I wasn't supposed to say anything THEN, and it takes forever to get the changes into a driver release. Heh.
- Gurm
------------------
Listen up, you primitive screwheads! See this? This is my BOOMSTICK! Etc. etc.
The Internet - where men are men, women are men, and teenage girls are FBI agents!
I'm the least you could do
If only life were as easy as you
I'm the least you could do, oh yeah
If only life were as easy as you
I would still get screwed
Originally posted by dZeus: what do you mean exactly?
the shadow problem? that was fixed already with the 5.10 drivers and 'optimize for accuracy' in the MTST util 2.0 version.
or do you mean something else?
In Q3's driver info you get a readout of the ICD version along with all supported GL extensions and I thought there could have been some new entries, but I wasn't sure about that and I don't have Q3 here at work ...
Originally posted by Surfwienix: why aren't the new drivers in the "latest drivers" section ????????????????
[This message has been edited by Surfwienix (edited 14 September 2000).]
Just because these are certified to fullfill MS standards and usually this is a very time consuming process (certification).
This means that normally the 'latest drivers' are faster and more mature than certified ones.
Cheers,
Maggi
Despite my nickname causing confusion, I am not female ...
Originally posted by Maggi: Just because these are certified to fullfill MS standards and usually this is a very time consuming process (certification).
This means that normally the 'latest drivers' are faster and more mature than certified ones.
Sure, but then why give the Certified drivers a higher revision number?
I don't pretend to know anything (cause I don't) I would tend to think that this "certified" driver release is probably to appease the 'business class' masses who purchase a G450 and will only use Microsoft "Certified" driver. But if it isn't the latest, (again I ask) why the higher revision number?
2Whyzzi
ECS K7S5A Pro, Athlon XP 2100+, 512 Megs PC-3200 CAS2.5, HIS Radeon 9550/VIVO 256Meg DDR
Asus A7N8X-E Deluxe C Mobile Athlon 2500+ @ 2.2GHz, 1GB PC-3200 CAS2.5, Hauppauge MCE 150, Nvidia 6600 256DDR
Asus A8R32 MVP, Sempron 1600+ @ 2.23GHz, 1 Gig DDR2 RAM, ATI 1900GT
To be honest I would prefere certified drivers over other releases, they may be a little older, (the revision number here seems to contradict this) but I'm perfectly happy to loose a few fps if it means more stability - over the past months I've had my fair share of problems with beta drivers (mostly from Creative) so a certified driver release is always welcome - at least they've had stringent testing.
I Can E-mail you one later.
On second thought I no longer have the machine that it was on. I should be able to remake it but won't have a G200 to test it on
[size=1]D3/\/7YCR4CK3R
Ryzen: Asrock B450M Pro4, Ryzen 5 2600, 16GB G-Skill Ripjaws V Series DDR4 PC4-25600 RAM, 1TB Seagate SATA HD, 256GB myDigital PCIEx4 M.2 SSD, Samsung LI24T350FHNXZA 24" HDMI LED monitor, Klipsch Promedia 4.2 400, Win11
Home: M1 Mac Mini 8GB 256GB
Surgery: HP Stream 200-010 Mini Desktop,Intel Celeron 2957U Processor, 6 GB RAM, ADATA 128 GB SSD, Win 10 home ver 22H2
Frontdesk: Beelink T4 8GB
Beta drivers and uncertified drivers are frequently two different things. All beta drivers might be uncertified but not all uncertified drivers are beta.
I can't speak with any real authority about the W2K drivers, certified or uncertified, since I only use a G200 and haven't noticed great difference in terms of stability from driver set to driver set. I don't really push this system.
However, I've seen certified Windows 98 drivers that were not only slower, but less stable than the uncertified drivers that were released beforehand. I believe this happened around the time of either the PD 5.25 or 5.30 drivers. If memory serves me correctly, because the certification process was so lengthly, the cerified driver set Matrox released afterwards was far older than and contained none of the fixes in the certified set.
I doubt certification process involves any rigorous stability testing. I believe the certification standards involve interface and control issues. For instance, Microsoft will not certify drivers with an option to disable Direct3D Vsync. That's why you have to hack the registry or use a separate utility.
I also believe Matrox had to remove the built in uninstaller from the PD 5.XX driver sets because of some arcane certification issue that had nothing to do with its effectiveness.
What's good for Microsoft (or Intel) and OEM's like Dell and Gateway is not necessarily good for for the end user. In fact, I've found the opposite to be true. For instance, the AMR slot and integrated sound have done nothing to enhance my life.
Paul
paulcs@flashcom.net
[This message has been edited by paulcs (edited 14 September 2000).]
Originally posted by paulcs: I also believe Matrox had to remove the built in uninstaller from the PD 5.XX driver sets because of some arcane certification issue that had nothing to do with its effectiveness.
but the new (certified) 6.14.051 (6.04 whatever) driver has still the pd6-uninstaller built-in!
Comment