I personally don't mind it eitherway ('.iso' or '.iso.bin'). Of course, this is only relevant from a 'historical preservation' perspective, and that too only if we can assume the '.toast' file in question has never been mounted that way before.Thoughts? To my knowledge, on Mac, non-locked images aren't preserved in their purest state once mounted, because it accepts write operations to them, and there are things the Mac system writes to the image by default in that case. But first, about the '.bin' wrapper, there's one thing that made me consider it: Creator/Type codes and, in particular, to have the image file pre-locked, once decoded. I'm OK with whatever you decide, I just don't think it's necessary for this particular iso, but that's also just my opinion. Those who do care about such things will probably (like myself) ensure all DL'd mountable archives are read-only, out of habit.But if you feel it's more appropriate to include it in a.bin wrapper, then do so, I'll leave it up to you. I don't think most people downloading it will care one way or the other, will likely use it once to install and then toss it in the Trash. What someone does with it after this is up to them. Uploading it here as a raw.iso, preserves this, so it is fine IMO to upload it here as is for archiving. Roxio Toast Titanium Trial Downloadīut manually locking the image may be required before mounting it.Mac OS X will go by the '.iso' suffix file-name ending and give it to Disk Image Mounter to mount - but again, manually locking the image may be required before mounting it, if the downloader wants to preserve date and time stamps.The Toast image in question appears to be unmodified since time of creation. The Virtual Utility also mounts all images as locked by default, so mounted images do not get written to by that app, and there's no need to lock any image it mounts.Toast will have no issue with mounting a generic Creator/Type code-less image, it will read from the data fork and determine it's OK as is. To my knowledge, on Mac, non-locked images aren't preserved in their purest state once mountedThe newest version of the Virtual CD/DVD Utility includes a handy Creator/Type restore dropper which turns a generic icon into a native Virtual CD/DVD Utility icon (double-click and it mounts the image without needing to launch the Utility separately). sit archives over to your Mac OS 9.1 machines, decompress the archives, and manually put everything in the same locations under Mac OS 9.1 that they were installed with under Mac OS 9.2.2, and see if the Roxio Toast Titanium 5.2 will then launch - If it crashes remove the Toast USB Support B and Toast USB Support C INITs from the Extensions Folder, and try again.By - 2019, October 3 - 2:57amabout the '.bin' wrapper, there's one thing that made me consider it: Creator/Type codes and, in particular, to have the image file pre-locked, once decoded. sit archives of everything installed, and copy the. In terms of your Roxio Toast Titanium 5.2 installer crashing - You might try installing it on a Mac OS 9.2.2 machines, then make. Roxio Toast Titanium 5.2.1, 5.2.2, and 5.2.3 were listed by Roxio as "compatible with Mac OS 9.1 and higher, including Mac OS 10.3". Roxio Toast Titanium 5.2 was listed by Roxio as "compatible with Mac OS 9.1 and higher, including Mac OS 10.2". Worked under Mac OS 9.1, and Mac OS 9.0.x, and Mac OS 8.6, with older versions of Toast - going all the way back to Adaptec Toast 4.1.3, but that:ĭid not work under Mac OS 8.6, some versions of Mac OS 9.0.x, and some versions of Mac OS 9.1, and sometimes crashed versions of Toast under pre Mac OS 9.2.x, if installed. I also seem to recall that these Extensions (copied over from a Roxio Toast Titanium 5.2.x install under Mac OS 9.2.2): I seem to recall that copying over the Roxio Toast Titanium 5.2 application and all folders and files ( except Toast USB Support B and Toast USB Support C) and folders installed under Mac OS 9.2.2 on a G4 Sawtooth, worked on a Blue and White G3 Revision 2 machine worked under Mac OS 9.1.
0 Comments
Leave a Reply. |