Parallels Desktop for Mac build 3170 RC3 is available for download.

sjs said:
lindy: Coherence mode makes the desktop look like one large monitor to the guest OS. Differing resolutions make the resolution non-rectangular and hence invalid. I hope they get a multi-display driver going soon because having coherence mode on one monitor only is kind of lame. I have no idea how these releases can really be candidates for release! They are more like tech previews... the betas weren't even feature complete.
Click to expand...

Has anyone heard if they have a multi-display driver in the works? I've never heard a peep about it, other than the complaints during the beta process, and this single-display approach has been there since the first coherence beta. Seems like this would be important given the number of users with multiple displays. I've got a MBP (1440x900) and a 20" cinema (1680x1050) and getting coherence working across both is the single biggest reason I want to upgrade. But not yet. I'll stick with 1970 for now.

Mark
 
It must my imagination became Parallels didn't mention it. However I swear that the build 3170 has crisper graphics or something.

Last night I ran 3170 nonstop for about an hour, and I could see little details that I never saw before.

To me that finally the version 2.5 is 99% done. I give Parallels another week or so to come with build 3180 the final version, AT LAST! :)
 
Last edited:
sjs said:
lindy: Coherence mode makes the desktop look like one large monitor to the guest OS. Differing resolutions make the resolution non-rectangular and hence invalid. I hope they get a multi-display driver going soon because having coherence mode on one monitor only is kind of lame. I have no idea how these releases can really be candidates for release! They are more like tech previews... the betas weren't even feature complete.
Click to expand...


I disagree, even when I have both displays at the SAME resolution I get the same error from parallels. Currently coherence only works effectively on one monitor (side by side) and 2 monitors top/bottom. Even with differing resolutions.

Side by side is what I prefer.


Which is sheer annoying... Great feature that is limited.

I am sure they know about it, make more noise so it will be on the top of the to do list. LOL.
 
Last edited:
Honestly I'd rather not that be on the top of their list. Coherence works, albeit limited on two screens. Other stuff needs their attention far more.
 
install fails

I get the same result as the last build. The new 3170 build launches, then wants to build a virtual machine. It doesn't seem to see the existing WinXP VM.

Reinstalling the current release version brings up the VM no problem.
 
jcwelch said:
Anyone tried this with Boot Camp running Vista yet?
Click to expand...

I'm really looking for this support, too. Any word on whether RC3 supports Vista Bootcamp partiontions? My guess is no, or that'd be listed in the features.

Please, Parallels, can you add this soon?
 
3170 CRASHING in less then 24 hours.

Apparently Parallels hasn't found the issue with Parallels CRASHING. Build 3170 crashed in less then 24 hours taking all of my work with it.

Here's a copy of the Problem Report (also emailed to [email protected]). Let's see if they can manage to fix it this time.

--------------------

Date/Time: 2007-02-16 15:44:00.923 -0500
OS Version: 10.4.8 (Build 8L2127)
Report Version: 4

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

Version: 2.5 (2.5 Build 3170.0)

PID: 6101
Thread: 8

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

Thread 0:
0 libSystem.B.dylib 0x90009857 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.parallels.desktop 0x0054e765 0x1000 + 5560165
4 com.parallels.desktop 0x004e3d3b 0x1000 + 5123387
5 com.parallels.desktop 0x004e3e54 0x1000 + 5123668
6 com.parallels.desktop 0x00302edd 0x1000 + 3153629
7 com.parallels.desktop 0x00040e9b 0x1000 + 261787
8 com.parallels.desktop 0x00006792 0x1000 + 22418
9 com.parallels.desktop 0x000066b9 0x1000 + 22201

