Need Help w/ Zinc in Mala with HCasto Wrapper

[andowhy]

Hi All, I know im rehashing an old toic, but it seems relevant to the problem I am having - I have followed the step by step instructions in installing Zinc via MaLa - I have installed all the relevant files, roms, etc and I can run Zinc via the dos command with no problems (eg \zinc 2 etc)

however as soon as I try to use the wrapper nothing works - once i enter the command (eg. \zinc sfex ) the screen goes black (as if loading) then comes back to the dos screen - also does the same in MaLa - screen goes black then returns to the MaLa gamelist screen.  I have made sure the cmd-launcher and lsconfig files are in teh zinc root dir and that MaLa is correct set up to point to these files but still no luck.  just wondering if I can get any help.

[SGT]

I assume you meant "cmd-launch7.exe sfex" instead of "zinc sfex".

Here are the settings that work for me in Mala.

Executable:
C:\emulators\zinc\cmd-launch7.exe

Rom Path:
C:\emulators\zinc\roms

Rom extensions:
zip

Command Line:

%rom%

Below is the contents of the wrapper's lconfig.ini file :

Code: [Select]

#this is a config file for the launcher wrapper program
#turn on wordwrap for best viewing results


# Leave at 0 to hide the command line while the emulator is launching.

LAUNCHSTYLE=0

#each command in an emu is usually followed by a delimeter (in mame it's a "-" for example)  put this deliemter in the following line

delimeter=--


#put the mame command or romname followed by a ";" and the command that does the same thing in the emu your launching (like in zinc to launch a game you type it's number so sfex;1 would launch sfex for you)

{cmdlist}
starglad;1
sfex;2
sfexj;3
sfexa;4
sfexp;5
sfexpu1;6
sfexpj;7
sfex2;8
sfex2j;9
sfex2p;10
sfex2pj;11
sfex2pa;12
plsmaswd;13
stargld2;14
rvschola;15
jgakuen;16
rvschool;17
shiryu2;18
strider2;19
kikaioh;20
techromn;21
ts2;22
ts2j;23
tgmj;24
sncwgltd;25
beastrzb;26
beastrzr;27
bldyror2;28
brvblade;29
psyforcj;30
psyforce;31
psyfrcex;32
mgcldtex;33
raystorj;34
raystorm;35
ftimpcta;36
gdarius;37
gdarius2;38
danceyes;39
xevi3dg;40
starswep;41
myangel3;42
tekkenb;43
tekkena;44
tekken;45
tekken2a;46
tekken2b;47
tekken2;48
souledga;49
souledgb;50
souledge;51
dunkmnia;52
dunkmnic;53
primglex;54
weddingr;55
hyperath;56
pbball96;57
susume;58
fgtlayer;59
ehrgeiz;60
tekken3;61
mrdrillr;62
aquarush;63
pacapp;64
glpracr3;65
shngmtkb;66
cbaj;67
doapp;68
tondemo;69
mfjump;70
hvnsgate;71
{/cmdlist}
#put the name of the emulator you wish to launch immediately following this comment

exe=zinc.exe

#Some emus don't like spaces in the filenames or paths
#turn this on to send a short filename to the emu

Short=0

# this will wrap your filepaths in quotes, an alternative to short

Quotes=0

#Set this to how often you want the wrapper to check for the exit key...
#It's in milliseconds.... 1000 = about 1 second

refreshspeed=1


#Choose which way to exit the emulator.
#0=Let emu close itself.
#1=Try all methods
#2=Try Alt-F4 method
#3=Try Posting a Close Message
#4=Try Posting a Exit Message
#5=Terminate Process (sloppy, but always works)
#Use only 0 or 1 unless you run into problems.

ExitType=5


#Current Problem Emus and the Settings your should use:

#Zinc=5
#Nebula=5
#Nebula Model 2=5

# If you discover another problem emu please contact me and I'll add it to the list.


[andowhy]

Thanks SGT,  the problem was with my config file.  Once I compared it to yours i realised my file had a heap of controller config settings against each game which were pointing to a e:\path that doesnt follw any of my path settings, once i removed these it ran in mala like a dream.

thanks for your help.

[Howard_Casto]

Thanks SGT,  the problem was with my config file.  Once I compared it to yours i realised my file had a heap of controller config settings against each game which were pointing to a e:\path that doesnt follw any of my path settings, once i removed these it ran in mala like a dream.

thanks for your help.

I'm guessing it pointed to these because you installed my zincconfig.exe and didn't actually rebuild the  cfg files.