I need Tribaljet in this:
Hey Rog do you remember a couple of weeks ago about a finding you
brought... something about a value from 0 to 5 in the REGs where 0 was
to increase the performance...
remember that? what were the results of that?
do you remeber the path to get to that REG? plssssssssssss
Yeah, it HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class
\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000 (and 0001)
It's a 32-bit DWORD called "Acceleration.Level", with values ranging
from 5 (disabled) all the way to 0 (full hw accel). 945GME defaults at
4 (minimum accel). If the value doesn't exist, just create it.
The results didn't seem to be consistent for some people. I did notice
improvements going from default 4 to 1 (2nd highest value), but I
can't link you to my results as google groups is messing up and
doesn't open pages for me.
On 3 Dez, 00:26, MAD_BEAST <josepi...@hotmail.com> wrote:
> I need Tribaljet in this:
> Hey Rog do you remember a couple of weeks ago about a finding you
> brought... something about a value from 0 to 5 in the REGs where 0 was
> to increase the performance...
> remember that? what were the results of that?
> do you remeber the path to get to that REG? plssssssssssss
even though both of them (DisableHWAcceleration and
Acceleration.Level) have similar task (hardware acceleration things),
seems they have different way to do the task... or do they complement
each other so that they can't exist without the other? ...or
DisbaleHWAcceleration is more to "hard calibrating", while
"Acceleration.Level" is more to "soft calibrating" because it has more
values to be choose? @_@
- Acceleration.Level has 5 values ranging from 0 to 5
- DisableHardwareAcceleration has 2 values, only capable to understand
0 or 1 (or maybe any numbers that's not ZERO), "true"/"false",
"enable"/"disable", "yes"/"no" ??
...it's just my impression to both of them "at a glance", so please
correct me if I'm wrong. >_<
On Dec 3, 7:38 am, tribaljet <roller...@hotmail.com> wrote:
> Yeah, it HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class
> \{4D36E968-E325-11CE-BFC1-08002BE10318}\0000 (and 0001)
> It's a 32-bit DWORD called "Acceleration.Level", with values ranging
> from 5 (disabled) all the way to 0 (full hw accel). 945GME defaults at
> 4 (minimum accel). If the value doesn't exist, just create it.
> The results didn't seem to be consistent for some people. I did notice
> improvements going from default 4 to 1 (2nd highest value), but I
> can't link you to my results as google groups is messing up and
> doesn't open pages for me.
maybe this can be of help http://msdn.microsoft.com/en-us/library/aa970912.aspx it seems that he definitely disabled multisample (value equal to 0)
while microsoft had it set on 4 by default ( in a range from 0 to 16)
this should affect the whole 3d performance... by the way I'm just
reporting an impression based on the link i posted =)
On 3 Dic, 05:10, Kiki <kiki.cs....@gmail.com> wrote:
> hmm... another interesting lines of parameter...
> even though both of them (DisableHWAcceleration and
> Acceleration.Level) have similar task (hardware acceleration things),
> seems they have different way to do the task... or do they complement
> each other so that they can't exist without the other? ...or
> DisbaleHWAcceleration is more to "hard calibrating", while
> "Acceleration.Level" is more to "soft calibrating" because it has more
> values to be choose? @_@
> - Acceleration.Level has 5 values ranging from 0 to 5
> - DisableHardwareAcceleration has 2 values, only capable to understand
> 0 or 1 (or maybe any numbers that's not ZERO), "true"/"false",
> "enable"/"disable", "yes"/"no" ??
> ...it's just my impression to both of them "at a glance", so please
> correct me if I'm wrong. >_<
> On Dec 3, 7:38 am, tribaljet <roller...@hotmail.com> wrote:
> > Yeah, it HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class
> > \{4D36E968-E325-11CE-BFC1-08002BE10318}\0000 (and 0001)
> > It's a 32-bit DWORD called "Acceleration.Level", with values ranging
> > from 5 (disabled) all the way to 0 (full hw accel). 945GME defaults at
> > 4 (minimum accel). If the value doesn't exist, just create it.
> > The results didn't seem to be consistent for some people. I did notice
> > improvements going from default 4 to 1 (2nd highest value), but I
> > can't link you to my results as google groups is messing up and
> > doesn't open pages for me.
> hmm... another interesting lines of parameter...
> even though both of them (DisableHWAcceleration and
> Acceleration.Level) have similar task (hardware acceleration things),
> seems they have different way to do the task... or do they complement
> each other so that they can't exist without the other? ...or
> DisbaleHWAcceleration is more to "hard calibrating", while
> "Acceleration.Level" is more to "soft calibrating" because it has more
> values to be choose? @_@
> - Acceleration.Level has 5 values ranging from 0 to 5
> - DisableHardwareAcceleration has 2 values, only capable to understand
> 0 or 1 (or maybe any numbers that's not ZERO), "true"/"false",
> "enable"/"disable", "yes"/"no" ??
> ...it's just my impression to both of them "at a glance", so please
> correct me if I'm wrong. >_<
> On Dec 3, 7:38 am, tribaljet <roller...@hotmail.com> wrote:
> > Yeah, it HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class
> > \{4D36E968-E325-11CE-BFC1-08002BE10318}\0000 (and 0001)
> > It's a 32-bit DWORD called "Acceleration.Level", with values ranging
> > from 5 (disabled) all the way to 0 (full hw accel). 945GME defaults at
> > 4 (minimum accel). If the value doesn't exist, just create it.
> > The results didn't seem to be consistent for some people. I did notice
> > improvements going from default 4 to 1 (2nd highest value), but I
> > can't link you to my results as google groups is messing up and
> > doesn't open pages for me.
Actually he didn't turn off multisampling, but disabled multisampling
from being used. It was set as having a maximum value of x4, and now
not even x1 can't be used. So if it wasn't being used in the first
place, it won't affect performance at all.
On 3 Dez, 09:23, Zentradis <Zentra...@hotmail.it> wrote:
> maybe this can be of help http://msdn.microsoft.com/en-us/library/aa970912.aspx > it seems that he definitely disabled multisample (value equal to 0)
> while microsoft had it set on 4 by default ( in a range from 0 to 16)
> this should affect the whole 3d performance... by the way I'm just
> reporting an impression based on the link i posted =)
> On 3 Dic, 05:10, Kiki <kiki.cs....@gmail.com> wrote:
> > hmm... another interesting lines of parameter...
> > even though both of them (DisableHWAcceleration and
> > Acceleration.Level) have similar task (hardware acceleration things),
> > seems they have different way to do the task... or do they complement
> > each other so that they can't exist without the other? ...or
> > DisbaleHWAcceleration is more to "hard calibrating", while
> > "Acceleration.Level" is more to "soft calibrating" because it has more
> > values to be choose? @_@
> > - Acceleration.Level has 5 values ranging from 0 to 5
> > - DisableHardwareAcceleration has 2 values, only capable to understand
> > 0 or 1 (or maybe any numbers that's not ZERO), "true"/"false",
> > "enable"/"disable", "yes"/"no" ??
> > ...it's just my impression to both of them "at a glance", so please
> > correct me if I'm wrong. >_<
> > On Dec 3, 7:38 am, tribaljet <roller...@hotmail.com> wrote:
> > > It's a 32-bit DWORD called "Acceleration.Level", with values ranging
> > > from 5 (disabled) all the way to 0 (full hw accel). 945GME defaults at
> > > 4 (minimum accel). If the value doesn't exist, just create it.
> > > The results didn't seem to be consistent for some people. I did notice
> > > improvements going from default 4 to 1 (2nd highest value), but I
> > > can't link you to my results as google groups is messing up and
> > > doesn't open pages for me.
Wha? So basically, I can make it seem like AA or multisampling doesn't exist? THAT WOULD BE EPIC for one game (Need for speed world, it will force AA at medium+ settings)
On Fri, Dec 3, 2010 at 4:30 AM, tribaljet <roller...@hotmail.com> wrote: > Actually he didn't turn off multisampling, but disabled multisampling > from being used. It was set as having a maximum value of x4, and now > not even x1 can't be used. So if it wasn't being used in the first > place, it won't affect performance at all.
> On 3 Dez, 09:23, Zentradis <Zentra...@hotmail.it> wrote: >> maybe this can be of help http://msdn.microsoft.com/en-us/library/aa970912.aspx >> it seems that he definitely disabled multisample (value equal to 0) >> while microsoft had it set on 4 by default ( in a range from 0 to 16) >> this should affect the whole 3d performance... by the way I'm just >> reporting an impression based on the link i posted =)
>> On 3 Dic, 05:10, Kiki <kiki.cs....@gmail.com> wrote:
>> > hmm... another interesting lines of parameter...
>> > even though both of them (DisableHWAcceleration and >> > Acceleration.Level) have similar task (hardware acceleration things), >> > seems they have different way to do the task... or do they complement >> > each other so that they can't exist without the other? ...or >> > DisbaleHWAcceleration is more to "hard calibrating", while >> > "Acceleration.Level" is more to "soft calibrating" because it has more >> > values to be choose? @_@
>> > - Acceleration.Level has 5 values ranging from 0 to 5 >> > - DisableHardwareAcceleration has 2 values, only capable to understand >> > 0 or 1 (or maybe any numbers that's not ZERO), "true"/"false", >> > "enable"/"disable", "yes"/"no" ??
>> > ...it's just my impression to both of them "at a glance", so please >> > correct me if I'm wrong. >_<
>> > On Dec 3, 7:38 am, tribaljet <roller...@hotmail.com> wrote:
>> > > It's a 32-bit DWORD called "Acceleration.Level", with values ranging >> > > from 5 (disabled) all the way to 0 (full hw accel). 945GME defaults at >> > > 4 (minimum accel). If the value doesn't exist, just create it.
>> > > The results didn't seem to be consistent for some people. I did notice >> > > improvements going from default 4 to 1 (2nd highest value), but I >> > > can't link you to my results as google groups is messing up and >> > > doesn't open pages for me.
That would work. I personally only have font quality settings on
Avalon folder, but either using that reg file or creating the keys
manually would possibly work.
For your specific case Espio, You wouldn't need to use all the things
contained on that reg file, specially since your gpu is between tiers.
I'd manually create the multisampling value only, and check the
results. Just create a DWORD with value 0 and you're all set ;)
On 3 Dez, 09:38, Espionage724 <espionage...@gmail.com> wrote:
> Wha? So basically, I can make it seem like AA or multisampling doesn't
> exist? THAT WOULD BE EPIC for one game (Need for speed world, it will
> force AA at medium+ settings)
> On Fri, Dec 3, 2010 at 4:30 AM, tribaljet <roller...@hotmail.com> wrote:
> > Actually he didn't turn off multisampling, but disabled multisampling
> > from being used. It was set as having a maximum value of x4, and now
> > not even x1 can't be used. So if it wasn't being used in the first
> > place, it won't affect performance at all.
> > On 3 Dez, 09:23, Zentradis <Zentra...@hotmail.it> wrote:
> >> maybe this can be of help http://msdn.microsoft.com/en-us/library/aa970912.aspx > >> it seems that he definitely disabled multisample (value equal to 0)
> >> while microsoft had it set on 4 by default ( in a range from 0 to 16)
> >> this should affect the whole 3d performance... by the way I'm just
> >> reporting an impression based on the link i posted =)
> >> On 3 Dic, 05:10, Kiki <kiki.cs....@gmail.com> wrote:
> >> > hmm... another interesting lines of parameter...
> >> > even though both of them (DisableHWAcceleration and
> >> > Acceleration.Level) have similar task (hardware acceleration things),
> >> > seems they have different way to do the task... or do they complement
> >> > each other so that they can't exist without the other? ...or
> >> > DisbaleHWAcceleration is more to "hard calibrating", while
> >> > "Acceleration.Level" is more to "soft calibrating" because it has more
> >> > values to be choose? @_@
> >> > - Acceleration.Level has 5 values ranging from 0 to 5
> >> > - DisableHardwareAcceleration has 2 values, only capable to understand
> >> > 0 or 1 (or maybe any numbers that's not ZERO), "true"/"false",
> >> > "enable"/"disable", "yes"/"no" ??
> >> > ...it's just my impression to both of them "at a glance", so please
> >> > correct me if I'm wrong. >_<
> >> > On Dec 3, 7:38 am, tribaljet <roller...@hotmail.com> wrote:
> >> > > It's a 32-bit DWORD called "Acceleration.Level", with values ranging
> >> > > from 5 (disabled) all the way to 0 (full hw accel). 945GME defaults at
> >> > > 4 (minimum accel). If the value doesn't exist, just create it.
> >> > > The results didn't seem to be consistent for some people. I did notice
> >> > > improvements going from default 4 to 1 (2nd highest value), but I
> >> > > can't link you to my results as google groups is messing up and
> >> > > doesn't open pages for me.
Need for speed world is interesting, but recently it got a major
upgrade from version 4 to version 5, and that's causing gma users to
have a weird bug that during the countdown to start the race, others
start first. It's supposed not to affect the end result as the game
calculates individual lap times, but still I'm waiting for that to be
fixed. Other than that issue, it's a fun game, EA bought and improved
the ferrari challenge game engine, it's a friendly arcade game :) I
can run it ok at 1024x768 with minimum settings at 15-35 fps with my
core duo 2.16ghz and 2gb ram on win7.
On 3 Dez, 15:39, MAD_BEAST <josepi...@hotmail.com> wrote:
On Sat, Dec 4, 2010 at 10:30 AM, tribaljet <roller...@hotmail.com> wrote: > Need for speed world is interesting, but recently it got a major > upgrade from version 4 to version 5, and that's causing gma users to > have a weird bug that during the countdown to start the race, others > start first. It's supposed not to affect the end result as the game > calculates individual lap times, but still I'm waiting for that to be > fixed. Other than that issue, it's a fun game, EA bought and improved > the ferrari challenge game engine, it's a friendly arcade game :) I > can run it ok at 1024x768 with minimum settings at 15-35 fps with my > core duo 2.16ghz and 2gb ram on win7.
> On 3 Dez, 15:39, MAD_BEAST <josepi...@hotmail.com> wrote: > > @zentradis bro he is on WIN7
> > @everybody SO what happend to Avalon did you test it? results?
> > @Everybody what about Need for speed Wolrd? is it good as game? how it > > runs?
If the download link is invalid, just create the reg file yourself.
Though it's supposed to be 965 chipsets, but there doesn't seem to be
any noticeable 965 only feature.
On 4 Dez, 19:09, MaxiJazz <Lexpr...@yandex.ru> wrote:
hi guys its been long since i posted but was a bit shocked when i saw the post , i didnt entirely understand but since its a new finding then , congrats i knw ive been ignoring the group for so long but thats bcuz of my studies with the university this sem is a very disturbing one .... so until i come back i say " stack everything for me :D " i want to test everything :)
I didn't get any performance boost, but then again I tried this on AMD hardware :p but I guess it's intel-specific?
And idk what site I was on, but apparently this could be helpful on getting Aero to non-aero cards, or somethign along those lines...
On Sun, Dec 5, 2010 at 12:38 PM, MAD_BEAST <josepi...@hotmail.com> wrote: > MAXI THANK YOU SO MUCH! thats waht i was expecting! these are nothing > but great NEWS!!!! AVALONS is a succes!
This is for those who are stuck with graphics hardware that just went
legacy status but want to run Windows 7 at top speed just like they
did with XP/2003. Before someone shoots off with "get a new card", try
saying that to those who bought laptops very recently stuck with a
chipset that was not very old but nonetheless made legacy status – or
making an XP net book run Win7.
Windows 7/Server 2008 R2 is definitely a nice fast OS, but Microsoft
decided to clip out any 2D acceleration for any WDDM 1.0 drivers...
certain recent DX9 cards (ATI) fell into legacy status and will not
receive the WDDM 1.1 upgrade that restores their old 2D GDI
acceleration. The way around this is to load XPDM drivers, which is
easily done with the 32bit Windows. The 64bit Windows is a different
beast... but it is very possible to load XP drivers and get a fully
accelerated Windows just as fast as XP’s graphics engine. This affects
DVD playback, Flash playback, web browsing, and also has an effect on
3D gaming when there are 2D elements present (your windows, in game
FMV’s).
There are 2 options:
First being you load XPDM drivers in, regain 2D acceleration and have
DX9 capabilities, and loose Aero. Note: This should only be done if
the WDDM 1.0 settings down below do not work or your 2D application is
horribly bogged down still and Aero cannot be enabled which acts like
fully asccelerated GDI (Eg. older Autocad). The default registry
settings are not optimal either way for DX9 cards.
.
.
~~~~~Option 1 – XPDM install on a 64Bit OS
.
.
1. First, download your favourite XP graphics driver you know that
works well on XP.
2. Extract the driver from its installer and open the driver’s INF
file
3. Look for your graphics card and its corresponding PCI_ID, example:
"ATI Radeon X1200 Series " = ati2mtag_RS690M, PCI\VEN_1002&DEV_791F
4. This example has my laptop’s chipset listed, the “ati2mtag_RS690M”
is our point of interest, CTRL+F and search for later occurrences of
it
5. You will arrive to this point in file (for your specific card...
mine is an example)
[ati2mtag_RS690M]
FeatureScore=FC
CopyFiles=ati2mtag.Miniport, ati2mtag.Display, ati2mtag.OpenGL,
ati2mtag.Wow64OpenGL, Uninstall.CopyFiles, ati2mtag.OGL,
ati2mtag.ORCA;, DVCR.CopyCodec
AddReg=Uninstall.AddReg
DelFiles=ati2mtag_DelFiles
UninstallFiles=Uninstall.CopyFiles
UninstallReg=Uninstall.AddReg
CleanFiles=ati2mtag.Miniport, ati2mtag.Display, ati2mtag.OpenGL,
ati2mtag.Wow64OpenGL, ati2mtag.OGL, ati2mtag.ORCA
CleanReg=ati2mtag_SoftwareDeviceSettings,
ati2mtag_RS690M_SoftwareDeviceSettings,
atioglxx_OpenGLSoftwareSettings,
ati2mtag_Mobile_SoftwareDeviceSettings,
ati2mtag_MobileLargeDesktopSettings
CleanService=ati2mtag_RemoveService
6. The FeatureScore=FC line is what I added to the INF under my
device’s installation section as shown above, this is what makes or
breaks an INF from installing on Windows 7. “FC” is chosen so the OS
recognizes the INF as an XPDM driver and to install it accordingly. If
the FeatureScore is set to mimic a Windows Vista or 7 drivers (F6 and
E6 respectively), the driver will install wrong and not start! More
info on FeatureScore can be found here>> http://msdn.microsoft.com/en-us/library/ee229540.aspx 7. Save the modified INF and go to Device Manager, select the
offending graphics card and update its drivers, answer the nag prompts
from Windows as required to get it installed.
8. Merge the following dwords into your registry (I do not know of
HKLM takes precedence yet... MS is very stupid setting the engine by
the user... so go through the keys in HKEY_USERS and add this in...
especially for .DEFAULT as this is the login screen)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Avalon.Graphics]
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics]
[HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Avalon.Graphics]
(And ideally all other user accounts)
9. This forces GDI acceleration (DisableHWAcceleration was done on
purpose to force the GDI hooks.. the XPDM driver will accelerate them
in this situation) and all 2D speed should be back just as it was with
XP. Test your 3D, it should remain quick, but I have gotten the WDDM
1.0 fully accelerated Aero mode to finally match, and Classic is 20%
faster (only window drag and resize piss off the CPU - not bad).
.
.
~~~~~~Option 2 – WDDM compatibility maintained, for DX10 cards with no
hope of WDDM 1.1 upgrade that fixes the GDI problems, for those that
want to maintain Aero but have almost as close to XP speed as
possible:
.
.
1. At this point you should already have a WDDM 1.0 driver installed,
with whatever modifications you have done.
2. If you have the troubleshooting notch available in the Screen
Resolution>Advanced Properties, bring it one notch over to the left
from Full Acceleration (you may try two over... anymore and D3D is
lost).
3. If this setting is not available (like mine). Open Regedit and
navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\
{y our video card’s CLSID – varies from each driver install}\0000 and
input in:
“Acceleration.Level"=dword:00000004
Or
(Try 4, 3 ,2, then 1... check to make sure Direct3D vis dxdiag is
still enabled.. technically at level 3 it is supposed to not work..
but in my case D3D stays running but all 2D succesfully takes the
older recognized pipeline)
4. Merge the following into the registry
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Avalon.Graphics]
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics]
[HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Avalon.Graphics]
(And ideally all other user accounts)
5. DisableHWAcceleration is left enabled, in both cases this is the
major reason for the speed increase -- and even Aero runs better at
LOWER cpu usage with it on.. odd-- whatever it works.
6. This mode will allow the use of Aero, if done right like this does
for me, Aero will run as fast as the XPDM drivers for both 2D and
3D... much better than stock configuration I had and not what I
expected. Going to windows Classic mode still running WDDM drivers...
I gain 20% increase in speed over the XPDM in 3D gaming, 2D elements
(movies, flash) are faster, the only bog down - that I know off and my
CPU can keep pace.. is a window drag and resize... even YouTube HD is
playable... except fullscreen (I am not expecting to get this working
on my X1200 as it is not accelerated... I need to find a way of
fooling it to do so).
Interesting read. It seems that graphics can be sent for either the
cpu or the gpu to process, yet certain aero functions do work better
on a gpu, even integrated chipsets like ours.
Somehow I feel that some tweaking might give quite the performance,
while maintaining WDDM 1.0 and NOT offloading GDI to the cpu.
Basically it feels like the more powerful the cpu, more features can
be sent to the cpu. But most gma 950 systems are limited in that
matter to a certain extent, meaning that I don't believe that there's
any cpu being a core 2 duo T7300 with an active gma 950.
On 6 Dez, 08:37, CHAMPION <adityapra...@gmail.com> wrote:
> This is for those who are stuck with graphics hardware that just went
> legacy status but want to run Windows 7 at top speed just like they
> did with XP/2003. Before someone shoots off with "get a new card", try
> saying that to those who bought laptops very recently stuck with a
> chipset that was not very old but nonetheless made legacy status – or
> making an XP net book run Win7.
> Windows 7/Server 2008 R2 is definitely a nice fast OS, but Microsoft
> decided to clip out any 2D acceleration for any WDDM 1.0 drivers...
> certain recent DX9 cards (ATI) fell into legacy status and will not
> receive the WDDM 1.1 upgrade that restores their old 2D GDI
> acceleration. The way around this is to load XPDM drivers, which is
> easily done with the 32bit Windows. The 64bit Windows is a different
> beast... but it is very possible to load XP drivers and get a fully
> accelerated Windows just as fast as XP’s graphics engine. This affects
> DVD playback, Flash playback, web browsing, and also has an effect on
> 3D gaming when there are 2D elements present (your windows, in game
> FMV’s).
> There are 2 options:
> First being you load XPDM drivers in, regain 2D acceleration and have
> DX9 capabilities, and loose Aero. Note: This should only be done if
> the WDDM 1.0 settings down below do not work or your 2D application is
> horribly bogged down still and Aero cannot be enabled which acts like
> fully asccelerated GDI (Eg. older Autocad). The default registry
> settings are not optimal either way for DX9 cards.
> .
> .
> ~~~~~Option 1 – XPDM install on a 64Bit OS
> .
> .
> 1. First, download your favourite XP graphics driver you know that
> works well on XP.
> 2. Extract the driver from its installer and open the driver’s INF
> file
> 3. Look for your graphics card and its corresponding PCI_ID, example:
> "ATI Radeon X1200 Series " = ati2mtag_RS690M, PCI\VEN_1002&DEV_791F
> 4. This example has my laptop’s chipset listed, the “ati2mtag_RS690M”
> is our point of interest, CTRL+F and search for later occurrences of
> it
> 5. You will arrive to this point in file (for your specific card...
> mine is an example)
> [ati2mtag_RS690M]
> FeatureScore=FC
> CopyFiles=ati2mtag.Miniport, ati2mtag.Display, ati2mtag.OpenGL,
> ati2mtag.Wow64OpenGL, Uninstall.CopyFiles, ati2mtag.OGL,
> ati2mtag.ORCA;, DVCR.CopyCodec
> AddReg=Uninstall.AddReg
> DelFiles=ati2mtag_DelFiles
> UninstallFiles=Uninstall.CopyFiles
> UninstallReg=Uninstall.AddReg
> CleanFiles=ati2mtag.Miniport, ati2mtag.Display, ati2mtag.OpenGL,
> ati2mtag.Wow64OpenGL, ati2mtag.OGL, ati2mtag.ORCA
> CleanReg=ati2mtag_SoftwareDeviceSettings,
> ati2mtag_RS690M_SoftwareDeviceSettings,
> atioglxx_OpenGLSoftwareSettings,
> ati2mtag_Mobile_SoftwareDeviceSettings,
> ati2mtag_MobileLargeDesktopSettings
> CleanService=ati2mtag_RemoveService
> 6. The FeatureScore=FC line is what I added to the INF under my
> device’s installation section as shown above, this is what makes or
> breaks an INF from installing on Windows 7. “FC” is chosen so the OS
> recognizes the INF as an XPDM driver and to install it accordingly. If
> the FeatureScore is set to mimic a Windows Vista or 7 drivers (F6 and
> E6 respectively), the driver will install wrong and not start! More
> info on FeatureScore can be found here>>http://msdn.microsoft.com/en-us/library/ee229540.aspx > 7. Save the modified INF and go to Device Manager, select the
> offending graphics card and update its drivers, answer the nag prompts
> from Windows as required to get it installed.
> 8. Merge the following dwords into your registry (I do not know of
> HKLM takes precedence yet... MS is very stupid setting the engine by
> the user... so go through the keys in HKEY_USERS and add this in...
> especially for .DEFAULT as this is the login screen)
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Avalon.Graphics]
> [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics]
> [HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Avalon.Graphics]
> (And ideally all other user accounts)
> 9. This forces GDI acceleration (DisableHWAcceleration was done on
> purpose to force the GDI hooks.. the XPDM driver will accelerate them
> in this situation) and all 2D speed should be back just as it was with
> XP. Test your 3D, it should remain quick, but I have gotten the WDDM
> 1.0 fully accelerated Aero mode to finally match, and Classic is 20%
> faster (only window drag and resize piss off the CPU - not bad).
> .
> .
> ~~~~~~Option 2 – WDDM compatibility maintained, for DX10 cards with no
> hope of WDDM 1.1 upgrade that fixes the GDI problems, for those that
> want to maintain Aero but have almost as close to XP speed as
> possible:
> .
> .
> 1. At this point you should already have a WDDM 1.0 driver installed,
> with whatever modifications you have done.
> 2. If you have the troubleshooting notch available in the Screen
> Resolution>Advanced Properties, bring it one notch over to the left
> from Full Acceleration (you may try two over... anymore and D3D is
> lost).
> 3. If this setting is not available (like mine). Open Regedit and
> navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\
> {y our video card’s CLSID – varies from each driver install}\0000 and
> input in:
> “Acceleration.Level"=dword:00000004
> Or
> (Try 4, 3 ,2, then 1... check to make sure Direct3D vis dxdiag is
> still enabled.. technically at level 3 it is supposed to not work..
> but in my case D3D stays running but all 2D succesfully takes the
> older recognized pipeline)
> 4. Merge the following into the registry
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Avalon.Graphics]
> [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics]
> [HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Avalon.Graphics]
> (And ideally all other user accounts)
> 5. DisableHWAcceleration is left enabled, in both cases this is the
> major reason for the speed increase -- and even Aero runs better at
> LOWER cpu usage with it on.. odd-- whatever it works.
> 6. This mode will allow the use of Aero, if done right like this does
> for me, Aero will run as fast as the XPDM drivers for both 2D and
> 3D... much better than stock configuration I had and not what I
> expected. Going to windows Classic mode still running WDDM drivers...
> I gain 20% increase in speed over the XPDM in 3D gaming, 2D elements
> (movies, flash) are faster, the only bog down - that I know off and my
> CPU can keep pace.. is a window drag and resize... even YouTube HD is
> playable... except fullscreen (I am not expecting to get this working
> on my X1200 as it is not accelerated... I need to find a way of
> fooling it to do so).
this is interesting indeed, im gonna test it later on...
do u guys think that by including this registry setting implemented in 9xxssf driver would be a good thing? also i do interested on how these setting to solve flash playback problem on our GMA...i think tribaljet know better on that issue :)
On Mon, Dec 6, 2010 at 4:43 PM, tribaljet <roller...@hotmail.com> wrote: > Interesting read. It seems that graphics can be sent for either the > cpu or the gpu to process, yet certain aero functions do work better > on a gpu, even integrated chipsets like ours.
> Somehow I feel that some tweaking might give quite the performance, > while maintaining WDDM 1.0 and NOT offloading GDI to the cpu.
> Basically it feels like the more powerful the cpu, more features can > be sent to the cpu. But most gma 950 systems are limited in that > matter to a certain extent, meaning that I don't believe that there's > any cpu being a core 2 duo T7300 with an active gma 950.
> On 6 Dez, 08:37, CHAMPION <adityapra...@gmail.com> wrote: > > This is for those who are stuck with graphics hardware that just went > > legacy status but want to run Windows 7 at top speed just like they > > did with XP/2003. Before someone shoots off with "get a new card", try > > saying that to those who bought laptops very recently stuck with a > > chipset that was not very old but nonetheless made legacy status – or > > making an XP net book run Win7.
> > Windows 7/Server 2008 R2 is definitely a nice fast OS, but Microsoft > > decided to clip out any 2D acceleration for any WDDM 1.0 drivers... > > certain recent DX9 cards (ATI) fell into legacy status and will not > > receive the WDDM 1.1 upgrade that restores their old 2D GDI > > acceleration. The way around this is to load XPDM drivers, which is > > easily done with the 32bit Windows. The 64bit Windows is a different > > beast... but it is very possible to load XP drivers and get a fully > > accelerated Windows just as fast as XP’s graphics engine. This affects > > DVD playback, Flash playback, web browsing, and also has an effect on > > 3D gaming when there are 2D elements present (your windows, in game > > FMV’s).
> > There are 2 options:
> > First being you load XPDM drivers in, regain 2D acceleration and have > > DX9 capabilities, and loose Aero. Note: This should only be done if > > the WDDM 1.0 settings down below do not work or your 2D application is > > horribly bogged down still and Aero cannot be enabled which acts like > > fully asccelerated GDI (Eg. older Autocad). The default registry > > settings are not optimal either way for DX9 cards.
> > . > > . > > ~~~~~Option 1 – XPDM install on a 64Bit OS > > . > > .
> > 1. First, download your favourite XP graphics driver you know that > > works well on XP. > > 2. Extract the driver from its installer and open the driver’s INF > > file > > 3. Look for your graphics card and its corresponding PCI_ID, example: > > "ATI Radeon X1200 Series " = ati2mtag_RS690M, PCI\VEN_1002&DEV_791F > > 4. This example has my laptop’s chipset listed, the “ati2mtag_RS690M” > > is our point of interest, CTRL+F and search for later occurrences of > > it > > 5. You will arrive to this point in file (for your specific card... > > mine is an example) > > [ati2mtag_RS690M] > > FeatureScore=FC > > CopyFiles=ati2mtag.Miniport, ati2mtag.Display, ati2mtag.OpenGL, > > ati2mtag.Wow64OpenGL, Uninstall.CopyFiles, ati2mtag.OGL, > > ati2mtag.ORCA;, DVCR.CopyCodec > > AddReg=Uninstall.AddReg > > DelFiles=ati2mtag_DelFiles > > UninstallFiles=Uninstall.CopyFiles > > UninstallReg=Uninstall.AddReg > > CleanFiles=ati2mtag.Miniport, ati2mtag.Display, ati2mtag.OpenGL, > > ati2mtag.Wow64OpenGL, ati2mtag.OGL, ati2mtag.ORCA > > CleanReg=ati2mtag_SoftwareDeviceSettings, > > ati2mtag_RS690M_SoftwareDeviceSettings, > > atioglxx_OpenGLSoftwareSettings, > > ati2mtag_Mobile_SoftwareDeviceSettings, > > ati2mtag_MobileLargeDesktopSettings > > CleanService=ati2mtag_RemoveService
> > 6. The FeatureScore=FC line is what I added to the INF under my > > device’s installation section as shown above, this is what makes or > > breaks an INF from installing on Windows 7. “FC” is chosen so the OS > > recognizes the INF as an XPDM driver and to install it accordingly. If > > the FeatureScore is set to mimic a Windows Vista or 7 drivers (F6 and > > E6 respectively), the driver will install wrong and not start! More > > info on FeatureScore can be found here>> > http://msdn.microsoft.com/en-us/library/ee229540.aspx > > 7. Save the modified INF and go to Device Manager, select the > > offending graphics card and update its drivers, answer the nag prompts > > from Windows as required to get it installed. > > 8. Merge the following dwords into your registry (I do not know of > > HKLM takes precedence yet... MS is very stupid setting the engine by > > the user... so go through the keys in HKEY_USERS and add this in... > > especially for .DEFAULT as this is the login screen)
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Avalon.Graphics] > > [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics] > > [HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Avalon.Graphics] > > (And ideally all other user accounts)
> > 9. This forces GDI acceleration (DisableHWAcceleration was done on > > purpose to force the GDI hooks.. the XPDM driver will accelerate them > > in this situation) and all 2D speed should be back just as it was with > > XP. Test your 3D, it should remain quick, but I have gotten the WDDM > > 1.0 fully accelerated Aero mode to finally match, and Classic is 20% > > faster (only window drag and resize piss off the CPU - not bad).
> > . > > . > > ~~~~~~Option 2 – WDDM compatibility maintained, for DX10 cards with no > > hope of WDDM 1.1 upgrade that fixes the GDI problems, for those that > > want to maintain Aero but have almost as close to XP speed as > > possible: > > . > > .
> > 1. At this point you should already have a WDDM 1.0 driver installed, > > with whatever modifications you have done. > > 2. If you have the troubleshooting notch available in the Screen > > Resolution>Advanced Properties, bring it one notch over to the left > > from Full Acceleration (you may try two over... anymore and D3D is > > lost). > > 3. If this setting is not available (like mine). Open Regedit and > > navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\ > > {y our video card’s CLSID – varies from each driver install}\0000 and > > input in: > > “Acceleration.Level"=dword:00000004 > > Or > > (Try 4, 3 ,2, then 1... check to make sure Direct3D vis dxdiag is > > still enabled.. technically at level 3 it is supposed to not work.. > > but in my case D3D stays running but all 2D succesfully takes the > > older recognized pipeline) > > 4. Merge the following into the registry > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Avalon.Graphics] > > [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics] > > [HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Avalon.Graphics] > > (And ideally all other user accounts)
> > 5. DisableHWAcceleration is left enabled, in both cases this is the > > major reason for the speed increase -- and even Aero runs better at > > LOWER cpu usage with it on.. odd-- whatever it works. > > 6. This mode will allow the use of Aero, if done right like this does > > for me, Aero will run as fast as the XPDM drivers for both 2D and > > 3D... much better than stock configuration I had and not what I > > expected. Going to windows Classic mode still running WDDM drivers... > > I gain 20% increase in speed over the XPDM in 3D gaming, 2D elements > > (movies, flash) are faster, the only bog down - that I know off and my > > CPU can keep pace.. is a window drag and resize... even YouTube HD is > > playable... except fullscreen (I am not expecting to get this working > > on my X1200 as it is not accelerated... I need to find a way of > > fooling it to do so).
> This is for those who are stuck with graphics hardware that just went
> legacy status but want to run Windows 7 at top speed just like they
> did with XP/2003. Before someone shoots off with "get a new card", try
> saying that to those who bought laptops very recently stuck with a
> chipset that was not very old but nonetheless made legacy status – or
> making an XP net book run Win7.
> Windows 7/Server 2008 R2 is definitely a nice fast OS, but Microsoft
> decided to clip out any 2D acceleration for any WDDM 1.0 drivers...
> certain recent DX9 cards (ATI) fell into legacy status and will not
> receive the WDDM 1.1 upgrade that restores their old 2D GDI
> acceleration. The way around this is to load XPDM drivers, which is
> easily done with the 32bit Windows. The 64bit Windows is a different
> beast... but it is very possible to load XP drivers and get a fully
> accelerated Windows just as fast as XP’s graphics engine. This affects
> DVD playback, Flash playback, web browsing, and also has an effect on
> 3D gaming when there are 2D elements present (your windows, in game
> FMV’s).
> There are 2 options:
> First being you load XPDM drivers in, regain 2D acceleration and have
> DX9 capabilities, and loose Aero. Note: This should only be done if
> the WDDM 1.0 settings down below do not work or your 2D application is
> horribly bogged down still and Aero cannot be enabled which acts like
> fully asccelerated GDI (Eg. older Autocad). The default registry
> settings are not optimal either way for DX9 cards.
> .
> .
> ~~~~~Option 1 – XPDM install on a 64Bit OS
> .
> .
> 1. First, download your favourite XP graphics driver you know that
> works well on XP.
> 2. Extract the driver from its installer and open the driver’s INF
> file
> 3. Look for your graphics card and its corresponding PCI_ID, example:
> "ATI Radeon X1200 Series " = ati2mtag_RS690M, PCI\VEN_1002&DEV_791F
> 4. This example has my laptop’s chipset listed, the “ati2mtag_RS690M”
> is our point of interest, CTRL+F and search for later occurrences of
> it
> 5. You will arrive to this point in file (for your specific card...
> mine is an example)
> [ati2mtag_RS690M]
> FeatureScore=FC
> CopyFiles=ati2mtag.Miniport, ati2mtag.Display, ati2mtag.OpenGL,
> ati2mtag.Wow64OpenGL, Uninstall.CopyFiles, ati2mtag.OGL,
> ati2mtag.ORCA;, DVCR.CopyCodec
> AddReg=Uninstall.AddReg
> DelFiles=ati2mtag_DelFiles
> UninstallFiles=Uninstall.CopyFiles
> UninstallReg=Uninstall.AddReg
> CleanFiles=ati2mtag.Miniport, ati2mtag.Display, ati2mtag.OpenGL,
> ati2mtag.Wow64OpenGL, ati2mtag.OGL, ati2mtag.ORCA
> CleanReg=ati2mtag_SoftwareDeviceSettings,
> ati2mtag_RS690M_SoftwareDeviceSettings,
> atioglxx_OpenGLSoftwareSettings,
> ati2mtag_Mobile_SoftwareDeviceSettings,
> ati2mtag_MobileLargeDesktopSettings
> CleanService=ati2mtag_RemoveService
> 6. The FeatureScore=FC line is what I added to the INF under my
> device’s installation section as shown above, this is what makes or
> breaks an INF from installing on Windows 7. “FC” is chosen so the OS
> recognizes the INF as an XPDM driver and to install it accordingly. If
> the FeatureScore is set to mimic a Windows Vista or 7 drivers (F6 and
> E6 respectively), the driver will install wrong and not start! More
> info on FeatureScore can be found here>>http://msdn.microsoft.com/en-us/library/ee229540.aspx > 7. Save the modified INF and go to Device Manager, select the
> offending graphics card and update its drivers, answer the nag prompts
> from Windows as required to get it installed.
> 8. Merge the following dwords into your registry (I do not know of
> HKLM takes precedence yet... MS is very stupid setting the engine by
> the user... so go through the keys in HKEY_USERS and add this in...
> especially for .DEFAULT as this is the login screen)
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Avalon.Graphics]
> [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics]
> [HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Avalon.Graphics]
> (And ideally all other user accounts)
> 9. This forces GDI acceleration (DisableHWAcceleration was done on
> purpose to force the GDI hooks.. the XPDM driver will accelerate them
> in this situation) and all 2D speed should be back just as it was with
> XP. Test your 3D, it should remain quick, but I have gotten the WDDM
> 1.0 fully accelerated Aero mode to finally match, and Classic is 20%
> faster (only window drag and resize piss off the CPU - not bad).
> .
> .
> ~~~~~~Option 2 – WDDM compatibility maintained, for DX10 cards with no
> hope of WDDM 1.1 upgrade that fixes the GDI problems, for those that
> want to maintain Aero but have almost as close to XP speed as
> possible:
> .
> .
> 1. At this point you should already have a WDDM 1.0 driver installed,
> with whatever modifications you have done.
> 2. If you have the troubleshooting notch available in the Screen
> Resolution>Advanced Properties, bring it one notch over to the left
> from Full Acceleration (you may try two over... anymore and D3D is
> lost).
> 3. If this setting is not available (like mine). Open Regedit and
> navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\
> {y our video card’s CLSID – varies from each driver install}\0000 and
> input in:
> “Acceleration.Level"=dword:00000004
> Or
> (Try 4, 3 ,2, then 1... check to make sure Direct3D vis dxdiag is
> still enabled.. technically at level 3 it is supposed to not work..
> but in my case D3D stays running but all 2D succesfully takes the
> older recognized pipeline)
> 4. Merge the following into the registry
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Avalon.Graphics]
> [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics]
> [HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Avalon.Graphics]
> (And ideally all other user accounts)
> 5. DisableHWAcceleration is left enabled, in both cases this is the
> major reason for the speed increase -- and even Aero runs better at
> LOWER cpu usage with it on.. odd-- whatever it works.
> 6. This mode will allow the use of Aero, if done right like this does
> for me, Aero will run as fast as the XPDM drivers for both 2D and
> 3D... much better than stock configuration I had and not what I
> expected. Going to windows Classic mode still running WDDM drivers...
> I gain 20% increase in speed over the XPDM in 3D gaming, 2D elements
> (movies, flash) are faster, the only bog down - that I know off and my
> CPU can keep pace.. is a window drag and resize... even YouTube HD is
> playable... except fullscreen (I am not expecting to get this working
> on my X1200 as it is not accelerated... I need to find a way of
> fooling it to do so).
