Possible to run WHDLoad games as Read-only?

Foebane · 08 November 2018, 16:54

I'm thinking about trying to run WHDLoad games (in .lha archives from Retroplay) as bootable read-only archives in WinUAE, but some of these games require the saving of high-score tables or other info into the folder, but of course, WinUAE doesn't allow the alteration of such archives.

So how can I get WHDLoad to redirect or prevent the writing of such info. Or is there an alternative?

daxb · 08 November 2018, 17:26

Try this: http://whdload.de/docs/en/opt.html#SavePath for redirect saves.
PreloadSize is written to program icon when started from WB. So don't start from WB.

AMIGASYSTEM · 08 November 2018, 18:18

But then you have to edit all the Tooltypes, then unpack and reassemble all the archives

Foebane · 08 November 2018, 18:29

This is only speculation at this time, I've got a system that uses a modified ClassicWB Lite HDF with the games already installed and set up, but I was thinking about by-passing the mass install altogether.

daxb · 08 November 2018, 18:37

Quote:

Originally Posted by AMIGASYSTEM

But then you have to edit all the Tooltypes, then unpack and reassemble all the archives

That is not needed. SavePath can be set global (whdload.prefs).

AMIGASYSTEM · 08 November 2018, 18:40

Ok, but I do not think it's a good idea to use archives

Foebane · 08 November 2018, 18:42

Quote:

Originally Posted by daxb

Try this: http://whdload.de/docs/en/opt.html#SavePath for redirect saves.
PreloadSize is written to program icon when started from WB. So don't start from WB.

1. How do I avoid WB altogether? Put the .lha archive as the only boot option?
2. Where do I modify this global WHDLoad variable?
3. How can I run a game from the Shell?

Quote:

Originally Posted by AMIGASYSTEM

Ok, but I do not think it's a good idea to use archives

I could extract each .lha into its own tiny .hdf file and boot that, then I wouldn't have the read/write issues.

Looks like I've got some experimenting to do... Fun times. Honestly.

AMIGASYSTEM · 08 November 2018, 19:16

It would not be better to put all the WHDLoad games on one, two or three HDFs arranged by theme

daxb · 08 November 2018, 19:40

Usually WB start means double klick on program icon. Just start it from command line to avoid WB start. E.g. "whdload mygame.save preload". See whdload docs for more info.

s:whdload.prefs is the file for global settings. Open it with an text editor

But it seems your are on the wrong way like AMIGASYSTEM said already.

Foebane · 08 November 2018, 19:43

Quote:

Originally Posted by AMIGASYSTEM

It would not be better to put all the WHDLoad games on one, two or three HDFs arranged by theme

If I could take a whole bunch of small .hdfs, equal to the number of games, and extract each game fresh onto each one, then there would be a unique configuration for each one and I could bypass the mass extract onto the ClassicWB .hdf.

I'd say each .hdf would be 6Mb at most, or make them different sizes to accommodate each game (2Mb, 4Mb, 6Mb).

But I do need to know how to properly run the WHDLoad games from the Shell: I tried "WHDLoad Vaxine.Slave" for one game and it ran, but I don't know if it took account of the WHDLoad variables in the icon information. I have used IconLoad on the icons themselves when in DOpus, so what is my best bet?

daxb · 08 November 2018, 19:56

If you start a game from command line then of course the icon and its information are ignored. That was your goal if I understand you right. You can use "WBRun whdload mygame.slave" to simulate the double klick on game icon (WB start). AmigaOS unfortunately distinguish between WB start and CLI start.

Foebane · 08 November 2018, 20:16

Yeah, I just tried to create a test .hdf with it's own configuration and "launch" archive (which have worked fine for the read-only demos), but it really is a lot of hassle, especially having to extract each game to its own .hdf, when ClassicWB has a custom folder for games, complete with tools to build lists for the GamesMenu launcher.

Also, normally, the ClassicWB .hdf on a fresh install is mostly empty in a 200Mb uncompressed file - by extracting lots of game data into it, it helps to fill it up and make proper use of this space, and the games are runnable from scratch.

I'm probably giving up too easily, but I just thought I'd investigate the option. But if bootable read-only WHDLoad archives are impractical, and I can't even use CLI start for the games, AND the games are already running perfectly fine on my current system, then what's the point?

If I was in the middle of a big game like Cannon Fodder, I could always back up the ClassicWB .hdf itself, so I wouldn't lose my progress. Or back it up some other way.

Thanks anyway, AmigaSystem and Daxb, for your assistance and generous advice.

AMIGASYSTEM · 08 November 2018, 20:21

Quote:

Originally Posted by Foebane

Also, normally, the ClassicWB .hdf on a fresh install is mostly empty in a 200Mb uncompressed file - by extracting lots of game data into it, it helps to fill it up and make proper use of this space, and the games are runnable from scratch.

Create a new 6/8 Giga HardFile and transfer everything ClassicWB, in this way you will have all the space you want

Foebane · 08 November 2018, 20:30

Quote:

Originally Posted by AMIGASYSTEM

Create a new 6/8 Giga HardFile and transfer everything ClassicWB, in this way you will have all the space you want

I heard that Workbench 3.1 balks at more than 2Gb in a hardfile.

AMIGASYSTEM · 08 November 2018, 21:16

If you use a modern Filesystem (SFS/PFS) you do not have this limit.

