Attract-Mode Support Forum
Related Stuff => Emulators => Topic started by: KTURNER on December 23, 2016, 10:42:13 AM
-
So I have a xp machine with mameui 0.154 and everything works great on it and my roms are in the mame rom folder. I copied the entire mame folder over to my windows 7 machine and my roms show up but do not run. The rom path is correct. Does anyone know what I am doing wrong?
-
set compatibility mode to Windows XP SP3
-
You might also try redownloading a 0.154 from mame dev and make sure that it is 64-bit for your windows 7. You never did say if you were using windows XP 32 or 64-bit. Most versions of winxp are 32-bit.
The compatibility mode should work though as hermine.potter suggested.
-
I could be underestimating the situation, but did you make sure that your "Executable" path is set correctly under the "Emulators - mame' setting in AM? If it got overlooked, thatll cause the symptoms youre describing.
-
Sorry for the long response. My xp is 32 bit. I though 32 bit would run on 64 but I could be wrong. I tried to change the compatibility mode and it didn't seem to work. It wont work in attract mode or going directly through mame. My main issue was with time crises. My xp machine had mame 32 and mame ui. My sights were off in 32 but not in ui. My windows 7 pc had mame32 only and everything worked great except for time crises. I thought I would just put UI on my windows 7 pc and that would take care of it. I messed around with 32 and figured out how to get the sight adjusted. Apparently you are suppose to hold 9 then f2 and the menu will pop up. For some reason I have to do it 4 or 5 times and hit the fire button before it will work. Its seems ok now. Thanks for all the advise. This is got to be the most helpful forum I've been on. It would still be nice to get ui to work though.
-
Sorry for the long response. My xp is 32 bit. I though 32 bit would run on 64 but I could be wrong. I tried to change the compatibility mode and it didn't seem to work. It wont work in attract mode or going directly through mame. My main issue was with time crises. My xp machine had mame 32 and mame ui. My sights were off in 32 but not in ui. My windows 7 pc had mame32 only and everything worked great except for time crises. I thought I would just put UI on my windows 7 pc and that would take care of it. I messed around with 32 and figured out how to get the sight adjusted. Apparently you are suppose to hold 9 then f2 and the menu will pop up. For some reason I have to do it 4 or 5 times and hit the fire button before it will work. Its seems ok now. Thanks for all the advise. This is got to be the most helpful forum I've been on. It would still be nice to get ui to work though.
Post your mame.ini from MAME and your emulator file from AttractMode.
-
# Generated by Attract-Mode v2.2.0-1
#
executable C:\games\MameUI32_0.155\mameui.exe
args [name]
rompath C:\games\Mame32\roms
romext .zip;.7z;<DIR>
system Arcade
info_source listxml
exit_hotkey Joy0 Button12
artwork flyer
artwork marquee C:\games\attract-v2.2.0-1-win64\menu-art\marquee
artwork snap C:\games\attract-v2.2.0-1-win64\menu-art\snap\mame
artwork wheel
----------------------------------------------------------------------------------------------------------
#
# CORE CONFIGURATION OPTIONS
#
readconfig 1
writeconfig 0
#
# CORE SEARCH PATH OPTIONS
#
rompath C:\games\Mame32\roms
hashpath hash
samplepath samples
artpath artwork
ctrlrpath ctrlr
inipath ini
fontpath .
cheatpath cheat
crosshairpath crosshair
#
# CORE OUTPUT DIRECTORY OPTIONS
#
cfg_directory cfg
nvram_directory nvram
input_directory inp
state_directory sta
snapshot_directory snap
diff_directory diff
comment_directory comments
#
# CORE STATE/PLAYBACK OPTIONS
#
state
autosave 0
playback
record
mngwrite
aviwrite
wavwrite
snapname %g/%i
snapsize auto
snapview internal
statename %g
burnin 0
#
# CORE PERFORMANCE OPTIONS
#
autoframeskip 0
frameskip 0
seconds_to_run 0
throttle 1
sleep 1
speed 1.0
refreshspeed 0
#
# CORE ROTATION OPTIONS
#
rotate 1
ror 0
rol 0
autoror 0
autorol 0
flipx 0
flipy 0
#
# CORE ARTWORK OPTIONS
#
artwork_crop 0
use_backdrops 1
use_overlays 1
use_bezels 1
use_cpanels 1
use_marquees 1
#
# CORE SCREEN OPTIONS
#
brightness 1.0
contrast 1.0
gamma 1.0
pause_brightness 0.65
effect none
#
# CORE VECTOR OPTIONS
#
antialias 1
beam 1.0
flicker 0
#
# CORE SOUND OPTIONS
#
samplerate 48000
samples 1
volume 0
#
# CORE INPUT OPTIONS
#
coin_lockout 1
ctrlr
mouse 1
joystick 1
lightgun 0
multikeyboard 0
multimouse 0
steadykey 0
ui_active 0
offscreen_reload 0
joystick_map auto
joystick_deadzone 0.3
joystick_saturation 0.85
natural 0
joystick_contradictory 0
coin_impulse 0
#
# CORE INPUT AUTOMATIC ENABLE OPTIONS
#
paddle_device mouse
adstick_device keyboard
pedal_device keyboard
dial_device keyboard
trackball_device keyboard
lightgun_device mouse
positional_device keyboard
mouse_device mouse
#
# CORE DEBUGGING OPTIONS
#
update_in_pause 0
debugscript
#
# CORE MISC OPTIONS
#
drc 1
drc_use_c 0
bios
cheat 0
skip_gameinfo 0
uifont default
ramsize
confirm_quit 0
ui_mouse 0
autoboot_command
autoboot_delay 2
autoboot_script
http 0
http_port 8080
http_path web
console 0
#
# OSD DEBUGGING OPTIONS
#
log 0
verbose 0
debug 0
debugger auto
oslog 0
watchdog 0
#
# OSD PERFORMANCE OPTIONS
#
multithreading 0
numprocessors auto
bench 0
#
# OSD VIDEO OPTIONS
#
video auto
numscreens 1
window 1
maximize 1
keepaspect 1
unevenstretch 1
waitvsync 0
syncrefresh 0
#
# OSD PER-WINDOW VIDEO OPTIONS
#
screen auto
aspect auto
resolution auto
view auto
screen0 auto
aspect0 auto
resolution0 auto
view0 auto
screen1 auto
aspect1 auto
resolution1 auto
view1 auto
screen2 auto
aspect2 auto
resolution2 auto
view2 auto
screen3 auto
aspect3 auto
resolution3 auto
view3 auto
#
# OSD FULL SCREEN OPTIONS
#
switchres 0
#
# OSD SOUND OPTIONS
#
sound auto
audio_latency 2
#
# WINDOWS DEBUGGING OPTIONS
#
debugger_font "Lucida Console"
debugger_font_size 9
#
# WINDOWS PERFORMANCE OPTIONS
#
priority 0
profile 0
#
# WINDOWS VIDEO OPTIONS
#
prescale 1
menu 0
#
# DIRECTDRAW-SPECIFIC OPTIONS
#
hwstretch 1
#
# DIRECT3D-SPECIFIC OPTIONS
#
filter 0
#
# DIRECT3D POST-PROCESSING OPTIONS
#
hlsl_enable 0
hlslpath hlsl
hlsl_prescale_x 0
hlsl_prescale_y 0
hlsl_preset -1
hlsl_write
hlsl_snap_width 2048
hlsl_snap_height 1536
shadow_mask_alpha 0.0
shadow_mask_texture aperture.png
shadow_mask_x_count 320
shadow_mask_y_count 240
shadow_mask_usize 0.09375
shadow_mask_vsize 0.109375
curvature 0.03
pincushion 0.03
scanline_alpha 1.0
scanline_size 1.0
scanline_height 1.0
scanline_bright_scale 1.0
scanline_bright_offset 0.0
scanline_jitter 0.0
defocus 0.0,0.0
converge_x 0.3,0.0,-0.3
converge_y 0.0,0.3,-0.3
radial_converge_x 0.0,0.0,0.0
radial_converge_y 0.0,0.0,0.0
red_ratio 1.0,0.0,0.0
grn_ratio 0.0,1.0,0.0
blu_ratio 0.0,0.0,1.0
saturation 1.4
offset 0.0,0.0,0.0
scale 0.95,0.95,0.95
power 0.8,0.8,0.8
floor 0.05,0.05,0.05
phosphor_life 0.4,0.4,0.4
#
# NTSC POST-PROCESSING OPTIONS
#
yiq_enable 0
yiq_cc 3.59754545
yiq_a 0.5
yiq_b 0.5
yiq_o 1.570796325
yiq_p 1.0
yiq_n 1.0
yiq_y 6.0
yiq_i 1.2
yiq_q 0.6
yiq_scan_time 52.6
yiq_phase_count 2
#
# VECTOR POST-PROCESSING OPTIONS
#
vector_length_scale 0.8
vector_length_ratio 500.0
#
# BLOOM POST-PROCESSING OPTIONS
#
vector_bloom_scale 0.3
raster_bloom_scale 0.225
bloom_lvl0_weight 1.0
bloom_lvl1_weight 0.21
bloom_lvl2_weight 0.19
bloom_lvl3_weight 0.17
bloom_lvl4_weight 0.15
bloom_lvl5_weight 0.14
bloom_lvl6_weight 0.13
bloom_lvl7_weight 0.12
bloom_lvl8_weight 0.11
bloom_lvl9_weight 0.10
bloom_lvl10_weight 0.09
#
# FULL SCREEN OPTIONS
#
triplebuffer 0
full_screen_brightness 1.0
full_screen_contrast 1.0
full_screen_gamma 1.0
#
# INPUT DEVICE OPTIONS
#
dual_lightgun 0
-
Please clarify, MAMEUI works but not with AttractMode or MAMEUI doesn't work at all?
-
On my xp pc mameui works in and out of a/m. On my windows 7 pc the exact copy of mameui does not work in or out of a/m.
-
If mameui doesn't work on its own there is no chance it will work in AM. You need to get mameui working first. Run mameui from the command line and provide the results/errors.
-
Mameui will start up and show the roms it just wont run any and I understand it wont work in a/m if it wont work on its own. I am launching it from a shortcut. When I get home I will launch it from a command line and see what it does.
-
I almost want to say there is a mismatch on the rom set/mame version there.
Or a rom path is mis-configured.
Knowing what the command line output says will be very helpful. If it outputs a few missing files for a game then it might be version problem...if it's a whole bunch of them then it might be a path..
and try to use one that doesn't require a bios..it cuts down on problems...
-
I guess I don't understand how the command line works. I launch mame from the command line and it shows up just like it would as if I opened it through the shortcut. I go to cmd and go to my file then type in mameui.exe.
-
ok you are on windows I take it...
when you do type cmd and the cli (command line interface) shows up...you go to the directory. .(or at least you are in the directory I take it..)
type this
mameui dkong
note that i don't know the actual exe name so fill in the blanks if any (it's the mame-exeucuatable.exe game name)
however i am guessing you know at least that or the program wouldn't start..
typing mameui.exe will start mame itself..now that it has it's own "gui"
so as I said you type mameui ..then the game name...that is the ROM name..
mameui dkong will start donkey kong
mame ui pacman will start pacman
ect ect..
now..if any errors popup they will show there in the command line.
this:
"dkongr" approximately matches the following
supported machines (best match first):
dkong Donkey Kong (US set 1)
dkonghrd Donkey Kong (hard kit)
dkongjnrj Donkey Kong Junior (Japan?)
dkongjr Donkey Kong Junior (US set F-2)
tells you that mame that you misspelled it..so mame doesn't recognize anything..so it is nice enough to give you options..
this (most of the time but not all the time)
c_5et_g.bin NOT FOUND (tried in dkong dkong)
c_5ct_g.bin NOT FOUND (tried in dkong dkong)
c_5bt_g.bin NOT FOUND (tried in dkong dkong)
c_5at_g.bin NOT FOUND (tried in dkong dkong)
s_3i_b.bin NOT FOUND (tried in dkong dkong)
s_3j_b.bin NOT FOUND (tried in dkong dkong)
v_5h_b.bin NOT FOUND (tried in dkong dkong)
v_3pt.bin NOT FOUND (tried in dkong dkong)
l_4m_b.bin NOT FOUND (tried in dkong dkong)
l_4n_b.bin NOT FOUND (tried in dkong dkong)
l_4r_b.bin NOT FOUND (tried in dkong dkong)
l_4s_b.bin NOT FOUND (tried in dkong dkong)
c-2k.bpr NOT FOUND (tried in dkong dkong)
c-2j.bpr NOT FOUND (tried in dkong dkong)
v-5e.bpr NOT FOUND (tried in dkong dkong)
Fatal error: Required files are missing, the machine cannot be run. <----
means just that..and you can guess that the path is wrong because the list is so long
c_5et_g.bin NOT FOUND (tried in dkong dkong)
c_5ct_g.bin NOT FOUND (tried in dkong dkong)
c_5bt_g.bin NOT FOUND (tried in dkong dkong)
c_5at_g.bin NOT FOUND (tried in dkong dkong)
s_3i_b.bin NOT FOUND (tried in dkong dkong)
Fatal error: Required files are missing, the machine cannot be run.
means (normally) that is found some of them as valid..but not all of them..thus the game will not run.
This is not scientific by any mans what so ever..but over the years I have learned to notice these things. The shorter list implies two things:
1. Some of the files in the rom have been re-named / named different
2. (or) you are missing some needed (nomally added / updated) rom because of a rom/mame version upgrade
(sometimes both)
Sorry I know that was long...just wanted to give you some info what to look for so you don't have to "wait on us" :)
So I have a xp machine with mameui 0.154 and everything works great on it and my roms are in the mame rom folder. I copied the entire mame folder over to my windows 7 machine and my roms show up but do not run. The rom path is correct. Does anyone know what I am doing wrong?
referring to your op can I ask you have mame version 1.54 64 bit on your win7 machine correct? Remember version mame 1.81 will not version 1.45 roms (or very few of them) you need to have mame version 1.54 for your 1.54 roms (I run that version myself on a machine...and version 1.06 on another.) It doesn't have to be the 64 bit version of mame...but it might make performance smoother in the long run...
-
ok you are on windows I take it...
when you do type cmd and the cli (command line interface) shows up...you go to the directory. .(or at least you are in the directory I take it..)
type this
mameui dkong
note that i don't know the actual exe name so fill in the blanks if any (it's the mame-exeucuatable.exe game name)
however i am guessing you know at least that or the program wouldn't start..
typing mameui.exe will start mame itself..now that it has it's own "gui"
so as I said you type mameui ..then the game name...that is the ROM name..
mameui dkong will start donkey kong
mame ui pacman will start pacman
ect ect..
now..if any errors popup they will show there in the command line.
this:
"dkongr" approximately matches the following
supported machines (best match first):
dkong Donkey Kong (US set 1)
dkonghrd Donkey Kong (hard kit)
dkongjnrj Donkey Kong Junior (Japan?)
dkongjr Donkey Kong Junior (US set F-2)
tells you that mame that you misspelled it..so mame doesn't recognize anything..so it is nice enough to give you options..
this (most of the time but not all the time)
c_5et_g.bin NOT FOUND (tried in dkong dkong)
c_5ct_g.bin NOT FOUND (tried in dkong dkong)
c_5bt_g.bin NOT FOUND (tried in dkong dkong)
c_5at_g.bin NOT FOUND (tried in dkong dkong)
s_3i_b.bin NOT FOUND (tried in dkong dkong)
s_3j_b.bin NOT FOUND (tried in dkong dkong)
v_5h_b.bin NOT FOUND (tried in dkong dkong)
v_3pt.bin NOT FOUND (tried in dkong dkong)
l_4m_b.bin NOT FOUND (tried in dkong dkong)
l_4n_b.bin NOT FOUND (tried in dkong dkong)
l_4r_b.bin NOT FOUND (tried in dkong dkong)
l_4s_b.bin NOT FOUND (tried in dkong dkong)
c-2k.bpr NOT FOUND (tried in dkong dkong)
c-2j.bpr NOT FOUND (tried in dkong dkong)
v-5e.bpr NOT FOUND (tried in dkong dkong)
Fatal error: Required files are missing, the machine cannot be run. <----
means just that..and you can guess that the path is wrong because the list is so long
c_5et_g.bin NOT FOUND (tried in dkong dkong)
c_5ct_g.bin NOT FOUND (tried in dkong dkong)
c_5bt_g.bin NOT FOUND (tried in dkong dkong)
c_5at_g.bin NOT FOUND (tried in dkong dkong)
s_3i_b.bin NOT FOUND (tried in dkong dkong)
Fatal error: Required files are missing, the machine cannot be run.
means (normally) that is found some of them as valid..but not all of them..thus the game will not run.
This is not scientific by any mans what so ever..but over the years I have learned to notice these things. The shorter list implies two things:
1. Some of the files in the rom have been re-named / named different
2. (or) you are missing some needed (nomally added / updated) rom because of a rom/mame version upgrade
(sometimes both)
Sorry I know that was long...just wanted to give you some info what to look for so you don't have to "wait on us" :)
So I have a xp machine with mameui 0.154 and everything works great on it and my roms are in the mame rom folder. I copied the entire mame folder over to my windows 7 machine and my roms show up but do not run. The rom path is correct. Does anyone know what I am doing wrong?
referring to your op can I ask you have mame version 1.54 64 bit on your win7 machine correct? Remember version mame 1.81 will not version 1.45 roms (or very few of them) you need to have mame version 1.54 for your 1.54 roms (I run that version myself on a machine...and version 1.06 on another.) It doesn't have to be the 64 bit version of mame...but it might make performance smoother in the long run...
+1 Good advice.
-
"mameui dkong" this it what I didn't know. I will try that. Thank you very much for the detailed explanation. It was very well written and is great advice for anyone starting out. Its hard to learn how to do this stuff without a little help. As far as the 64 bit question I copied the 32 bit file from my xp onto my windows 7. The entire mame folder with the roms and everything in it. Every thing is and exact duplicate. Even made them have the same path C:\games\mameui.
-
and your path in your mame.ini is set correctly as well?
makes me wonder if that might be the case here...from different from one operating system to another...(yeah I know they are both windows..but still)
example on one linux system I have /home/username/.mame/roms
I can copy every thing over one for one however...
my user name is different on my other computer so my path would be different..
/home/otherusername/.mame/roms
may want to check that...(may not be a problem in windows..but still..you try everything that's what problem solving is)
if you want post the directory paths in you mame.ini from both systems to compare and we can look at them...
I notice from one of your previous posts...(cut down of course)
#
# CORE SEARCH PATH OPTIONS
#
rompath C:\games\Mame32\roms
hashpath hash
samplepath samples
artpath artwork
as that it<i>looks</i> correct....but for pits and piggles...use a full path on the roms on your win7 machine..
also..I take it that you can not get any game to run from mame itself...upon reading on of your posts it seems that you got time crisis to run on the win7 machine?
also please let me know...(because I am assuming that you were about to get mame gui to run) if you are able to start mameui.exe..by itself...then see if it lists any games..if so try to run one from there...
if you can't try in your mame.ini to make your mame path
rompath roms
If you can then I am betting it's something in your AM set up..path or something
these are one of the times if I could get my hands on it I know I could fix it 5 minutes..maybe....
-
Last night I copyed all of my roms into the mame rom folder and made shure my rom path was correct. (Before I was directing it to my mame32 rom folder) I opened mamui and then I refreseh my rom list. All my roms showed up but they still did not work. I went into the command line and once I got into my folder I typed in "mamui.exe timecris" and the screen went blank just like it does when I open it with the shortcut. No errors. Yes Time crises is running on my windows 7 machine but under my mame32. It would be realy nice to get this to work but I guess I could always just use the mame32 but ui is so much better.
-
that is just sooo weird... ???
I'll look into mameui a little more..however I only have a xp box...it's just weird..
so ok you get it to work with the mame32..but not the mameui..correct?
and as your roms are showing up..your rom path in your ini is correct. if that is all set up..(as it to be)..then it should work..without problem...
you said..
I went into the command line and once I got into my folder I typed in "mamui.exe timecris" and the screen went blank just like it does when I open it with the shortcut. No errors.
went blank..what does that mean exactly...so you had to drop out of mameui (esc) as if it had loaded the rom? if that is the case..and that one loads..everything else should too. try renaming your rom folder on your win7 machine...make a new folder the same name as your old on and re-coping one single game..any game..and try to start it. I'm wondering if your zips got corrupted...any out put from the command line would really help..
-
Yes it works with mame 32 but not ui. I can rename my rom path to mame32/roms and it still does not work. I know those zips are not corrupt because they work with mame32. Im at work now but I'm pretty shure I hit esc once the screen went blank. I should have said the screen blacked out. So far the command line has not givin me any output but I will look again. This has turned into a "I have to fix this because I cain't figure it" out and not because I have to kinda thing.
-
Yeah loading it direct from the command line should giveout put..unless of course everything is working correctly to begin with..then noting (no need). This is just weird..when you can try another game..because I am assuming that is the problem..time crisis works but no others?
This has turned into a "I have to fix this because I cain't figure it" out and not because I have to kinda thing.
I understand all to well...everybody else can do it so I know it can be done thing...all it does it make you hunker down harder..I wonder how much sleep I have lost over these things ::)
-
Time crisis works on mame 32 and mame ui on my xp machine. On my windows 7 it only works on mame 32. I tried hellfire from the command line and got the blackscreen. When I open mame ui from the shortcut I get the user account control window popping up asking if I want to allow the following program from an unknown publisher to make changes to this computer yes or no. Could that be an issue.
-
OK windows 7 users help me out here..
do you have that prblem as well...it asking for permission?
Is the windows version and installer or a portable version?
if it wants to install something then that may be the reason..I forget you can "install" mame..I have always used the portable version..
ok it is a portable version..the binary is mameui64.exe..as far I understand it shouldn't want permissions..that's very strange
-
It's just mameui.exe if that matters
-
hmmm...I'm going to assume here that you are running the 32-bit version of mameui then...(again it shouldn't matter..but still)
again try the 64-bit version mameui64.exe if you don't have that then you go here http://www.progettosnaps.net/mameui/ (http://www.progettosnaps.net/mameui/) to get it
and remember you neet to get the mame 154 version...because you are using 154 roms
(it's the "0.154 Jul 23, 2014 64" column)
-
You can try to rename your mame.ini to mame.ini.org as a backup (so you can name back later if this doesn't work). Next, run your mameui.exe and setup your rom path and anything else fresh on the Windows 7 build.
If you still have issues, the command line output from "mameui pacman" would help a lot.
-
Ok, I will try all of this. It might be latter into the week though. Thanks everyone. I will post the results.