Thread 1:
0 libSystem.B.dylib 0x90009857 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.apple.audio.CoreAudio 0x9145c8da HALRunLoop::OwnThread(void*) + 158
4 com.apple.audio.CoreAudio 0x9145c6f5 CAPThread::Entry(CAPThread*) + 93
5 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 2:
0 libSystem.B.dylib 0x90048a47 semaphore_timedwait_signal_trap + 7
1 com.parallels.desktop 0x003ce3f2 0x1000 + 3986418
2 com.parallels.desktop 0x003cec9a 0x1000 + 3988634
3 com.parallels.desktop 0x00333006 0x1000 + 3350534
4 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 3:
0 libSystem.B.dylib 0x90037697 mach_wait_until + 7
1 libSystem.B.dylib 0x90039d62 usleep + 82
2 com.parallels.desktop 0x00591f66 0x1000 + 5836646
3 com.parallels.desktop 0x00594e5a 0x1000 + 5848666
4 com.parallels.desktop 0x003b9326 0x1000 + 3900198
5 com.parallels.desktop 0x00333006 0x1000 + 3350534
6 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 4:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00595178 0x1000 + 5849464
2 com.parallels.desktop 0x00333006 0x1000 + 3350534
3 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 5:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00595178 0x1000 + 5849464
2 com.parallels.desktop 0x00333006 0x1000 + 3350534
3 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 6:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00595178 0x1000 + 5849464
2 com.parallels.desktop 0x00333006 0x1000 + 3350534
3 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 7:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00595178 0x1000 + 5849464
2 com.parallels.desktop 0x00333006 0x1000 + 3350534
3 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 8 Crashed:
0 <<00000000>> 0xffff0897 __memcpy + 247 (cpu_capabilities.h:228)
1 com.parallels.desktop 0x0068ca68 0x1000 + 6863464
2 com.parallels.desktop 0x005a1d75 0x1000 + 5901685
3 com.parallels.desktop 0x005a2553 0x1000 + 5903699
4 com.parallels.desktop 0x00858594 QList<TGDev>::append(TGDev const&) + 212
5 com.parallels.desktop 0x00661911 0x1000 + 6686993
6 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 9:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x00595178 0x1000 + 5849464
2 com.parallels.desktop 0x00333006 0x1000 + 3350534
3 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 10:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 ...ple.CoreServices.CarbonCore 0x90cb4129 MPWaitOnQueue + 198
2 com.parallels.desktop 0x00661ada 0x1000 + 6687450
3 com.parallels.desktop 0x005a252b 0x1000 + 5903659
4 com.parallels.desktop 0x00858594 QList<TGDev>::append(TGDev const&) + 212
5 com.parallels.desktop 0x00661911 0x1000 + 6686993
6 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 11:
0 libSystem.B.dylib 0x90009857 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x9083a577 CFRunLoopRun + 60
3 com.parallels.desktop 0x003b863c 0x1000 + 3896892
4 com.parallels.desktop 0x00333006 0x1000 + 3350534
5 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 12:
0 libSystem.B.dylib 0x90037697 mach_wait_until + 7
1 libSystem.B.dylib 0x90039d62 usleep + 82
2 com.parallels.desktop 0x003b9241 0x1000 + 3899969
3 com.parallels.desktop 0x00333006 0x1000 + 3350534
4 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 13:
0 libSystem.B.dylib 0x90048a47 semaphore_timedwait_signal_trap + 7
1 com.apple.audio.CoreAudio 0x91469a10 CAGuard::WaitFor(unsigned long long) + 212
2 com.apple.audio.CoreAudio 0x91469932 CAGuard::WaitUntil(unsigned long long) + 66
3 com.apple.audio.CoreAudio 0x914683a2 HP_IOThread::WorkLoop() + 690
4 com.apple.audio.CoreAudio 0x914680e9 HP_IOThread::ThreadEntry(HP_IOThread*) + 17
5 com.apple.audio.CoreAudio 0x9145c6f5 CAPThread::Entry(CAPThread*) + 93
6 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 14:
0 libSystem.B.dylib 0x90048a47 semaphore_timedwait_signal_trap + 7
1 com.apple.audio.CoreAudio 0x91469a10 CAGuard::WaitFor(unsigned long long) + 212
2 com.apple.audio.CoreAudio 0x91469932 CAGuard::WaitUntil(unsigned long long) + 66
3 com.apple.audio.CoreAudio 0x914683a2 HP_IOThread::WorkLoop() + 690
4 com.apple.audio.CoreAudio 0x914680e9 HP_IOThread::ThreadEntry(HP_IOThread*) + 17
5 com.apple.audio.CoreAudio 0x9145c6f5 CAPThread::Entry(CAPThread*) + 93
6 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 8 crashed with X86 Thread State (32-bit):
eax: 0x0001363a ebx: 0x90023d44 ecx: 0x0000003a edx: 0xffff0a00
edi: 0x16a09600 esi: 0x0977411d ebp: 0xb03a3e78 esp: 0xb03a3e70
ss: 0x0000001f efl: 0x00010286 eip: 0xffff0897 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037


Model: MacBookPro1,1, BootROM MBP11.0055.B08, 2 processors, Intel Core Duo, 2 GHz, 2 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86), 0.1.30
Bluetooth: Version 1.7.9f12, 2 service, 1 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
Network Service: Parallels Host-Guest, Ethernet, en2
Network Service: Parallels NAT, Ethernet, en3
Serial ATA Device: ST910021AS, 93.16 GB
Parallel ATA Device: MATSHITADVD-R UJ-857
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
 
Vista upgrade still does not work

Under 3170 I still get the ACPI error when trying to upgrade to Vista. This has been solved on another thread, by reinstalling XP, which creates some new .dll files, and then by renaming the hal files, so it can be done; but the release notes for 3170 seemed to indicate that the problem had been resolved--seems not, at least for me.
 
Apple USB Modem

In 3150 I could attach to the modem but got on static (like others). Now, with 3170 I can't attached to the modem. I always get the message