Foebane · 08 November 2018, 22:00

Quote:

Originally Posted by AMIGASYSTEM

If you use a modern Filesystem (SFS/PFS) you do not have this limit.

200Mb is plenty for me, as there's not that many Amiga games I like. In fact, I think I'm being generous with the 60 games I've already installed. However, I have 600 demos as well, and I've always preferred the latter anyway.

Foebane · 29 January 2019, 18:14

BUMP

I've just discovered that with a System.hdf (ClassicWB) and using archives as read-only on WinUAE, that I CAN, in most cases, run some games (and certainly demos) direct from the archive and not have to extract (install) them first. A lot of these WHDLoad archives don't seem to need writing to, except the ones that store high scores, but even then no error messages occur, it just seems to ignore them and not save them.

I have a config attached to each WHDLoad archive, with each one asking if I want to install the game yes/no, but it seems I might be saying no more and more now.

08 November 2018, 16:54	#1
Foebane Banned Join Date: Sep 2011 Location: Cardiff, UK Age: 51 Posts: 2,871	Possible to run WHDLoad games as Read-only? I'm thinking about trying to run WHDLoad games (in .lha archives from Retroplay) as bootable read-only archives in WinUAE, but some of these games require the saving of high-score tables or other info into the folder, but of course, WinUAE doesn't allow the alteration of such archives. So how can I get WHDLoad to redirect or prevent the writing of such info. Or is there an alternative?

08 November 2018, 18:29	#4
Foebane Banned Join Date: Sep 2011 Location: Cardiff, UK Age: 51 Posts: 2,871	This is only speculation at this time, I've got a system that uses a modified ClassicWB Lite HDF with the games already installed and set up, but I was thinking about by-passing the mass install altogether. Last edited by Foebane; 08 November 2018 at 18:39.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
CD32 compilation Games run on 2mb only..why can't WHDLoad games run on 2mb	spannernick	support.Games	2	12 July 2017 17:15
Do games run slower under WHDLoad?	stu232	support.Hardware	4	17 April 2014 02:59
Why Does WHDload run only 20% of my AGA games??	magnetic	support.Games	12	16 June 2012 16:03
How to make read whdload games in more partitions?	Omolungo	project.ClassicWB	5	10 April 2011 12:45
WHDLoad registration to run games	Dagon	support.Games	5	28 February 2011 15:41

08 November 2018, 17:26	#2
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,303	Try this: http://whdload.de/docs/en/opt.html#SavePath for redirect saves. PreloadSize is written to program icon when started from WB. So don't start from WB.

08 November 2018, 18:18	#3
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,248	But then you have to edit all the Tooltypes, then unpack and reassemble all the archives

08 November 2018, 18:40	#6
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,248	Ok, but I do not think it's a good idea to use archives

08 November 2018, 19:16	#8
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,248	It would not be better to put all the WHDLoad games on one, two or three HDFs arranged by theme

08 November 2018, 19:40	#9
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,303	Usually WB start means double klick on program icon. Just start it from command line to avoid WB start. E.g. "whdload mygame.save preload". See whdload docs for more info. s:whdload.prefs is the file for global settings. Open it with an text editor But it seems your are on the wrong way like AMIGASYSTEM said already.

08 November 2018, 19:56	#11
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,303	If you start a game from command line then of course the icon and its information are ignored. That was your goal if I understand you right. You can use "WBRun whdload mygame.slave" to simulate the double klick on game icon (WB start). AmigaOS unfortunately distinguish between WB start and CLI start.

08 November 2018, 20:16	#12
Foebane Banned Join Date: Sep 2011 Location: Cardiff, UK Age: 51 Posts: 2,871	Yeah, I just tried to create a test .hdf with it's own configuration and "launch" archive (which have worked fine for the read-only demos), but it really is a lot of hassle, especially having to extract each game to its own .hdf, when ClassicWB has a custom folder for games, complete with tools to build lists for the GamesMenu launcher. Also, normally, the ClassicWB .hdf on a fresh install is mostly empty in a 200Mb uncompressed file - by extracting lots of game data into it, it helps to fill it up and make proper use of this space, and the games are runnable from scratch. I'm probably giving up too easily, but I just thought I'd investigate the option. But if bootable read-only WHDLoad archives are impractical, and I can't even use CLI start for the games, AND the games are already running perfectly fine on my current system, then what's the point? If I was in the middle of a big game like Cannon Fodder, I could always back up the ClassicWB .hdf itself, so I wouldn't lose my progress. Or back it up some other way. Thanks anyway, AmigaSystem and Daxb, for your assistance and generous advice.

08 November 2018, 21:16	#15
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,248	If you use a modern Filesystem (SFS/PFS) you do not have this limit.

29 January 2019, 18:14	#17
Foebane Banned Join Date: Sep 2011 Location: Cardiff, UK Age: 51 Posts: 2,871	BUMP I've just discovered that with a System.hdf (ClassicWB) and using archives as read-only on WinUAE, that I CAN, in most cases, run some games (and certainly demos) direct from the archive and not have to extract (install) them first. A lot of these WHDLoad archives don't seem to need writing to, except the ones that store high scores, but even then no error messages occur, it just seems to ignore them and not save them. I have a config attached to each WHDLoad archive, with each one asking if I want to install the game yes/no, but it seems I might be saying no more and more now.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)