Savestates

[bladecgn]

I get a warning message when making savestates saying that they are not compatible with my setup.

Yet it works but one thing puzzles me: When I restore a snapshot, the system seems to be frozen. I have to disable JIT first and then the system resumes, I can even re-eanable JIT then.

When I am running a game with whdload, snapshots are resumed instantly without the before mentioned procedure.

Could it have sth. to do with the display (I am using DBLPAL for workbench)?

[Toni Wilen]

You have one or more unsupported expansion(s) enabled: uaescsi.device, network etc..

[bladecgn]

Hyvää päivää! ( I had a Finish girlfriend once) ... Good memories of that sauna near that lake in Finland where a bunch of drunk youngsters had great fun....

Originally Posted by Toni Wilen

You have one or more unsupported expansion(s) enabled: uaescsi.device, network etc..

I think I don't, here's my config file:

config_description=PFS: Kick+WB 3.9 (custom MagicWB)
config_hardware=true
config_host=true
config_version=2.6.1
config_hardware_path=
config_host_path=
win32.rom_path=./
win32.floppy_path=./
win32.hardfile_path=./
; host-specific
win32.soundcard=0
win32.soundcardname=Primärer Soundtreiber
win32.soundcardname.utf8=Primärer Soundtreiber
win32.cpu_idle=30
win32.powersavedisabled=false
; common
use_gui=yes
use_debugger=false
kickstart_rom_file=.\ROMs\Kick3.9_First512MB.rom
kickstart_ext_rom_file=.\ROMs\Kick3.9_Second512MB.rom
flash_file=
cart_file=
rtc_file=
kickshifter=false
ks_write_enabled=false
floppy0=
floppy1=
floppy2=
floppy2type=0
floppy3=
floppy3type=0
nr_floppies=4
floppy_speed=0
floppy_volume=33
parallel_on_demand=false
serial_on_demand=false
serial_hardware_ctsrts=true
serial_direct=false
scsi=false
uaeserial=false
sana2=false
sound_output=exact
sound_channels=stereo
sound_stereo_separation=7
sound_stereo_mixing_delay=0
sound_max_buff=4096
sound_frequency=48000
sound_interpol=rh
sound_filter=off
sound_filter_type=standard
sound_volume=0
sound_volume_cd=0
sound_auto=true
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_oldsegv=false
comp_flushmode=soft
compfpu=true
fpu_strict=false
comp_midopt=false
comp_lowopt=false
avoid_cmov=false
cachesize=8192
joyport0=mouse
joyport0autofire=none
joyport1=joy0
joyport1autofire=none
bsdsocket_emu=true
synchronize_clock=true
maprom=0x0
parallel_postscript_emulation=false
parallel_postscript_detection=false
ghostscript_parameters=
parallel_autoflush=5
gfx_display=0
gfx_display_rtg=0
gfx_framerate=1
gfx_width=720
gfx_height=568
gfx_top_windowed=675
gfx_left_windowed=68
gfx_width_windowed=720
gfx_height_windowed=568
gfx_width_fullscreen=1920
gfx_height_fullscreen=1200
gfx_refreshrate=0
gfx_autoresolution=false
gfx_backbuffers=2
gfx_backbuffers_rtg=1
gfx_vsync=true
gfx_vsyncmode=busywait
gfx_vsync_picasso=true
gfx_vsyncmode_picasso=busywait
gfx_lores=false
gfx_resolution=hires
gfx_lores_mode=filtered
gfx_flickerfixer=true
gfx_linemode=double
gfx_fullscreen_amiga=true
gfx_fullscreen_picasso=true
gfx_center_horizontal=smart
gfx_center_vertical=smart
gfx_colour_mode=32bit
gfx_blacker_than_black=false
gfx_api=direct3d
gfx_filter_mask=Scanlines75.png
gfx_filter_autoscale=integer
immediate_blits=true
ntsc=false
genlock=false
chipset=aga
chipset_refreshrate=50.000000
displaydata_pal=50.000000,locked,pal
displaydata_ntsc=50.000000,locked,ntsc
collision_level=playfields
chipset_compatible=Generic
fatgary=0
ramsey=15
fastmem_size=0
a3000mem_size=0
mbresmem_size=64
z3mem_size=0
z3mem_start=0x10000000
bogomem_size=0
gfxcard_size=8
gfxcard_type=ZorroIII
gfxcard_hardware_vblank=false
gfxcard_hardware_sprite=true
chipmem_size=16
cpu_speed=max
cpu_throttle=0.0
cpu_type=68020/68881
cpu_model=68030
fpu_model=68881
cpu_compatible=false
cpu_24bit_addressing=false
cpu_cycle_exact=false
blitter_cycle_exact=false
cycle_exact=false
rtg_nocustom=true
rtg_modes=0x212
log_illegal_mem=false
kbd_lang=us
hardfile2=rw,DH0:.\HardDisks\dh0_wb3.9_MagicWB.PFS.hdf,63,4,2,512,0,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
uaehf0=hdf,rw,DH0:.\HardDisks\dh0_wb3.9_MagicWB.PFS.hdf,63,4,2,512,0,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
hardfile2=rw,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
uaehf1=hdf,rw,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
hardfile2=rw,DH2:.\HardDisks\dh2_WHDLoad_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
uaehf2=hdf,rw,DH2:.\HardDisks\dh2_WHDLoad_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
filesystem2=rw,DH3:Scratch:.\HardDisks\Scratch,-128
uaehf3=dir,rw,DH3:Scratch:.\HardDisks\Scratch,-128
input.config=1
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.1.joystick.0.friendlyname=Joystick [1]
input.1.joystick.0.name=\\?\HID#VID_16C0&PID_27DC&Col01#6&313a9aad&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.1.joystick.0.empty=true
input.1.joystick.0.disabled=0
input.1.joystick.1.friendlyname=Joystick [2]
input.1.joystick.1.name=\\?\HID#VID_16C0&PID_27DC&Col02#6&313a9aad&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.1.joystick.1.empty=true
input.1.joystick.1.disabled=0
input.1.joystick.2.empty=true
input.1.joystick.2.disabled=0
input.1.joystick.3.empty=true
input.1.joystick.3.disabled=0
input.1.joystick.4.empty=true
input.1.joystick.4.disabled=0
input.1.joystick.5.empty=true
input.1.joystick.5.disabled=0
input.1.joystick.6.empty=true
input.1.joystick.6.disabled=0
input.1.joystick.7.empty=true
input.1.joystick.7.disabled=0
input.1.joystick.8.empty=true
input.1.joystick.8.disabled=0
input.1.joystick.9.empty=true
input.1.joystick.9.disabled=0
input.1.joystick.10.empty=true
input.1.joystick.10.disabled=0
input.1.joystick.11.empty=true
input.1.joystick.11.disabled=0
input.1.joystick.12.empty=true
input.1.joystick.12.disabled=0
input.1.joystick.13.empty=true
input.1.joystick.13.disabled=0
input.1.joystick.14.empty=true
input.1.joystick.14.disabled=0
input.1.joystick.15.empty=true
input.1.joystick.15.disabled=0
input.1.mouse.0.friendlyname=Windows mouse
input.1.mouse.0.name=WINMOUSE1
input.1.mouse.0.empty=true
input.1.mouse.0.disabled=0
input.1.mouse.1.friendlyname=Logitech HID-compliant Cordless Mouse
input.1.mouse.1.name=\\?\HID#VID_046D&PID_C50C&MI_01&Col01#7&8cacde5&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.1.mouse.1.empty=true
input.1.mouse.1.disabled=0
input.1.mouse.2.friendlyname=HID-konforme Maus
input.1.mouse.2.name=\\?\HID#VID_046D&PID_C52B&MI_01&Col01#8&3104d42c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.1.mouse.2.empty=true
input.1.mouse.2.disabled=0
input.1.mouse.3.friendlyname=Logitech HID-compliant Unifying Mouse [1]
input.1.mouse.3.name=\\?\HID#VID_046D&PID_C52B&REV_2400&MI_02&Qid_101B&WI_02#9&2821299b&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.1.mouse.3.empty=true
input.1.mouse.3.disabled=0
input.1.mouse.4.friendlyname=Logitech HID-compliant Unifying Mouse [2]
input.1.mouse.4.name=\\?\HID#VID_046D&PID_C52B&REV_2400&MI_02&Qid_4013&WI_01#9&3083db72&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.1.mouse.4.empty=true
input.1.mouse.4.disabled=0
input.1.mouse.5.empty=true
input.1.mouse.5.disabled=0
input.1.mouse.6.empty=true
input.1.mouse.6.disabled=0
input.1.mouse.7.empty=true
input.1.mouse.7.disabled=0
input.1.mouse.8.empty=true
input.1.mouse.8.disabled=0
input.1.mouse.9.empty=true
input.1.mouse.9.disabled=0
input.1.mouse.10.empty=true
input.1.mouse.10.disabled=0
input.1.mouse.11.empty=true
input.1.mouse.11.disabled=0
input.1.mouse.12.empty=true
input.1.mouse.12.disabled=0
input.1.mouse.13.empty=true
input.1.mouse.13.disabled=0
input.1.mouse.14.empty=true
input.1.mouse.14.disabled=0
input.1.mouse.15.empty=true
input.1.mouse.15.disabled=0
input.1.keyboard.0.friendlyname=HID-Tastatur
input.1.keyboard.0.name=\\?\HID#VID_046D&PID_ABD0&Col01#7&24518109&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.1.keyboard.0.empty=false
input.1.keyboard.0.disabled=false
input.1.keyboard.1.friendlyname=Logitech HID-Compliant Keyboard
input.1.keyboard.1.name=\\?\HID#VID_046D&PID_C50C&MI_00#7&2ca20ba7&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.1.keyboard.1.empty=false
input.1.keyboard.1.disabled=false
input.1.keyboard.1.button.87.F11=KEY_NP_MUL.0
input.1.keyboard.1.button.201.PRIOR=SPC_STATERESTORE.0
input.1.keyboard.1.button.209.NEXT=SPC_STATESAVE.0
input.1.keyboard.2.friendlyname=WinUAE null keyboard
input.1.keyboard.2.name=NULLKEYBOARD
input.1.keyboard.2.empty=true
input.1.keyboard.2.disabled=0
input.1.keyboard.3.friendlyname=WinUAE null keyboard
input.1.keyboard.3.name=NULLKEYBOARD
input.1.keyboard.3.empty=false
input.1.keyboard.3.disabled=false
input.1.keyboard.4.empty=true
input.1.keyboard.4.disabled=0
input.1.keyboard.5.empty=true
input.1.keyboard.5.disabled=0
input.1.keyboard.6.empty=true
input.1.keyboard.6.disabled=0
input.1.keyboard.7.empty=true
input.1.keyboard.7.disabled=0
input.1.keyboard.8.empty=true
input.1.keyboard.8.disabled=0
input.1.keyboard.9.empty=true
input.1.keyboard.9.disabled=0
input.1.keyboard.10.empty=true
input.1.keyboard.10.disabled=0
input.1.keyboard.11.empty=true
input.1.keyboard.11.disabled=0
input.1.keyboard.12.empty=true
input.1.keyboard.12.disabled=0
input.1.keyboard.13.empty=true
input.1.keyboard.13.disabled=0
input.1.keyboard.14.empty=true
input.1.keyboard.14.disabled=0
input.1.keyboard.15.empty=true
input.1.keyboard.15.disabled=0
input.1.internal.0.friendlyname=Internal events
input.1.internal.0.name=INTERNALEVENTS1
input.1.internal.0.empty=true
input.1.internal.0.disabled=0
input.2.joystick.0.friendlyname=Joystick [1]
input.2.joystick.0.name=\\?\HID#VID_16C0&PID_27DC&Col01#6&313a9aad&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.2.joystick.0.empty=true
input.2.joystick.0.disabled=0
input.2.joystick.1.friendlyname=Joystick [2]
input.2.joystick.1.name=\\?\HID#VID_16C0&PID_27DC&Col02#6&313a9aad&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.2.joystick.1.empty=true
input.2.joystick.1.disabled=0
input.2.joystick.2.empty=true
input.2.joystick.2.disabled=0
input.2.joystick.3.empty=true
input.2.joystick.3.disabled=0
input.2.joystick.4.empty=true
input.2.joystick.4.disabled=0
input.2.joystick.5.empty=true
input.2.joystick.5.disabled=0
input.2.joystick.6.empty=true
input.2.joystick.6.disabled=0
input.2.joystick.7.empty=true
input.2.joystick.7.disabled=0
input.2.joystick.8.empty=true
input.2.joystick.8.disabled=0
input.2.joystick.9.empty=true
input.2.joystick.9.disabled=0
input.2.joystick.10.empty=true
input.2.joystick.10.disabled=0
input.2.joystick.11.empty=true
input.2.joystick.11.disabled=0
input.2.joystick.12.empty=true
input.2.joystick.12.disabled=0
input.2.joystick.13.empty=true
input.2.joystick.13.disabled=0
input.2.joystick.14.empty=true
input.2.joystick.14.disabled=0
input.2.joystick.15.empty=true
input.2.joystick.15.disabled=0
input.2.mouse.0.friendlyname=Windows mouse
input.2.mouse.0.name=WINMOUSE1
input.2.mouse.0.empty=true
input.2.mouse.0.disabled=0
input.2.mouse.1.friendlyname=Logitech HID-compliant Cordless Mouse
input.2.mouse.1.name=\\?\HID#VID_046D&PID_C50C&MI_01&Col01#7&8cacde5&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.2.mouse.1.empty=true
input.2.mouse.1.disabled=0
input.2.mouse.2.friendlyname=HID-konforme Maus
input.2.mouse.2.name=\\?\HID#VID_046D&PID_C52B&MI_01&Col01#8&3104d42c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.2.mouse.2.empty=true
input.2.mouse.2.disabled=0
input.2.mouse.3.friendlyname=Logitech HID-compliant Unifying Mouse [1]
input.2.mouse.3.name=\\?\HID#VID_046D&PID_C52B&REV_2400&MI_02&Qid_101B&WI_02#9&2821299b&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.2.mouse.3.empty=true
input.2.mouse.3.disabled=0
input.2.mouse.4.friendlyname=Logitech HID-compliant Unifying Mouse [2]
input.2.mouse.4.name=\\?\HID#VID_046D&PID_C52B&REV_2400&MI_02&Qid_4013&WI_01#9&3083db72&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.2.mouse.4.empty=true
input.2.mouse.4.disabled=0
input.2.mouse.5.empty=true
input.2.mouse.5.disabled=0
input.2.mouse.6.empty=true
input.2.mouse.6.disabled=0
input.2.mouse.7.empty=true
input.2.mouse.7.disabled=0
input.2.mouse.8.empty=true
input.2.mouse.8.disabled=0
input.2.mouse.9.empty=true
input.2.mouse.9.disabled=0
input.2.mouse.10.empty=true
input.2.mouse.10.disabled=0
input.2.mouse.11.empty=true
input.2.mouse.11.disabled=0
input.2.mouse.12.empty=true
input.2.mouse.12.disabled=0
input.2.mouse.13.empty=true
input.2.mouse.13.disabled=0
input.2.mouse.14.empty=true
input.2.mouse.14.disabled=0
input.2.mouse.15.empty=true
input.2.mouse.15.disabled=0
input.2.keyboard.0.friendlyname=HID-Tastatur
input.2.keyboard.0.name=\\?\HID#VID_046D&PID_ABD0&Col01#7&24518109&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.2.keyboard.0.empty=false
input.2.keyboard.0.disabled=false
input.2.keyboard.1.friendlyname=Logitech HID-Compliant Keyboard
input.2.keyboard.1.name=\\?\HID#VID_046D&PID_C50C&MI_00#7&2ca20ba7&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.2.keyboard.1.empty=false
input.2.keyboard.1.disabled=false
input.2.keyboard.2.friendlyname=WinUAE null keyboard
input.2.keyboard.2.name=NULLKEYBOARD
input.2.keyboard.2.empty=true
input.2.keyboard.2.disabled=0
input.2.keyboard.3.friendlyname=WinUAE null keyboard
input.2.keyboard.3.name=NULLKEYBOARD
input.2.keyboard.3.empty=false
input.2.keyboard.3.disabled=false
input.2.keyboard.4.empty=true
input.2.keyboard.4.disabled=0
input.2.keyboard.5.empty=true
input.2.keyboard.5.disabled=0
input.2.keyboard.6.empty=true
input.2.keyboard.6.disabled=0
input.2.keyboard.7.empty=true
input.2.keyboard.7.disabled=0
input.2.keyboard.8.empty=true
input.2.keyboard.8.disabled=0
input.2.keyboard.9.empty=true
input.2.keyboard.9.disabled=0
input.2.keyboard.10.empty=true
input.2.keyboard.10.disabled=0
input.2.keyboard.11.empty=true
input.2.keyboard.11.disabled=0
input.2.keyboard.12.empty=true
input.2.keyboard.12.disabled=0
input.2.keyboard.13.empty=true
input.2.keyboard.13.disabled=0
input.2.keyboard.14.empty=true
input.2.keyboard.14.disabled=0
input.2.keyboard.15.empty=true
input.2.keyboard.15.disabled=0
input.2.internal.0.friendlyname=Internal events
input.2.internal.0.name=INTERNALEVENTS1
input.2.internal.0.empty=true
input.2.internal.0.disabled=0
input.3.joystick.0.friendlyname=Joystick [1]
input.3.joystick.0.name=\\?\HID#VID_16C0&PID_27DC&Col01#6&313a9aad&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.3.joystick.0.empty=true
input.3.joystick.0.disabled=0
input.3.joystick.1.friendlyname=Joystick [2]
input.3.joystick.1.name=\\?\HID#VID_16C0&PID_27DC&Col02#6&313a9aad&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
input.3.joystick.1.empty=true
input.3.joystick.1.disabled=0
input.3.joystick.2.empty=true
input.3.joystick.2.disabled=0
input.3.joystick.3.empty=true
input.3.joystick.3.disabled=0
input.3.joystick.4.empty=true
input.3.joystick.4.disabled=0
input.3.joystick.5.empty=true
input.3.joystick.5.disabled=0
input.3.joystick.6.empty=true
input.3.joystick.6.disabled=0
input.3.joystick.7.empty=true
input.3.joystick.7.disabled=0
input.3.joystick.8.empty=true
input.3.joystick.8.disabled=0
input.3.joystick.9.empty=true
input.3.joystick.9.disabled=0
input.3.joystick.10.empty=true
input.3.joystick.10.disabled=0
input.3.joystick.11.empty=true
input.3.joystick.11.disabled=0
input.3.joystick.12.empty=true
input.3.joystick.12.disabled=0
input.3.joystick.13.empty=true
input.3.joystick.13.disabled=0
input.3.joystick.14.empty=true
input.3.joystick.14.disabled=0
input.3.joystick.15.empty=true
input.3.joystick.15.disabled=0
input.3.mouse.0.friendlyname=Windows mouse
input.3.mouse.0.name=WINMOUSE1
input.3.mouse.0.empty=true
input.3.mouse.0.disabled=0
input.3.mouse.1.friendlyname=Logitech HID-compliant Cordless Mouse
input.3.mouse.1.name=\\?\HID#VID_046D&PID_C50C&MI_01&Col01#7&8cacde5&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.3.mouse.1.empty=true
input.3.mouse.1.disabled=0
input.3.mouse.2.friendlyname=HID-konforme Maus
input.3.mouse.2.name=\\?\HID#VID_046D&PID_C52B&MI_01&Col01#8&3104d42c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.3.mouse.2.empty=true
input.3.mouse.2.disabled=0
input.3.mouse.3.friendlyname=Logitech HID-compliant Unifying Mouse [1]
input.3.mouse.3.name=\\?\HID#VID_046D&PID_C52B&REV_2400&MI_02&Qid_101B&WI_02#9&2821299b&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.3.mouse.3.empty=true
input.3.mouse.3.disabled=0
input.3.mouse.4.friendlyname=Logitech HID-compliant Unifying Mouse [2]
input.3.mouse.4.name=\\?\HID#VID_046D&PID_C52B&REV_2400&MI_02&Qid_4013&WI_01#9&3083db72&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
input.3.mouse.4.empty=true
input.3.mouse.4.disabled=0
input.3.mouse.5.empty=true
input.3.mouse.5.disabled=0
input.3.mouse.6.empty=true
input.3.mouse.6.disabled=0
input.3.mouse.7.empty=true
input.3.mouse.7.disabled=0
input.3.mouse.8.empty=true
input.3.mouse.8.disabled=0
input.3.mouse.9.empty=true
input.3.mouse.9.disabled=0
input.3.mouse.10.empty=true
input.3.mouse.10.disabled=0
input.3.mouse.11.empty=true
input.3.mouse.11.disabled=0
input.3.mouse.12.empty=true
input.3.mouse.12.disabled=0
input.3.mouse.13.empty=true
input.3.mouse.13.disabled=0
input.3.mouse.14.empty=true
input.3.mouse.14.disabled=0
input.3.mouse.15.empty=true
input.3.mouse.15.disabled=0
input.3.keyboard.0.friendlyname=HID-Tastatur
input.3.keyboard.0.name=\\?\HID#VID_046D&PID_ABD0&Col01#7&24518109&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.3.keyboard.0.empty=false
input.3.keyboard.0.disabled=false
input.3.keyboard.1.friendlyname=Logitech HID-Compliant Keyboard
input.3.keyboard.1.name=\\?\HID#VID_046D&PID_C50C&MI_00#7&2ca20ba7&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.3.keyboard.1.empty=false
input.3.keyboard.1.disabled=false
input.3.keyboard.2.friendlyname=WinUAE null keyboard
input.3.keyboard.2.name=NULLKEYBOARD
input.3.keyboard.2.empty=true
input.3.keyboard.2.disabled=0
input.3.keyboard.3.friendlyname=WinUAE null keyboard
input.3.keyboard.3.name=NULLKEYBOARD
input.3.keyboard.3.empty=false
input.3.keyboard.3.disabled=false
input.3.keyboard.4.empty=true
input.3.keyboard.4.disabled=0
input.3.keyboard.5.empty=true
input.3.keyboard.5.disabled=0
input.3.keyboard.6.empty=true
input.3.keyboard.6.disabled=0
input.3.keyboard.7.empty=true
input.3.keyboard.7.disabled=0
input.3.keyboard.8.empty=true
input.3.keyboard.8.disabled=0
input.3.keyboard.9.empty=true
input.3.keyboard.9.disabled=0
input.3.keyboard.10.empty=true
input.3.keyboard.10.disabled=0
input.3.keyboard.11.empty=true
input.3.keyboard.11.disabled=0
input.3.keyboard.12.empty=true
input.3.keyboard.12.disabled=0
input.3.keyboard.13.empty=true
input.3.keyboard.13.disabled=0
input.3.keyboard.14.empty=true
input.3.keyboard.14.disabled=0
input.3.keyboard.15.empty=true
input.3.keyboard.15.disabled=0
input.3.internal.0.friendlyname=Internal events
input.3.internal.0.name=INTERNALEVENTS1
input.3.internal.0.empty=true
input.3.internal.0.disabled=0
input.4.keyboard.0.friendlyname=HID-Tastatur
input.4.keyboard.0.name=\\?\HID#VID_046D&PID_ABD0&Col01#7&24518109&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.4.keyboard.0.custom=true
input.4.keyboard.1.friendlyname=Logitech HID-Compliant Keyboard
input.4.keyboard.1.name=\\?\HID#VID_046D&PID_C50C&MI_00#7&2ca20ba7&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
input.4.keyboard.1.custom=true
input.4.keyboard.2.friendlyname=WinUAE null keyboard
input.4.keyboard.2.name=NULLKEYBOARD
input.4.keyboard.2.custom=true
input.4.keyboard.3.friendlyname=WinUAE null keyboard
input.4.keyboard.3.name=NULLKEYBOARD
input.4.keyboard.3.custom=true

