Thread: Re: [GD-Windows] Omega Drivers? (shudder)
Brought to you by:
vexxed72
From: Rich <leg...@xm...> - 2003-06-16 19:34:19
|
In article <HEE...@mi...>, "Jon Watte" <hp...@mi...> writes: > Our customers aren't entirely happy about this situation, and=20 > neither are we. Does anyone have any brilliant ideas about what to=20 > do here? I'd be happy if I just knew how to detect that this=20 > problem is happening on the machine... I'd report the problem to the original vendor of the driver. Surely they didn't make their driver license open to modifications without their consent? -- "The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ: <http://www.xmission.com/~legalize/book/> izfree: Open source tools for Windows Installer <http://izfree.sourceforge.net> |
From: Gareth L. <GL...@cl...> - 2003-06-17 08:22:46
|
Use windows xp to put an uninstall point before you install them, then you can see what changed. There must be some tool that can compare the current state to the restore point. > -----Original Message----- > From: Jon Watte [mailto:hp...@mi...] > Sent: 17 June 2003 00:44 > To: gam...@li... > Subject: RE: [GD-Windows] Omega Drivers? (shudder) > > > > > You should probably contact the Omega guy and see what (if any) > > info he can > > provide to find out how to detect that his modified drivers > are running, > > So here's the problem with these drivers: > > We can detect whether the last installed drivers are the > Omega drivers. > > However, when the user "reverts" to original drivers, by > installing on > top of the drivers, every measure that we've taken to detect > what drivers > we're running on show "factory" drivers. However, the bad > behavior (black > textures) still shows up. Something's gotten hosed somewhere in the > system (bets are: registry :-) and isn't getting un-hosed by > installing > regular drivers. > > Let's see if the Omega guy is talkative; I have a feeler out. > > Cheers, > > / h+ > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU > Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly > Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: > http://sourceforge.net/mailarchive/forum.php?forum_idU5 > |
From: Jon W. <hp...@mi...> - 2003-06-17 18:12:23
|
> Use windows xp to put an uninstall point before you install them, then = you > can see what changed. There must be some tool that can compare the = current > state to the restore point. Free marshmallows(*) to whomever can point me at such a tool! Cheers, / h+ (*) not including shipping and handling |
From: Ivan-Assen I. <as...@ha...> - 2003-06-17 08:27:37
|
> Use windows xp to put an uninstall point before you install > them, then you can see what changed. There must be some tool > that can compare the current state to the restore point. Well, plain old FileMon / RegMon during installation won't hurt either. |
From: Troy G. <Tr...@cs...> - 2003-06-17 14:49:55
|
Just taking a guess based on what I've read from the website... Perhaps the mipmap settings are getting mucked up? The website mentions that when the OmegaDriver is installed the mipmap drop-down will be blank. Perhaps it is still set to whatever internal mipmap setting the driver uses, which is invalid under the new driver, thus causing D3D/OGL to be unable to fetch the correct texture? I would assume that a re-install of the driver would reset these registry settings, but perhaps they're not (to prevent users from having to re-tweak their settings when they upgrade drivers). Try opening up the advanced settings for the display and manually reseting all of the display options (or using a "reset to defaults" option if available). Troy Developer Relations Criterion Software www.csl.com > -----Original Message----- > From: Jon Watte [mailto:hp...@mi...] > Sent: Monday, June 16, 2003 6:44 PM > To: gam...@li... > Subject: RE: [GD-Windows] Omega Drivers? (shudder) > > > > > You should probably contact the Omega guy and see what (if any) > > info he can > > provide to find out how to detect that his modified drivers > are running, > > So here's the problem with these drivers: > > We can detect whether the last installed drivers are the > Omega drivers. > > However, when the user "reverts" to original drivers, by > installing on > top of the drivers, every measure that we've taken to detect > what drivers > we're running on show "factory" drivers. However, the bad > behavior (black > textures) still shows up. Something's gotten hosed somewhere in the > system (bets are: registry :-) and isn't getting un-hosed by > installing > regular drivers. > > Let's see if the Omega guy is talkative; I have a feeler out. > > Cheers, > > / h+ > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU > Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly > Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: > http://sourceforge.net/mailarchive/forum.php?forum_idU5 > |
From: Tom F. <to...@mu...> - 2003-06-17 18:23:57
|
You can certainly look at which registry settings are getting changed during the installation of the dodgy drivers - try stuff like RegSpy. I haven't used it, but I know people who have. Tom Forsyth - Muckyfoot bloke and Microsoft MVP. This email is the product of your deranged imagination, and does not in any way imply existence of the author. > -----Original Message----- > From: Jon Watte [mailto:hp...@mi...] > Sent: 17 June 2003 19:11 > To: gam...@li... > Subject: RE: [GD-Windows] Omega Drivers? (shudder) > > > > > Use windows xp to put an uninstall point before you install > them, then you > > can see what changed. There must be some tool that can > compare the current > > state to the restore point. > > Free marshmallows(*) to whomever can point me at such a tool! > > Cheers, > > / h+ > > > (*) not including shipping and handling > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU > Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly > Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: > http://sourceforge.net/mailarchive/forum.php?forum_idU5 > |
From: Jon W. <hp...@mi...> - 2003-06-16 21:00:34
|
> In article <HEE...@mi...>, > "Jon Watte" <hp...@mi...> writes: >=20 > > Our customers aren't entirely happy about this situation, and=3D20 > > neither are we. Does anyone have any brilliant ideas about what = to=3D20 > > do here? I'd be happy if I just knew how to detect that this=3D20 > > problem is happening on the machine... >=20 > I'd report the problem to the original vendor of the driver. Surely > they didn't make their driver license open to modifications without > their consent? I believe the web site is outside of the jurisdiction of the=20 country that the vendor is operating it. I e, I believe the=20 companies are ATI (Canada) and NVIDIA (US) and the web site=20 might be in Russia. The web really DOES change the behaviour of information, no=20 matter what you do to the laws... Cheers, / h+ |