> Don't use Expander/ShrinkWrap to mount the disk image, it's a > (S)elf(M)ounting(I)mage file created with Disk Copy (that is, an > executable), simple double-click on it to launch and mount. As you noted, > you can also use DiskCopy to mount a .smi file, by dragging and dropping > the .smi file onto DC. I do just double click on the .smi file and that's when I get the error. I didn't look close enough to see if Stuffit is trying to open it or if Disk Copy is trying to open it. > > You might want to disable Expander's disk-mounting-zeal in its prefs, > I've only ever had trouble with that 'feature'. I'll try that this evening (don't have the Comet with me at work). > > Oh, well . . . of course the .bin file could have gotten corrupted in the > DL but that problem would have popped up when the image-mounting checksum > process noted a bad file. Re-DLing it ought to cure that. Tried redownloading, but still get the same error when trying to mount the .smi file on my dualie, so I don't think the file would be getting corrupted the same way during each d/l. > Can you unstuff and open the .smi on another Mac? > > Then burn the full installer to CD. > > Then run the install off the CD I have been d/l'ing the file on my dual 867 Powermac running OS X.2.6, and it unstuff's the .bin file fine, but then I think DiskCopy tries to mount the .smi file and that's when the error occurs. So, I can't even unstuff it on my high power Mac.