@Greystash A whole series of events led to this. I got a second emulated 68k mac machine added to the network and it saw my Power Mac's drives automatically right away when I went to Chooser looking for my netatalk server, so I decided to try mounting images from the Power Mac and then sharing those. A software I downloaded had its toast file apparently already set to Locked when I expanded it. That happened to be the first toast file I ever shared as a mount, and I saw no errors, and thought nothing of it and went installing several other things on that emulated mac.
But when I went and mounted 2 other toast files a few days later, that's when those messages would start coming up. I was scratching my head about why until I thought about that first toast file. I tested around mounting and unmounting, and then went to comparing attributes.
It's possible that locking an image first is the "Apple way" to do this, I was looking for some confirmation of that, mainly.
@ovalking For the past year and a half I thought I was on 9.2.2 lol. My Mac OS was down due to some corrupted disk drivers since last year, I just got the chance to take care of that a month ago and im getting that system back up and going. I'm just getting the chance to install different things on it. I think I had a good reason I was holding off the last OS update, I just don't remember exactly what. Probably something model-specific that I wanted to look into more. I don't really use Classic mode on OS X.