Some may know that I still have my iMac Bondi Blue running D-9.2.2. right now.
Like Ronald said, 31 characters for OS9 finder filenames sounds about right.
A folder can be named e.g. "The quick brown fox jumps over " but "the lazy dog" is not possible.
Still 31 characters were quite an improvement, thinking of the well known 8+3 format.
- The file names without extension, at least of these three files, are well within the 31 character limit.
- Although the files are in a typical Mac image format (pict) and were created and modified in February 2000, they do not have the usual Mac properties of resource fork and file type and creator metadata one would expect with such files.
- The files are packed in a ZIP archive, in MacOS times not a usual archive format unless one would want to archive and later unpack the files to be compatible with a PC/Windows environment.
Could it be that the original files were Mac files without file name extension, that they were processed in a way that would remove the Mac properties of the file and replace the type "PICT" code by a .pct extension, thus making the file names longer then 31 characters? This could happen when transferring the files to a PC environment or while archiving the files into a format that does not preserve the Mac properties of the files.
This thread has drifted from its original topic. Perhaps the part about filenames could be branched into a new thread, so that we can advise on ways to make those PICT files usable again under OS 9. (Hint: http://www.frederikseiffert.de/filetype/)
About the unresponsiveness error: the version you are currently using has some limitations/errors not fixed. One is the error where, after clicking/moving in and out of the sheepshaver window (around 40 times) the input becomes unresponsive.
About the unresponsiveness error: the version you are currently using has some limitations/errors not fixed. One is the error where, after clicking/moving in and out of the sheepshaver window (around 40 times) the input becomes unresponsive.
Best,
Cat_7
yes that sounds right, ok thanks for letting me know.
Cat_7 wrote: ↑Sun Apr 24, 2011 8:03 pm
About the unresponsiveness error: the version you are currently using has some limitations/errors not fixed. One is the error where, after clicking/moving in and out of the sheepshaver window (around 40 times) the input becomes unresponsive.
Aha! OK, that explains the unresponsiveness/lock-up problems I've been having with COI. This comment refers to SheepShaver version 2.3, which is the version that comes bundled inside COI a.k.a. Chubby Bunny, which I've been using (yes, I know, it's not recommended). So that gives me a good reason to go follow the manual on how to migrate my set-up from COI to regular SheepShaver: viewtopic.php?f=33&t=10833.