If you need me sth. elso to do please feel free to ask, I'm more than happy to help.

[Toni Wilen]

bsdsocket is not statefile compatible.

But it is also very dangerous to use HDFs and statefiles if there is any chance that HDF gets modified, HDF can become badly corrupted if statefile is created, hdf is modified, statefile is loaded. Now data in memory (buffers) are out of sync with data in disk.

Directory harddrives are mostly safe, only single file(s) can get corrupted, not whole drive.

[SedrynTyros]

Yeah, save states seem to work okay for me in v2.6.0/v2.6.1 when I'm running the game off a directory HD ... although recently I ran into a problem in v2.6.1 trying to save Warlords using its in-game save function after loading a WinUAE save state. Warlords returned a File creation error message. Wasn't a big deal, though; I just continued the game using only WinUAE save states.

[bladecgn]

Originally Posted by Toni Wilen

But it is also very dangerous to use HDFs and statefiles if there is any chance that HDF gets modified, HDF can become badly corrupted if statefile is created, hdf is modified, statefile is loaded. Now data in memory (buffers) are out of sync with data in disk.

Directory harddrives are mostly safe, only single file(s) can get corrupted, not whole drive.

You are absolutely right, I didn't consider this.

What if i run "c:Lock WHDLoad: on" and "c:Lock SYS: on" commands before I start a WHDLoad game? Is that safe then or are there still disk accesses possible at filesystem level?

