Welcome to the Gamebase 64 forums.                 An attempt to document ALL Commodore 64 gameware before it's too late!

gamebase amiga hdf script

Discuss GameBase, the Universal Emulator Frontend!

Moderator: Jimbo

User avatar
.mad.
Honoured Member
Honoured Member
Location: Lancashire
Posts: 2256
Joined: Sun Jun 19, 2005 3:30 pm

Re: gamebase amiga hdf script

Thu Feb 24, 2022 10:18 am

without seeing the HDF you are using it's hard to tell.
but mix and matching old scripts is a minefield and not going to work.

but i can guess you are linking a ZIP as the runnable file, not the HDF inside it.
that's why WinUAE is attaching at DF0: floppy instead of DH0: harddrive or both?.

for a test, link the .HDF as the game file (unzipped).

if GameType CONTAINS(HDF)
; notice all HD config names are same "HDF.UAE" not a mixture of "Gamebase Amiga.UAE"
; To run HDF Files, you must link HDF as the runnable file inside ZIP.
;**************************************************************************************************


;---------------------
;Floppy Disk (No disk)
;---------------------
Set_CFG_Value(%dbpath%\Scripts\HDF.uae||nr_floppies||1)
Set_CFG_Value(%dbpath%\Scripts\HDF.uae||floppy0type||0)
Set_CFG_Value(%dbpath%\Scripts\HDF.uae||floppy0||)

;-----------------------------------------------
;Put Game/Demo HDF File in Hard Drive 0.
;
; check drive number [uaehf1] or [uaehf0]
; check last number [-128] or [0]
;-----------------------------------------------
Set_CFG_Item(%dbpath%\Scripts\HDF.uae||hardfile2=rw,DH0||:||%gamepathfile%,32,1,2,512,0,,uae)
Set_CFG_Value(%dbpath%\Scripts\HDF.uae||uaehf0||hdf,rw,DH0:%gamepathfile%,32,1,2,512,0,,uae)

; Kickstart needs to be from HD Machine A600, A1200, A1500, A4000
Set_CFG_Value(%dbpath%\Scripts\HDF.uae||kickstart_rom||v3.1)
Add_CLP(-f "%dbpath%\Scripts\HDF.uae")
Run_Emulator()
End If
Fiery Phoenix
Keen Member
Keen Member
Location: Bury, Lancs
Posts: 73
Joined: Tue Aug 07, 2012 8:07 am

Re: gamebase amiga hdf script

Thu Feb 24, 2022 11:00 am

Morning

No - defo running the hdf. inside the zip (tried just attaching the .hdf also)

Nothing attached to the floppy drives at all - appears to be spot on, but will not auto boot.

For example trying the game Abduction - linked game file to zip and selected the runnable file as the .hdf inside it

I run the game in Gamebase, just get the purple WB 3.1 logo screen. I press F12, DF0 and DF1 are ticked - but nothing in them. CD & Hard Drives tab shows c:\gb game\abduction.hdf

If I enter the configuration tab - select HDF and load, then go back into the CD & Hard Drives tab, re-attach the .hdf. Game boots normally

When I try it un-zipped, exactly the same, purple WB screen, but only difference is the path in the CD & HardDrives tab - shows C:\gamebase\gamebase amiga\a\abduction.hdf

My GEMUS in the Gamebase for this game is:

chipmem_size=16
cpu_model=68040
chipset=AGA
cpu_type=68040
cpu_model=68040
fpu_model=68040
cpu_24bit_addressing=true
cpu_compatible=true
cpu_cycle_exact=false
blitter_cycle_exact=true
rtc=MSM6242B
fatgary=-1
ramsey=-1
maprom=0xf000000
hdf=no workbench

If I remove the no workbench part - it loads to the Workbench screen with a system disk icon, clicking this shows Abduction drawer - empty. Selected all files and 3 drawers load up (Disk 1, 2 and Game) but game.exe will not boot.

But Abduction.hdf should just autoboot - as it does when I load up the HDF configuration

So it looks like it is attaching fine but not auto-booting?

My HDF in the scripts is below (would not let me attach it, but opened as a notepad)

Code: Select all

