MegaFlashRomSCC+SD Mapper emulation bug?

Page 2/6
1 | | 3 | 4 | 5 | 6

By giuseve

Paladin (729)

giuseve's picture

06-03-2016, 22:47

Well,
I'm trying with this fantastic machine on BLUEMSX

[CMOS]
Enable CMOS=1
Battery Backed=1
[FDC]
Count=2
[CPU]
Z80 Frequency=3579545Hz
R800 Frequency=7159090Hz
[Board]
type=MSX-T9769C
[Video]
version=V9958
vram size=128kB
[Subslotted Slots]
slot 0=1
slot 1=0
slot 2=1
slot 3=1
[External Slots]
slot A=1 0
slot B=2 0
[Slots]
0 0 0 0 24 "Machines/MSXturboR - European SunNextor/KANJI.rom" ""
0 0 0 0 58 "" ""
0 0 0 0 33 "" ""
0 0 0 0 59 "" ""
0 0 0 0 60 "" ""
0 0 0 0 80 "" ""
0 0 0 0 84 "" ""
0 0 0 0 90 "" ""
0 0 0 0 79 "Machines/MSXturboR - European SunNextor/MOONSOUND.rom" ""
0 0 0 0 88 "" ""
0 0 0 4 141 "Machines/MSXturboR - European SunNextor/MSXTRE.ROM" ""
0 1 0 8 96 "Machines/MSXturboR - European SunNextor/NextorSunrise.rom" ""
0 2 2 2 78 "Machines/MSXturboR - European SunNextor/MSXTRMUS.ROM" ""
0 3 2 2 42 "Machines/MSXturboR - European SunNextor/MSXTROPT.ROM" ""
2 2 2 2 43 "" ""
3 0 0 512 22 "" ""
3 1 0 2 141 "Machines/MSXturboR - European SunNextor/MSXTREXTE.ROM" ""
3 1 2 1 141 "Machines/MSXturboR - European SunNextor/MSXKANJIE.rom" ""
3 2 2 4 143 "Machines/MSXturboR - European SunNextor/MSXDOS23.ROM" ""
3 3 2 2 42 "Machines/MSXturboR - European SunNextor/XBASIC2.rom" ""

But BLUEMSX HANGS UP when I try to insert these 2 disks on IDE

Sunrise_Prim_200mb.dsk
Sunrise_Sec_2000mb.dsk

Is it possible to modify the OpenMSX machine called
Boosted_MSXturboR_with_IDE.xml
to contain the same spec of the BLUEMSX machine above?

REgards !

By Manuel

Ascended (14552)

Manuel's picture

06-03-2016, 22:59

giuseve wrote:

I used your suggestion. Now i got your same results...
.. msx boots and shows the info about 2 HCSD cards...
.. then. it shows MSX-DOS 1.8 (???) and hangs up !

What did you put on the SD image?
What ROMdisk did you flash?

About that blueMSX machine: I don't know, if you put it in words, I can probably help you to modify the openMSX machine. Or you put in words what you want to change about the openMSX machine's config.

By giuseve

Paladin (729)

giuseve's picture

07-03-2016, 00:34

