Shared Folders won't work in Build 1884

manfredell said:
Can you please explain what you mean by that. I cannot find any preference in parallels relating to half/full duplex??
Click to expand...

Oh, sorry. I mean the preferences in Windows XP on this Network Adapter.
 
Confirmed - shared folders randomly stops working on build 1884

Well, I stand corrected. The Shared Folders just stopped working for me too after about 20 minutes of us. The dialog from within Microsoft Access stated "Can not open more files". I was unable to browse any of the linked files on the shared folder directory. I went back to My Computer and opened the mapped drive and the dialog says: "S:\ is not accessible. The system cannot open the file."

I quess I didn't run it long enough when I stated that I had no problems with the shared folder in build 1884. Sorry about that folks. :o
 
Hey all,

Will you please check the newer update which can be downloaded from here. Please don't forget to update Parallels Tools after upgrading.

As usual, your feedback about this specific problem is highly appreciated.

Best regards,
Tim
 
Installed, updated Tools opened WinXP:

Opened one shared folder. OK. Opened another folder inside this one: CRASH.
Parallels just went away. Opened it again and when trying to open the VM it told my that another instance was using it.....

Host Name: Manfred-Ell-Macbook
Date/Time: 2006-09-14 14:10:55.584 +0100
OS Version: 10.4.7 (Build 8J2135)
Report Version: 4

Command: Parallels
Path: /Applications/Parallels/Parallels.app/Contents/MacOS/Parallels
Parent: WindowServer [64]

Version: 2.2 (2.2.1892.0)

PID: 892
Thread: 7

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xe27b6000

Thread 0:
0 libSystem.B.dylib 0x9000a5c7 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082369a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90822eb5 CFRunLoopRunInMode + 61
3 com.parallels.desktop 0x00545b95 0x1000 + 5524373
4 com.parallels.desktop 0x004cbc7b 0x1000 + 5024891
5 com.parallels.desktop 0x004cbe12 0x1000 + 5025298
6 com.parallels.desktop 0x002cbec1 0x1000 + 2928321
7 com.parallels.desktop 0x0004e091 0x1000 + 315537
8 com.parallels.desktop 0x00006402 0x1000 + 21506
9 com.parallels.desktop 0x0000631d 0x1000 + 21277

