Updating from .160 to .169 incl Drivers

[Sledge]

I'm going to start this thread to keep it all in one spot and to help anyone else who needs to update from older GM etc to new.

I started by just putting the new mame.exe into the folder and switching to d3d9ex, running it to see how it would go, and it worked to a degree, but some games didn't work at all, others ran way too fast.
So I created a new mame.ini and made the appropriate adjustments for my monitor etc, and pretty much everything seems ok now as far as the few games i tested..

EXCEPT for mame run from cmd (no game). I get a really fast scrolling picture like it's out of sync. How do i fix this? (log attached)
Older mame would display on screen perfectly.

But.. what about the new drivers etc, how do i setup VMM now with my custom monitors preset?
Like i've done with vmm.ini and monitor.ini ? Is that all?

[Calamity]

VMMaker 2.0 is configured through the settings dialog, instead of vmm.ini. You need to create the moddrss with vmmaker 2.0 in order to use gm 169

[Sledge]

VMMaker 2.0 is configured through the settings dialog, instead of vmm.ini. You need to create the moddrss with vmmaker 2.0 in order to use gm 169

Ok, will look at that tomorrow...
moddrss ??

[Calamity]

Haha I meant modes, sorry, writting from a phone.

[Sledge]

Ok, I've updated the drivers, and used VMM to create the modes (ms9-29 15Khz only) and installed them, however when i switch to a 15Khz mode I get this:

I've tried adjusting the H.H.15 pot to adjust the horizontal hold, but nothing changes for the better as far as i can see..
Any ideas?

[Sledge]

I un-installed the drivers, and reinstalled the old ones again, but the same things happen now as before..
Before i run VMM i can't get the correct resolution to stick, but i persevere and run the new VMM, and it displays as above..

[Calamity]

Ok, I see, so you mean with the old drivers you still get the bad vertical sync in the picture. Is your card flashed with ATOM-15?

[Sledge]

Ok, I see, so you mean with the old drivers you still get the bad vertical sync in the picture. Is your card flashed with ATOM-15?

yes and yes

was working fine before update..

[Calamity]

Ok, I see, so you mean with the old drivers you still get the bad vertical sync in the picture. Is your card flashed with ATOM-15?

yes and yes

was working fine before update..

I've experienced weird behaviour when installing the drivers over a flashed card. It's much smoother to install drivers with the original bios, then flash it back with ATOM-15.

[Sledge]

Ok, I see, so you mean with the old drivers you still get the bad vertical sync in the picture. Is your card flashed with ATOM-15?

yes and yes

was working fine before update..

I've experienced weird behaviour when installing the drivers over a flashed card. It's much smoother to install drivers with the original bios, the flash it back with ATOM-15.

ok i'll update when i can with how it went

[Sledge]

ok, i uninstalled the drivers through windows (ticking the remove files box), and flashed the card back to standard, installed new drivers and the same thing happens again..
Still get the rolling picture above..

[Calamity]

The only thing I can think of right now is to try this:
http://forum.arcadecontrols.com/index.php/topic,148919.msg1552995.html#msg1552995

[Sledge]

The only thing I can think of right now is to try this:
http://forum.arcadecontrols.com/index.php/topic,148919.msg1552995.html#msg1552995

Would it be an issue of the previous driver not being removed properly? Is the windows uninstall feature good enough?

[Calamity]

Would it be an issue of the previous driver not being removed properly? Is the windows uninstall feature good enough?

It would be an issue indeed. In my experience the driver management in 7 is pretty good, at least much better than in XP. Double check which version is actually installed, in the device manager. It could be 2.0 has stuck.

[Sledge]

As far as i could tell the driver is changing as i un-install etc, but would there be remnants left that could interfere? Or would removing them be truly removing all of it?

[Calamity]

As far as i could tell the driver is changing as i un-install etc, but would there be remnants left that could interfere? Or would removing them be truly removing all of it?

Yeah they get removed properly, no remnants in my experience. The thing that does happens is the os replacing your drivers with another version it has available if it feels like, without notification.

btw the pictures you posted... it's not h-hold but v-hold what could be wrong.

[Calamity]

Do you get the sync back if you use VMMaker 1.4b? (despite the mode not sticking).

[Sledge]

As far as i could tell the driver is changing as i un-install etc, but would there be remnants left that could interfere? Or would removing them be truly removing all of it?

Yeah they get removed properly, no remnants in my experience. The thing that does happens is the os replacing your drivers with another version it has available if it feels like, without notification.

