What was different with AmigaOS approach, not sure I follow... MS has had warnings/prompts about a removed floppy all the way from DOS -> Win7.Solar wrote:Besides, AmigaOS was capable to detect the removal of a not-yet-unmounted floppy, and tell you in very precise terms what to do to recover from the situation. Since 1985. One of the things I never understood why other systems didn't copy that.
Kernel as your base kernel
Re: Kernel as your base kernel
Re: Kernel as your base kernel
Thanks for telling about UDI. It can save me a lot for designing new interface.That was the whole point of projects like UDI - cross-platform driver development.
Ah, what kind of warnings/prompts did DOS provide.. I had forgot about it. Is it prompts immediately after you eject the floppy?What was different with AmigaOS approach, not sure I follow... MS has had warnings/prompts about a removed floppy all the way from DOS -> Win7.
Most people get cars is not in the case for studying the engine.
Re: Kernel as your base kernel
If the floppy drive is in use for copying/reading only, obviously you're allowed to switch floppies if it's idle. I'm pretty sure that it also identified if you had changed to the wrong floppy on certain operations. The message read something like:Radian wrote:Ah, what kind of warnings/prompts did DOS provide.. I had forgot about it. Is it prompts immediately after you eject the floppy?
Code: Select all
Not ready reading drive X
Abort, Retry, Fail?
Re: Kernel as your base kernel
AmigaOS detected the ejection immediately (because even an idle floppy was polled regularly every two seconds or so).
And that prompt is the typical DOS joke of non-helpfulness. I don't have the exact wording of the Amiga requester at hand, but it was something to the effect of:
"Volume WORK: was removed from drive, but unwritten buffers exist. You must replace volume WORK: in any drive, or data will be lost."
And that prompt is the typical DOS joke of non-helpfulness. I don't have the exact wording of the Amiga requester at hand, but it was something to the effect of:
"Volume WORK: was removed from drive, but unwritten buffers exist. You must replace volume WORK: in any drive, or data will be lost."
Every good solution is obvious once you've found it.
Re: Kernel as your base kernel
I think it is clear that "not-yet-unmounted" is different from "being-accessed" ... 
Most people get cars is not in the case for studying the engine.
Re: Kernel as your base kernel
Well, there would be no need for that in DOS, AFAIK it didn't have any buffers that could be unwritten. Everything was written directly, and as such easy to detect if you ejected the floppy while accessing.Solar wrote:AmigaOS detected the ejection immediately (because even an idle floppy was polled regularly every two seconds or so).
I had no problem understanding what it meant and how to correct it when I was 10, but maybe you had special needs as a child?Solar wrote:And that prompt is the typical DOS joke of non-helpfulness.
Thats what you get for bad-mouthing DOS! 
BTW: DOS also gave volume name information on some occasions, can't remember exactly but I think it did if you for example ejected a floppy in the middle of a larger copy and not all files had been written..
The point is the was no need to unmount anything and it gave enough information to fix the problem. Obviously it would have needed additional checks if it used buffers for writing, but there was no need.
Re: Kernel as your base kernel
Well, what would you need buffering for if you're single-threading in the first place.
Every good solution is obvious once you've found it.
Re: Kernel as your base kernel
Well, yeah. Anyway, thats enough off-topic for now.. 