SainT

It should make no difference.

It seems pretty consistent if people reformat and copy the JCD files back onto the memory card it fixes a lot of problems. I don't think the files are getting corrupted as such, as I'm pretty sure I have heard people have done a file comparison between the files on the memory card and on their hard drive and they are the same. My current theory, which has been backed up by someone with first hand experience of this, is that while the file is not fragmented at a file system (FAT32) level, it becomes fragmented at a lower level (how the memory card maps sectors to its own storage cells, a process called wear leveling) and is causing some additional latency while reading. And this doesn't just happen when you write to a memory card, apparently the card will rearrange itself when you are just reading. The microcontroller on the JagGD isn't quite powerful enough to handle everything that's required for CD support well, so it's all very much on a knife edge as to whether it works or not, and this additional layer of uncertainty in the memory card is causing issues. I've got a few more things I can look into which may help, but it's getting close to being about as good as it can be.

Try reformatting the memory card and copying the jcd across again. I had the same issue and this fixed it. I have some theories as to why this happens, but currently nothing I can do about it. I should also say that if you’re running PAL, the intro resetting is normal, this happens in the actual CD unit. It should play fine, though, I’ve played it quite a lot.

The autobooting stuff is already present via autoexec.inf. You can add an image to display as well as a ROM to load. Example autoexec.inf: ROM=mygame.rom E2P=mygame.e2p E2S=2 Where E2S is 0:128,1:512,2:2048. It will display an image called title.pal or title.ntsc (depending on console region) which is in the root. The image should be 162 (NTSC) or 188 (PAL) pixels high and 256 pixels wide as 16bpp rgb. I have now added in the ability to hold down 0-9 and it will load /autoboot.[0-9] should you have some favorites.

Working for me. 🤷‍♂️

Just hang on until the next firmware update for Yopaz. It's broken currently.

I've fixed some issues with the CCD files, so the converter now works better with these files. Update in the usual place. https://www.retrohq.co.uk/products/atari-jaguar-gd-flash-cartridge

It's things like this I don't have a very good explanation for! Battlemorph seems to hang as it misses an interrupt saying data is ready for it. The very slight difference in timing between file location on the memory card is the only thing I can think somehow helps it work. Seriously frustrating.

Yeah, it is very broken, but I think I've done what the memory track bios must do and have it working now. Basically, if I get a name passed to me which is complete rubbish, I replace it with "NONAME". That way when it tries to open multiple files with different gibberish, it gets the same file. Which is what it's after.

Erm, after looking at what Yopaz is doing in terms of filenames being passed, etc, it looks to be complete gibberish data. I have no idea how this is working on a physical Memory Track, if it does, but it looks very broken.

Oddly, no problems for me. If I play for a bit and save, I get exactly the same file as you, no progress saved? If I reload and go back I have to start from level 1 again. So I'm not entirely sure how saving is supposed to work or what it saves...

No, works fine here.

Keep trying, sometimes it takes 5 or 10 attempts to load those two games. I know what the problem is, but not why it’s happening or how to fix it as yet.

That’s just one file, can you zip up the yopaz folder? The naming of files is down to the game, there are no types or extensions, it’s just however the game names it. Edit: Ah, sorry, there’s just the one file. I’ll try copy that across and see what happens…

So it’s either the save game is corrupt, or it’s doing something in the memory track bios which is hanging. If you send me over the yopaz directory I can see what’s what.

It’s in the root, and it’s hidden. So you’ll need to have view hidden files enabled.

Interesting, sounds like the save may be corrupted? Or it might be I’m not doing something right. There is a hidden folder on the memory card called MTRACK, in there each game has its own folder. Try deleting (or renaming) the folder with the name of the game on the memory card from a PC. You could also make a backup of the folder and send to me to see if I can replicate the problem on my system.

Just tried this again, working fine here. 🤷‍♂️

Updated ISO converted uploaded. I've tested with everything I have and it's working fine. There are quite a few ISO's I have with missing data markers, but it's usually the end markers which are missing, so these images should mostly work, but they will be missing some data. So things crashing can also be missing data as well, so something to consider with bad rips. Available linked at the bottom of this page: https://www.retrohq.co.uk/products/atari-jaguar-gd-flash-cartridge The main improvements in the newer converter are support for more tracks (Brett Hull) and support for multi-bin CUE files. Until proven otherwise the problems with QR reading above I can only attribute to crappy QR reading apps which are inserting adverts. It is absolutely, 100% completely, impossible for the JagGD to generate random links to other sites.

Please give me examples of this including a photo of the screen showing the QR code and link.

The only thing I can think is that it's a QR code reader inserting adverts, it's absolutely impossible for the QR code generation to randomly send you to other sites.

Not yet, no. There are a couple of improvements for CUE/BIN format and allowing for more tracks on the CD image (Brett Hull Hockey).

If there are missing markers then it is likely to be an incomplete CD read. All Atari released titles use a standard "ATRI" marker. If it's an unreleased title or homebrew then it may use different markers and the issue may infact be my fault, but I don't have any such examples. If an image is failing to do anything after opening, it will be unrecognised for some reason. Any specific examples of this I can take a look at, it may be I don't support the format version.

Oh... now that's interesting. I've tested the QR generation and it's always been correct in my tests, I guess the QR code could be wrong in some cases, then. 😬 Does it go to a 404 page when you scan it? If you happen to be able to provide an example of where the QR and URL displayed do not match, that would be really helpful. The QR is just generated from the URL displayed on screen. Thanks for the heads up, I've not heard of this issue before.

I’ve had the same issue with JCD’s failing. I can only assume the memory card can get corrupted, as I had Dragons Lair start failing on me, so I formatted the memory card and copied the JCD’s across again and it worked fine.