As for the structure of the RAM floppy—that is, what is located where in 1 MB of memory—and the structure of *.trd files:
Where does ide_tune.com poke the hard-drive parameters into ide+3.blk? (Can I get the source code for ide+3.blk and ide_tune?)
It looks like a file manager for *.trd files on a hard drive under iSDOS will be written in Krasnodar (so you can work with them properly without leaving the system). Something like this: put a path in extent.txt on the TRD... Then pressing ENTER takes you into it as if it were a subdirectory... Anyway, it’ll be a way to get some experience programming for iSDOS, and it should be useful too (they seem to have made iSDOS–TRDOS compatibility, but for now it’s all inconvenient to use.
My answers, point by point:
-
The 1 MB KAY-1024 memory layout...
KAY-1024 extended memory addressing:
┌─────┬─────────┬──────────────────┐
│ bit │ PORT-bit│ RAM size, kB │
├─────┼─────────┼─────┬─────┬──────┤
│ 0 │ 7FFD-0 │ │ │ │
│ 1 │ 7FFD-1 │ 128 │ │ │
│ 2 │ 7FFD-2 │ │ 256 │ │
│ 3 │ 1FFD-4 ├─────┘ │ 1024 │
│ 4 │ 1FFD-7 ├───────────┘ │
│ 5 │ 7FFD-7 │ │
└─────┴─────────┴──────────────────┘
The TRDOS RAM disk starts at bank 24 (#18 hex), meaning 7FFD=#00, 1FFD=#90, and occupies the computer’s last 640 kB (40 banks). In iSDOS, the easiest way to access that memory is through the electronic-disk driver, starting at block 512 (#200 hex). On KAY-1024, the iSDOS electronic disk starts at bank 16. The memory of a 256K machine is used only as a last resort; it’s better not to use the 128K banks at all. Though none of this is quite settled yet. Nemo is threatening to install an STS-type monitor in the shadow ROM, in which case we’ll have to give the electronic disk a couple of banks somewhere between 16 and 23. I’ll probably just write some sort of text file describing the ports and banks, and all the various setup programs can read it.
-
The structure of
*.trdfiles...There’s no particular structure to them. Take a look inside with
demon.comand see for yourself. They’re simply all the TRDOS disk blocks, one after another. In other words, it’s just a blank disk image like an*.imgfile, except that it contains a TRDOS disk rather than an iSDOS disk. -
As for “inconvenient,” that depends on who you ask. I think it’s easier to load the
*.trdinto a RAM disk (five seconds from the hard drive; by the way, that’s exactly the kind of loader I have inextent.txt), then use any ordinary TRDOS file manager (preferably one that doesn’t access ports 7FFD and 1FFD, or talk directly to the VG93, unless you want to blow yourself up). To save the*.trdback, reboot into iSDOS from the hard drive (about 10 seconds for the whole thing). Since 20.5.99,from_trdandto_trdoshave worked with the RAM disk. But it’s a matter of taste. Go ahead and make one if you want. The easiest thing is to rip the procedure for working with the panel out offrom_trd. If you need any help, write to me. -
About where it “pokes” and the source code: first, I’d like to know why you need it. I wouldn’t want to see the standards in iSDOS diverge—that is, to end up with what’s happening with the Spectrum itself (a bunch of different memory expansions beyond 128 kB, several varieties of “CGA,” “double screens,” and so on). On the cutting edge of hardware development, it’s often simply impossible to avoid that, but in system programming it can and should be avoided. Anyway, it pokes into the driver. 30 bytes at offset 16.
P.P.S. Feel free to contact Nemo about any questions like these at 159-55-69.
or write me letters in electronic script at:
n.leont@pop.ioffe.rssi.ru
or send letters and money orders to:
195256 St. Petersburg,
28 Nauki Ave., Apt. 123
Alexey Georgievich Leontiev
° ° °
╔═════════════════════════════════════════════════════════════╗
║ ║
║ Technical Editor - OPER. ║
║ ║
║ St. Petersburg–Moscow ║
║ 1999 ║
╚═════════════════════════════════════════════════════════════╝
Share your thoughts about the article