> So, how about some status reports. What we seem to have is 1001 > unfinished projects. > Hard drive?
Version 0.3 of the pcb was routed today -- we've found that a lot of bugs on our interfaces were due to not decoding the M1 line, which we've sorted out now. We're still building up version 0.2 of the pcb on the bench, and 0.1 is sitting there quite happily, having proved that it works (we have read and written sectors to the hard-drive). > Pro-Dos Comms? <<Oi! Johnathan!>> > Native Comms? Other than the Commix stuff, it's going quite well. Keyscan routines have been set to 1/25th of a second to improve data-->screen throughput, cursor is now on an idle-time based delay. Basically, as long as stuff is being transmitted, the cursor will toggle (the idea being so that if people hold down keys, the cursor will still show them where they are). If data is being received, the cursor is deactivated, and will not reactivate until 1/10th of a second after the last byte is received. It then nicely flashes. Currently implemented is three text modes (not switchable yet), the scrollback buffer is there (but doesn't yet scroll back), and --hey-- I've just come up with a really cool and quick way of scrolling the buffer screen!!! *grins*. Capture files are there in spirit, but the file i/o isn't in there yet. And a lot of the features can be disabled (the code will re-write itself to get rid of them) for speed. > New comms interface? Not my problem really :) I thought that was Bob's domain... > What else? Uh... Quazar, the MultiROM, the RYAN (I think). Simon
