Romdisk Swapping - Revision history

Unknown user at 18:12, 30 May 2020

2020-05-30T18:12:56Z

← Older revision		Revision as of 18:12, 30 May 2020
Line 19:		Line 19:

	This is the usual romdisk command, you can still keep this		This is the usual romdisk command, you can still keep this
	$(KOS_GENROMFS) -f romdisk.img -d path/to/romdisk -v		<syntaxhighlight lang="bash">$(KOS_GENROMFS) -f romdisk.img -d path/to/romdisk -v</syntaxhighlight>

	This is your new romdisk, replace the romdisk_name and romdisk_folder with what you want.		This is your new romdisk, replace the romdisk_name and romdisk_folder with what you want.
	$(KOS_GENROMFS) -f romdisk_name.img -d path/to/romdisk_folder -v		<syntaxhighlight lang="bash">$(KOS_GENROMFS) -f romdisk_name.img -d path/to/romdisk_folder -v</syntaxhighlight>

	If I'm using the example from earlier, I could make a "level1" romdisk this way		If I'm using the example from earlier, I could make a "level1" romdisk this way
	$(KOS_GENROMFS) -f level1.img -d path/to/level -v		<syntaxhighlight lang="bash">$(KOS_GENROMFS) -f level1.img -d path/to/level -v</syntaxhighlight>


Line 32:		Line 32:
	For more info, check this topic [https://dcemulation.org/phpBB/viewtopic.php?f=29&t=68795&hilit=romdisk+feet+of+fury]		For more info, check this topic [https://dcemulation.org/phpBB/viewtopic.php?f=29&t=68795&hilit=romdisk+feet+of+fury]

	#include <kos.h>		<syntaxhighlight lang="c">
	#include <zlib/zlib.h>		#include <kos.h>
			#include <zlib/zlib.h>
	// Thanks BlackAura ;)
	int mount_romdisk(char filename, char mountpoint) {		// Thanks BlackAura ;)
	void *buffer;		int mount_romdisk(char filename, char mountpoint) {
	int length = zlib_getlength(filename);		void *buffer;
			int length = zlib_getlength(filename);
	// Check failure
	if(length == 0)		// Check failure
	return 0;		if(length == 0)
			return 0;
	// Allocate memory, read file
	buffer = malloc(length);		// Allocate memory, read file
	gzread(file, buffer, length);		buffer = malloc(length);
	gzclose(file);		gzread(file, buffer, length);
			gzclose(file);
	// Mount
	fs_romdisk_mount(mountpoint, buffer, 1);		// Mount
	return 1;		fs_romdisk_mount(mountpoint, buffer, 1);
	}		return 1;
			}
			</syntaxhighlight>

	''' It is important that your mount point start with a '/' -> "/level1" and not "level1" '''		''' It is important that your mount point start with a '/' -> "/level1" and not "level1" '''
Line 59:		Line 61:

	You can unload the romdisk using:		You can unload the romdisk using:
	fs_romdisk_unmount(mountpoint);		<syntaxhighlight lang="c">fs_romdisk_unmount(mountpoint);</syntaxhighlight>


	= Usage with a Broadband adapter or dc-ipload =		= Usage with a Broadband adapter or dc-ipload =
	In order to use these new romdisk, you need to enable ''/pc'' redirection in your ''dc-tool'', update your ''dc-tool'' command to use ''-c'':		In order to use these new romdisk, you need to enable ''/pc'' redirection in your ''dc-tool'', update your ''dc-tool'' command to use ''-c'':
	dc-tool-ip -t dreamcast -c /path/to/project -x program_name.elf		<syntaxhighlight lang="bash">dc-tool-ip -t dreamcast -c /path/to/project -x program_name.elf</syntaxhighlight>

	You can now use the function below to access files in the ''/rd'' folder:		You can now use the function below to access files in the ''/rd'' folder:
	mount_romdisk("/pc/romdisk_name.img", "/rd");		<syntaxhighlight lang="c">mount_romdisk("/pc/romdisk_name.img", "/rd");</syntaxhighlight>

	Keep in mind that you'll have to switch ''/pc/'' to ''/cd/'' when you burn this to a CD.		Keep in mind that you'll have to switch ''/pc/'' to ''/cd/'' when you burn this to a CD.

Unknown user at 21:21, 11 January 2020

2020-01-11T21:21:01Z

← Older revision		Revision as of 21:21, 11 January 2020
Line 28:		Line 28:


	== ~~Step 3~~ ==		== Using your romdisk ==
	In your code you'll need a way to load those new romdisks, we'll use this code snippet by ''BlackAura''.		In your code you'll need a way to load those new romdisks, we'll use this code snippet by ''BlackAura''.
	For more info, check this topic [https://dcemulation.org/phpBB/viewtopic.php?f=29&t=68795&hilit=romdisk+feet+of+fury]		For more info, check this topic [https://dcemulation.org/phpBB/viewtopic.php?f=29&t=68795&hilit=romdisk+feet+of+fury]
Line 56:		Line 56:
	''' It is important that your mount point start with a '/' -> "/level1" and not "level1" '''		''' It is important that your mount point start with a '/' -> "/level1" and not "level1" '''

	You can now unload the romdisk using:		You can now load files that are located at "/level1". Example "/level1/spritesheet.png"

			You can unload the romdisk using:
	fs_romdisk_unmount(mountpoint);		fs_romdisk_unmount(mountpoint);

Line 64:		Line 66:
	dc-tool-ip -t dreamcast -c /path/to/project -x program_name.elf		dc-tool-ip -t dreamcast -c /path/to/project -x program_name.elf

	You can now use the function below to access files in the ''/~~rom~~'' folder:		You can now use the function below to access files in the ''/rd'' folder:
	mount_romdisk("/pc/romdisk_name.img~~.gz~~", "/~~rom~~");		mount_romdisk("/pc/romdisk_name.img", "/rd");

	Keep in mind that you'll have to switch ''/pc/'' to ''/cd/'' when you burn this to a CD.		Keep in mind that you'll have to switch ''/pc/'' to ''/cd/'' when you burn this to a CD.

Unknown user at 21:16, 11 January 2020

2020-01-11T21:16:34Z

← Older revision		Revision as of 21:16, 11 January 2020
Line 5:		Line 5:
	I also think that it could be a neat way to handle/manage your memory altogether.		I also think that it could be a neat way to handle/manage your memory altogether.

	* 2020 edit : Removed the GZ compression as it seemed to cause problem with filename longer than a certain length (16 IIRC?) *		''2020 edit : Removed the GZ compression as it seemed to cause problem with filename longer than a certain length (16 IIRC?)''

	= Guide =		= Guide =
Line 11:		Line 11:
	Organize the content or your romdisk in multiple folders:		Organize the content or your romdisk in multiple folders:

	~~```~~		/level1
	/level1		/level2
	/level2		/level3
	/level3
	~~```~~

	== Convert to romdisk ==		== Convert to romdisk ==
Line 56:		Line 54:
	}		}

	It is important that your mount point start with a '/' -> "/level1" and not "level1"		''' It is important that your mount point start with a '/' -> "/level1" and not "level1" '''

	You can now unload the romdisk using:		You can now unload the romdisk using:

Unknown user at 21:14, 11 January 2020

2020-01-11T21:14:28Z

← Older revision		Revision as of 21:14, 11 January 2020
Line 1:		Line 1:
	Author: Lerabot		Author: Lerabot/Magnes

	= Introduction =		= Introduction =
	When I started adding things to the ROM disk, I didn't realize that my 10MB+ .elf file would be problematic (i.e. not load) on the Dreamcast.		When I started adding things to the ROM disk, I didn't realize that my 10MB+ .elf file would be problematic (i.e. not load) on the Dreamcast.
	Also it's been mentioned in a forum topic that loading a romdisk instead of multiple files would be faster.		Also it's been mentioned in a forum topic that loading a romdisk instead of multiple files would be faster. Need source
	I also think that it could be a neat way to handle/manage your memory altogether.		I also think that it could be a neat way to handle/manage your memory altogether.

			* 2020 edit : Removed the GZ compression as it seemed to cause problem with filename longer than a certain length (16 IIRC?) *

	= Guide =		= Guide =
	== ~~Step 1~~==		== Organize your assets ==
	~~Organizing~~ the content or your romdisk in multiple folders:		Organize the content or your romdisk in multiple folders:

	/level1		```
	/level2		/level1
	/level3		/level2
			/level3
			```

			== Convert to romdisk ==
			In your Makefile, duplicate the usual romdisk generation command but change the romdisk name and directory.

			This is the usual romdisk command, you can still keep this
			$(KOS_GENROMFS) -f romdisk.img -d path/to/romdisk -v

	~~== Step 2 ==~~		This is your new romdisk, replace the romdisk_name and romdisk_folder with what you want.
	In your ~~Makefile~~, ~~duplicate the usual romdisk generation command but change~~ the ~~romdisk name~~ and ~~directory~~.		$(KOS_GENROMFS) -f romdisk_name.img -d path/to/romdisk_folder -v
	~~I also added GZip compression, however sometimes GZip~~-~~ed files fail~~ to ~~load. If thats the case for you then don't bother with GZip.~~

	~~romdisk.img:~~		If I'm using the example from earlier, I could make a "level1" romdisk this way
	~~$(KOS_GENROMFS) -f romdisk.img -d path/to/romdisk -v # <- this is the usual romdisk command, you can still keep this~~		$(KOS_GENROMFS) -f level1.img -d path/to/level -v
	~~$(KOS_GENROMFS) -f romdisk_name.img -d path/to/romdisk_folder -v # <- this is your new romdisk, replace the romdisk_name and romdisk_folder with what you want.~~
	~~$(KOS_GENROMFS) -f level1.img -d path/to/level -v # <- if~~ I'm using the ~~exemple~~ from earlier, I could make a "level1" romdisk this way
	~~gzip~~ -f ~~-9 romdisk_name~~.img ~~# <~~-~~make sure you add all your new romdisk names here~~

	~~''Note:'' the leading whitespace consists of a tab, not spaces.~~

	== Step 3 ==		== Step 3 ==
	In your code you'll need a way to load those new romdisks, we'll use this code snippet by ''BlackAura''.		In your code you'll need a way to load those new romdisks, we'll use this code snippet by ''BlackAura''.
	For more info, check this topic [https://dcemulation.org/phpBB/viewtopic.php?f=29&t=68795&hilit=romdisk+feet+of+fury]		For more info, check this topic [https://dcemulation.org/phpBB/viewtopic.php?f=29&t=68795&hilit=romdisk+feet+of+fury]


	#include <kos.h>		#include <kos.h>
Line 42:		Line 44:
	// Check failure		// Check failure
	if(length == 0)		if(length == 0)
	~~return 0;~~

	~~// Open file~~
	~~gzFile file = gzopen(filename, "rb");~~
	~~if(!file)~~
	return 0;		return 0;

Line 59:		Line 56:
	}		}

	It is important that your mount point start with a '/' -> "/level1" and not "level1"		It is important that your mount point start with a '/' -> "/level1" and not "level1"

	You can now unload the romdisk using:		You can now unload the romdisk using:

