#97 Sharing files through My Computer breaks things if long filenames used (can't empty trash)

[Why_I_Game]

When you use the Basilisk II option to share a disk, and try to drag-and-drop a filename that is longer than the MacOS 7.5.3 max filename length, the files become strangely inaccessible.

I had 4 photographs in my shared Z: drive, when I dragged them onto my Mac Desktop the filenames were truncated, but the files could no longer be accessed, renamed, or dragged to the Trash (when trying to drag them from my Desktop into the Trash, it kept saying the files did not exist). I also tried dragging them from the Desktop back into the shared Z: drive, but that also said the files did not exist.

After I rebooted Basilisk II, I was able to drag them into the Trash, but then my Trash can became permanently broken -- the progress bar when emptying freezes part way, it can't access the files to delete them. I also can't drag the files out of the Trash can to put them back on the Desktop. Also, the Disk First Aid app does not find any issues with the disk, so there's no way for me to fix the issue, thus it has permanently corrupted my disk in Mac OS in Basilisk II (unless I stop using the Trash can).

Is there any way to delete these files that the Mac OS 7 thinks does not exist?

It may be an issue that the character limit that is being truncated to during the import, is off-by-one character, then it would end up with a filename that is 1-too-many characters and inaccessible -- but I don't actually know anything about filename limitations on MacOS in-general, or on MacOS 7.5.3 specifically.

This reminds me of my MS-DOS days, where I would use a hex editor to rename a directory name to all lowercase letters (which were impossible filenames for DOS, which can only use uppercase), making the folders inaccessible until I unlocked them again by hex editing the names back to uppercase. It would confuse people that they couldn't go in the folder, saying NOT FOUND.

Attached a screenshot of the 3 broken long filenames in my Trash can, which cannot be deleted, along with the output of the disk check, and the output of "File > Get Info" for one of the broken files.

[Why_I_Game]

The broken filenames are 31 characters long.

I have no idea about Mac internals. Is the max filename length 30 characters? 31 chars? 32? 25?

[Why_I_Game]

Also, why is this Bug Report showing up as a Feature Request?

The only options to choose when submitting the bug report were "Feature_Request" or "Not_A_Bug".

[Why_I_Game]

I just managed to work around my bug and delete the files!

I had already rebooted multiple times, but for some reason after I shutdown and switched to my previous 7.5.3 system disk, I was then able to empty the 3 broken files from the Trash Can. I have no idea what changed to allow the files to be deleted from the Trash?

The only differences between them:

• MacOS 7.5.3 with only HyperCard added -- couldn't delete
• MacOS 7.5.3 from a premade hard disk with tons of apps and add-ons -- could delete

---

However, I think it was just because of rebooting a bunch of times, and not because of switching system disks.

So if anyone else is having the same issue, try rebooting Basilisk II a few times, or switch to a different system disk (and back again), and as soon as it boots up attempt to empty the Trash Can.

If a dev could look into the code that handles importing files from My Computer under Windows, that would be great.