mrr@amanpt1.UUCP (06/29/88)
I have been informed that there are three bugs in MRBackup V2.2. The first is a failure of the decompression routine (invoked by Restore) to initialize a status variable to zero. If an I/O error is encountered by a compress or decompress call, subsequent decompressions will fail since they will inherit the prior status value. The only workaround for this is to do a short backup with compression (that doesn't fail) or exit and reenter MRBackup. The second bug is in the Save Preferences command. The value for the Compress Files flag is incorrectly saved (it's actually one of the other flag values). Finally, it appears that the archive bits are not being set properly on a backup. I can't believe it! That was working before I recompiled with Aztec 3.6a. I know it was (I think)! Is anyone aware of a problem with SetProtection under 3.6a? The first two bugs have been fixed in version 2.3. I still don't know what the problem is with the archive bits. Now for a question: I recently encountered a 286 error while doing a restore from a munged backup disk. I scanned my include files and couldn't find a definition for this error. If I remember correctly, the Fault program told me that an error 286 is an error 286 (thanks!). Can someone enlighten me? I knew you could. Mark -- < Mark R. Rinfret, mrr@amanpt1.ZONE1.COM | ...rayssd!galaxia!amanpt1!mrr > < AMA / HyperView Systems Home: 401-846-7639 > < 28 Jacome Way Work: 401-849-9930 x301 > < Middletown, RI 02840 "If I just had a little more time...">