I doubt if Brian has been able to do much with the new tools yet. He headed off on his Xmas tour soon afterwards.
greg, the memory leak problem you describe and have it not occuring for anyone else like that
so its some setup incompatibility
so you could try the install to a new directory, create a file called 3wd.txt and start wd there instead and set up the basics as a test
and see how that goes, as a test
or stick with older version you have
when i get back home late in the week, i will find that memory debugger i saw mentioned in something else i had downloaded recently
Just for the record I am experiencing nightly crashes of 10.30u. Looks like last night’s happened at about 2:10AM. For a while there it was happening at the stroke of midnight. I suspect I may be experiencing the same memory leak others are referring to here.
Bob
I’m a bit slow here so can you elaborate a bit more on the installing to a new directory? WD is currently installed in c:/wdisplay Where do I put the file 3wd.txt? So I would have to start completly over loosing 5 years worth of data? 
This FAQ discusses installing another WD on your computer, withour affecting your current, for testing:
-Bob
Thanks Bob.
you install it to where ever you like, thats up to you…as long as its somewhere different
this is a test greg, i am not telling you to abandon all your data
you will be able to merge the data gathered during the test with your exisiting data
you put that created file , 3wd.txt, in that new installed location, as per my instructions above
make sure the file is not called 3wd.txt.txt i.e untick hide known file extensions in your windows folder options
I have seen more frequent jumps in memory usage since version 10.31d. So far, I have not had WD run for a full 24 hours without jumping up to 67 or more MB of memory usage. WD starts in the high teens and quickly rises to 25-26MB of memory. The highest Ihave seen is this morning’s value of 97MB. This was after several days of running undisturbed. At this point, the easiest solution appears to be to write a program to close the real time FTP upload utility, then close WD, wait a few seconds, and then restart WD. The job can be scheduled to run once or twice a day. I’m hoping that both applications respond to a WM_CLOSE message so the shut down gracefully…
A question: Is there a way to have WD start up minimized to the system tray? That would make things easier!
On the debugging front, one possibility that comes to mind is to insert a logging application in each major WD functional block. The calling procedure would be passed to this app, and stored in a static string (no need to write to a file here). WD’s memory usage would be checked with each call; if it increases more than 50% from the last check, the calling function, time, etc. could be logged to a file. Just a thought – but one that has served me in the past when tracking down similar oddities in large programs. If you have a few known problem systems to work on (volunteering mine here!), it does not take long to isolate the problem routine(s).
The dropdown under Setup has settings for starting WD minimized.
–Dave
wd does have a facility to restart itself at sheduled times, see in the ftp/internet setup, reboot setup
i am also going to add option to restart itself if an access violation error occurs (i.e so many in total, etc)
(as long as you dont have a problem with WD not exiting cleanly…but then what i will do is get a kill bill (i mean kill WD) program to run which will try killing off the process before restarting wd…that should do the trick (and the clientrawrealtimeftp.exe (but note that wd does not start a 2nd version of the clientrawrealtimeftp.exe if it finds its already running (but it still restarts the clientrawrealtimeftp2.exe, something i need to work on)