I have to confess, I fell in love recently. Sounds weird? Right, it gets even more weird if I tell you that I fell in love with a file manager. The file manager is called Speed Commander (SC) and I am truly sorry to not have found it years ago. The respective project exists already for more than a decade.
So what’s so cool with it you ask? SC is shareware. This means you can try before you decide whether to buy it. Although I am developer of more than one OpenSource (and therefore also free - as in “free beer”) software, I usually try to balance between the effort required to write it myself and the time it would spare me to use such a program instead of the one I am using at the moment. The predecessor of SC on my machine was Turbo Navigator. Since it was written in Delphi or Borland C++ Builder, its Unicode support was non-existent. However, it was free (as in “free beer”) but not OpenSource. Neither is SC, in fact SC is commercial and ClosedSource. Nevertheless it rocks. This file manager is a joy to use. The only things that really distract me at the moment are the new program icons, the rest is better and some stuff I have to get used to.
Give it a try. In fact I think about porting the treemap code into an ActiveX and write a plugin for SC to show treemaps directly there. Of course such an ActiveX (COM) control would be accessible from any other application as well. The idea is to make WDS more modular and allow to share the code-base for the treemap between WDS and this ActiveX.
// Oliver
Several users had contacted us and claimed that WDS caused their systems to show the dreaded BSOD. As a driver developer I know that this is impossible since no user mode program can crash the system with BSOD unless some driver or other kernel mode component fails to check its parameters or whatever else.
Anyhow, one of the users sent me a minidump. This is the only way to find out who’s the culprit after a BSOD. In fact a full dump does as well, but a full dump has the size of the RAM on the user’s machine which is not usually practical (given sizes of 1 GiB and more).
The minidump showed that the fault had occured in a component of the Novell Client software. Although this justifies a strong suspicion, it is not a guarantee, since the respective bugcheck code occurs if some kernel mode component has corrupted the memory of the driver shown as faulty. My only recipe was to update the client software, if possible. There is no other way than this or uninstalling it completely (which usually isn’t an option at all ;)).
// Oliver
As before, the
As you know, the
Continue reading ‘<Unknown> keeping us busy’
Thanks to the ever-increasing amount and frequency of spam-comments, I removed the option for comments for now. However, I’ll attempt to work out a fix (possibly similar to the fix I use in the UVNC forum) and then enable it again.
Sorry for the annoyance :-[
// Oliver
A user sent us the following registry script via the feedback mailing list. Thanks!
Copy and paste it into a text file and save the text file with the file extension “.reg“. Make sure to modify the path in case you have a non-english system or in case you installed WDS into a different folder. Also make sure to use double-backslashes within the double-quotes.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Folder\shell\WinDirStat Here]
@="Win Dir Stat (Graphical)"
[HKEY_CLASSES_ROOT\Folder\shell\WinDirStat Here\command]
@="\"C:\\Program Files\\WinDirStat\\windirstat.exe\" %1"
// Oliver