Alright. After testing the Mini vMac compiled for use with the same applications I run often on my 128k (thanks to it almost perfectly emulating a 128k), I sit here and try something that doesn't produce any problems on the emulated machine on my real hardware, and I get the following completely incongruous result:
I have MacWrite or MacPaint open, go to save my document with the application still open, put my disk in the external drive, and then the computer says there's no room to save it, even though there should be slightly over 20 files remaining until the MFS file storage limit. But then the weirdest part yet occurs...
My real 128k thinks there should be an operating system on the documents disk, when it doesn't do this when you put the disk in before you launch MacWrite or MacPaint but after you get to the desktop, and so it switches the Clipboard File and Scrapbook File to the documents disk. And this was found out by the disk no longer having any room to store my documents, even though there's over 80KB of space and 21-22 separate files left on the file number count, as well as the Scrapbook suddenly being empty and the Finder reporting that there is indeed a phantom Clipboard File and Scrapbook File that weren't there all the times I put the documents disk in before I launched MacWrite.
Eject the documents disk, shut down and restart the computer, and then you can delete both the Clipboard and Scrapbook Files thus created and it goes back to normal.
(The only reason I use an emulated 128k is to make sure my real hardware stays alive so that I can continue to have a legal right to a virtual machine.)
Was this discrepancy intentional, or was it one of those things called an "undocumented feature" ?
I am just amazed by this difference.