config_description=UAE default configuration
config_hardware=true
config_host=true
config_version=4.4.0
config_hardware_path=
config_host_path=
config_all_path=
comp_catchdetect=true
win32.rom_path=./
win32.floppy_path=./
win32.hardfile_path=./
; host-specific
win32.middle_mouse=true
win32.map_cd_drives=true
win32.rtg_match_depth=false
win32.soundcard=8
win32.soundcardname=Primary Sound Driver
win32.cpu_idle=150
win32.expansion_gui_page=ide_mb
; common
use_gui=no
use_debugger=false
kickstart_rom_file=C:\GameBase\GameBase Amiga 2.1\WinUAE\roms\KS ROM v3.1 (A500,A600,A2000) rev 40.63 (512k).rom
kickstart_rom_file_id=FC24AE0D,KS ROM v3.1 (A500,A600,A2000)
kickstart_ext_rom_file=
kickstart_rom=v3.1
picassoiv_rom_file=C:\GameBase\GameBase Amiga 2.1\WinUAE\roms\Picasso IV (128k).rom
picassoiv_rom_file_id=A8133E7E,Picasso IV
ide_mb_rom_file=:ENABLED
pcmcia_mb_rom_file=:ENABLED
flash_file=
cart_file=
rtc_file=
picassoiv_rom_file=C:\GameBase\GameBase Amiga\Emulators\WinUAE\Roms\Picasso_iv_flash.rom
kickshifter=false
floppy_volume=33
floppy0=
floppy1=
floppy1type=-1
floppy2=
floppy3=
nr_floppies=1
floppy_speed=0
cd_speed=100
parallel_on_demand=false
serial_on_demand=false
serial_hardware_ctsrts=true
serial_direct=false
scsi=true
uaeserial=false
sana2=false
sound_output=exact
sound_channels=stereo
sound_stereo_separation=7
sound_stereo_mixing_delay=0
sound_max_buff=16384
sound_frequency=44100
sound_interpol=anti
sound_filter=emulated
sound_filter_type=standard
sound_volume=0
sound_volume_paula=0
sound_volume_cd=0
sound_volume_ahi=0
sound_volume_midi=0
sound_volume_genlock=0
sound_auto=true
sound_cdaudio=false
sound_stereo_swap_paula=false
sound_stereo_swap_ahi=false
comp_trustbyte=direct
comp_trustword=direct
comp_trustlong=direct
comp_trustnaddr=direct
comp_nf=true
comp_constjump=true
comp_flushmode=soft
compfpu=true
comp_catchdetect=true
cachesize=16384
joyport0=mouse
joyport0autofire=none
joyport0mode=mousenowheel
joyportfriendlyname0=Windows mouse
joyportname0=WINMOUSE1
joyport1=joy0
joyport1autofire=none
joyport1mode=djoy
joyportfriendlyname1=
joyportname1=
bsdsocket_emu=false
synchronize_clock=false
maprom=0xf000000
parallel_postscript_emulation=false
parallel_postscript_detection=false
ghostscript_parameters=
parallel_autoflush=5
gfx_display=0
gfx_display_rtg=0
gfx_framerate=10
gfx_width=800
gfx_height=600
gfx_top_windowed=117
gfx_left_windowed=138
gfx_width_windowed=800
gfx_height_windowed=600
gfx_width_fullscreen=800
gfx_height_fullscreen=600
gfx_refreshrate=0
gfx_autoresolution=0
gfx_autoresolution_vga=true
gfx_backbuffers=2
gfx_backbuffers_rtg=1
gfx_vsync=false
gfx_vsyncmode=normal
gfx_vsync_picasso=false
gfx_vsyncmode_picasso=normal
gfx_lores=false
gfx_resolution=hires
gfx_lores_mode=normal
gfx_flickerfixer=false
gfx_linemode=double2
gfx_fullscreen_amiga=false
gfx_fullscreen_picasso=false
gfx_center_horizontal=none
gfx_center_vertical=none
gfx_colour_mode=32bit
gfx_blacker_than_black=false
gfx_api=direct3d
gfx_api_options=hardware
immediate_blits=true
ntsc=false
genlock=false
chipset=aga
chipset_refreshrate=49.920410
collision_level=playfields
chipset_compatible=A1200
rtc=MSM6242B
ksmirror_a8=true
pcmcia=true
ide=a600/a1200
fastmem_size=2
debugmem_start=0x0
debugmem_size=0
mem25bit_size=0
a3000mem_size=8
mbresmem_size=0
z3mem_size=32
z3mem_start=0x40000000
bogomem_size=0
gfxcard_hardware_vblank=false
gfxcard_hardware_sprite=false
gfxcard_multithread=false
gfxcard_size=4
gfxcard_type=ZorroIII
chipmem_size=4
cpu_speed=real
cpu_throttle=0.0
cpu_type=68040
cpu_model=68040
cpu_compatible=false
cpu_24bit_addressing=false
cpu_data_cache=false
cpu_cycle_exact=false
cpu_memory_cycle_exact=false
blitter_cycle_exact=false
cycle_exact=false
fpu_strict=false
rtg_nocustom=false
rtg_modes=0x212
debug_mem=false
log_illegal_mem=false
kbd_lang=us
warp=true
input.config=0
input.joymouse_speed_analog=100
input.joymouse_speed_digital=10
input.joymouse_deadzone=33
input.joystick_deadzone=33
input.analog_joystick_multiplier=15
input.analog_joystick_offset=-1
input.mouse_speed=100
input.autofire_speed=600
input.autoswitch=1
input.1.joystick.0.friendlyname=Atari/C64 Joystick [1]
input.1.joystick.0.name=\\?\HID#VID_16C0&PID_27DC&MI_00#8&7c56d60&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.1.joystick.0.empty=true
input.1.joystick.1.friendlyname=Atari/C64 Joystick [2]
input.1.joystick.1.name=\\?\HID#VID_16C0&PID_27DC&MI_01#8&1f88f9a5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.1.joystick.1.empty=true
input.1.joystick.2.empty=true
input.1.joystick.3.empty=true
input.1.joystick.4.empty=true
input.1.joystick.5.empty=true
input.1.joystick.6.empty=true
input.1.joystick.7.empty=true
input.1.joystick.8.empty=true
input.1.joystick.9.empty=true
input.1.joystick.10.empty=true
input.1.joystick.11.empty=true
input.1.joystick.12.empty=true
input.1.joystick.13.empty=true
input.1.joystick.14.empty=true
input.1.joystick.15.empty=true
input.1.joystick.16.empty=true
input.1.joystick.17.empty=true
input.1.joystick.18.empty=true
input.1.joystick.19.empty=true
input.1.mouse.0.friendlyname=Windows mouse
input.1.mouse.0.name=WINMOUSE1
input.1.mouse.0.empty=true
input.1.mouse.1.friendlyname=HID-compliant mouse
input.1.mouse.1.name=\\?\HID#VID_1D57&PID_AD03&MI_01&Col01#7&14f69dfe&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.1.mouse.1.empty=true
input.1.mouse.2.empty=true
input.1.mouse.3.empty=true
input.1.mouse.4.empty=true
input.1.mouse.5.empty=true
input.1.mouse.6.empty=true
input.1.mouse.7.empty=true
input.1.mouse.8.empty=true
input.1.mouse.9.empty=true
input.1.mouse.10.empty=true
input.1.mouse.11.empty=true
input.1.mouse.12.empty=true
input.1.mouse.13.empty=true
input.1.mouse.14.empty=true
input.1.mouse.15.empty=true
input.1.mouse.16.empty=true
input.1.mouse.17.empty=true
input.1.mouse.18.empty=true
input.1.mouse.19.empty=true
input.1.keyboard.0.friendlyname=WinUAE keyboard
input.1.keyboard.0.name=NULLKEYBOARD
input.1.keyboard.0.empty=false
input.1.keyboard.0.disabled=false
input.1.keyboard.1.friendlyname=USB Keyboard
input.1.keyboard.1.name=\\?\HID#VID_0461&PID_0010&MI_00#7&a5ad4c3&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.1.keyboard.1.empty=true
input.1.keyboard.2.friendlyname=Gaming Mouse
input.1.keyboard.2.name=\\?\HID#VID_1D57&PID_AD03&MI_00#7&38cddbc0&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.1.keyboard.2.empty=true
input.1.keyboard.3.empty=true
input.1.keyboard.4.empty=true
input.1.keyboard.5.empty=true
input.1.keyboard.6.empty=true
input.1.keyboard.7.empty=true
input.1.keyboard.8.empty=true
input.1.keyboard.9.empty=true
input.1.keyboard.10.empty=true
input.1.keyboard.11.empty=true
input.1.keyboard.12.empty=true
input.1.keyboard.13.empty=true
input.1.keyboard.14.empty=true
input.1.keyboard.15.empty=true
input.1.keyboard.16.empty=true
input.1.keyboard.17.empty=true
input.1.keyboard.18.empty=true
input.1.keyboard.19.empty=true
input.1.internal.0.friendlyname=Internal events
input.1.internal.0.name=INTERNALEVENTS1
input.1.internal.0.empty=true
input.2.joystick.0.friendlyname=Atari/C64 Joystick [1]
input.2.joystick.0.name=\\?\HID#VID_16C0&PID_27DC&MI_00#8&7c56d60&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.2.joystick.0.empty=true
input.2.joystick.1.friendlyname=Atari/C64 Joystick [2]
input.2.joystick.1.name=\\?\HID#VID_16C0&PID_27DC&MI_01#8&1f88f9a5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.2.joystick.1.empty=true
input.2.joystick.2.empty=true
input.2.joystick.3.empty=true
input.2.joystick.4.empty=true
input.2.joystick.5.empty=true
input.2.joystick.6.empty=true
input.2.joystick.7.empty=true
input.2.joystick.8.empty=true
input.2.joystick.9.empty=true
input.2.joystick.10.empty=true
input.2.joystick.11.empty=true
input.2.joystick.12.empty=true
input.2.joystick.13.empty=true
input.2.joystick.14.empty=true
input.2.joystick.15.empty=true
input.2.joystick.16.empty=true
input.2.joystick.17.empty=true
input.2.joystick.18.empty=true
input.2.joystick.19.empty=true
input.2.mouse.0.friendlyname=Windows mouse
input.2.mouse.0.name=WINMOUSE1
input.2.mouse.0.empty=true
input.2.mouse.1.friendlyname=HID-compliant mouse
input.2.mouse.1.name=\\?\HID#VID_1D57&PID_AD03&MI_01&Col01#7&14f69dfe&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.2.mouse.1.empty=true
input.2.mouse.2.empty=true
input.2.mouse.3.empty=true
input.2.mouse.4.empty=true
input.2.mouse.5.empty=true
input.2.mouse.6.empty=true
input.2.mouse.7.empty=true
input.2.mouse.8.empty=true
input.2.mouse.9.empty=true
input.2.mouse.10.empty=true
input.2.mouse.11.empty=true
input.2.mouse.12.empty=true
input.2.mouse.13.empty=true
input.2.mouse.14.empty=true
input.2.mouse.15.empty=true
input.2.mouse.16.empty=true
input.2.mouse.17.empty=true
input.2.mouse.18.empty=true
input.2.mouse.19.empty=true
input.2.keyboard.0.friendlyname=WinUAE keyboard
input.2.keyboard.0.name=NULLKEYBOARD
input.2.keyboard.0.empty=false
input.2.keyboard.0.disabled=false
input.2.keyboard.1.friendlyname=USB Keyboard
input.2.keyboard.1.name=\\?\HID#VID_0461&PID_0010&MI_00#7&a5ad4c3&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.2.keyboard.1.empty=true
input.2.keyboard.2.friendlyname=Gaming Mouse
input.2.keyboard.2.name=\\?\HID#VID_1D57&PID_AD03&MI_00#7&38cddbc0&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.2.keyboard.2.empty=true
input.2.keyboard.3.empty=true
input.2.keyboard.4.empty=true
input.2.keyboard.5.empty=true
input.2.keyboard.6.empty=true
input.2.keyboard.7.empty=true
input.2.keyboard.8.empty=true
input.2.keyboard.9.empty=true
input.2.keyboard.10.empty=true
input.2.keyboard.11.empty=true
input.2.keyboard.12.empty=true
input.2.keyboard.13.empty=true
input.2.keyboard.14.empty=true
input.2.keyboard.15.empty=true
input.2.keyboard.16.empty=true
input.2.keyboard.17.empty=true
input.2.keyboard.18.empty=true
input.2.keyboard.19.empty=true
input.2.internal.0.friendlyname=Internal events
input.2.internal.0.name=INTERNALEVENTS1
input.2.internal.0.empty=true
input.3.joystick.0.friendlyname=Atari/C64 Joystick [1]
input.3.joystick.0.name=\\?\HID#VID_16C0&PID_27DC&MI_00#8&7c56d60&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.3.joystick.0.empty=true
input.3.joystick.1.friendlyname=Atari/C64 Joystick [2]
input.3.joystick.1.name=\\?\HID#VID_16C0&PID_27DC&MI_01#8&1f88f9a5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.3.joystick.1.empty=true
input.3.joystick.2.empty=true
input.3.joystick.3.empty=true
input.3.joystick.4.empty=true
input.3.joystick.5.empty=true
input.3.joystick.6.empty=true
input.3.joystick.7.empty=true
input.3.joystick.8.empty=true
input.3.joystick.9.empty=true
input.3.joystick.10.empty=true
input.3.joystick.11.empty=true
input.3.joystick.12.empty=true
input.3.joystick.13.empty=true
input.3.joystick.14.empty=true
input.3.joystick.15.empty=true
input.3.joystick.16.empty=true
input.3.joystick.17.empty=true
input.3.joystick.18.empty=true
input.3.joystick.19.empty=true
input.3.mouse.0.friendlyname=Windows mouse
input.3.mouse.0.name=WINMOUSE1
input.3.mouse.0.empty=true
input.3.mouse.1.friendlyname=HID-compliant mouse
input.3.mouse.1.name=\\?\HID#VID_1D57&PID_AD03&MI_01&Col01#7&14f69dfe&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.3.mouse.1.empty=true
input.3.mouse.2.empty=true
input.3.mouse.3.empty=true
input.3.mouse.4.empty=true
input.3.mouse.5.empty=true
input.3.mouse.6.empty=true
input.3.mouse.7.empty=true
input.3.mouse.8.empty=true
input.3.mouse.9.empty=true
input.3.mouse.10.empty=true
input.3.mouse.11.empty=true
input.3.mouse.12.empty=true
input.3.mouse.13.empty=true
input.3.mouse.14.empty=true
input.3.mouse.15.empty=true
input.3.mouse.16.empty=true
input.3.mouse.17.empty=true
input.3.mouse.18.empty=true
input.3.mouse.19.empty=true
input.3.keyboard.0.friendlyname=WinUAE keyboard
input.3.keyboard.0.name=NULLKEYBOARD
input.3.keyboard.0.empty=false
input.3.keyboard.0.disabled=false
input.3.keyboard.1.friendlyname=USB Keyboard
input.3.keyboard.1.name=\\?\HID#VID_0461&PID_0010&MI_00#7&a5ad4c3&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.3.keyboard.1.empty=true
input.3.keyboard.2.friendlyname=Gaming Mouse
input.3.keyboard.2.name=\\?\HID#VID_1D57&PID_AD03&MI_00#7&38cddbc0&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.3.keyboard.2.empty=true
input.3.keyboard.3.empty=true
input.3.keyboard.4.empty=true
input.3.keyboard.5.empty=true
input.3.keyboard.6.empty=true
input.3.keyboard.7.empty=true
input.3.keyboard.8.empty=true
input.3.keyboard.9.empty=true
input.3.keyboard.10.empty=true
input.3.keyboard.11.empty=true
input.3.keyboard.12.empty=true
input.3.keyboard.13.empty=true
input.3.keyboard.14.empty=true
input.3.keyboard.15.empty=true
input.3.keyboard.16.empty=true
input.3.keyboard.17.empty=true
input.3.keyboard.18.empty=true
input.3.keyboard.19.empty=true
input.3.internal.0.friendlyname=Internal events
input.3.internal.0.name=INTERNALEVENTS1
input.3.internal.0.empty=true
input.4.keyboard.0.friendlyname=WinUAE keyboard
input.4.keyboard.0.name=NULLKEYBOARD
input.4.keyboard.0.custom=true
floppy0type=0
hardfile2=rw,DH0:c:\gbgame\0\abduction.hdf,32,1,2,512,-128,,uae
uaehf1=hdf,rw,DH0:c:\gbgame\0\abduction.hdf,32,1,2,512,-128,,uae
gfx_filter=null
User avatar
.mad.
Honoured Member
Honoured Member
Location: Lancashire
Posts: 2256
Joined: Sun Jun 19, 2005 3:30 pm

