Need help with defective floppy drive in A1WSX

Page 3/3
1 | 2 |

By doba

Resident (39)

doba's picture

21-05-2004, 22:45

Actually, since you asked! There are some RFFs (requests for features) from my side:

1) optional feature:

replace first command after "AB" to jump to a block of code, allocated in the end of megarom, and this code should check if hot key (let's say CTRL+B) is pressed, and if it is, then replace "AB" with 0x0000 and reboot MSX, if hot key is not pressed, just modify first instruction after "AB" to it's original value and jump to it, so the game plays as it's supposed.

The use for this feature is a quick SCC+ cartridge reset done in software. Right now I need to wait about 5 minutes before DRAM in SCC+ zeroes and I can boot.

I know I can either take the cart out and put it back in or add a button to power off dram, but I don't like those hardware solutions, because they damage external look of cartridge Sad

2) support load from at least one of the popular MSX archive formats: pma/lha, arc or sl (whatever was this superfast MSX packager from Erog "SOLiD" Voznesensky). This way a user can put about twice as many games on a floppy!

3) add visual mode. I.e. if I launch romload -v (or any other parameter you prefer), open a nice simple 40-character wide menu, which have simple disk browser and allows to choose the rom file, and after this choose settins to launch it.

4) create CRC database with known parameters, so users don't have to experiment to get a rom working, if they have a popular ROM image that is in database

By BiFi

Enlighted (4348)

BiFi's picture

22-05-2004, 08:52

1) optional feature:

replace first command after "AB" to jump to a block of code, allocated in the end of megarom, and this code should check if hot key (let's say CTRL+B) is pressed, and if it is, then replace "AB" with 0x0000 and reboot MSX, if hot key is not pressed, just modify first instruction after "AB" to it's original value and jump to it, so the game plays as it's supposed.

The use for this feature is a quick SCC+ cartridge reset done in software. Right now I need to wait about 5 minutes before DRAM in SCC+ zeroes and I can boot.I think it can be done with ROM images that are smaller than the 64KB or 128KB available in the cartridge. In other cases it's not that easy as you can't know if there is some free space left in the ROM image where that code can be stored to add this feature. And I'm not into modifying ROM images just for that. Meanwhile, you can always use the patch feature to modify one of these bytes to prevent it from restaring after a reset. The /R option would reboot to DOS or BASIC though instead of starting the ROM image. I'll take it in consideration to add.

I know I can either take the cart out and put it back in or add a button to power off dram, but I don't like those hardware solutions, because they damage external look of cartridge SadSo you'll have to stick with this. What I do is switch off the computer, take out cartridge, switch on the computer, wait until it's booted, switch it off, insert the cartridge and switch it on again. For me it seems enough time has passed for the DRAM's to get at least the first 2 bytes differently.

2) support load from at least one of the popular MSX archive formats: pma/lha, arc or sl (whatever was this superfast MSX packager from Erog "SOLiD" Voznesensky). This way a user can put about twice as many games on a floppy!This might be an idea. It'll require just 1 file in the archive (matching the criteria, in most cases it'll be the extension of a file) and I do need sources for the extraction part as well as permission to add it to get the feature going and to release the source.

3) add visual mode. I.e. if I launch romload -v (or any other parameter you prefer), open a nice simple 40-character wide menu, which have simple disk browser and allows to choose the rom file, and after this choose settins to launch it.I actually have been thinking about this, but for version 2. I don't see it as a significant part of the program to implement it in a hurry.

4) create CRC database with known parameters, so users don't have to experiment to get a rom working, if they have a popular ROM image that is in databaseI have added a list with common ROM image file names with the options necessary to get it working in one go. It's called ROMLOAD.LST and should get most people started. It might be an idea to combine with the previous feature request.

By dhau

Paragon (1570)

dhau's picture

22-05-2004, 18:49

Hi BiFi, the tool is good as is Smile

1) You are right about patching as alternative to (1), but very few are capable of it Smile

If you implement it as optional, then folks can try this option, and if it corrupts the game, won't use it Wink

2) Well, then you can use gzip format, since it is GNU. But it could be tough to come up with fast unpack code Smile

3) sweet! I'll be waiting for 2.0!

4) CRC is more reliable then name of the rom. GoodMSX names are usually reliable, but they don't fit in 8+3 DOS format... But I understand your point Wink

PS: I think we should move this thread to "Software" -> "ROMLoad feature request" Smile

By BiFi

Enlighted (4348)

BiFi's picture

22-05-2004, 19:29

1) You are right about patching as alternative to (1), but very few are capable of it Smile

If you implement it as optional, then folks can try this option, and if it corrupts the game, won't use it WinkI'm sure there are people who can find out which block(s), address(es) and byte(s) need to be changed and these can be published.

2) Well, then you can use gzip format, since it is GNU. But it could be tough to come up with fast unpack code SmileThat tackles one format, now for the rest... unless all these formats are supported by it.

3) sweet! I'll be waiting for 2.0!That may take a while.

4) CRC is more reliable then name of the rom. GoodMSX names are usually reliable, but they don't fit in 8+3 DOS format... But I understand your point WinkThe filenames in that list are names from about 8 years back. I did add a list of konami titles with their RC number which is my way of identifying it.

Page 3/3
1 | 2 |