atw: Re: SnagIt / Icon rendering problem

Yep. Had the same problem with MS Word crashing when I tried to insert Snagit graphics. Blew me right out of the software and sometime right off the computer. I too resorted to the same work-around - spreading folders all over the place and limiting the number of graphics in each. I thought it was MS Word acting persnickety. Memory is fading on that particular project, but seems to me that allowing Snagit to create its own folder (the new default function), rather than creating a "regular" folder for it, was showing promise. The new updated Snagit, with the compete overhaul in appearance, appears to have developed a few growing pains. Bummer, as I love Snagit and all the new bells and whistles - but hate the new GUI interface and the landmine feature is a real problem.
Regards,
MNMary

On 2/20/2008 11:10:59 PM, austechwriter@xxxxxxxxxxxxx wrote:
> Hi Guys.
>
> When I started this contract (6+ weeks ago), I installed FM7.1, Photoshop > 7 and a trial version of SnagIt onto my Lenovo machine (has dual core + 1Gb
> RAM). All worked well together as usual without any drama.
>
> A couple of weeks ago, however, I upgraded to FM 8.0.1, reinstalled
> Photoshop 7 and installed the full version of SnagIt 8.2.3. Now, it seems
> that whenever I capture too many items to a directory, and then go into
> that directory using either FM or Photoshop, the application I#8217;m
> using crashes. When I try to recapture again, SnagIt crashes.
>
> It seems (visually at least), that when the icons are rendering on the
> screen, there is some sort of conflict that causes the problem. The file
> names display but when the icons associated with each start rendering on
> the screen, only half display before the application crashes.
>
> This has caused a lot of downtime this week, reinstalling software,
> rebuilding my machine and finally rebuilding another machine; all to no
> avail.
>
> I have sent queries to SnagIt support and spent several hours trawling the
> Internet also to no avail (and SnagIt support seems to be missing in
> action).
>
> My work-around is to ensure that th  

Other related posts: