Mapped Mac Folders Crash Windows Explorer

G

garudha

Bit poster
I recently upgraded to Parallels Desktop 3 and I like the new features in it, but I'm having problems with the new feature that creates a mapped network drive for the Parallels shared folder on your Mac (eg. Z: and Y: are mapped to the Mac Home and main hard drive respectively).

Any time I try to access these network drives from within Windows (XP SP2) using Windows Explorer, it shows the list of folders/files but then immediately hangs and then crashes. It does this with both Z: and Y: However, if I go to the .psf equivalent (\\.psf\.Home and \\.psf\.Mac) they both work fine and don't crash.

Has anyone else experienced this, and are there are solutions? For now I can access my Mac files using the \\.psf, but it would be nicer to have the mapped drives.

I'm using the latest Parallels (5582) on a MacBook Pro C2D running 10.5.1

Thanks!
 
Hello,

did you try to re-install Parallels Tools?
Do you have any Parallels crash logs in /Library/Logs/CrashReporter/?

Best regards,
Stacey
 
Same problem here - very annoying

Same situation here - I tried upgrading to 5584 yesterday, parallel tools was installed afterward, but the problem continues. Anytime I try to work with any of the shared directories or drives explorer will crash. Help!!
 
Bump

Same problem here, submitted a support ticket on 2/25 and have still not received a response. Please help with this, Parallels. I have since started evaluating VMWare Fusion, it doesn't have this problem. However, I have put a lot of time into my parallels installation and I don't want to have to start over with VMWare.
 
This solved it for me:
1. disable drive letter mapping
2. only have your complete mac drive shared (not mapped)
3. the Mac drive will appear in my network places
4. Make direct shortcuts on the desktop (righthand butten drag)
No more crashes on my part.
 
Thanks MeneerOptimel,

I too found that solution, and can take it a step further, by mapping my documents (right click my docs...) to the \\ path instead of the drive letter path. However, I still have a problem with this since I have some picky programs that don't play well with UNC paths, especially ones with "."'s in them. So, I need the functionality that is supplied by the drive mapping.

Where is a response from parallels on this !?!??!?! My VMWare machine is almost setup and doesn't have this problem yet, I'd still like to use parallels, but where is the support?
 
Stacey M said:
Hello,

did you try to re-install Parallels Tools?
Do you have any Parallels crash logs in /Library/Logs/CrashReporter/?

Best regards,
Stacey
Click to expand...

This is our only response from parallels? To answer your questions, Yes, tried re-installing parallels tools. No crash logs, because parallels isn't crashing, it's windows explorer that's crashing, I've tested this on a fresh xp install and it still crashes.
 
Xenos said:
Hello,

Please install the latest MacFUSE version and let me know if this will help.

Best regards,
Xenos
Click to expand...

Thanks for the response Xenos,

Unfortunately, that didn't solve my problem. When I re-install parallels tools, windows file protection was prompting me to replace files from the cd, to which I have been clicking cancel. This time I tried to put the xp cd in and let the files copy over. This also didn't fix it. The windows log is very vague in this regard, this is the only entry I get:

Application popup: Visual Studio Just-In-Time Debugger : An unhandled win32 exception occurred in explorer.exe [1240]. Just-In-Time debugging this exception failed with the following error: No installed debugger has Just-In-Time debugging enabled. In Visual Studio, Just-In-Time debugging can be enabled from Tools/Options/Debugging/Just-In-Time.

Check the documentation index for 'Just-in-time debugging, errors' for more information.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Click to expand...

I have Visual Studio installed so I can have the option to debug, which I've turned off, but if you want any info from that, let me know.
 
Well, I have nothing else to do, so, here is the Debugging info:

Exception:
Unhandled exception at 0x7c910370 in explorer.exe: 0xC0000005: Access violation reading location 0x00000000.
Click to expand...

Then I get this:
No symbols are loaded for any call stack frame. The source code cannot be displayed.
Click to expand...

Show disassembly:
7C910370 mov cx,word ptr [eax]
7C910373 inc eax
7C910374 inc eax
7C910375 test cx,cx
7C910378 jne 7C910370
7C91037A sub eax,dword ptr [ebp+8]
7C91037D sar eax,1
7C91037F dec eax
7C910380 pop ebp
... Much more
Click to expand...
 
Latest installment in the saga:

I installed a fresh xp using a new mac user account, and all works as expected, so (a little obvious) the problem lies either with my mac user acct or the xp install. Now I'm going to try that same cd and fresh install on my mac user acct. Note that I've already done this, but the cd I used last time was an unattended disk of my own that I use on our non-virtual machines here. This time, I'm using a plain old xp sp2 disc, we'll see how that goes.
 
Hello Gergmeister,

Glad to know about your progress. You can use an ISO image of the disk for installation which is quicklier and more reliable.

To make an ISO image of the installation CD-ROM:

1. In the Finder, browse to Macintosh HD -> Applications -> Utilities. Choose Disk Utility.
2. Insert the CD-ROM into the CD/DVD-ROM drive of your Mac.
3. Select the CD/DVD-ROM drive from the Disk Utility device list.
4. Click the New Image button on the top of the Disk Utility window.
5. Specify the name and location for the image or leave the default settings.
6. Set Image Format to read-only.
7. Click Save and wait till the image creation process is complete.
Now you can connect this image to the virtual machine’s CD/DVD-ROM drive:

- Launch Parallels Desktop.
- Click the CD/DVD-ROM icon in the main Configuration window to open the CD/DVD-ROM drive’s settings.
- Select the Use image file option and click Browse to locate the ISO image file.

You can use the successfully created image file as a bootable media for the guest OS installation instead of a real CD.

If during the image creation I/O errors occurred, this may indicate that there is either a problem with your disc, or your Mac CD/DVD-ROM drive doesn’t function properly.

Best regards,
Xenos
 
I have exactly this problem in a new Parallels v4 installation. Has a fix ever been identified?

Incidentally I have raised a problem report for this, but can't provide the number as your bug tracking system doesn't generate any email confirmation to the user reporting the issue. This would be a useful enhancement.
 
Hi Twynne,

I don't think I'll ever know the real problem here, but my solution ended up being to use a different install disc. The XP cd I was using was a slipstreamed build of xp with some extras like Norton AV etc, and I removed some components as well, so it was pretty custom, works fine for our workstations here, but not on parallels I guess. I still used a slipstreamed disc but all that was included were windows updates and sp2. After installing with the new plain xp disc, I didn't have the problem anymore. So, I'm not sure what your installation disc is like, but maybe try another.
 
Thanks - unfortunately this is a Boot Camp partition and already has all my apps, etc. I'd sooner switch off shared folders than rebuild from scratch.

Parallels - would love an official reply here. I have raised the issue via your problem reporting system, but don't know the number.
 
You must log in or register to reply here.
Back
Top