Thread 1:
0 libSystem.B.dylib 0x9000a5c7 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082369a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90822eb5 CFRunLoopRunInMode + 61
3 com.apple.audio.CoreAudio 0x914588da HALRunLoop::OwnThread(void*) + 158
4 com.apple.audio.CoreAudio 0x914586f5 CAPThread::Entry(CAPThread*) + 93
5 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 2:
0 libSystem.B.dylib 0x9002521f semaphore_wait_trap + 7
1 com.parallels.desktop 0x0058386f 0x1000 + 5777519
2 com.parallels.desktop 0x003b7148 0x1000 + 3891528
3 com.parallels.desktop 0x003b7603 0x1000 + 3892739
4 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
5 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 3:
0 libSystem.B.dylib 0x90037ee7 mach_wait_until + 7
1 libSystem.B.dylib 0x9003a652 usleep + 82
2 com.parallels.desktop 0x00580382 0x1000 + 5763970
3 com.parallels.desktop 0x00583730 0x1000 + 5777200
4 com.parallels.desktop 0x003a22b8 0x1000 + 3805880
5 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
6 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 4:
0 libSystem.B.dylib 0x900251a7 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00583a48 0x1000 + 5777992
2 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
3 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 5:
0 libSystem.B.dylib 0x900251a7 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00583a48 0x1000 + 5777992
2 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
3 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 6:
0 libSystem.B.dylib 0x900251a7 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00583a48 0x1000 + 5777992
2 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
3 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 7 Crashed:
0 <<00000000>> 0xffff07c7 __memcpy + 39 (cpu_capabilities.h:189)
1 com.parallels.desktop 0x0058d0d8 0x1000 + 5816536
2 com.parallels.desktop 0x006a3296 0x1000 + 6955670
3 com.parallels.desktop 0x006a3683 0x1000 + 6956675
4 com.parallels.desktop 0x006581f3 0x1000 + 6648307
5 com.parallels.desktop 0x00659b23 0x1000 + 6654755
6 com.parallels.desktop 0x0065fcbd 0x1000 + 6679741
7 com.parallels.desktop 0x0058d37e 0x1000 + 5817214
8 com.parallels.desktop 0x005839e0 0x1000 + 5777888
9 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
10 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 8:
0 libSystem.B.dylib 0x900251a7 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00583a48 0x1000 + 5777992
2 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
3 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 9:
0 libSystem.B.dylib 0x900251a7 semaphore_wait_signal_trap + 7
1 ...ple.CoreServices.CarbonCore 0x90cdcdbf MPWaitOnSemaphore + 152
2 com.parallels.desktop 0x005847a6 0x1000 + 5781414
3 com.parallels.desktop 0x007670b8 sound_thread::_thread_proc(void*) + 798
4 com.parallels.desktop 0x00766dd9 sound_thread::_thread_proc(void*) + 63
5 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 10:
0 libSystem.B.dylib 0x900492e7 semaphore_timedwait_signal_trap + 7
1 com.apple.audio.CoreAudio 0x91465a10 CAGuard::WaitFor(unsigned long long) + 212
2 com.apple.audio.CoreAudio 0x91465932 CAGuard::WaitUntil(unsigned long long) + 66
3 com.apple.audio.CoreAudio 0x914643a2 HP_IOThread::WorkLoop() + 690
4 com.apple.audio.CoreAudio 0x914640e9 HP_IOThread::ThreadEntry(HP_IOThread*) + 17
5 com.apple.audio.CoreAudio 0x914586f5 CAPThread::Entry(CAPThread*) + 93
6 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 11:
0 libSystem.B.dylib 0x900251a7 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00583a48 0x1000 + 5777992
2 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
3 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 12:
0 libSystem.B.dylib 0x900251a7 semaphore_wait_signal_trap + 7
1 ...ple.CoreServices.CarbonCore 0x90cdcdbf MPWaitOnSemaphore + 152
2 com.parallels.desktop 0x005847a6 0x1000 + 5781414
3 com.parallels.desktop 0x00767096 sound_thread::_thread_proc(void*) + 764
4 com.parallels.desktop 0x00766dd9 sound_thread::_thread_proc(void*) + 63
5 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 13:
0 libSystem.B.dylib 0x900492e7 semaphore_timedwait_signal_trap + 7
1 com.apple.audio.CoreAudio 0x91465a10 CAGuard::WaitFor(unsigned long long) + 212
2 com.apple.audio.CoreAudio 0x91465932 CAGuard::WaitUntil(unsigned long long) + 66
3 com.apple.audio.CoreAudio 0x914643a2 HP_IOThread::WorkLoop() + 690
4 com.apple.audio.CoreAudio 0x914640e9 HP_IOThread::ThreadEntry(HP_IOThread*) + 17
5 com.apple.audio.CoreAudio 0x914586f5 CAPThread::Entry(CAPThread*) + 93
6 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 14:
0 libSystem.B.dylib 0x900251a7 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00583a48 0x1000 + 5777992
2 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
3 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 15:
0 libSystem.B.dylib 0x9000a5c7 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082369a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90834577 CFRunLoopRun + 60
3 com.parallels.desktop 0x003a1c91 0x1000 + 3804305
4 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
5 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 16:
0 libSystem.B.dylib 0x90037ee7 mach_wait_until + 7
1 libSystem.B.dylib 0x9003a652 usleep + 82
2 com.parallels.desktop 0x003a21df 0x1000 + 3805663
3 com.parallels.desktop 0x0030f24a 0x1000 + 3203658
4 libSystem.B.dylib 0x90024b07 _pthread_body + 84

Thread 7 crashed with i386 Thread State:
eax: 0x01c6a1a7 ebx: 0x006a2ddb ecx:0x00000001 edx: 0x00000004
edi: 0xe27b6000 esi: 0xb0322c50 ebp:0xb0322b98 esp: 0xb0322b90
ss: 0x0000002f efl: 0x00010296 eip:0xffff07c7 cs: 0x00000027
ds: 0x0000002f es: 0x0000002f fs:0x00000000 gs: 0x00000037
 
Last edited:
Andrew @ Parallels said:
Thanks - we will see to it! Did anyone else tried Shared Folders in 1892?
Click to expand...

On a further try I could open the folder. BUT when try to open an app which looks for the data files in the shared folder the app stalled forever....

Opening the folder while the app tried to start crashed Parallels again.


So we have a nogo here. Back to problem-free 1862 (on MBP)


UPDATE: reverted to 1862.2 restore VM disk. App opens instantly!!
 
Last edited:
Works here

Andrew @ Parallels said:
Thanks - we will see to it! Did anyone else tried Shared Folders in 1892?
Click to expand...

I just installed 1892 and the Parallels Tools on top of the 1884 installation and so far it works as expected! :)

If I run into any problems I'll let you know. Thanks for the quick turnaround!

Grant Hutchins
Spiceworks
 
shared folders in 1892

Installed 1892 and shared folders are working well. Shared folders failed for me in 1884.
 
1892 seem to work for me

I tested shared folders with my external disk for some minutes. No more faults with build 1892.
1884 failed ever after a few seconds.
 