Re: gamebase amiga hdf script

Thu Feb 24, 2022 12:48 pm

your attached config shows UAEHF1 and -128...
you need UAEF0 and 0 for bootable.

hardfile2=rw,DH0:c:\gbgame\0\abduction.hdf,32,1,2,512,[-128]<---,,uae
uaehf[1]<---=hdf,rw,DH0:c:\gbgame\0\abduction.hdf,32,1,2,512,[-128]<---,,uae

if using the script example above, you should see this...

hardfile2=rw,DH0:c:\gbgame\0\abduction.hdf,32,1,2,512,0<---,,uae
uaehf[0]<---=hdf,rw,DH0:c:\gbgame\0\abduction.hdf,32,1,2,512,[0]<---,,uae

when the game is working, re-save the config HDF2.UAE and compare them. :wink:
Fiery Phoenix
Keen Member
Keen Member
Location: Bury, Lancs
Posts: 73
Joined: Tue Aug 07, 2012 8:07 am

Re: gamebase amiga hdf script

Thu Feb 24, 2022 2:23 pm

Cheers fella - appreciate it (pain in da ass I know)

I tried just opening the config. as a notepad again, copied:

hardfile2=rw,DH0:c:\gbgame\0\abduction.hdf,32,1,2,512,0<---,,uae
uaehf[0]<---=hdf,rw,DH0:c:\gbgame\0\abduction.hdf,32,1,2,512,[0]<---,,uae

