3 ms·
> In Win95 or MacOS 7, if you started a file copy (for example), the whole desktop froze until the copy was done. You couldn't do anything else except sit there
by Sesse__ 5y ago
> In Win95 or MacOS 7, if you started a file copy (for example), the whole desktop froze until the copy was done. You couldn't do anything else except sit there and watch the progress bar.
In Win95, the copy happened on the destination folder's thread. You could still open other windows and keep browsing around, but that specific window would be unresponsive.
- lproven 5y agoThat is not how I remember it, from *extensive* use at the time, but I would have to spin up a VM to try it. I don't think you're right. The OS was still running; you could switch to an app and keep working, for instance. But Explorer had only 1 thread, AFAICR, and a large file operation visibly locked that thread.
- mnl 5y agoI honestly can't remember about such details, but with IDE drives and 95A you were limited to PIO. You could enable DMA in 95B, it wasn't by default. It was in W98. That should make a drastic difference.
- lproven 5y agoI think it depended on the disk controller, no? https://www.philscomputerlab.com/windows-98-dma-mode.html https://www.philscomputerlab.com/windows-98-dma-mode.html I wrote about this in PC Pro in about 1995-1996. Because it had a true pre-emptive kernel, it could do other stuff while waiting for disk I/O, and on NT, enabling DMA made a big difference. As I recall, on 98, it just made disk access a bit quicker, that was all.