DjayBee

Scan of German manual: DiskMaster-DE.pdf OCR of German manual: DiskMaster-DE.txt English DeepL translation (mostly unedited): DiskMaster-EN.txt

Does this mean that any software using this RAM area will play havoc with the write protection and (however this happens) the overflow flag of the CPU? I am asking because @ijor stated that DiskMaster needs the whole 8 KB of RAM to operate. If my fear is justified, DiskMaster cannot be used together with the Option Board.

Altirra (the Swiss Army Knife of everything Atari emulation-wise). Use its Disk Explorer.

Now I'm confused (or don't know it correctly). I thought there was only an APX release. I rephrase: The XEX is identical to the AUTORUN in Atariwiki's ATR image. Meanwhile I am also a bit farther in analyzing the CAR: It seems to be identical to the XEX except: "Transposed" from $3C00 to $A000. Different title text on screen. (The implementation is weird.) The first two screen rows are contained in the code in obfuscated form but the disk version skips the title row and replaces it with plain text taken from a binary load segment which is attached at the beginning of the file. If you replace starting at offset $180 in the XEX with this code, you will receive the same text as in the CAR (see attached XEX): XEX : 82 20 E4 3F 20 B9 45 Patch: 58 A0 3B EA 20 53 3B The CAR does some calculations around MEMTOP. I only did a binary diff and did not disassemble the files completely. Besides the above differences there are only single-bytes differing - just like it is expected when program code has been moved from $wx00 to $yz00. This is the reason for my assumption that there were no other changes made. Calculator-reverted.xex

What is CALCULATOR.XEX in your ZIP archive? It differs completely from CALCULATOR.CAR. Found it out myself: The AUTORUN.SYS from the APX release.

The difference between 2.0S and 2.0D are only a few bytes.

This is definitely true for Atari's release but the MMG release contains a configuration program which IIRC allows to select the density per drive. I have not tried the program, which is why I am not sure. If somebody wants to check it: https://archive.org/details/cssa8d_MMG_Basic_Compiler_v2_0_1984_MMG_Micro_Software_US

Just disable the screensaver and go ahead.

MMG BASIC compiler v2.0 had it on its side B as @bf2k+ remembers correctly.

You are confusing cause and effect. Fluxdumping shows the defects caused by sectors that became corrupt over the course of time. That this happens more often on the inner tracks of a disk because of their higher write density is only logical. But in general we can only dump as good as the original disks are aged. You will also find many images in the A8SP distribution that have corrupt sectors on the inner tracks; simply because there is no better alternative dump. But these are only images that work, which means that the corrupt sectors are not used by the program. We also try to repair broken sectors where possible, if we have an alternative dump at all.

The above image was generated from Yellowman's dump. These ones are generated from dumps contained in the current A8SP torrent: This version should work on Happy enhanced 1050s (only): DiskMaster v1.0 [cr test1].atr An alternate v1.3 (only for Speedies): DiskMaster v1.3 [alt version][cr test4].atr Now we only need somebody who tests if they really work.

He unfortunately died in 2011.

Slightly off-topic: Could somebody with a Speedy please check if this image works? DiskMaster v1.3 [cr test1].atr DiskMaster v1.3 [cr test3].atr

Did you choose the correct screen driver? Each screen type needs the matching firmware. Otherwise you will not see anything on the display.

Perhaps your HP is interpolating pixels instead of keeping them edged. My setting is (instead of "Fit to Window": "Filter Mode" might also have an influence.

Thanks but are these your not-yet-working settings for ED and DD? I was interested in your seemingly working settings for SD disks.

Please post your configuration and program parameters. We were not yet able to write anything successful back to real disks using the Greaseweazle.

Did you find a method to distinguish a stock 810 from a stock 1050 except different status codes for some of the bad sectors?

/me has a Déjà-vu.

A design must not necessarily have been registered for the time to start running. It only must have been "disclosed" to the public before - which is a fact for nearly 40 years now.

What do you need it for?

Yes and no. The unchanged filename was a mistake I corrected now but I won't change the program display besides 1.0E vs. 1.0e because there is no space to add something and I do not deliberately remove copyrights etc.

A guy named David Wragg commented on Twitter that a registered design has to be NEW (similar to a patent) and gives links to the EUIPO. If a design has been disclosed before, in may not be registered anymore. If it has been registered (as in this case), it can be challenged and the registration will probably be withdrawn. Since the Atari desings date back to the 1980s, earlier disclosure can easily be proven and RGL is acting on very thin ice. Let's community-fund the challenge and send RGL to where they belong. Using the name ATARI is certainly a different matter. Even when RGL did not show any proof that they have a valid agreement with Atari, Atari themselves hold the rights on the name.

In case someone uses AMAC with SpartaDos, I applied @drac030's patch to 1.0E and changed the on-screen version to 1.0e (lower case e). AMAC-10e-Drac030patch.xex I cannot test myself, therefore please report back.

Particularly with the registered design showing only STs and something which is not really discernible but resembles a home A/V component.