over the lines held on - re-saved it as HDF.uae, but does not work? I saved it as configuration HDF.uae - double click this and autoboots with Adbuction - as saved it with it attached - but if load up via Gamebase - same problem as before. WB purple screen

But if re-load the HDF configuration, re-start, auto -boots in WinUAE, just will not trigger in Gamebase. Is there nothing in the game GEMUS to enter to make it autoboot - or all from the Script? Like mode=cd32 for those games?

When I open the re-saved HDF.uae with notepad it has 1 line near the top:

uaehf[0]<---=hdf,rw,DH0:c:\gbgame\0\abduction.hdf,32,1,2,512,[0]<---,,uae

And these 2 in the middle:

hardfile2=rw,DH0:..\..\..\GBGame\0\Abduction.hdf,32,1,2,512,0,,uae0
uaehf0=hdf,rw,DH0:..\\..\\..\\GBGame\\0\\Abduction.hdf,32,1,2,512,0,,uae0

To be honest, absolutely rock solid, think a bit over my head I struggle with DosBox lol. Is it perhaps better just doing a re-install of new Gamebase 2.3 - do they include all required scripts? Or just the basic ones?

If this gets working going forward - do you then have to load a different GEMUS script each time you want to play WHDLoad or normal Amiga games - any Script that includes all of them together?

