Spectrum Computing

This is way off topic, but does bobs browser work on a standard divide like the 57c I have? I've got it in my head that it doesn't. I don't own a divIDE but I have had reports and seen YouTube videos of people using my browser with it. After copying over the modified BIN and SYS files from the brow...

Today I did a more comprehensive test of my ZX-Uno sd card with the latest LFN 25-3. I ruled out the possibility, that cluster size was an important factor, after testing two different 16Gb SD cards, with 4096 and 8192 values. In both cases, LFN worked well, with the minimum required files to work ...

Pegaz wrote: ↑Wed Sep 20, 2023 1:19 pm Thanks Bob, I sent you the image link in a PM.

I don't appear to have a PM off you. My mailbox isn't full so I'm not sure what is going on.

Luzie wrote: ↑Tue Sep 19, 2023 6:03 pm Have you tried this:

It's probably not device number related as the browser won't start at all if that is not correct.

Maybe it's the cause of the problem, because I'm not using the whole 16Gb sd card, just a first 5 Gb FAT32 partition on it, for easier backup. The rest is unallocated space. No, it's probably a bug in the C code I rewrote in assembly. If you can zip up the disk image and make it available for downl...

"Auto detect" is the best option as it uses information from the esxDOS file system to get the correct device number. The other system where you manually set the device number is left behind code from the old version for people who have set up multiple partition devices before v0.16. I sho...

Apologies, could not find the answer (did I miss it?), so I would like to clarify one thing about devices, partitions and "Auto detect device" control. It looks like "Auto detect device" must be "ON" if esxDOS is not on the first partition on the SD card. Is that expec...

I tested it on the Omni and the eLeMeNt as usual and this version works fine on both machines. Many thanks for your work @bob_fossil . This version seems to be slightly faster or more snappy. But maybe this is just in my mind. The last bit of FAT code was the one that was doing the bulk of the work...

I've updated the code in the previous link, so please re-download it. After releasing it yesterday I found two issues with the new FAT code which should now be fixed. I also managed to get the TAP plugin to support the new realtime tape loading mode for ZX-UNOs. For the moment, to enable it you need...

New test version available here . Final bit of size reduction in the FAT handling code as it's now all written in assembly. Seems to work on my FAT32 setup under emulation in Fuse and in FAT16 on my +2 - but there may be issues. Typically this would manifest itself as corrupted or empty directory li...

I do not understand what is the point of loading a tape image file at normal speed off a memory card-based interface :? Neither can I. :) If you want to load a .tap at normal speed you can convert it to a .pzx file and load it that way. The supplied source code for the PZX plugin could be taken as ...

And now I tested it on the eLeMeNt, no problems either. Thanks for the update @bob_fossil . Overwriting a SNA is a nice feature that comes in handy when using SNA as savestates. Just curious, would it be possible to save in Z80 instead of SNA as this format is more compatible. It's possible but it'...

New test version available here.

More size reduction as I've completed the refactoring of the FAT initialisation code to assembly (just one C function left to refactor in the FAT code now).
You can now overwrite an existing filename when you save a snapshot from the browser.

I've updated the zip file linked in my previous post so it now contains a .dsk file. Seems to run from Loader under +3 emulation in Fuse. Not sure if this is what you need but at least I now know how to do disk releases for the +3.

Here's my patch with the +2 trainer options from the original mod preserved:

http://www.thefossilrecord.co.uk/wp-con ... x/fsay.zip

Did the previous .sna file fix the screen corruption for you? I've put an updated file at: http://www.thefossilrecord.co.uk/wp-content/uploads/zx/fs8.zip The Game Over crash was due to an off by one error in one of my patches. Assuming you've got the contents of bank 1 into bank 4, the following pok...

The following patched .sna file seems to fix the screen glitching on my +2. http://www.thefossilrecord.co.uk/wp-content/uploads/zx/fs5.zip Long story short, I moved the music to another memory bank and then patched the code at $a9a9 (and a couple of other places) to page bank 20 in, instead of bank ...

Some initial findings: The game uses IM2 and the IM2 table jumps to address $fdfd. In game this jumps to $a0c4 but in the title and high score it jumps to $a0b0 which is why you don't get the screen corruption there is it's executing different code on interrupt. The interrupt function at $a0c4 is al...

Hi @bob_fossil, thank you for the suggestion :) It seems that on later levels that address for the IM2 table is too low, with obstacles appearing out of nowhere in the lowest lanes and other glitches, so I moved it to 57856 and so far it seems safe enough to hold it there. Good work! As I said, I h...

For your MC128.szx, try poking: POKE 25541,195 POKE 25547,195 and then press SPACE to start the game. This will move the IM2 table from $6000 to $C300 and change I from $60 to $C3. Hopefully the run of zeroes at this address that gets overwritten with the IM2 table aren't crucial for the game. I've ...

I think the issue is that the interrupt table is in contended memory. In game, the I register is $60, which means the IM2 table is at $6060 - 24672. I think it needs to be moved so it's above 32768 to avoid the snow effect. So you'd need to find another 257 bytes of free memory above address 32768 o...

The loaders are all basic. Theoretically the skeleton ROM could just have picked out the LOAD and USR tokens and continued from there. The loaders may be BASIC but the commercial protection systems and custom loading schemes did some odd things with BASIC. Some loaders like the Lenslok on the origi...

@bob_fossil I discovered the same as @Chris23235 with v0.25a1 under SpecEmu https://spectrumcomputing.co.uk/forums/viewtopic.php?p=118894#p118894 : https://i.postimg.cc/wMPn4hmp/Spec-Emu-v3-4-2023-06-09-Spec-Emu-v3-3-2023-06-09.jpg Reverting to v0.24 Final cures it: https://i.postimg.cc/90gz8FV9/Sp...

Dear Bob, certainly a very good idea to display registers and have a possibility of changing them. But it does not enable the user to trace the program. Practically any monitor of your like will do. I personally like Devastace+ since it is easy to use and takes up screen memory only. https://spectr...

Dear Bob, your work is really perfect. Maybe the only thing I am missing is some debugger in your nmi menu. A debugger that would show registers, Interrupt mode and DI/EI state in th emoment the nmi button was pressed. This would help debugging programs on real HW a great deal. Years ago I applied ...