You may know all of this already -- if so, forgive me.
I love VDT dearly, but there are times that it is, ummm, a bit slow. I am running it on two different dual Xeon machines and jobs like create a new desktop have none of the ZAP sort of flash I expect from other jobs. In particular, things I want to do on the Desktops Explorer require patience.
Just looking, right now after about 6 hours of running, VDTlbx shows a peak working set size of 15 MB and the Kernel Authority another 36. That means that VDT is adding about 50 MB of memory overhead to XP at the minute. (Those numbers may be higher than typical: I use VDT to support 8 virtual desktops and several applications sitting idle.) On any machine, XP doesn't really run at its best with less than 512 MB of RAM, and some argue for 1GB. With 128 MB you are going to have to wait while your processor creates extra memory out of smoke, mirrors and pagefile space.
I am not saying you don't have enough hardware to use VDT happily -- I don't know. VDT functions adequately on a Dell laptop with a 1.2 GB processor and 768 MB, but that is the least horsepower I have ever fed VDT. I am saying that with your processor and memory configuration you may need to wait what seems a long time for some operations to complete.
I downloaded it 3 days ago, so the latest version. It maybe that the machine can handle VDT, are there any minimal system requirement?
I would expect the classic menu to work, but it doesn't popup. It's a pretty old PC, i'm installing WinXP on a 2nd old PC with slightly more RAM to see if that one works.
(Btw i also tested under windows 2000 with sp2, thats why i updated to sp4.)
Or am i missing some files? (directx or anything VDT uses on win2k to work properly?
Just curious.
Don't put too much effort in, i will let you know soon if the winxp machine does work. (so i will switch to it).
I never defined minimum system requirements, but I'm regularly testing VDT on old (512Mb, PIII 400Mhz) and recent computers. I already did many efforts to reduce memory usage and I will continue to do so.
As I said before, I already had a message about VDT failing to work on W2K; this disturbs me, so I will continue to try. Can you verify if the components below are installed: MSCOMCTL.OCX tabctl32.ocx COMDLG32.OCX MSCOMCT2.OCX MsMask32.ocx msmapi32.ocx Msflxgrd.ocx
Moreover, you should have a VDTInstall.log file in C:\Program Files\R2d2 Software. Can you send it to support@r2d2-software.com?
Feedback is always appreciated, so continue this thread if you need so.