Edit - actually may be worth a re-install as the Belgarath script wont boot up WinUAE now - just goes to configuartion screen as soon as starts
User avatar
.mad.
Honoured Member
Honoured Member
Location: Lancashire
Posts: 2256
Joined: Sun Jun 19, 2005 3:30 pm

Re: gamebase amiga hdf script

Thu Feb 24, 2022 3:06 pm

the basic scripts will work for everything.
running old scripts and emulators will mess up the kickstarts and paths.
you will need to rescan and verify roms with each new version.
*download and install V4.9.1
forget other versions for now.

problem is when adding multiple Harddrives.
WinUAE creates duplicate name entries in the config (not checked this with very latest version).
so every possible option needs to be manually added to the config file first, with an empty or correct value (true/false).
Only then will Gamebase have a chance of editing the UAE correctly.

Gamebase scripting will only see and edit the first name value in the config file.
This can be made to work by using 3 separate UAE files, for each Amiga machine mode.
editing only the game image values in Amiga.UAE (no HD options), HDF.UAE (all HD's configured) or CD32.UAE (no floppy or HD options).


i have attached a script set which works for me with autobooting HDF's.
it uses same GEMUS and romset as Belgarath's gamebase v2.1x updated version by dax.
it will not work with other older versions.

workbench=yes
will boot workbench HDF and attach game on 2nd Hard drive.
this won't run some autobooting HDF from this drive.

but you can see correct code to run HDF.
it's the same as i posted above.
Attachments
scripts.zip
(23.87 KiB) Downloaded 830 times
Fiery Phoenix
Keen Member
Keen Member
Location: Bury, Lancs
Posts: 73
Joined: Tue Aug 07, 2012 8:07 am

Re: gamebase amiga hdf script

Thu Feb 24, 2022 9:29 pm

Gonna have another go!

Wish me luck!

Downloaded attachment (ta!)

Ok man - quick check - Gamebase Amiga Script attachment (2018)

When loaded get a the Expected ")" Line 1345 error

Cannot type any more than this and can see the Script has 1433 lines

I am using Gamebase 1.3 - newer ones have more line perhaps?

In the emulator properties where you load the Gemus Script - does the Script Files need anything loaded. Always confused me this - can leave blank and as long as GEMUS script loaded, games load up
User avatar
.mad.
Honoured Member
Honoured Member
Location: Lancashire
Posts: 2256
Joined: Sun Jun 19, 2005 3:30 pm

Re: gamebase amiga hdf script

Fri Feb 25, 2022 11:15 am

As you are editing and messing with the script, and trying old and new versions of the emulator.
i ??think?? you might be linking an old (edited) script from the emulators.ini.?
or you might have several options in the GEMUS.ini.

emulators.ini
[Emulators]
1=WinUAE
[WinUAE]
UseShortFilenames=0
SupportedTypes=ADF;IPF;HDF;ISO;CUE;ZIP
EmulatorPathFile=C:\GameBase\Amiga\Emulators\WinUAE4910\winuae.exe
ScriptFile=Amiga.txt


i can assure you, it works for me without any error.

move all other versions of the emulator and scripts to another directory.
and start with a clean emulator setup. :idea:
Fiery Phoenix
Keen Member
Keen Member
Location: Bury, Lancs
Posts: 73
Joined: Tue Aug 07, 2012 8:07 am

Re: gamebase amiga hdf script

Fri Feb 25, 2022 12:08 pm

Ok - thankyou - as suggested - moved everything to another folder

1. Could not run Emulator setup wizard in Gamebase - states GEMUS script could not be found in the \Scripts folder

C:\Gamebase\gemus.dat (Line 13)

2. Went into Gemus / Manage Emulators instead (currently blank) pressed top left square to go into Emulator Properties. Browsed to Winuae and named emulator

3. Un-ticked defaults and entered:

ADF;IPF;HDF;ISO;CUE;ZIP

4. Selected load GEMUS script and loaded Amiga.txt (Belgarath v2.1 / 2018)

5. Pressed ok - get GEMUS error - Expected ")" Line 1345

Nothing below this line and half cuts line out so it reads:

Set_CFG_Value(%dbpath%\Scripts\WHDLoad.uae||immediate_b

Cannot type anything else below this
User avatar
.mad.
Honoured Member
Honoured Member
Location: Lancashire
Posts: 2256
Joined: Sun Jun 19, 2005 3:30 pm

Re: gamebase amiga hdf script

Fri Feb 25, 2022 1:39 pm

you are over thinking it.
the GEMUS.dat will not have the CRC32 for latest emulators for the wizard to work.

And i see that the script exceeds the VB6 view/ editor box limits (65,525) in the tools. :D
*this value can't be increased.

i have NEVER used that option!, and it is not needed in this case anyway.

all they do is help create an "emulators.ini" file manually.

just use the example one i posted above.
and don't worry about it. ;)

same script with comments removed...
Attachments
Amiga(64589).zip
(6.61 KiB) Downloaded 813 times
Fiery Phoenix
Keen Member
Keen Member
Location: Bury, Lancs
Posts: 73
Joined: Tue Aug 07, 2012 8:07 am

Re: gamebase amiga hdf script

Fri Feb 25, 2022 5:06 pm

Cheers man - getting close, can smell it (I hope it is that smell!)

Ok mind blown a bit as never knew that you did not need to manually load a script into Gemus - I always did and manually setup the emulator in it! Doh

As long as the Emulators.ini points to paths (for emulator and script file) all good

Update

Yeah defo close after following your advice. CDTV Xenon 2 and HDF Abduction load up fine :D

Get an error on WHDLoad as delwhd.bat could not be found, but game still runs when I select yes (maybe a quick fix, never had this on old WHDLoad checked my Script and no delwhd.bat on there - maybe able to delete this line on Amiga.txt)

Only problem is playing a normal .adf game - get "The script for this game has no functions to process!" Not sure why???

A few could not find system ROM / using system replacement on HDF & CD32 games - but continues to load after press ok

Note - will give this a go again on Sunday / Night - prob messed up as you said somewhere / deleted something

ROMS go in the Scripts folder dont they - not in WinUAE Roms folder?
Still have configuration of all different types in WinUAE configuration paths?
User avatar
.mad.
Honoured Member
Honoured Member
Location: Lancashire
Posts: 2256
Joined: Sun Jun 19, 2005 3:30 pm

Re: gamebase amiga hdf script

Fri Feb 25, 2022 7:46 pm

Kickstart checksums and machine settings have changed over the years in WinUAE.
could be something hard to spot with a quick glance.

kickstart checksums and paths will be saved in the WINUAE.INI file.
*attached file (put in same folder as WINUAE.EXE)

the WHD batch file, just deletes previous loaded WHDLoad folder.
the folder will just keep getting fuller, left unattended.

this is the batch file...

Code: Select all

rmdir /s /q c:\GBGame\rezip\
kickstarts stored in scripts folder (must use these names)...
CD32.rom
CD32EX.rom
CDTV.rom
CDTVEX10.rom
CDTVEX23.rom
CDTVEX27.rom
Kick12.rom
Kick13.rom
Kick30.rom
Kick31.rom
Kick204.rom
Kick205.rom
Attachments
winuaeini.zip
(1.46 KiB) Downloaded 824 times
User avatar
.mad.
Honoured Member
Honoured Member
Location: Lancashire
Posts: 2256
Joined: Sun Jun 19, 2005 3:30 pm

Re: gamebase amiga hdf script

Sat Feb 26, 2022 9:40 am

Fiery Phoenix wrote:
Fri Feb 25, 2022 5:06 pm
Only problem is playing a normal .adf game - get "The script for this game has no functions to process!" Not sure why???
That's because ZIP is a supported filetype.
WHDLoad are linked to GameBase using "name.zip" (they have no runnable file).
WHDRUN then takes control of the ZIP unpacking away from GameBase and WinUAE.
without that, WinUAE would try to unpack and run the WHDLoad ZIP as a floppy.

Same as HDF, if the ADF is set as the runnable file inside ZIP, it will work.
Also if you want to add a lot more ADF's to the GB. Removing ZIP from the emulators.ini, will speed up the file selection and insert the runnable ADF file automatically.

example:
Filename - A\'Allo 'Allo! Cartoon Fun!.zip
FileToRun - 'Allo 'Allo! Cartoon Fun!_Disk1.adf

when you want to add WHDLoads. adding ZIP to the emulators.ini is needed, so you can link only the ZIP as the game file.
Fiery Phoenix
Keen Member
Keen Member
Location: Bury, Lancs
Posts: 73
Joined: Tue Aug 07, 2012 8:07 am

Re: gamebase amiga hdf script

Mon Feb 28, 2022 12:25 am

Cheers man - hope you had a good weekend

Ok back to try

Yes I have all the named .roms in my Gamebase Script folder

In the Scripts.zip you attached, do I keep HDF, CD32, CDTV and Amiga in the Scripts folder?

I Put Winuae.ini in the WinUAE folder (shows correct Kickstart paths in Scripts and configuration path)

Edited emulators.ini to point to Script path

delwhd.bat - worked a treat and WHDLoad games start up now (thanks) :wink:

Managed to get Xenon 2 CDTV working (thanks again) :wink:

However normal games, CD32 and HDF still struggling with

CD32 - hanging on boot screen

HDF - Selected ROM requires a 68020 with 32 bit addressed or 68030 or higher CPU

Normal games - Deleted zip from emulators.ini but still getting "This script for this game has no function progress" (not in WHDLoad - normal selecting Play Game) Seems I have to-re-select the game file and then select a runnable file (Did not have to do this before)

However when I then select Play Game my WinUAE Properties screen loads up instead on the Configuration screen (Tried my old Script and game boots fine, but WHDLoad goes to WinUAE configuation this time - noticed this stops when WHDLoad.uae is put into my Gamebase Amiga folder)

So My Script folder holds:

CD32.rom
CD32EX.rom
CDTV.rom
CDTVEX10.rom
CDTVEX23.rom
CDTVEX27.rom
Kick12.rom
Kick13.rom
Kick30.rom
Kick31.rom
Kick204.rom
Kick205.rom

WHDLoad.uae
HDF.uae
Gamebase Amiga.uae
CDTV.uae
CD32.uae

WB31.hdf

delwhd.bat

Tried putting the attached .uae files in Script, Gamebase Amiga folder and WinUAE (configurations) no change to above errors
Fiery Phoenix
Keen Member
Keen Member
Location: Bury, Lancs
Posts: 73
Joined: Tue Aug 07, 2012 8:07 am

Re: gamebase amiga hdf script

Mon Feb 28, 2022 8:37 am

Morning - back (like a bad smell)

Got further - sort of started again with emulation / scripts

Moved a lot further

WHDLoad working

HDF working

CDTV working

ADF working (but still have to manually attatch the runnable file inside Gamebase first - won't auto do this as before)

CD32 is the only one with an issue hanging on boot screen. Although when I press F12 the file is attached in the CD drive and required Roms loaded?
User avatar
.mad.
Honoured Member
Honoured Member
Location: Lancashire
Posts: 2256
Joined: Sun Jun 19, 2005 3:30 pm

Re: gamebase amiga hdf script

Mon Feb 28, 2022 11:04 am

GEMUS
MODE=CD32
MODE=CDTV

there are several types of CD image (Amiga CD, CDTV, CD32), which most images use a .CUE file to boot.
gamebase has to be told what type it is.

both of these kickstart roms will be attached when working.
CD32EX.rom
CD32.rom

can you start the CD32 manually, after the point where gamebase stops?.
tweaking a few WinUAE options and resetting.

the ADF "problem" is by design.

The original gamebase release had every game in multiple zips (10 disk game = 10 zip files).
and let winUAE control the loading of ZIPPED ADF.

I repacked the GameBase disks for my personal copy, merging all disks into game sets, and linked disk 1 ADF as a runnable file for every game in my MDB (2 mins work).
* just because it looks cleaner and i prefer it that way.

why edit it in such a way, loosing compatibility?
the original GB doesn't have CD32, CDTV, HDF, and updated WHDLoad either.
It's 3 GameBases merged into 1.

This is no way a criticism on the excellent work of Belgarath.
The GameBase release works 100% perfectly with everything it contains.

Return to “The GameBase Frontend”

Who is online

Users browsing this forum: Google [Bot] and 41 guests