And what if I unlock again, is there maybe a write buffer that gets synced then automatically possibly altering data it should not?

[Toni Wilen]

Originally Posted by bladecgn

You are absolutely right, I didn't consider this.

What if i run "c:Lock WHDLoad: on" and "c:Lock SYS: on" commands before I start a WHDLoad game? Is that safe then or are there still disk accesses possible at filesystem level?

And what if I unlock again, is there maybe a write buffer that gets synced then automatically possibly altering data it should not?

Lock probably won't do anything else than mark it read-only (and even if it flushes written data, already read data stays stored) and filesystem may do it but disk driver can still keep old data cached.

I don't see any guaranteed way to force it.

[bladecgn]

Originally Posted by Toni Wilen

Lock probably won't do anything else than mark it read-only (and even if it flushes written data, already read data stays stored) and filesystem may do it but disk driver can still keep old data cached.

I don't see any guaranteed way to force it.

Interesting! Could I unmount the write protected drive und remount it unlocked? For that it would be of key interest to know if Lock works on filesystem or disk driver level. If it works on filesystem level I could maybe lock it with uae-configuration.

My interest is to have a way to be able to create safe satefiles so that damiging the hfs ist impossible. Another way would be of course to have the .hdfs locked until reboot. I could very well still load a new whdload game. For Whdload saves I could have the save be stored on a Directory harddrive.