USB device you are trying to connect to the virtual machine is being used by another application. Close that application or unplug the device and plug it again. Then try to connect the device again.


I do an 'lsof | grep -i modem' and only see the Apple kext with attachement to the modem.

lsof | grep -i modem
AppleMode 956 scott txt REG 14,2 193588 20862 /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalModemSupport.kext/Contents/Resources/AppleModemOnHold.app/Contents/MacOS/AppleModemOnHold
AppleMode 956 scott 8u unix 0x6c0a550 0t0 /tmp/.modemOnHold

Is there a work around. I've been trying to get this to work since I bought the first beta.
 
Hey BillInSoBe, have you ever considered of saving your VM file and then just deleting all of your Parallels stuff from your HD and re-installing 3170 from scratch and put back your old VM file?

It sounds to me that your Parallels got corrupted somehow maybe.
 
I think since Apple sells a ton of notebooks, being able to use coherence with multiple displays at differing resolutions should be a high priority. Having an external display the same size as the notebook is probably the exception.

I sounded pretty upset about the whole beta/RC thing before. I love that the team is pumping out these awesome new features, and I really appreciate that they are all free upgrades for existing customers. I just can't wrap my head around how they name the releases. I think I came off as a jerk, sorry about that.
 
Bad sound and video under RC3

I have windows vista business edition and macbook with 2Ghz and 2Gb. I still have the same problem of glitchy video and sound that i had in Rc2. I expected such major stuff to be fixed with a release candidate.
 
Why Windows Vista??

Since we all know when Microsoft releases a NEW operating system it usually takes till at least SP1 before they have it right. It seems there are a lot of complaints about Vista. Why not stick with XP or older versions for now since they seem to WORK. In time I'm sure Parallels will have it so it works with Vista. Microsoft is STILL having problems with Vista so use and enjoy what you have and quite complaining about Vista. If you REALLY need Vista, Buy a PC. Lets give the Parallels Team a Brake and a Hats off for the work that has BEEN DONE. Just my 2 cents....... JIM
PS..... Good JOB Parallels Team :D
 
dkp said:
Bill - I wouldn't discount bad memory, yet.
Click to expand...

I don't have any problems if I'm not running Parallels. Parallels is crashing not the whole system. This isn't a Kernel panic. It's Parallels shutting down unexpectedly.

I've had a system with bad memory and have seen how it effects applications. This doesn't seem the same. Granted... I don't understand what's happening in that Crash dump. Perhaps someone could read and explain.
 
The only thing that stands out is CoreAudio in that error report.

I havnt had your crashing issue. It seems like it is localized. How far from standard is your system?? Any 3rd party audio drivers, etc....

Coherence is my issue. I need to use 2 monitors side by side. I trade stocks and find it grossly annoying to be trapped on one screen or have to remind myself that the screen to my right is actually beneath me. So I;d prefer it at the top of their list. I dont have any other issues with paralles. I run both XP and Vista, and life is good.

I can even run Vista on one screen and XP on the other in coherence mode (concurrently) and I dont have issues.
 
wael said:
I have windows vista business edition and macbook with 2Ghz and 2Gb. I still have the same problem of glitchy video and sound that i had in Rc2. I expected such major stuff to be fixed with a release candidate.
Click to expand...


Play around with your memory needs. I adjusted mine to the bare minimum and turned off that crappy windows gui. I put it in classic mode and I get no glitches. Also launch activity monitor in OS X to view what type of CPU useage you are getting. Finally, I keep my Windows partitions on an external HD. Keeps the hogging down.

Vista in full graphics mode is a SERIOUS processor hog. Better to almost run it in bootcamp if the visuals are grossly important to you, instead of trying to have your MacBook run 2 OS's.

You have 2 major thing going against you... It's called a 5400rpm Hard Drive. These OS's run best with a 7200rpm or higher. (due to all the hard disc access)
 
Last edited:
Stevamundo said:
Hey BillInSoBe, have you ever considered of saving your VM file and then just deleting all of your Parallels stuff from your HD and re-installing 3170 from scratch and put back your old VM file?

It sounds to me that your Parallels got corrupted somehow maybe.
Click to expand...

I did an uninstall before installing 3170. Would be nice to hear from someone from Parallels... they should be able to look at that crash report and figure out what's going on.

Of course since they don't respond to messages I'll never know.
 
tlxreed said:
I get the same result as the last build. The new 3170 build launches, then wants to build a virtual machine. It doesn't seem to see the existing WinXP VM.

Reinstalling the current release version brings up the VM no problem.
Click to expand...


Sorry to say I havent had that problem, from 3120 to 3150 to 3170 it has flawlessly seen all my existing VM's

These sound like preference issues. Or shutting the VM off without allowing windows to shut down. After all you are not supposed to be in suspend mode when you do an update.
 
You must log in or register to reply here.
Back
Top