For all those who say shared folders work, please test to place data files of an app there and then runn the app. (e.g. Thunderbird profiles, Access databases etc etc).

On my system I could browse the folders BUT data intense operations (apps accessing files continuously) failed!

It works PERFECTLY in 1862!!
 
1892 still no good here

I just tried with 1892, and I am still getting a very hard crash of Parallels after drilling down about 4 or 5 levels in the shared folder hierarchy in Windows Explorer (XP sp2) on my Mac Book Pro.

With 1884, I would either get that, or a blue screen in Windows.

Also, the first time I tried to start my VM after installing 1892, my system kernel panicked. On restart, Parallels seemd OK.
 
MacBook Pro w/2GB of memory running Win XP SP2...

I'm cautiously optimistic. It seems that Shared Folders are working as expected again. I will continue to test and will let you know.
 
I'm running a development-mode rails website from a network drive mapped to a parallels shared folder, which is filesystem intensive. I am constantly editing files on the Mac side and the Windows side is picking up the changes instantly. It's been running all day through heavy edits, without even restarting the server.

So I think I can safely say that 1892 works great for me.

Grant Hutchins
 
manfredell said:
For all those who say shared folders work, please test to place data files of an app there and then runn the app. (e.g. Thunderbird profiles, Access databases etc etc).

On my system I could browse the folders BUT data intense operations (apps accessing files continuously) failed!

It works PERFECTLY in 1862!!
Click to expand...
I am able to run Outlook 2003 and Access 2003 using datafiles located in shared folders without any problems. My Outlook 2003 'pst' file is in a shared folder and sending, receiving mail, etc so far work fine.
 
1892 on MacPro

Shared folders work, finally!

One exception.

The only Windows program I really use is called Newsbin, used for usenet.

There are small text files ending in an .nzb extension which has a series of instructions as to what files to d/l from what newsgroup.

Newsbin has a feature that it will automatically (every 30 seconds or less) scan a user defined directory for those files, and if found, will automatically read and process the .nzb files.

If I tell Newsbin to look at a directory on my Mac, for the .nzb files, it will never find them. If I tell Newsbin to look for the .nzb files at a directory on a networked machine, it works fine. :confused:

Now of course Newsbin has it's configuration files in a directory on my Mac and that works fine.

Perhaps it's a Newsbin problem, but just figured I would report it. Perhaps others here use programs that have similar functions and they can report back. Perhaps I have confused all of you? :D
 
Works Great...

I downloaded and installed build 1892.

1) Before installing, loaded by 1884 VM, shutdown Windows, and disabled Shared Folders, then saved the configuration and quit.
2) Installed build 1892.
3) Launched PW and tried to start the VM -- got 2 error messages. One non-fatal about the network adapter, the second a "critical" on about en-2. My VM was set to use host-only networking. I then realized the PW DHCP server probably needed to be reset. Rebooting the MacBookPro solved both problems and got rid of the errors.
NOTE: I would recommend that PW suggest that the user reboots the machine after upgrading. This could save problems later if user changed to host-only networking but has not rebooted the machine since the upgrade.
4) I then successfully launced the VM. The first boot was slow. I immediately installed the new Tools and rebooted Windows. Second boot much, much faster.
5) Once I confirmed that the VM started with no problems, I quit Windows again, went to PW configuration and re-enabled the Shared Folders.
6) Launched Windows and tested. All is well. I ran a cleint-server database off of a Shared directory using Access 2003 with zero problems.

All looks good here! :)

I would highly recommend rebooting of the Mac aftering installing the updates. This should be made manditory in the installer. I suspect some of the problems encountered is that older services remain running and are incompatible with the newer version.
 
manfredell said:
For all those who say shared folders work, please test to place data files of an app there and then runn the app. (e.g. Thunderbird profiles, Access databases etc etc).

On my system I could browse the folders BUT data intense operations (apps accessing files continuously) failed!

It works PERFECTLY in 1862!!
Click to expand...


manfredell is correct. I installed the new build and yes you can see your folders, but if you try to use a program that uses the data files located on these shared drives, the data is inaccessable. It doesn't work. In addition some of the files not locted directly in your root directly may not be accessable as well. Don't assume it is working because you can view the directory. Build 1862 was working great.
 
mqandil said:
manfredell is correct. I installed the new build and yes you can see your folders, but if you try to use a program that uses the data files located on these shared drives, the data is inaccessable. It doesn't work. In addition some of the files not locted directly in your root directly may not be accessable as well. Don't assume it is working because you can view the directory. Build 1862 was working great.
Click to expand...


Thanks for the head up on this! I've certainly tried all I could. And at first look it seems to work BUT when you really use it, it breaks.

If others are not having these problems at least this shows that it is working inconsistently...
 
You must log in or register to reply here.
Back
Top