resolution assistance

[dax]

I'm hoping someone can help me with this issue.  I keep working on settings and just do not know what's wrong.

First, I have a P3-550 running two versions of mame: .69 dos and 102.  I think the computer is too slow to run 102, but .69 runs well.  The problem is there are differences in how these two versions work and read config/rom info and I can't seem to get straight answers on the details.

I have a ArcadeVGA card and can't seem to figure out how to force the proper video modes for the games.  When I run 0.69 from ArcadeOS the video modes generally look really nice.  When I run 102 from MameWAH, the modes are horrible if they display at all (I have to hit ALT-ESC after the screen blanks to get the "ok" screen, and the resolution looks to be something like 640x480).

1.  Does 0.69 read the .ini files in /mame/ini ?  Or does it use that older .cfg style?

I am playing around with running .69 and .102 in Mamewah to figure out if the different versions read the same config files - I cannot figure this out yet.  102 seems to not work properly except the mame32 version.  0.69 runs much better, so I'm assuming it has better code to select monitor mode or isn't confused by some other ini file?

And does anybody know what mame.dat does?

What files and things to do I need to get working to get the game resolutions proper?

EDIT: removed some questions I got answers for

[dax]

Update... I figured out the Mamewah resolution generation tool and got it working.  The problem is the sequence of events you need to do are not clearly outlined (if you update the game list, alter the resolution, auto-generate native resolutions and generate ini files out of sequence, it un-does previous settings).  Now that I've gotten the ini files generated, I can't seem to get the windows command line version of mame102 to read them when called from Mamewah and I still don't know why.

[subcriminal]

If the inipath is set correctly in mame.cfg. It should read the resolution ok. Have you opened a cmd prompt and typed 'mame gamename -verbose'? When you exit the game there'll be some info in the cmd prompt to tell you if the ini file was read or not. I had a problem with the mamewah res tool generating ini files that mame didn't recognise, I cleared the folder and regenerated them and it worked. Strange.

[dax]

Thanks for the reply!

I still have this problem.  MameWah just shows every game in the same, high resoluion...

My directory setup is this:

