Greetings, My VM is Windows 2000 SP4. I have drive mapping "Z:" to "\\.PSF\Projects" and a bunch of Java source files located on this drive. Before upgrading to 3.0, an ant build of those Java sources would take less than a minute. Immediately after upgrading to 3.0 (and reinstalling Parallels Tools), the same build now takes over 4 minutes. Literally nothing else has changed. I ran the ant build immediately before the upgrade and immediately after and the difference was staggering. Any help would be appreciated. Thanks! Patrick
I've noticed access to the Shared Drive is excessively slow as well. What build of PD are you using? I was originally using an early build of 3.0, and it took even longer to open files on the shared drive than it does now. After upgrading to build 4560 yesterday, I noticed a slight improvement in Shared folder access, but it is still far from stellar. I did not use previous versions of PD enough to compare, but I will say that shared folder access is slower than accessing files over the network.
Thanks for the reply. Unfortunately, my build is also 4560 so this may be as good as it gets for a while. Unless I'm missing a setting somewhere, it seems Parallels 2 had far superior performance when it comes to shared drives. Has anyone else observed this? Thanks.
Hi, I have exactly the same issue. I was compiling java files (from a z drive also) with a decent speed prior to 3.0 but now it is just unusable. When I move the files to the "windows space" (i.e. c the compilation process is *very* fast. The problem is definitely coming from shared drives. So now I am hosting the files on Windows and editing/processing them through the drive that mounts the windows file system Renaud
Shared disk slow - I wish this would be fixed I also have the same problem. I tried setting the security level to medium and re-creating the drives, but that did not help. This used to work much better in Parallels 2.0. I wish the Parallels team would fix it.
