Accessing SD data on Megaflashrom SCC+ SD on 64kb MSX2+

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

By michellybells

Rookie (18)

michellybells's picture

12-07-2020, 15:34

Oh, I'll try all that! Wyrdwad and I both had been unable to find an answer to the cold boot issue, and all I could find online were some people suggesting that the FPGA was just too slow to start up before the MSX BIOS. This is the first I heard that updating the recovery menu to a newer version would help. Also, I downloaded all those files already, but before you, nobody seemed to document the commands to install them! So that's good, because I've been wanting to make sure this thing was all updated. I'll let you know if it helps any when I'm finished.

By michellybells

Rookie (18)

michellybells's picture

12-07-2020, 15:48

sdsnatcher73 wrote:

Might it also be the FAT in the SD card is somehow corrupt? And how big is the partition you are using? You could try with another SD card and create a 32MB partition using _FDISK from Nextor Basic (not entirely sure it will work as Nextor needs 128kB but maybe _FDISK works with 64kB). Then copy your files to the SD again.

I've used two different SD cards, one of which was the one that Wyrdwad gave me with the MRF, and the other my own, which I formatted with 16mb partitions using FDISK (which is apparently the most you can do with the MSX-DOS for 64kb.) And just to make sure it wasn't getting confused by multiple partitions, I formatted it all over again with only one 16mb partition. So it's definitely nothing to do with the SD card, especially since literally every other ROM works except for A Life M36, and I've even added newer copies of the ROM file from various websites.

By michellybells

Rookie (18)

michellybells's picture

12-07-2020, 16:32

OH FOR THE LOVE OF F--------

I found the problem, or at least a symptom of a larger problem maybe? When you suggested renaming the ROM file, I had the thought that MAYBE opfxsd doesn't like the fact that the filename has numbers in it (36), since that's literally the ONLY thing different between this ROM and all the others. Turns out I was right, renaming it without the "36" made it load just fine. I did some more tests, renaming a copy of Theseus to "THESEUS2.ROM" "THESEUS3.ROM" "THESEUS6.ROM" and "THESEU36.ROM" and what I discovered is that specifically the number "3" being anywhere in the filename makes opfxsd unable to read it. (For the record, this is opfxsd v1.19) Apparently my MFR has Triskaphobia...

You're right about one thing though, I noticed that this cart still has recovery v1.0 in it... I'm gonna get on to updating everything next.

By Grauw

Ascended (9181)

Grauw's picture

12-07-2020, 16:34

A-ha! This is a known bug in Nextor DOS1 mode, which will be fixed in the next Nextor 2.1.0-final release.

By michellybells

Rookie (18)

michellybells's picture

12-07-2020, 16:38

The bug documentation suggests that it's a problem with extensions only, but it would seem it applies to filenames as well. Still, this is good to know! I'm surprised nobody else thought of this a year ago when Wyrdwad was trying to figure it out. (Oh, I see it wasn't documented until just a couple months ago, that's why...)

By Grauw

Ascended (9181)

Grauw's picture

12-07-2020, 16:40

It’s a rather unexpected bug, I would never think characters 3 and 4 would have problems. It was reported just a few months ago, I was made aware by a GitHub notification a few days ago myself. Also, most of us run in DOS2 mode so I reckon that’s why it managed to stay undetected for so long.

By michellybells

Rookie (18)

michellybells's picture

12-07-2020, 17:15

You dadburnt young'ns with your newfangled 128 killabuilt MSX-DOS2doodle thingamaboopers! *shakes fist at cloud*

By konamiman

Paragon (1078)

konamiman's picture

12-07-2020, 17:56

I can tell you exactly what was the problem with those 3s and 4s. And it was a very silly one.

Initially the code for the DOS 1 kernel had a list of invalid characters for filenames like this:

defb '."/[]:+=;,'

The double quote here drove my IDE crazy, as it considered the entire file past that line an unterminated string and thus it displayed it with a single ugly color.

So I said, ok, let's replace that double quote with its ASCII code:

defb '.",34,"/[]:+=;,'

Can you spot it? I mistakenly used the double quote instead of the single quote for terminating and opening again the string, and the result was that ",34," ended up being part of the list of invalid filename characters. oO

By michellybells

Rookie (18)

michellybells's picture

14-07-2020, 03:13

Not only is that amazing (and potentially disastrous), but it’s also hilarious that it randomly affects this ONE game which just so happens to be called “A Life M36 Planet: Mother Brain Has Been Aliving” and like... what if it was “A Life M17” or “A Life M86” or “A Life M69” (lol)... but I guess there’s a two in ten chance, huh?

By Guillian

Prophet (3328)

Guillian's picture

14-07-2020, 12:11

Grauw wrote:

A-ha! This is a known bug in Nextor DOS1 mode, which will be fixed in the next Nextor 2.1.0-final release.

So that is why it was working here.
I use Nextor 2.1.0 Alpha 2. That is the version MegaFlashROM SCC+ SD cartridges have installed.
So probably Wyrdwad updated it and that caused the problem :P

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