Puzzling crash resolved?

As some of you might have noticed there was a very puzzling bug in ForkLift 2.0.4 that caused random crashes on certain systems. It turned out to be related to the command line tool called smbtree which ForkLift uses to discover Windows shares on the network. This tool seems to be really unstable and causes ForkLift to crash under certain circumstances and thus we decided to ditch it and find another method. Here’s test-build for everyone who encountered such problems:


What we are curious about in the first place is if the discovery of Windows shares still works fine with the new method and if the crashes are finally eliminated.

We are looking forward to your great feedback once again!

Sleep is for the Weak

The positive response to ForkLift 2 has been overwhelming, and we’d like to send out our sincere thanks to the armada of new users, as well as all the loyal fans who have upgraded. Your support is essential to the continuing development of ForkLift.

We’ve been slaving away squashing all your bug reports and sleeping only a few hours a night. Three releases since the launch, 2.0.1 – 2.0.4, have taken down many of the worst offenders. We will continue to focus on bug fixes and stability improvements before we dive back into the feature express leading up to v2.1.

Don McAllister at ScreenCastsOnline put together a comprehensive overview of ForkLift, walking through everything from basic features to more complex elements like Stacks, Workspaces, Syncing, Multi-Renaming, managing Favorites, the new Transfer Manager and more. If a picture is worth a thousand words, this screencast is an entire novel of ForkLift knowledge:

Click to Play

Two other things on our plate keeping us from sleeping: finishing up the documentation for v2.0, and getting the forums back up and spam-free. We’re evaluating several platforms to find the best solution and will have something up soon.

Thanks for your patience, and keep the great feedback coming! You guys keep us going!

ForkLift 2.0

the second coming...Finally the day has come to announce the second coming of file management and proudly present the final version of ForkLift 2.0.

It’s faster, more reliable, stronger and you will love it twice as much!

We spent many nights and days with re-building ForkLift from scratch inside and out and the outcome is not only simple beauty but also extreme reliability and a streamlined UI with many new and innovative features.

I could start an endless list of new and improved features in ForkLift 2, but I would just pick out the most significant ones:

Disklets, Synclets, new view modes, transfer queue, improved archive handling, new search modes and filters (with RegExp), improved Sync, Stacks, incredible speed!, integrated favorite manager, improved Multi-Rename, Workspaces, and a lot more to discover…

We released 7 public Betas in a row and got tremendous feedback from our highly respected users during this period and thus we tried to take all opinions very seriously and tailor ForkLift 2 to your needs. I think together we did an amazing job, even if some wishes didn’t come true, but hey, don’t be sad if you miss anything, as ForkLift constantly keeps evolving of course!

I would like to send our great community of adventurous and constructive beta testers a damn big THANK YOU! Without you ForkLift wouldn’t be what it is today.

ForkLift 2.0 is our first paid upgrade since we released 1.0 almost 4 years ago. If you already own a ForkLift license you can upgrade for $19.95, for new users the price will be $29.95 and now we also offer a new family pack at $49.95 in our store.

Click here to download ForkLift while you finsih reading this post.

If you encounter any bugs (and we are sure that despite all our effort you will…) please report them here.
Your feedback is highly appreciated.

You might also have noticed that our website changed a little bit 🙂 … therefore you won’t find our forum anymore as we decided to discontinue it and introduce a new platform for public discussion on ForkLift soon.

Please don’t use the blog for bugreports and support questions, rather send them by e-mail…. and try to be nice. Thanks!