[bladecgn]

What puzzles me ist the output from uae-configuration:

hardfile2=rw,DH0:.\HardDisks\dh0_wb3.9_MagicWB.PFS.hdf,63,4,2,512,0,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
uaehf0=hdf,rw,DH0:.\HardDisks\dh0_wb3.9_MagicWB.PFS.hdf,63,4,2,512,0,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
hardfile2=rw,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
uaehf1=hdf,rw,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
hardfile2=rw,DH2:.\HardDisks\dh2_WHDLoad_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
uaehf2=hdf,rw,DH2:.\HardDisks\dh2_WHDLoad_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
filesystem2=rw,DH3:Scratch:.\HardDisks\Scratch,-128
uaehf3=dir,rw,DH3:Scratch:.\HardDisks\Scratch,-128
hardfile2=rw,DH4:.\HardDisks\dh0_Gaming.hdf,63,4,2,512,-128,,uae
uaehf4=hdf,rw,DH4:.\HardDisks\dh0_Gaming.hdf,63,4,2,512,-128,,uae

Why ist hardfile2 listed threee times with different hdfs?

[bladecgn]

I tried to write-protect with

uae-configuration uaehf1 hdf,r,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae

but this does not work

[Toni Wilen]

Originally Posted by bladecgn

Why ist hardfile2 listed threee times with different hdfs?

