2025-01-21 19:29 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0006575WHDLoad[All Projects] Generalpublic2024-12-03 09:49
Reporterztronzo 
Assigned ToWeplProject InfoHD-Installer for OS-Killer
http://whdload.de/
 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusclosedResolutionwon't fix 
Product Version 
Target VersionFixed in Version 
Summary0006575: Feature improvement for SavePath option to allow 2 locations (optional 2nd)
DescriptionCan we allow for 2 savepath locations which could be comma-separated?
As example: SavePath=RAM:WHDSaves,DH0:WHDSaves

TagsNo tags attached.
MachineA1200
CPU68020
CPUSpeed50
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem0 MB
WorkbenchOS 3.0
KickROM40 - Kick 3.1
KickSoftNone
WHDLoad19.0beta
Attached Files

-Relationships
+Relationships

-Notes

note ~0013903

DJ Mike (developer)

What is the purpose for this?

note ~0013938

Wepl (manager)

it can only write to one location, which is always the first data directory
do you want to read from multiple locations?

note ~0014220

ztronzo (reporter)

My personal purpose is because I use save states with an emulated machine, and store everything in RAM for portability of saved states between users.
And also want a 2nd copy on DH1: (so I can later sync score files with a webserver).

Right now, I use one or the other and convert them when needed.

I took the liberty for requesting this feature as it would make sense to me if we could also store to multiple locations as I already know that the ability for reading from multiple locations is already available through comma separated paths. Although I havnt fully tested this, I believe if the contents in one path are lost (for example RAM: after a reset). We can failback to loading data from the 2nd location (for example the DH1:)

In real conditions it could be thought of as a secondary repository for safe-keeping of scores and saves.

note ~0014229

Wepl (manager)

This would make the io operations and error handling much more complex.
Sorry, I'm not going to implement this.
You could try to use ExecuteCleanup to manually copy changed files to a second location.

note ~0014233

ztronzo (reporter)

No problem, I had to ask though and thanks for the suggestion.

I am just starting to look into the series of "Execute*" commands.
Seems ExecutePostDisk might be useful for my case, so Will be giving it a try.

Thanks again!
You guys are the best!
+Notes

-Issue History
Date Modified Username Field Change
2024-09-06 03:22 ztronzo New Issue
2024-09-06 09:00 DJ Mike Note Added: 0013903
2024-09-15 14:13 Wepl Assigned To => Wepl
2024-09-15 14:13 Wepl Status new => assigned
2024-09-15 14:15 Wepl Note Added: 0013938
2024-11-24 07:55 ztronzo Note Added: 0014220
2024-11-24 20:34 Wepl Note Added: 0014229
2024-11-24 20:35 Wepl Status assigned => resolved
2024-11-24 20:35 Wepl Resolution open => won't fix
2024-11-25 03:30 ztronzo Note Added: 0014233
2024-12-03 09:49 Wepl Status resolved => closed
+Issue History