ZX in the world - A number of programs (for example ALASM 4.1 (and 3.8), REAL COMMANDER 1.4, PC-866 and BE_VIEW views, the new EMS terminal and many others) cannot work normally with TR-DOS 5.03...

╔════════════════════════ ═══════════════════ ═══════════════════╗
║  ZX in the world  ║
╙─────────────────────────────── ───────────────────────────────╜
(C) EVP-SOFT

A whole range of programs (for example ALASM 4.1 (and 3.8), REAL COMMAN-
DER 1.4, viewers PC-866 and BE_VIEW, new terminal EMS and many
others) cannot work normally with TR-DOS 5.03.

 The glitch is the same everywhere - when changing the current drive it seems
everything is OK, the directory is read normally, but the files are not readable
(immediately an error message on the disk) and of course, it won’t start
repent. And if TR-DOS 5.04S or 5.04T, then everything is OK.

 I started researching this glitch with ALASMa. By downloading it from the dis-
Drive A, I selected B in it and entered the debugger. In system re-
The following were the TR-DOS variables: #SCC8 - #83, #SCC9 - #80.And these
variables determine the mode of operation of the drive with a specific disk-that, and the purpose of their bits is:
 D7 - drive type: 40(0)/80(1);
 D1 - number of sides of a disk or drive: one (0)/two (1);
 D0 - if (0) then use 80-dor. like 40-dor.,
and hence the diagnosis - when selecting drive B, it was installed as
80-track, but at the same time one-sided and also forced
thoroughly switched to 40-track emulation mode.

 And the reason for this glitch is simply that the authors above
numerical programs do not know that the System Function Interpreter
TR-DOS has a command called "Setting on disk-
that", code #18.

 Well, TR-DOS 5.04S (a turbo format also appeared in 5.04T)
differs from 5.03 only in that it is the default, i.e. before setup
to a floppy disk, this TR-DOS writes to addresses #SCC8...#SCCB
#80 (as in 5.03), and immediately #83.

 In the case of ALASMom, everything is very simple:
... LET d=VAL"131":POKE VAL"23752",d:POKE VAL"23753",d:
    POKE VAL"23754",d:POKE VAL"23755",d ...
and you can safely use the driVe command.

And in the case of EMS (there is the same glitch - when trying to launch the file
after a "successful" Abortion Ifound a value in the variable #SCC8
#80) one can only hope that its author will send it to Moscow
version where he will finally use command #18 or though
I would just put the value #83 at the addresses #SCC8...#SCCB.

Or it will turn out like with CDOS, where users could load
can you see about a dozen of its “authors”...