Because thats how it original worked, each hardfile2 (originally was "hardfile", "2" added new parameters) adds new hardfile.

Originally Posted by bladecgn

I tried to write-protect with

uae-configuration uaehf1 hdf,r,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae

but this does not work

"Does not work" does not work.

[bladecgn]

Originally Posted by Toni Wilen

"Does not work" does not work.

Right... it does not change anything, the hdf ist still writeable, not read only.

How can you make a .hdf read-only with uae-configuration in the shell?

[Toni Wilen]

You need to change hardfile2 too. Backwards compatibility reasons. (Why not just use the GUI to change it?)

[bladecgn]

Originally Posted by Toni Wilen

You need to change hardfile2 too. Backwards compatibility reasons. (Why not just use the GUI to change it?)

But as you see in above output, hardfile2 is there several times:
hardfile2=rw,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
uaehf1=hdf,rw,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
hardfile2=rw,DH2:.\HardDisks\dh2_WHDLoad_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae

I want to make the hardfile read-only in a script on amiga side (if I start a WHDLoad-Game the FS shall get lock so that savestes are possible but no more writes until next reboot where it gets unlocked again in user-startup).

[Toni Wilen]

Originally Posted by bladecgn

But as you see in above output, hardfile2 is there several times:
hardfile2=rw,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
uaehf1=hdf,rw,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae
hardfile2=rw,DH2:.\HardDisks\dh2_WHDLoad_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae

