fast read/write - was RE: [sebhc] Emulator H17 progress

[Dwight K. Elvey]

Hi
 Most timing is done relative to the 2ms timer registers
these can be altered by the emulator. Most code loops will
not be as big an issue. Still, for a first level, keeping
things happening on a time scale based on instruction
cycle times isn't too bad.
 As for disk image formats, I'm flexable. If things are done
as binaries, using tailer instead of headers makes sense.
If it is in an ASCII format, headers make sense.
As far as the simulator goes, it wouldn't take but a second
or two to convert a sector binary to a full track type binary.
This would make it so that the disk truely looked like
a real floppy to the software.
 We can make simple converters. I do think using one archiving
method is a good idea. There are many reasons to have something
that is in human readable format. Octal is wasteful but HEX is
better here. Still, it is a format that already exist.
Dwight

>From: "Jack Rubin" <jack.rubin at ameritech.net>
>
>> Yea, timing is an issue with seeks .. but you can
>> read and write as fast as 
>> you want!  (Just be sure to skip ahead to "no hole"
>> condition after a read 
>> or write that starts on a hole).
>>
>
>Am I right in thinking that this could be a real speed
>enhancer for a serial-serial H8 to PC connection?
>
>I'm really looking forward to being able to intechange
>"disks" between real and virtual machines - it doesn't
>seem like Dave, Dwight, Steven and Eric are too far
>apart. Can you guys iron out the differences before
>things start to diverge?
>
>Jack
>--
>Delivered by the SEBHC Mailing List
>


--
Delivered by the SEBHC Mailing List