Recent content by xhul

Hello there =] On your side, does 0.381 work once you "enabled" the read|write using 0.127d? I mean, by loading 0.381 boot.bin, from 0.127d. Cause it definitely should. Speaking of multiple backups, unfortunately, despite the current version supports any file name for restoring, it only...

That's actually the tool i intended to use for you. Glad you managed to do everything by yourself =]

In the mean time, i took a look at the Mednafen save system, and i think i found why SDL doesn't digest the saves right away. Additionally, i found a way to make them compatible. So, if you manage to upload the data somewhere, be sure to include all the .bkr files located inside the "sav"...

I check this thread daily, but i only log in when i have to reply something, so a post would offer better visibility as far as i'm concerned. But if for some reason you want some privacy regarding the data, a PM would be more appropriate. You call =]

Murzik seems to be a little busy, but maybe we can help. It's likely that the Mednafen save format isn't the same as the one used by the SDLoader software, which is why it fails to restore the saves on real hardware. If you provide your Mednafen save file, i can investigate, and maybe do the...

For the record, i tried removing the module when at the main menu, and putting it back. When i do that, i have to reinitialise the card again, which pretty much confirms that it's indeed SPI mode related, at least for versions 0.1XX. Deactivating SPI mode that way should allow me to try test...

I'm just back from having tested the 40 versions i found in this forum, thanks to The Rockin'-B for having spared my CDs. In a nutshell: VERSIONS 0.1XX All those basically follow what i had already discovered about 0.1. "SD card init error" is always displayed on the first read|write attempt...

On emulator at least, the Atlas IP.BIN + 0.381 SDLOADER.BIN combo worked like a charm! That means i can pretty much test a maximum of 50 different versions on a single CD now. I'll start by building 1 entry per version, but yeah, additional test versions are of course welcome if you have the...

I see, thanks for the clarification. So far i've tested with the 0.BIN only, but i'm surprised it didn't work, since the IP.BIN i extracted from the ISO should point to 0x06010000, right? Atlas uses IP.BIN files for that reason, to ensure the 0.BIN gets loaded at the right location. I'll see if...

In case we never solve the issue, i found a new trick =] I believe it's the most convenient way to make 0.381 work on machines that aren't compatible with it natively. You basically use 0.1 to enable the proper communication with the TF card, and then boot 0.381 from it. You just need 1 CD, and...

Cool, thanks again for your time. Regarding the potential hardware part of the problem, we already have obvious differences between a concerned VA9-PAL unit and a non-concerned one. When it comes to VA5-PAL units, i asked my contact to provide some photos of his, since it's the only...

A VA5 made in indonesia then, thanks. Same as my two VA5 actually, which are both concerned by the problem. What's the original region though (EU|USA|JPN)?

Don't open the machine, just let us know the first 4 characters of the serial number (sticker at the back). Also, i wanna point that PAL-VA5 motherboards might vary as well, considering one of my contact has one that shows no problems with the SDL software.

Nice, i was starting to think i'm the only cursed user. We'll get to the bottom of this. ####### Just back from another testing session, and i think i made an interesting discovery. But hold on to your butts, cause that's some crazy testing wizardry. On 0.1, the first attempt, despite it...

After having been pretty busy, i went back to the testing. This time, i tried the 0.1 CD version, and the results were a bit unexpected. The good news is that i finally managed to save|restore the save RAM. So at least, it's safe to say that the hardware itself (both module and TF card i used)...