Unknown user: Created page with "Author: Lerabot = Introduction = When I started adding things to the ROM disk, I didn't realize that my 10MB+ .elf file would be problematic (i.e. not load) on the Dreamcast...."

2020-01-11T03:50:37Z

Created page with "Author: Lerabot = Introduction = When I started adding things to the ROM disk, I didn't realize that my 10MB+ .elf file would be problematic (i.e. not load) on the Dreamcast...."

New page

Author: Lerabot

= Introduction =
When I started adding things to the ROM disk, I didn't realize that my 10MB+ .elf file would be problematic (i.e. not load) on the Dreamcast.
Also it's been mentioned in a forum topic that loading a romdisk instead of multiple files would be faster.
I also think that it could be a neat way to handle/manage your memory altogether.

= Guide =
== Step 1==
Organizing the content or your romdisk in multiple folders:

/level1
/level2
/level3

== Step 2 ==
In your Makefile, duplicate the usual romdisk generation command but change the romdisk name and directory.
I also added GZip compression, however sometimes GZip-ed files fail to load. If thats the case for you then don't bother with GZip.

romdisk.img:
$(KOS_GENROMFS) -f romdisk.img -d path/to/romdisk -v # <- this is the usual romdisk command, you can still keep this
$(KOS_GENROMFS) -f romdisk_name.img -d path/to/romdisk_folder -v # <- this is your new romdisk, replace the romdisk_name and romdisk_folder with what you want.
$(KOS_GENROMFS) -f level1.img -d path/to/level -v # <- if I'm using the exemple from earlier, I could make a "level1" romdisk this way
gzip -f -9 romdisk_name.img # <-make sure you add all your new romdisk names here

''Note:'' the leading whitespace consists of a tab, not spaces.

== Step 3 ==
In your code you'll need a way to load those new romdisks, we'll use this code snippet by ''BlackAura''.
For more info, check this topic [https://dcemulation.org/phpBB/viewtopic.php?f=29&t=68795&hilit=romdisk+feet+of+fury]

#include <kos.h>
#include <zlib/zlib.h>

// Thanks BlackAura ;)
int mount_romdisk(char *filename, char *mountpoint) {
void *buffer;
int length = zlib_getlength(filename);

// Check failure
if(length == 0)
return 0;

// Open file
gzFile file = gzopen(filename, "rb");
if(!file)
return 0;

// Allocate memory, read file
buffer = malloc(length);
gzread(file, buffer, length);
gzclose(file);

// Mount
fs_romdisk_mount(mountpoint, buffer, 1);
return 1;
}

It is important that your mount point start with a '/' -> "/level1" and not "level1"

You can now unload the romdisk using:
fs_romdisk_unmount(mountpoint);

= Usage with a Broadband adapter or dc-ipload =
In order to use these new romdisk, you need to enable ''/pc'' redirection in your ''dc-tool'', update your ''dc-tool'' command to use ''-c'':
dc-tool-ip -t dreamcast -c /path/to/project -x program_name.elf

You can now use the function below to access files in the ''/rom'' folder:
mount_romdisk("/pc/romdisk_name.img.gz", "/rom");

Keep in mind that you'll have to switch ''/pc/'' to ''/cd/'' when you burn this to a CD.