Hello Chad,

I got ShrinkWrap Version 2.0.1.  Lots of nice new features and formats.
And it's much more tolerant of my pre-Superdrive SE.  Thanks.
Naturally, nonetheless I wish for more.

1. Glitch.  I set my preferences to Save Floppy as DiskCopy Image File;
   Save Other as ShrinkWrap image file.  When I do a Image; New Image
   and select format Other; size 1440K, it creates a DiskCopy Image
   rather than a ShrinkWrap Image.  It would seem to be keying on the
   device size rather than the selected format.
   
2. Glitch.  I have an archive with Type hdrv; Creator ddsk.  When I
   drag it to ShrinkWrap, it fails to mount, with the message that
   I need Expander Enhancer to mount archives.  If I simply change
   the creator to Wrap, it mounts fine, even though I don't have DSEE.
   Shouldn't I be able to mount this as long as the type is suitable,
   regardless of creator?
   
3. Glitchlet.  Using System 7.1 on an SE with a Mobius 68030 accelerator
   and Connectix Virtual, I experience the following:  I can mount an
   image at startup by putting an alias in the Startup Items.  But if
   I do this, and the folder containing the ShrinkWrap application is
   open on the desktop, the Mac crashes.  I suspect this is a System bug
   rather than a ShrinkWrap bug, since I get quite the same crash with
   DropDisk if I put an alias of a DropDisk archive in Startup Items and
   leave the folder containing DropDisk open on the desktop.
   
4. Wish.  It's nice to be able to mount images at startup; it would be
   even nicer to control the characteristics of the mount by attributes
   (resources?) of the image file.  For example, suppose I want one
   image automatically mounted locked and another unlocked.  I can control
   this by locking or unlocking the Image file.  But suppose I want one
   image mounted as a RAM disk at startup, while another, larger image
   mounts non-RAN.  Can I control this?
   
5. Wish.  To be able to mount an image of a DOS floppy so that Apple File
   Exchange recognizes it.  (I don't have PC Exchange).  But, again, I
   realize this might require getting more down-and-dirty with the driver
   than is safe.
   
Thanks for your attention,
gil