I use C-BIOS as MSX 1 system rom and works great with the emulator.

Quote:

But AFAIK, fMSX normally runs w/ 128kb RAM and 128kb VRAM, so the (quicksaved) state could also be stored in the cache (Of course when no disk is inserted)

Just a small progress report on the new stuff...

I implemented state saving (but no loading yet, hehe). The state file seems to take just below 100kB for MSX1 and less than 280kB for MSX2(+). I'm thinking of adding an option for 256kB RAM for MSX2(+), this would then of course make the state file 128kB bigger.

Also, I implemented tape support with "autorun" possibilty, i.e. the emulator detects which type of file the first file on the tape image is and feeds the correct command automatically to the BASIC prompt to load&run it =) I will extend this to the disk side as well with a file selector when I have the time to implement it.

Anyways, I thank you all for your suggestions, they have all been taken into account! I will try hard to fix especially the disk access performance... mmm... sound... mmm...

Since I've seen so many people having problems with the system&game ROM/dsk install I've started to make a separate Windows GUI application to make it a bit easier... As the sources for gzip and makesis are publicly available there shouldn't be any too big obstacles in doing this but it will be on a lower priority than the emulator itself. Hmmm... I guess that means that someone else could do that as well

My to-do list is getting longer...

Quote:

Since I've seen so many people having problems with the system&game ROM/dsk install I've started to make a separate Windows GUI application to make it a bit easier... As the sources for gzip and makesis are publicly available there shouldn't be any too big obstacles in doing this but it will be on a lower priority than the emulator itself. Hmmm... I guess that means that someone else could do that as well

Before your to-do list starts to get even longer (and the sound gets delayed ), I could code that app. Would be glad to help
Only have to find Delphi 6 PE... must be here somewhere

It's a good idea that Saosuke could program the Windows programs to make the SIS package of roms, although the current tool set is very easy to use, if people read the documentation... I think that Jr should work in the emulator.

Just a little observation about the emulator. At the main menu, once you have selected a ROM image for the slot 1 or 2, you can't remove it for "none". You only can exchange the rom for another (I don't know if this happend to the disk menu as well). I guess that we should able to select "None" as cartridge to leave the slot empty, right?

Quote:

Just a little observation about the emulator. At the main menu, once you have selected a ROM image for the slot 1 or 2, you can't remove it for "none". You only can exchange the rom for another (I don't know if this happend to the disk menu as well). I guess that we should able to select "None" as cartridge to leave the slot empty, right?

This should be possible by pressing the clear key over the cartridge slot/disk drive -- it was still working last time I checked but perhaps I managed to break it just before making the install packet. I will double-check with my current version, I anyway refactored the whole menu system so it is more dynamic to add new stuff and also the code size reduced by a few kilobytes =)

Quote:

This should be possible by pressing the clear key over the cartridge slot/disk drive

Oh, yeah, It works. I didn't notice of that ^^U

Quote:

It's a good idea that Saosuke could program the Windows programs to make the SIS package of roms, although the current tool set is very easy to use, if people read the documentation...

You're right, although it's pretty easy to use, it is now (actually it should) even easier!
Yesterday in the evening, I started to code that promised gui and already completed a (small) part. Although some features are still missing, it's already capable to make a *functioning* package-file for the SIS-builder.
I've uploaded a prerelease for preview purposes
www.hl-soft.net/downloads/ROM_Packager_v1.00.rar

Done features:
* neat design
* create package-files
* shows total size needed on the phone

Upcoming features:
* auto-compress files to save space
* select multiple files in open-dialogues
* sorted file-lists (tho it wouldn't make a big difference )
* ability to load package-files
* automatically build sis-files
* readme file
* full source-code (released under GPL)
* complete package for building SIS-files (e.g. makesis is missing...)

Suggestions, comments and bug-reports are welcome
(sousuke@hl-soft.net)

[edit]
Nearly forgot to tell you guys how to use that app!
0. Extract the file somewhere on your HDD and start it.
1. Select all your systemROMs you want to have on the left panel
2. And the other panel gets all your gamefiles (ROMs/DSKs) phone
3. Save the list as a package-file in the fMSX/S60 ROMTool directory
4. Start makesis -v fmsx_roms.pkg
5. install the created SIS-file on your phone
6. Enjoy

As said before, these steps also won't be needed in future
[/edit]

one more thing.. we've been calling the emulator fMSX for Nokia Series 60 mobile phones since the beginning... maybe it's a good thing to make that name a bit smaller?

like...

fMSX-60
fMSX/Symbian
etc.

snout is just too lazy to type the big name all the time

true

but

"ROMPackager for fMSX for Nokia Series 60 mobile phones"

It's not the most catchy name in the world, rite?

Quote:

Suggestions, comments and bug-reports are welcome (sousuke@hl-soft.net)

Excellent! One suggestion: add somewhere the possibility to choose which version of the emulator you are building the package file for... or else you'll have to update it once for every emulator release.

BTW, it is also possible to make the SIS an independent packet - this would make it then also independent from the emulator version. The problem is that then you would need a separate ID for it, now the "patch" packet can use the emulator application's ID. One solution to that could be to use a random ID from the "development" ID range...

Quote:

"ROMPackager for fMSX for Nokia Series 60 mobile phones" It's not the most catchy name in the world, rite?

Well, it says "ROM Packager v1.00 for fMSX/S60" in the title bar...

Quote:

>"ROMPackager for fMSX for Nokia Series 60 mobile phones" It's not the most catchy name in the world, rite? <

Hey snout, thx for the newspost
(Wondering whether my nick is really that difficult to write )

Quote:

Excellent! One suggestion: add somewhere the possibility to choose which version of the emulator you are building the package file for... or else you'll have to update it once for every emulator release. BTW, it is also possible to make the SIS an independent packet - this would make it then also independent from the emulator version. The problem is that then you would need a separate ID for it, now the "patch" packet can use the emulator application's ID. One solution to that could be to use a random ID from the "development" ID range...

U're right, didn't think about that 'prob'.
I'll then make an option to set the emulator-version. Don't think that that will be too difficult for sum ppls out there

Quote:

(Wondering whether my nick is really that difficult to write

There was a little typo there

Quote:

There was a little typo there

It's ok, I'm used to it
Thx for the correction tho