The computer, or rather its OS, has no idea about a directory, in fact not even what constructs a file. It can only open/read/write/close data streams from devices on the bus. Getting a directory is a clever hack of 'loading' a dummy program. This works since
LOAD command is implemented as opening a data stream and loading what is returned into ...
the drive could end up only being able to transfer one bit per horizontal blank = 63 microseconds. 1/(63e-6) = 15873 bits/s = 1984 bytes/s.
That would be the bitrate during transmission within a byte, but bytes are framed and handshaked, which adds an average of 160 µs per byte. Resulting in (63 * 8) + 160 µs, or ~664 µs per byte. So the upper transfer sped ...
And now this: disk drive outputs the video signal through the serial bus connector!
"Freespin" Demo by Matthias Kramm (Quiss/Reflex):
Technical details are described on the author's website:
Every single raster line, we have generate sync pulse by pulling both
DATA and CLK ...
The RP06 maintenance manual says
Emergency Retract. An emergency retract operation is used to remove
the heads from the pack if the retract operation fails, or if there is
a power or power supply failure.
18.104.22.168 Emergency Retract Mode
Only one positioning operation can occur in this mode, this being an emergency-retract operation. In the
The first version of Windows to support out-of-the-box DVD playback is Windows XP Media Centre Edition*, which was created specifically to target the HTPC fad that you mention, and it also has some special hardware requirements.
The only mainstream versions of Windows to play DVDs without additional software were Windows Vista Home Premium and Ultimate, and ...
The standard load routine will not handle this.
If you need to load under $D000-$DFFF you will have to handle it yourself; you can still use kernal routines (such as OPEN, CHKIN and CHRIN) to do it but will have to buffer and transfer or set the bank configuration for each byte stored.
Loading under BASIC ($A000-$BFFF), $C000-$CFFF or KERNAL space ($E000-$...
No it doesn't adjust the memory configuration - which is why loading an 'executable' file (i.e. start address of $0800) bigger than 202 blocks (about 50 KB) using a standard kernal will crash a C64. Same for your 8 KB/$C000 example.
Nemesis' Bonzo Doo Dah and Richard Monteiro's FastForm/BigK in Amstrad Action Issue 16 gave somewhere between 203 – 206 K per side, leaving one or two standard tracks for a small boot stub to load up the custom disk parameters.
Both of these hit all three of your parameters: all they did was modify some settings held in RAM. I was a dedicated user of Bonzo ...
Just a small addition from the technical department:
trackdisk.device (TDD) polls the disk status in regular intervalls. In order to detect a quick disk change in between two polls, the drive latches a DC status until the head is moved. So, TDD needs to move the head to update the status.
Moving the head outwards usually stops once track 0 is reached by ...
This is not yet a complete and verified answer, because I haven't tested it on real hardware.
There is a utility by CNGSoft called '2H' (written in 2013) which claims a capacity of 208K, using 41 tracks of 10 sectors each.
I found this on the CPCWiki forum and a dsk image of the tool on CPC-Power.