btw the pictures you posted... it's not h-hold but v-hold what could be wrong.

Yeah pretty sure it was installing the MS WDDM drivers 1.1 (or whatever they're called)
I don't think there's a v-hold adjustment pot on a MS9-29??

Do you get the sync back if you use VMMaker 1.4b? (despite the mode not sticking).

I'll let you know in a few days when i get back...

[Calamity]

Do you get the sync back if you use VMMaker 1.4b? (despite the mode not sticking).

I'll let you know in a few days when i get back...

Anyway, you run VMMaker 2.0 all the time, even when reinstalled the old drivers, didn't you?

[Sledge]

Do you get the sync back if you use VMMaker 1.4b? (despite the mode not sticking).

I'll let you know in a few days when i get back...

Anyway, you run VMMaker 2.0 all the time, even when reinstalled the old drivers, didn't you?

Yes that is correct
I wish i could keep going with it today, but time is short for 2 days

[Calamity]

That's fine, hopefully I'll have a fix by the time you're back.

[Sledge]

That's fine, hopefully I'll have a fix by the time you're back.

Thanks mate..
You really opened up a can of worms with all this new stuff
But we appreciate your hard work!

[Calamity]

You really opened up a can of worms with all this new stuff
But we appreciate your hard work!

Too many new things at the same time, never a good idea 

[Sledge]

Well no matter what i try i can't get it stable now...
Old drivers, old tools,(windows working mostly) old mame.. out of sync
New Tools, new mame... out of sync
Old drivers, new tools out of sync..

Might see if i've got an older image i can put on to get things back up and running, or might start from scratch

[Calamity]

Well no matter what i try i can't get it stable now...
Old drivers, old tools,(windows working mostly) old mame.. out of sync
New Tools, new mame... out of sync
Old drivers, new tools out of sync..

Might see if i've got an older image i can put on to get things back up and running, or might start from scratch

Are you testing beta 4?

Also, you may want to check this guide: http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=298

[Sledge]

Well no matter what i try i can't get it stable now...
Old drivers, old tools,(windows working mostly) old mame.. out of sync
New Tools, new mame... out of sync
Old drivers, new tools out of sync..

Might see if i've got an older image i can put on to get things back up and running, or might start from scratch

Are you testing beta 4?

Also, you may want to check this guide: http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=298

Yep Beta 4, and followed that guide during the first test as well..

[Calamity]

Yep Beta 4, and followed that guide during the first test as well..

That's so strange. At least you should get sync using the old drivers & old tools, it makes me think something else is wrong.

If you decide to follow the guide starting from scratch, please let me know at what step thigs get bad.

[Sledge]

Yep Beta 4, and followed that guide during the first test as well..

That's so strange. At least you should get sync using the old drivers & old tools, it makes me think something else is wrong.

If you decide to follow the guide starting from scratch, please let me know at what step thigs get bad.

Will do.
With GM.169 with old drivers/tools should we be using d3d9ex? or stick with ddraw?
Also, i'm using standard resolutions, not super resolutions, so didn't do that part of the guide..

[Calamity]

Will do.
With GM.169 with old drivers/tools should we be using d3d9ex? or stick with ddraw?
Also, i'm using standard resolutions, not super resolutions, so didn't do that part of the guide..

- Old drivers/old tools -> GM 168
- New drivers/new tools -> GM 169

Don't mix them.

Neither d3d9ex nor ddraw. Always use d3d by default until things are up and running.

[Calamity]

Besides make sure to grab GM 169 fix 3.

[Jonny G]

Neither d3d9ex nor ddraw. Always use d3d by default until things are up and running.

Hi Calamity, just to clarify, we should have D3D set in mame.ini rather than AUTO?

[Calamity]

Hi Calamity, just to clarify, we should have D3D set in mame.ini rather than AUTO?

auto = d3d

[Jonny G]

Thanks for that, you learn something every day.

[Sledge]

Besides make sure to grab GM 169 fix 3.

My mistake sorry, grabbed that, booted in safe mode, removed drivers (to get a stable picture on LCD lol)
Started over, but installing new drivers, ran VMM, (did a little test here and didn't follow your guide, just set it to the correct res (LCD seems to be able to display 640x480 15Khz) and shut down.
Rebooted with CRT connected, and all was good!
Tried (fix 3) Mame with d3d (frame delay on i think), and all good there too so far.

So now i can switch to d3d9ex with frame delay off?

[Calamity]

So now i can switch to d3d9ex with frame delay off?

Sure.

It was a relief to hear that