win7 it works !!

[caskad]

Hello,

after trying various system for groovymame, it's ok for win 7


thx!!!!!

[Calamity]

Hi caskad,

Are you using the same setup you mentioned here?:

http://forum.arcadecontrols.com/index.php?topic=110905.msg1200986#msg1200986

I'm really interested in how this works in Win7.
So you just forced the XP64 drivers on Win7 and it accepted them?
Have you done basic testing of it, does it properly update vertical refresh for different games? Works for interlaced resolutions?

Thanks for testing!

[caskad]

Hello,



I can't test for now, i update my cabs, and my system win7 is still under construction (Jammasd waiting ), but groovymame is OK with command line and switchres with my setup.

Yes actualy using forcing method for drivers, but its ok, there's registry error isuppose (arcadeoSd and driver'slocation in registry), but i just test pacman and some cps2 game... looks like OK

I tell you later when my digging is done

tshuss

[krick]

I think that Windows XP x64 is still the best option for arcade cabinets.

I gave up on Windows 7 for my arcade monitor for two reasons...

1) Vector games like asteroids ran at half-speed.  There's something weird going on in Windows 7 where the refresh rate for interlaced resolutions gets reported at half what it should be.  I suspect it would affect all interlaced games, not just vector games.

2) Windows 7 has issues when switching between interlaced and non-interlaced resolutions as reported on the Ultimarc website...
http://www.ultimarc.com/avgainst.html

Important note about Windows 7

There is currently a known issue with Windows 7 switching between resolutions.

If the desktop is running at an interlaced resolution (eg 640 x 480 on a standard-res monitor), When any game which uses a non-interlaced res is started (which is pretty much any Mame game), an error resuts "Unable to initialize directdraw".

Note this only happens if the desktop is running at an interlaced res, which is the case when using a standard res monitor (not a multi-frequency monitor).

There is a workaround for this: Run the desktop at a non-interlaced res such as 640 x 288. This might mean using a front end which has a 640 x 288 mode such as Mamewah.

The resolution can be switched using the Quickres icon.

Note to Mame devs: This issue does not arise if D3D is selected. But owing to not being able to disable stretching in D3D in Mame this results in a poor quality picture.

[caskad]

I think that Windows XP x64 is still the best option for arcade cabinets.

I gave up on Windows 7 for my arcade monitor for two reasons...

1) Vector games like asteroids ran at half-speed.  There's something weird going on in Windows 7 where the refresh rate for interlaced resolutions gets reported at half what it should be.  I suspect it would affect all interlaced games, not just vector games.

2) Windows 7 has issues when switching between interlaced and non-interlaced resolutions as reported on the Ultimarc website...
http://www.ultimarc.com/avgainst.html

Important note about Windows 7

There is currently a known issue with Windows 7 switching between resolutions.

If the desktop is running at an interlaced resolution (eg 640 x 480 on a standard-res monitor), When any game which uses a non-interlaced res is started (which is pretty much any Mame game), an error resuts "Unable to initialize directdraw".

Note this only happens if the desktop is running at an interlaced res, which is the case when using a standard res monitor (not a multi-frequency monitor).

There is a workaround for this: Run the desktop at a non-interlaced res such as 640 x 288. This might mean using a front end which has a 640 x 288 mode such as Mamewah.

The resolution can be switched using the Quickres icon.

Note to Mame devs: This issue does not arise if D3D is selected. But owing to not being able to disable stretching in D3D in Mame this results in a poor quality picture.

hello krick,

Probably true for vector games, (doesn't matter in fact, i play only 80'games), and i don't use arcadevga anymore^^, so no direct draw initialize problem

just some fiew "bsod" when Alt-Tab, but it sems to be know as bug and ran perfectly under hyperspin after all.

 But... groovymame seems to use mame's ini instead of switchrez (failed to initialize).

SO after diging, it appears some games have wrong resolution with it, and we can't use vmmaker to solve the problem... just using soft15khz to inject custom usermodes, but ive upgrade my cabinet (newgame-> mj25), so my modeline with soft 15khz aren't appropriate.. switch back to winxp

windows7 is cool for driver's install with old config, general configuration, and perhaps for pc game compatibility, but taitoX game (unplayable with hd4350), are a little slower with this OS to

cheers!