Announcement

Collapse
No announcement yet.

Crash taking Snapshot

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Crash taking Snapshot

    I have BC3 (3.1.4, build 10554) and I'm getting consistent crashes when trying to take a snapshot of C:\

    Please see the attached bug reports.
    Aaron
    Team Scooter
    Last edited by Aaron; 28-Jul-2009, 03:12 PM. Reason: removed bugreport.zip. You probably want to email that privately.

  • #2
    UPDATE: the crash seems to happen only when I use the Archive contents flag.

    Comment


    • #3
      Hello,

      I took a look at your files (and removed them from our public forum). This is probably related to 'some CAB files that use a different format' crash that will be fixed in the next version of BC3 (3.1.5). Try using a File Filter to filter them out, and let us know if the issue persists in after the next update.
      Aaron P Scooter Software

      Comment


      • #4
        I've tried filtering out *.cab but to no avail. Even unchecking Items excluded by file filters on the Save Snapshot dialog made no difference.

        The odd thing is that even with *.cab set up as an explicit exclusion, it seems as though the Snapshot still wants to process these files (at least I see these file names pop up in the progress dialog prior to crashing).

        Is there any way I can test a debug/beta version of 3.1.5? I'd be happy to verify if the issue is fixed in 3.1.5 prior to its official release.

        Comment


        • #5
          Is the session treating archives as Files or Folders?

          The files should not appear in view (unless you suppress filters); that is how to verify they are filtered out.

          We do not have a beta of 3.1.5 currently available. If you would like to contact us via email, please send your request to [email protected] and include a link back to this forum post.
          Aaron P Scooter Software

          Comment


          • #6
            UPDATE: everything seems to be working for me correctly now in the latest version (3.1.6). Thanks for fixing that.

            Comment

            Working...
            X