First a huge thanks to DaOld Man for his MROTATE2 program and to BadBoyBill for his Hyperspin FE.
Hyperotate is a vb script I wrote to help with a problem I was having with Hyperspin and my rotating monitor.
Namely Hyperspin doesn't rotate it's view (like Mala can) The setup of Hyperspin is designed for a standard
horizontal layout. Also there was no way already built in to Hyperspin to call MROTATE2.
Using Hyperlaunch (Hyperspins Autohotkey scripting) the rom name is sent to Hyperotate which checks an
ini file of all rom names and their rotating degrees, then calls MROTATE2 with the appropriate command line to
turn the monitor or leave it be, if it's in the right orientation. When you click out of your mame game back to
the FE, MROTATE2 is called again to turn back into the horizontal orientation.
The ini file currently holds over 8300 roms (as of the .133 release) with all their rotation values. Most monitors
are either in the 0 (horizontal) or 90(vertical) position, however you will see rotation values of 180 and 270. I assume this
is a reflection on how the standard monitor for that rom's cabinet was put in. In these cases you will need to use mame's
menu (tab key) to change to the correct orientation. This change should be saved in mame's cfg folder for the next run of the game.
Do not worry MRotate will not try and rotate your monitor 270 degrees. I only send 90 degrees no matter what (unless 0).
I wrote this with Hyperspin in mind, but I see no reason why it could not work with any other Frontend that will let you
call an outside executable with the rom name on game start-up.
If you have any questions feel free to ask and I hope someone finds this useful. My way of saying thanks to the community
who got me hooked on a fantastic hobby.