No SD Image at the moment (I didn't find a good software that creates FAT16 Images in .DSK format)
I'm using a .dsk of 200Mb that works on a SUNRISE IDE patched with Nextor that cointains NEXTOR DOS.
I installed the latest build 177 64bit of OPENMSX. It says that on my drive I got DOS 1.08 !!!!
I flashed the files available on MSXCARTDIGESHOP website but no ROMDISK (I don't like it)

This is the last machine that WORKS on BlueMSX. I'm using it to have MEGAFLASHROMSCC support (no SD) and the IDE modified rom (called NexSun.rom) with Nextor on it to support fat16 partitions. My disks works and size and DOS versions are recognized correctly.

[CMOS]
Enable CMOS=1
Battery Backed=1
[AUDIO]
PSG Stereo=0
[FDC]
Count=1
[CPU]
Z80 Frequency=3579545Hz
R800 Frequency=7159090Hz
[Board]
type=MSX-T9769C
[Video]
version=V9958
vram size=128kB
[Subslotted Slots]
slot 0=1
slot 1=0
slot 2=0
slot 3=1
[External Slots]
slot A=1 0
slot B=2 0
[Slots]
0 0 0 0 84 "" ""
0 0 0 0 58 "" ""
0 0 0 0 33 "" ""
0 0 0 0 59 "" ""
0 0 0 0 60 "" ""
0 0 0 0 90 "" ""
0 0 0 0 88 "" ""
0 0 0 0 26 "" ""
0 0 0 0 24 "Machines/MSXturboR - FS-A1GT SUN/a1gtkfn.rom" ""
0 0 0 4 141 "Machines/MSXturboR - FS-A1GT SUN/a1gtbios.rom" ""
0 1 0 8 96 "Machines/MSXturboR - FS-A1GT SUN/NexSun.rom" ""
0 2 2 2 78 "Machines/MSXturboR - FS-A1GT SUN/a1gtmus.rom" ""
0 3 2 4 20 "Machines/MSXturboR - FS-A1GT SUN/a1gtopt.rom" ""
3 0 0 128 22 "" ""
3 1 0 2 141 "Machines/MSXturboR - FS-A1GT SUN/a1gtext.rom" ""
3 1 2 4 141 "Machines/MSXturboR - FS-A1GT SUN/a1gtkdr.rom" ""
3 2 2 4 143 "Machines/MSXturboR - FS-A1GT SUN/a1gtdos.rom" ""
3 3 0 8 68 "Machines/MSXturboR - FS-A1GT SUN/a1gtfirm.rom" ""

It's a 1 Mb European TurboR where the modified version of SUNRISE IDE ROM is called NexSun.ROM of 128Kb. Thanks to its Nextor support I'm able to use my 2 fat16 .DSK images.
It works, with only this 3 issue
- no comandline support to mount the HDD image. The command line of bluemsx maybe look for IDE
- BlueMSX launcher works only if I set up NexSun.ROM as a 2nd controller, with the results that my 2 HDD become drive C and D (because A and B is for SunriseIDE)
- everytime I use BlueMSX from gui I have to select both .dsk images manually

About OPENMSX
- Is it possible to have something like this on OPENMSX (a Nextor Patched SunriseIde version to use MEGAFLASHROMSCC & SUNRISEIDE NEXTOR PATCHED?). Sorry but at the moment OpenMSX dosen't load my .DSk as SD neither modifying the .XML file
- Or better, considering the support of OpenMSX to MFRSCCSD: is it possible to use these 2 .dsk on MFRSCCSD512K as SD card (IT WOULD NOT REQUIRE A NEXTOR-PATCHED-IDE ANYMORE)

Sunrise_Prim_200mb.dsk
Sunrise_Sec_2000mb.dsk

Bye !

By Manuel

Ascended (14552)

Manuel's picture

07-03-2016, 10:10

I don't think you can just mix Sunrise IDE images with MegaFlashROM SCC+ SD SD-card images. It seems that is what you are trying to do... THe reason is that the ROM software of both devices use a slightly different partition format.

By Wild_Penguin

Champion (461)

Wild_Penguin's picture

07-03-2016, 15:26

Manuel wrote:

I don't think you can just mix Sunrise IDE images with MegaFlashROM SCC+ SD SD-card images. It seems that is what you are trying to do... THe reason is that the ROM software of both devices use a slightly different partition format.

This may be the problem I had with the one partition on my OpenMSX emulated MegaFlashROMSCC+SD... giuseves problem sound similar, but I was not sure from the description, if it is the same issue or not.

Giuseve: If you haven't yet, I'd try the following workflow in OpenMSX (this is what I did - it's a kind of step-by-step troubleshooting process - if a step fails, you know you can not continue, but make the current step working):

1) Flash the ROMDisk just for testing. This is because that way you can be sure the MFRSCC+SD Kernel is working correctly. Just remove it afterwards, once you got your sdcard image(s) working. You can also try to run "call fdisk" - if that fails, SD Kernel was not flashed properly. (But you may need the ROMdisk in any case, see part 2.1 below).

2) I noticed that at least on my system, OpenMSX creates SD images for the MFRSCC+SD, if none were given to it (I use catapult, I'm not sure if it gives some command line parameters to openMSX or if these default image locations are hardcoded in hardwareconfig.xml). In any case, I'd try to format these blank images first, before using your own (that's what I did) - that is, run "call fdisk", and make some partitions. (On Linux the images are in ~/.openMSX/persistent/MegaFlashRom_SCC+_SD/untitled1, on Windows probably somewhere in the users directory, but I don't know about modern Windowses).

2.1) I noticed a minor bug (in MFRSCC+SD Kernel?) - I was not able to partition the µSDcards without a ROMdisk; if I did not have flashed a ROMDisk, and two blank µSDcard images, fdisk will hang when I choose the MFRSCC+SD device. However, if there either a) is a ROMDisk or b) no ROMdisk but already partitioned µSDcard(s), it will not hang. This is something that is good to know if you take this approach (and perhaps report to Guillian - I can reproduce this on OpenMSX repeatedly).

