Can anyone explain me how roms are named in GB64?
Let's take the example for The Three Musketeers. We have 3 files:
3MUSKET0.D64
3MUSKET1.D64
3MUSKET2.D64
But looking at the TOSEC set seems the actual game is only 2 Disks, also in the comments it states : " Comment: 2 versions (trained / intro)"
So we probably have 2 different versions mixed here, but looking at the filenames I have no clue which one is which. Are there any specific rules used to name them? I couldn't find anything on it.
Thanks
Welcome to the Gamebase 64 forums. An attempt to document ALL Commodore 64 gameware before it's too late!
Rom Namig
Moderator: Jimbo
- .mad.
- Honoured Member
- Location: Lancashire
Post
disk names with 0 are usually BOOT disks.
so as not to get confused when inserting disk 1 or 2.
in this case the disk 0 is for the hacked intro version.
booting with disk 1 will load the alternate version which needs true drive emulation to work.
disk 2 is the same for either version.
so as not to get confused when inserting disk 1 or 2.
in this case the disk 0 is for the hacked intro version.
booting with disk 1 will load the alternate version which needs true drive emulation to work.
disk 2 is the same for either version.
- brolly
- New Member
Post
Thanks for the reply.
But does this naming follow any standard? I mean I couldn't know both disk 0 and disk 1 were both the boot disk just by looking at the filenames.
On this kind of situations, where you have more than 1 version of the same disk, is this always noted in the comments?
But does this naming follow any standard? I mean I couldn't know both disk 0 and disk 1 were both the boot disk just by looking at the filenames.
On this kind of situations, where you have more than 1 version of the same disk, is this always noted in the comments?
- .mad.
- Honoured Member
- Location: Lancashire
Post
the objective is to have only one hacked 100% working version in the archive, with the original in the Extras.
but on the rare occasion you find two versions.
this is because of bugs, copy protection, or better trainers.
example
the game might have a broken high-score saver which crashes at game over.
so there is a 2nd version being temporary fixed with the hi-score saver disabled.
the bugged version is kept, until it can be fixed or replaced.
it will always be noted in the NFO file if there are two versions.
but on the rare occasion you find two versions.
this is because of bugs, copy protection, or better trainers.
example
the game might have a broken high-score saver which crashes at game over.
so there is a 2nd version being temporary fixed with the hi-score saver disabled.
the bugged version is kept, until it can be fixed or replaced.
it will always be noted in the NFO file if there are two versions.
Who is online
Users browsing this forum: No registered users and 98 guests