|
![](/i/fill.gif) |
On 07/06/2011 02:47 PM, Darren New wrote:
> On 6/7/2011 5:00, Invisible wrote:
>> Still, why it can't build an image of what the final disk layout will
>> look
>> like in RAM and then write it all to disk in the most efficient order, I
>> don't know. That's how I would probably do it.
>
> It's a removable disk.
And?
> There were backup programs under DOS that worked this way, incidentally.
> You'd just page floppies and it would write them as fast as it could,
> even alternating drives. But when it was done, they were all valid files.
Yeah. That seems like the most sensible way to go.
> Why would you optimize something as slow as floppy access instead of
> improving other parts of the system to start with?
Because it's a trivially easy optimisation?
Post a reply to this message
|
![](/i/fill.gif) |