forum.defence-force.org

There it is
Displaying "!" if a loaded block has parity errors

Currenly working at ISS idea.
Should work with 12 extra bytes only!

Yes, I'd say so. What I'd do is: -Correct the number of zeros in the header. -Correct the $22 instead of $4e error -Correct the loop so it does not produce extra DRQ (inside the loop it should be set DRQ, Pause, read data register, store, decrement counter) -Probably force a card update (flush) aft...

@Symoon give it a try, but no need for you to modify the disk image. Just check what happens to discard it is only a timing issue in my unit. Ok, it took a while to find back a machine that worked with the Cumulus but finally I could do the test (on an Oric-1!), and... After a few disk flashes, I g...

Symoon... you might have pinpointed the issue!!! Cool if it can lead to something! That's luck, I got the idea because I was fighting with my progress bar code and some similar issues (decrease first then stop and loop, or decrease after, and so on ;) ) I don't know if I would be able to do it toda...

Finally, after chasing the (hopefully) last bugs, there it is. Read the docs and have fun ;) Progress-v1.1.zip Feedback appreciated. For instance, do we really need the start/end boundaries? Their management takes about 12% of the code - nothing wrong with this version, but it could be saved for fur...

Forgive me in advance if the question is stupid, because I feel faaaaar away from what you're explaining here (never had a look at any code for Cumulus and my C language has become weak) while (cnt) { (...) wait_for_next_byte(); cnt --; (...) } The fact that the system waits for the next byte BEFORE...

Chema wrote: ↑Thu Aug 31, 2017 1:53 pmIf anybody can do a quick test with his Cumulus, just to discard it is my unit only (I played with the firmware in the past, who knows...), I'd appreciate it.

I'm travelling tomorrow and should be able to test tomorrow night or Sunday morning.

I second Chema on many missed opportunities that would have made life much easier on Oric ;) It would be handy to know how much is left to load - i.e a countdown rather than a count up. Or something like percentage shown. Would that sort of thing be possible or is there too little room? If you look ...

You can take any of the floppy images I posted and try yourself. If you see the flashing disk and the screen ends pitch black, it worked. If you see a red line at the bottom, it failed. Ah, thanks. I tried running a DSK file with Euphoric yesterday, saw the flashing loading disk but wasn't sure tha...

Very true about the Hires screen loading not really needing a progress bar. But you can: 1- load a Hires screen 2- then load a big program => for the 2nd program, the progress bar could be useful, and in Hires screen. :mrgreen: Anyway, I'm currently cleaning the source code and writing a doc before ...

Ouch, this Cumulus #00 bug is dirty :shock: I see no other difference than #22/#4E (and the two extra #22) with what would be a Sedoric disk structure. Here's how I see things: the problem can be in your test program (sorry ;) ), on FloppyBuilder with the identified #22/#4E difference giving unexpec...

Actually E122 seems to be the sector CRC; I don't know how to calculate it but this is my interpretation of what I see around offset #1060: in Cumulus DSK, there are 2 bytes at #22 and 6 bytes at #00 missing in the "gaps" between sectors, so the sector datas begins 8 bytes earlier and end ...

I second Dbug in trying to fix things one by one. 1st difference we noticed, let's try to check if it changes anything. I tried to look anyway at the DSK files, as you explained the interleaves are very different one from the other, with a different amount of #22, a different amound of #00. But I al...

Interesting idea. It doesn't say Searching or Loading on the status bar so why not put the display up there out of the way of the main screen ? It doesn't here because it's a HIRES screen loading ;) Searching and Loading are still there in TEXT mode. I first planned having the progress bar up there...