If you can not get the above two steps working, then there is probably no way to get your real µSDcard images working, either.

After I got the blank images partitioned and working above, I just copyed my µSDcard image over the one created automatically (Only then I proceeded to remove the ROMDisk via recovery). I guess I could use the HD image selector, too.

By giuseve

Paladin (729)

giuseve's picture

07-03-2016, 21:27

Thanks.
Now I'm going a little bit more...
Few questions...
1) where damn .. are the automatically generated sd cards?
2) why it cannot be possible to change the default size of the SD cards? I tried modifying the .XML file, but after all the operations CALL FDISK says that the 1st is always FAT12 8Mb and the second is FAT 16 amd 200Mb. I'd like to have only one SD FAT16 4 gbyte. How to do this?
3) after all I would mount my 4gb partitions as IDE and then I would make a copy of the files from it to the 4Gb SD

By Manuel

Ascended (14552)

Manuel's picture

07-03-2016, 23:49

1) I think I gave you this hint before: start up and type in the console hda and it will show you the path. hdb for the 2nd slot.
2) the only way is to change the XML file as you did. But it is only used when no sd card image is present. Then it is auto-created with the size you specify there. The size is in MegaBytes. (So, use 4096 for 4 GB.)
3) Yes, that works, I did it too to populate my SD card image when testing the emulation.

By giuseve

Paladin (729)

giuseve's picture

08-03-2016, 18:27

@manuel
1) done (uhm, what a strange path. No problem. i erase the 2 files. I modifued the .XML file with 4096. I try to boot again the MSX trying to enter the recovery mode... ant CATAPULT SAYS

Couldn't create HD image: Files >= 2GB are not supported on 32-bit platforms: C:/Users/SeVe/Documents/openMSX/persistent/MegaFlashROM_SCC+_SD/untitled1/SDcard1.sdc
Uncaught exception: Files >= 2GB are not supported on 32-bit platforms: C:/Users/SeVe/Documents/openMSX/persistent/MegaFlashROM_SCC+_SD/untitled1/SDcard1.sdc

But I got the 64bit version of OPENMSX build 177.

By Wild_Penguin

Champion (461)

Wild_Penguin's picture

08-03-2016, 19:31

giuseve wrote:

@manuel
1) done (uhm, what a strange path. No problem. i erase the 2 files. I modifued the .XML file with 4096. I try to boot again the MSX trying to enter the recovery mode... ant CATAPULT SAYS

Couldn't create HD image: Files >= 2GB are not supported on 32-bit platforms: C:/Users/SeVe/Documents/openMSX/persistent/MegaFlashROM_SCC+_SD/untitled1/SDcard1.sdc
Uncaught exception: Files >= 2GB are not supported on 32-bit platforms: C:/Users/SeVe/Documents/openMSX/persistent/MegaFlashROM_SCC+_SD/untitled1/SDcard1.sdc

But I got the 64bit version of OPENMSX build 177.

I think the 2GB limit is referring to your OS and / or filesystem capabilities? What OS (which Windows, 32 or 64bit?) are you on, and what filesystem is the C: drive?

EDIT: Unless you are using something ancient, I think it is unlikely this is your host OS / FS limitation. It could be an OpenMSX bug after all - maybe it is enforcing some limitation by mistake when making an image? Let's see what manuel says on this. On the other hand - do you really need 4GB image? How much of MSX files do you need to put on your MSX Smile

As for the <size> parameter in MegaFlashRom_SCC+_SD.xml - I didn't even notice it before! I just copied my images over the ones created by openMSX and it worked oO . I'm not sure if that is by design, or an unintentional fluke Wink . It seems the code will use whatever file if present, and ignore <size>XXX</size> (and use it only for creating new). It may or may not work in your case (it could be OpenMSX build specific).

P.s. Hey, I finally got "<" -marks to work on this forum - one needs to use HTML special character tags such as &#60 - now I know how to filter hardwareconfig.xmls trough sed while posting to this forum Wink

By Manuel

Ascended (14552)

Manuel's picture

08-03-2016, 19:33

That size parameter only determines the size of the auto-generated default HD image. It has no other meaning. See my previous post.

I'll check on the error you got... but it seems like it's a Windows specific bug of some kind.

Page 2/6
1 | | 3 | 4 | 5 | 6
My MSX profile