I want to make the hardfile read-only in a script on amiga side (if I start a WHDLoad-Game the FS shall get lock so that savestes are possible but no more writes until next reboot where it gets unlocked again in user-startup).

As I said above, hardfile2 means "add this new hardfile", it does not mean there are duplicates. (There are few old option names that are not unique)

(Why not just use directory harddrives?)

[bladecgn]

I issue:

uae-configuration uaehf1 hdf,r,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae hardfile2 r,DH1:.\HardDisks\dh1_HD_PFS.hdf,63,4,2,512,-128,G:\Emulator\Amiga\WinUAE\HardDisks\pfs3_aio-handler,uae

But DH1: is still r/w.

[Toni Wilen]

I didn't notice you wanted to use uae-configuration. It does not work. (because it needs single attribute, not multiple)

This should work (from some beta changelog)

- Added uae-configuration harddrive attribute modification support:
Syntax: uaehfX_Z where X = unit number, Z = attribute name. (for example: "uaehf0_bootpri 10")
Attribute names: devicename, volumename, root, bootpri, read-only, filesys, controller.
Syntax is write-only. Use plain uaehfX to check current values.
Reset required to activate modified settings.

[bladecgn]

Glad we go this sorted Toni. I don't think it will serve my purpouse because of:

Originally Posted by Toni Wilen

Reset required to activate modified settings.

An immediate write protect should not be a problem for PFS as it's a journaling filesystem so the integrity of the hdf should be guaranteed.

I want the w attribute to be off immediately (issued by a script) without a reset and want it to turn on again by user-startup at next reboot.
This shall ensure that reading savestates does do no harm to the disk at driver level.

I'm afraid an immediate change of the rw flags during emulation is impossible, correct?

[Toni Wilen]

Originally Posted by bladecgn

I'm afraid an immediate change of the rw flags during emulation is impossible, correct?

Of course emulation can make drive write protected instantly but it would only break everything if there are unflushed data (driver or filesystem) that emulation knows nothing about it. You would only get "volume x is write protected" message during next flush attempt and data loss.

And problem is not just writes, driver can cache read data which may not be ever "forgotten" because driver is made for non-removable drives.

Data gets written to disk, this data is kept in driver's cache, state is saved, something new gets written to save blocks, state is restored, now data in disk is different vs data in driver cache.

This is unsolvable problem, without storing whole hdf (or at least changed blocks) with the state file but it would also introduce other annoying side-effects like save files, config files etc.. reverting back to originals.