c:\mame  (standard with all the roms, artowrk, ini, etc)
c:\mame\mamewah (contains the Mamewah files, mamewah's ini dir, etc.)

I have two versions of mame in the c:\mame directory, mamep102.exe and dmame.exe (0.69 that I use with ArcadeOS)

Now IF these two versions create files of the same name somewhere that conflict with other versions, this might have something to do with the problem, but I can run 0.69 through AOS with no trouble, and then command line mamep102 from DOS or Mame32, but just not Mamewah - it does not work. (mamep102 is the windows command line version of mame)

I notice that since I renamed the program to mamep102.exe, it expects to see mamep102.ini - so I have that file set up, and I've made copies of it everywhere trying to figure out where MameWah expects it to be, because it sure as hell isn't looking for it in \mame for some reason...

when I run from Mamewah here's what I get: (running RType II for example)

loading roms..
parsing mamep102.ini ... N/A
parsing drivers/m72.ini ... N/A
parsing rtype2.ini ... OK
...

It finds the .ini file for rtype2, but it doesn't find the mamep102.ini???  This doesn't make sense since the rtype2.ini file would be in the standard mame path, just like where mamep102.ini is.

Here are my config file contents:

/mame/mamewah/mamewah.ini:

### mamewah.ini (mamewah v1.61) ###

### (Global) Screen-Saver Options ###
delay                       300
slide_duration              3

### Audio Options ###
enable_sounds               1
sound_volume                100
music_path                 
enable_music                1
music_volume                100

### Movie Options ###
intro_movie_file           
exit_movie_file             
keep_movie_preview_aspect   game_aspect
delay_before_movie_preview  2
music_movie_mix             mute_movies
movie_volume                100

### Misc Options ###
layout                      Classic 640x480
ctrlr                       
wrap_list                   0
remember_current_game       1
keep_image_aspect           1
refresh_images              0
correct_orientations        horizontal
safe_mode                   0
show_cursor                 0
keyboard_led_states         -,-,-
winipac_file               
mamewah_ipc_file           
lcd_com_port                1
lcd_settings               
exit_action                 windows

/mame/mamewah/ini/mame.ini:

### mame.ini (mamewah v1.61) ###

emulator_title                            M.A.M.E.

### List Generation Settings ###
rom_path                                  c:\mame\roms
rom_extension                             zip
dat_file                                  c:\mame\arcadeos\mame.dat
nms_file                                 
catver_ini_file                           
list_generation_method                    rom_folder_vs_listinfo

### Execution Settings ###
emulator_executable                       c:\mame\mamep102.exe
commandline_format                        [name] -readconfig
alt_commandline_format_1                  [name]{autodosbox}{nosafelaunch}
alt_commandline_format_2                  [name]{autodosbox}{nosafelaunch}
game_specific_config_path                 

### Artwork Locations ###
artwork_1_image_path                      c:\mame\snap
artwork_2_image_path                      c:\mame\marquees
artwork_3_image_path                      c:\mame\cabinets
artwork_4_image_path                      c:\mame\cpanels
artwork_5_image_path                     
artwork_6_image_path                     
artwork_7_image_path                     
artwork_8_image_path                     
artwork_9_image_path                     
artwork_10_image_path                     
movie_preview_path                       
movie_artwork_no                          1

### Screen-Saver Settings ###
enable_music_in_screensaver               1
saver_type                                slideshow

\mame\mamep102.ini

### MAMEP102.ini ###

### Frontend Related ###

### Windows path and directory options ###
rompath                 roms
samplepath              samples
inipath                 ini
cfg_directory           cfg
nvram_directory         nvram
memcard_directory       memcard
input_directory         inp
hiscore_directory       hi
state_directory         sta
artwork_directory       artwork
snapshot_directory      snap
diff_directory          diff
ctrlr_directory         ctrlr
cheat_file              cheat.dat

### Windows video options ###
autoframeskip           1
frameskip               0
waitvsync               0
triplebuffer            0
window                  0
ddraw                   1
direct3d                0
hwstretch               1
# screen                <NULL> (not set)
cleanstretch            auto
resolution              auto
refresh                 0
scanlines               0
switchres               1
switchbpp               1
maximize                1
keepaspect              1
matchrefresh            0
syncrefresh             0
throttle                1
full_screen_brightness   0.000000
frames_to_run           0
effect                  none
screen_aspect           4:3

### Windows Direct3D 2D video options ###
zoom                    2
d3dtexmanage            1
d3dfilter               1
d3dfeedback             0
d3dscan                 100
d3deffectrotate         1
d3dprescale             auto
d3deffect               none
# d3dcustom             <NULL> (not set)
# d3dexpert             <NULL> (not set)

### Windows misc options ###
sleep                   1
rdtsc                   0
high_priority           0

### Windows sound options ###
audio_latency           1
# wavwrite              <NULL> (not set)

### Input device options ###
mouse                   0
joystick                0
lightgun                0
dual_lightgun           0
offscreen_reload        0
steadykey               0
keyboard_leds           1
led_mode                ps/2
a2d_deadzone            0.300000
# ctrlr                 <NULL> (not set)
paddle_device           keyboard
adstick_device          keyboard
pedal_device            keyboard
dial_device             keyboard
trackball_device        keyboard
lightgun_device         keyboard
digital                 none

### Mame CORE video options ###
norotate                0
ror                     0
rol                     0
autoror                 0
autorol                 0
flipx                   0
flipy                   0
gamma                   1.000000
brightness              1.000000
pause_brightness        0.650000

### Mame CORE vector game options ###
antialias               1
translucency            1
beam                    1.000000
flicker                 0.000000
intensity               1.500000

### Mame CORE sound options ###
samplerate              44100
samples                 1
sound                   1
volume                  0

### Mame CORE misc options ###
artwork                 0
use_backdrops           1
use_overlays            1
use_bezels              1
artwork_crop            0
artwork_resolution      0
cheat                   0
debug                   1
# debugscript           <NULL> (not set)
# playback              <NULL> (not set)
# record                <NULL> (not set)
log                     1
oslog                   1
skip_gameinfo           0
bios                    default
# state                 <NULL> (not set)
autosave                0

### Configuration options ###
readconfig              1
verbose                 1

[dax]

Here's what the mamewah log shows:

1/4/06 12:37:25 PM MAMEWAH launched
1/4/06 12:37:25 PM Desktop colour: 0
1/4/06 12:37:25 PM Wallpaper filename:
1/4/06 12:37:25 PM Display mode: 800x600 @ 0Hz, 32 bit colour
1/4/06 12:37:25 PM Decimal symbol: '.'
1/4/06 12:37:25 PM Games list read: mame-0.lst
1/4/06 12:37:28 PM Layout selected: C:\MAME\MAMEWAH\layouts\Classic 640x480\layout.lay
1/4/06 12:37:29 PM Ctrlr file selected: C:\MAME\MAMEWAH\ctrlr\default.ini
1/4/06 12:37:34 PM Commandline run: c:\MAME\MAMEP102.EXE RTYPE2 -readconfig {flags=18}

It still can't find the mamep102.ini.  I put the file in both mamewah's directory and in \mame and Mamewah still doesn't find it... 

Where is it coming up with this 800x600 display mode?

If I put mamep102.ini in \mame\ini  then when MameWah spawns mame, it reads the ini file, HOWEVER, it still shows every game in 800x600... arg!

[2600]

Take out -readconfig in
/mame/mamewah/ini/mame.ini

[dax]

Take out -readconfig in
/mame/mamewah/ini/mame.ini

Done.  Makes no difference.  I only put that option there for debugging and it seems to have no bearing on the operation of Mame.

Where is this 800x600 coming from?

I removed the reference to mame.dat from the mame.ini and it still didn't help.

I am thinking this must have something to do with the way mamewah is configured.

Is it possible that MameWah no longer supports Windows 98?  Or maybe it never has and that's my mistake?  I'm running Win98.

[Minwah]

I notice that since I renamed the program to mamep102.exe, it expects to see mamep102.ini - so I have that file set up, and I've made copies of it everywhere trying to figure out where MameWah expects it to be, because it sure as hell isn't looking for it in \mame for some reason...

OK I didn't read this thread before so I guess this is what you have been picking about.  Anyway...

You are correct in your above assumption (in theory)...however there were some problems (mame bug) in the past with MAME parsing the correct ini file (there are threads about it here).  My suggestion is to copy your correctly configured 'mamep102.ini' to 'mame.ini' (in the same folder) - see if that works.  Failing that rename mamep102.exe to mame.exe, and rename mamep102.ini to mame.ini.

Oh, and ALWAYS run MAME from a commandline to begin with until you are happy with its configuration - then run it from the FE.

[dax]

Ok, I'm going to test this now.  I may have actually tried this before too.  I know I was shuffling ini files all over the place trying to get this to work.  I will report back right away.

Thanks for the reply!!

[dax]

Still no luck... this is driving me nuts....

I copied mamep102.ini to mame.ini and stuck it everywhere, from \mame to \mame\ini to \mame\mamewah and it still didn't work.  I even deleted \mame\mamewah\ini\mame.ini and redid it, and no luck.

Here's my \mame\mame.cfg:  (if this helps)

emulate_three = no
[directory]
rompath = roms
samplepath = samples
cfg = cfg
nvram = nvram
memcard = memcard
inp = inp
hi = hi
sta = sta
artwork = artwork
snap = snap
diff = diff
ctrlr_directory = ctrlr

[config]
scanlines = no
stretch = no
artwork = yes
use_backdrops = yes
use_overlays = yes
use_bezels = yes
artwork_crop = no
resolution = auto
samples = yes
vsync = no
waitvsync = no
triplebuffer = no
tweak = no
vesamode = vesa3
mmx = auto
dirty = auto
antialias = yes
translucency = yes
vgafreq = -1
alwayssynced = no
depth = auto
skiplines = 0
skipcolumns = 0
beam = 1.000000
flicker = 0.000000
intensity = 1.500000
gamma = 1.2000
brightness = 1.000000
frameskip = auto
throttle = yes
norotate = no
ror = no
rol = no
autoror = no
autorol = no
flipx = no
flipy = no
keepaspect = yes
screen_aspect = 4:3
soundcard = 1
sound = yes
samplerate = 22050
stereo = yes
volume = 0
sampleratedetect = no
resamplefilter = no
mouse = no
joystick = auto
steadykey = no
keyboard_leds = yes
ctrlr = standard
cheat = no
cheatfile = cheat.dat
historyfile = history.dat
mameinfofile = mameinfo.dat
resolution = auto
vectorres = auto
debug_resolution = auto
language = english
monitor = standard
centerx = 0
centery = 0
waitinterlace = no
pause_brightness = 0.650000
skip_disclaimer = no
skip_gameinfo = no
crconly = no
bios = 0
maxlogsize = -1
artwork_resolution = auto
ym3812opl = no
hotrod = no
hotrodse = no
debug = yes

[tweaked]
224x288_h = 95
224x288_v = 84
240x256_h = 103
240x256_v = 35
256x240_h = 85
256x240_v = 67
256x256_h = 108
256x256_v = 35
256x256_hor_h = 85
256x256_hor_v = 96
288x224_h = 95
288x224_v = 12
240x320_h = 90
240x320_v = 140
320x240_h = 95
320x240_v = 12
336x240_h = 95
336x240_v = 12
384x224_h = 108
384x224_v = 12
384x240_h = 108
384x240_v = 12
384x256_h = 108
384x256_v = 35
224x288arc_h = 93
224x288arc_v = 56
288x224arc_h = 93
288x224arc_v = 9
256x240arc_h = 93
256x240arc_v = 9
256x256arc_h = 93
256x256arc_v = 23
320x240arc_h = 105
320x240arc_v = 9
320x256arc_h = 105
320x256arc_v = 23
352x240arc_h = 106
352x240arc_v = 9
352x256arc_h = 106
352x256arc_v = 23
368x224arc_h = 106
368x224arc_v = 9
368x240arc_h = 106
368x240arc_v = 9
368x256arc_h = 106
368x256arc_v = 23
512x224arc_h = 191
512x224arc_v = 9
512x256arc_h = 191
512x256arc_v = 23
512x448arc_h = 191
512x448arc_v = 9
512x512arc_h = 191
512x512arc_v = 23
640x480arc_h = 193
640x480arc_v = 9

[dax]

I'm going to dump whatever files I can in hopes of figuring out WTF is wrong..

\mame\error.log:

using performance counter for timing ... cycles/second = 1193180
width 384, height 256 depth 16
set visible area 0-0 0-0
set visible area 64-447 128-383
Physical width 640, height 480
Machine reset
Warning: sound latch 0 written before being read. Previous: 00, new: 20
cpu #0 (PC=00010413): unmapped I/O byte write to 0000008C = 10
cpu #0 (PC=00010413): unmapped I/O byte write to 0000008D = 00
cpu #1 (PC=000001EF): unmapped I/O byte write to 00000087 = 00
cpu #1 (PC=000001FC): unmapped I/O byte write to 00000087 = 01
cpu #1 (PC=000001EF): unmapped I/O byte write to 00000087 = 00
cpu #1 (PC=000001FC): unmapped I/O byte write to 00000087 = 01

(some of this data may be old, I don't know)

\mame\mamewah\mamewah.log  (Note this indicates the 800x600 resolution - which is where things are wrong -- further evidence Mamewah has something to do with this?):


1/9/06 1:59:02 PM MAMEWAH launched
1/9/06 1:59:02 PM Desktop colour: 0
1/9/06 1:59:02 PM Wallpaper filename:
1/9/06 1:59:02 PM Display mode: 800x600 @ 0Hz, 32 bit colour
1/9/06 1:59:02 PM Decimal symbol: '.'
1/9/06 1:59:03 PM Games list read: mame-0.lst
1/9/06 1:59:05 PM Layout selected: C:\MAME\MAMEWAH\layouts\Classic 640x480\layout.lay
1/9/06 1:59:06 PM Ctrlr file selected: C:\MAME\MAMEWAH\ctrlr\default.ini
1/9/06 1:59:10 PM Commandline run: c:\MAME\MAMEP102.EXE RTYPE2 {flags=17}
1/9/06 1:59:28 PM MAMEWAH quit

1/9/06 2:01:12 PM MAMEWAH launched
1/9/06 2:01:12 PM Desktop colour: 0
1/9/06 2:01:12 PM Wallpaper filename:
1/9/06 2:01:12 PM Display mode: 800x600 @ 0Hz, 32 bit colour
1/9/06 2:01:12 PM Decimal symbol: '.'
1/9/06 2:01:12 PM Games list read: -0.lst
1/9/06 2:01:13 PM Layout selected: C:\MAME\MAMEWAH\layouts\Classic 640x480\layout.lay
1/9/06 2:01:13 PM Ctrlr file selected: C:\MAME\MAMEWAH\ctrlr\default.ini
1/9/06 2:01:19 PM MAMEWAH quit

1/9/06 2:02:10 PM MAMEWAH launched
1/9/06 2:02:10 PM Desktop colour: 0
1/9/06 2:02:10 PM Wallpaper filename:
1/9/06 2:02:10 PM Display mode: 800x600 @ 0Hz, 32 bit colour
1/9/06 2:02:10 PM Decimal symbol: '.'
1/9/06 2:02:10 PM Games list read: mame-0.lst
1/9/06 2:02:11 PM Layout selected: C:\MAME\MAMEWAH\layouts\Classic 640x480\layout.lay
1/9/06 2:02:11 PM Ctrlr file selected: C:\MAME\MAMEWAH\ctrlr\default.ini
1/9/06 2:02:14 PM Commandline run: c:\MAME\MAMEP102.EXE RTYPE2 {flags=9}
1/9/06 2:02:35 PM MAMEWAH quit

1/9/06 2:02:55 PM MAMEWAH launched
1/9/06 2:02:56 PM Desktop colour: 0
1/9/06 2:02:56 PM Wallpaper filename:
1/9/06 2:02:56 PM Display mode: 800x600 @ 0Hz, 32 bit colour
1/9/06 2:02:56 PM Decimal symbol: '.'
1/9/06 2:02:56 PM Games list read: mame-0.lst
1/9/06 2:02:57 PM Layout selected: C:\MAME\MAMEWAH\layouts\Classic 640x480\layout.lay
1/9/06 2:02:57 PM Ctrlr file selected: C:\MAME\MAMEWAH\ctrlr\default.ini
1/9/06 2:02:59 PM Commandline run: c:\MAME\MAMEP102.EXE RTYPE2 {flags=10}
1/9/06 2:03:13 PM MAMEWAH quit


Again, let me REITERATE that I can do this from DOS:
cd \mame
mamep102.exe rtype2

and the game runs perfectly in 392x240 resolution as indicated in \mame\ini\rtype2.ini

as you can see from the logs above, MameWah is also running the same version of mame, but it throws it into 800x600.  Note that this is the command line version of Mame and not Mame32.

So what is wrong here?

[dax]

Renaming mamep102.exe to mame.exe and changing the reference in the mamewah\ini\mame.ini file didn't make a difference.

Here's the version of mame.ini that's in \mame and \mame\ini

### MAMEP102.ini ###

### Frontend Related ###

### Windows path and directory options ###
rompath                 roms
samplepath              samples
inipath                 ini
cfg_directory           cfg
nvram_directory         nvram
memcard_directory       memcard
input_directory         inp
hiscore_directory       hi
state_directory         sta
artwork_directory       artwork
snapshot_directory      snap
diff_directory          diff
ctrlr_directory         ctrlr
cheat_file              cheat.dat

### Windows video options ###
autoframeskip           1
frameskip               0
waitvsync               0
triplebuffer            0
window                  0
ddraw                   1
direct3d                0
hwstretch               1
# screen                <NULL> (not set)
cleanstretch            auto
resolution              auto
refresh                 0
scanlines               0
switchres               1
switchbpp               1
maximize                1
keepaspect              1
matchrefresh            0
syncrefresh             0
throttle                1
full_screen_brightness   0.000000
frames_to_run           0
effect                  none
screen_aspect           4:3

### Windows Direct3D 2D video options ###
zoom                    2
d3dtexmanage            1
d3dfilter               1
d3dfeedback             0
d3dscan                 100
d3deffectrotate         1
d3dprescale             auto
d3deffect               none
# d3dcustom             <NULL> (not set)
# d3dexpert             <NULL> (not set)

### Windows misc options ###
sleep                   1
rdtsc                   0
high_priority           0

### Windows sound options ###
audio_latency           1
# wavwrite              <NULL> (not set)

### Input device options ###
mouse                   0
joystick                0
lightgun                0
dual_lightgun           0
offscreen_reload        0
steadykey               0
keyboard_leds           1
led_mode                ps/2
a2d_deadzone            0.300000
# ctrlr                 <NULL> (not set)
paddle_device           keyboard
adstick_device          keyboard
pedal_device            keyboard
dial_device             keyboard
trackball_device        keyboard
lightgun_device         keyboard
digital                 none

### Mame CORE video options ###
norotate                0
ror                     0
rol                     0
autoror                 0
autorol                 0
flipx                   0
flipy                   0
gamma                   1.000000
brightness              1.000000
pause_brightness        0.650000

### Mame CORE vector game options ###
antialias               1
translucency            1
beam                    1.000000
flicker                 0.000000
intensity               1.500000

### Mame CORE sound options ###
samplerate              44100
samples                 1
sound                   1
volume                  0

### Mame CORE misc options ###
artwork                 0
use_backdrops           1
use_overlays            1
use_bezels              1
artwork_crop            0
artwork_resolution      0
cheat                   0
debug                   1
# debugscript           <NULL> (not set)
# playback              <NULL> (not set)
# record                <NULL> (not set)
log                     1
oslog                   1
skip_gameinfo           0
bios                    default
# state                 <NULL> (not set)
autosave                0

### Configuration options ###
readconfig              1
verbose                 1

[Minwah]

\mame\mamewah\mamewah.log  (Note this indicates the 800x600 resolution - which is where things are wrong -- further evidence Mamewah has something to do with this?):

All this part in Mamewah does is read your current (desktop) display settings...so that it can switch back to them after you quit Mamewah (if you are using a layout with a different mode to your desktop).  Launch a few games and check the log and you'll see that line is only displayed once, after launching Mamewah.

Earlier on you said this was displayed:

'loading roms..
parsing mamep102.ini ... N/A
parsing drivers/m72.ini ... N/A
parsing rtype2.ini ... OK'

...does that still happen if you run Mame from a command prompt?  If so we need to figure out why mamep102.ini isn't being parsed.  What I suggest is the following:

Move any non-Windows commandline versions of Mame (dos mame inc. mame.cfg, mame32 etc. and associated files into another directory out of the way,
Make sure your (Windows commandline) Mame executable is called mame.exe,
Delete any ini files you have in the \mame folder (leave the ones in the \mame\ini folder tho),
Go to a command prompt and do a 'mame -cc' to create a fresh mame.ini,
Leave mame.ini as default and run a game - see if mame.ini is parsed.

Next you could change a few obvious settings (not the inipath one tho) to make sure the settings are taking effect - set the resolution to 1024x768 or something (assuming you're not using an arcade monitor).

If the above works you should be almost there...

[dax]

Minwah,

Thanks very much for your assistance here.  I'm still having problems.  I did everything you suggested.  I wiped all the ini and cfg files and created them from scratch.  No luck.  I did notice that if mame.ini is in \mame it shows <null> for inipath, but if you move mame.ini to \mame\ini it will show properly when mame -sc is run.

To clean things up, I've installed Mame 0.69 and am running the i686 version (which is not the "dos" version so I assume this is the "windows command line" version you mention).

I am still having problems and I just don't know what is going on.

Many games, when run from MameWah, show in the wrong resolution.  But I can open a DOS window from Win98 and type "mame (gamename)" and they display perfectly.  It seems like when invoked from MameWah, the .ini files are being ignored.

I am at my wits end.  I just can't figure out why from MameWah, things don't work right.  I've removed all extraneous config files, all other Mame versions and it's still messed up.

Could this possibly have anything to do with my directory structure? 

Mame's root is c:\mame, but MameWah is in c:\mame\mamewah

When MameWah invokes mame, does it change the directory to c:\mame?  If not, this could possibly be the problem, and I'm wondering if I moved MameWah's files into c:\mame, would this help?  I'd prefer not to do that and mix that stuff together.  Plus, MameWah expects a mame.ini in it's ini folder that is different from what Mame expects in a similar path.  But I tried the -inipath parm in the config and that didn't work. 

Any help?   Anybody?  I'm so close to having all of this working beautifully and I really like MameWah, but I cannot for the life of me figure out why the games are displaying in the wrong resolution... any help from anybody would be much appreciated!!

[dax]

If the inipath is set correctly in mame.cfg. It should read the resolution ok. Have you opened a cmd prompt and typed 'mame gamename -verbose'? When you exit the game there'll be some info in the cmd prompt to tell you if the ini file was read or not. I had a problem with the mamewah res tool generating ini files that mame didn't recognise, I cleared the folder and regenerated them and it worked. Strange.

I've done all that.  The problem is, when I run Mame from the command line manually, everything works perfect.  It's only when it's run from MameWah that things are messed up.