Author Topic: relative path in a *.cfg - File ? (Read 7152 times)

Vicman · « **on:** 2010.July.29. 19:16:16 »

Hi all,

i need your help.

For my GameBase Enterprise Project, i've made this *.cfg to run *.bas files that needs the zrom :

Code: [Select]

memory.configFile	""
memory.ram.size	128
memory.rom.00.file	"E:\\GameBase\\Enterprise\\Emulator\\ep128emu\\roms\\exos21.rom"
memory.rom.00.offset	0
memory.rom.01.file	"E:\\GameBase\\Enterprise\\Emulator\\ep128emu\\roms\\exos21.rom"
memory.rom.01.offset	16384
memory.rom.02.file	""
memory.rom.02.offset	0
memory.rom.03.file	""
memory.rom.03.offset	0
memory.rom.04.file	"E:\\GameBase\\Enterprise\\Emulator\\ep128emu\\roms\\asmon15.rom"
memory.rom.04.offset	0
memory.rom.05.file	"E:\\GameBase\\Enterprise\\Emulator\\ep128emu\\roms\\asmon15.rom"
memory.rom.05.offset	16384
memory.rom.06.file	"E:\\GameBase\\Enterprise\\Emulator\\ep128emu\\roms\\basic21.rom"
memory.rom.06.offset	0
memory.rom.07.file	"E:\\GameBase\\Enterprise\\Emulator\\ep128emu\\roms\\epdos_z.rom"
memory.rom.07.offset	0
memory.rom.10.file	"E:\\GameBase\\Enterprise\\Emulator\\ep128emu\\roms\\epfileio.rom"

but the end-user of my GameBase will probably not use the same folder for the GameBase....(in my case , it's on drive E:)

my question is :
is it possible to use "relative paths" in the *cfg-file ?

otherwise my "selfmade-cfg's" won't work for other peoples

i thought something like :

Code: [Select]

memory.rom.00.file ".\GameBase\\Enterprise\\Emulator\\ep128emu\\roms\\exos21.rom"

is there a way to make it work ?

IstvanV · « **Reply #1 on:** 2010.July.29. 20:38:35 »

Unfortunately, in the current version it is not possible to use paths that are relative to the emulator's installation directory in the configuration files. They can only be relative to the current directory, which, on Windows, might be where the ep128emu.exe is found at startup, but I am not sure if this is always the case.
If the configuration files are generated automatically with a program, then it is possible to find out where the emulator is installed from the HKEY_CURRENT_USER\Software\ep128emu2\InstallDirectory registry key.

Vicman · « **Reply #2 on:** 2010.July.29. 21:22:00 »

Quote from: IstvanV on 2010.July.29. 20:38:35

They can only be relative to the current directory, which, on Windows, might be where the ep128emu.exe is found at startup...

o.k.,
i've copied the roms directly where the ep128emu.exe is...
and tried this :

Code: [Select]

memory.rom.04.file ".\asmon15.rom"and this :

Code: [Select]

memory.rom.04.file "asmon15.rom"
both don't work....(error opening config.-file)

is there something wrong in the "commandline"

(maybe .\\asmon15.rom")

Vicman · « **Reply #3 on:** 2010.July.29. 21:48:34 »

Quote from: IstvanV on 2010.July.29. 20:38:35

If the configuration files are generated automatically with a program, then it is possible to find out where the emulator is installed from the HKEY_CURRENT_USER\Software\ep128emu2\InstallDirectory registry key.

for this case, i will ask a Guy from the GameBase-Forum.
maybe he can make this work with the GEMUS-Script
(by using Set_CFG_Value() and/or Set_CFG_Item() )

btw. :
see the "relative path - thing" as a feature request for the ep128emu

Author Topic: relative path in a *.cfg - File ? (Read 7152 times)

Vicman

relative path in a *.cfg - File ?

IstvanV

Re: relative path in a *.cfg - File ?

Vicman

Re: relative path in a *.cfg - File ?

Vicman

Re: relative path in a *.cfg - File ?