Parallels Desktop for Mac build 3094 Beta 2 is available for download.

General issues with Vista in Parallels build 3094

I have tried both Vista Business and Vista Ultimate and both have the same issues:-

1. Stability
After a new install Vista is set to goto sleep (standby mode) after 20mins. On clicking start in the Parallels menu Vista starts running again. But it does not always come out of standby.
Of course there is no need to have standby mode enabled in the VM but i am sure when Vista enters standby they will think the VM has locked up.

2. Time syncronization does not always seem to work.
I am running Vista in Coherence mode and will just shut the lid on my MacBook Pro. On opening the lid the mac comes back alive but Vista's clock is still working from the time that i closed the lid on the MacBook Pro. Every morning i have to go into Visa and resynch the time with the windows timeserver.
Paralells tools are installed and the time synchronization option is enable.

3. In Coherence mode Parallels get confused!
Sometimes Parallels thinks a window is open in a certian location but it is not really there so i end up seeing a square of the windows desktop being shown.
 
Spanish (Spain) keyboard is not right mapped.

Hi all:

Thanks by that great program. I'm using it six months now (from the firsts betas).
But this beta has not a right keyboard mapping. It is impossible to work with it (I know it is a beta).
Any solution?

Thanks in advance.
 
As for what paco.blasco reports, I find it odd. I happen to use a Spanish keyboard on both my XP Boot Camp installation and my Parallels Vista Ultimate 30-day trial and both work flawlessly on Mac Pro. In any case, I don't think the Parallels team are responsible for any shortcomings in keyboard definitions; those are attributable to Microsoft and Apple. In any case, perhaps paco.blasco uses a MacBook or MacBook Pro. If that is the case, I also happen to know that the keys for <> and ºª\ are swapped. If you want a fix, you have to create a keyboard definition for your own use (there's a Microsoft utility for such things), or, if an email address is provided, or I am suggested an alternative procedure, I can send you the keyboard definition I created.

All the best.
 
Can't use boot camp

And now, with the 3106(?) build, it's smart enough to know that I have the earlier Parallels Tools for BootCamp installed, and it refuses to run.

But I'm faced with the fact that I can't boot into BootCamp anymore. It freezes up around mup.sys. I tried the "repair" function -- the second one, not the Recovery kind -- and now it opens in Windows, and gets stuck about halfway. I can't use Safe Mode, because I've repaired the system, and it wants to run those files and configure them first. I think I'm totally, uh, screwed. I can find the folder, "Parallels Tools for Boot Camp on my Windows partition, but it's read only. I can't just trash it.

Any help would be delightful. My limited Windows expertise is at an end.
 
Beta3 3106 Bootcamp option available, but not supported yet...;-(

- How many HDDs does your Mac have?
MacBook Pro (2,33 GHz Core2Duo), with internal 120 GB HD
- Where is your Boot Camp partition located?
On the 4th partition
- What is the OS installed on Boot Camp exact name and version? Is it 64-bit one or 32-bit one?
XP SP2, 32bit
- open Terminal, issue the "mount" command and post its output here please
/dev/disk0s2 on / (local, journaled)
devfs on /dev (local)
fdesc on /dev (union)
<volfs> on /.vol
/dev/disk0s3 on /Volumes/DATEN_FAT (local)
/dev/disk0s4 on /Volumes/Windows (local, read-only)
automount -nsl [144] on /Network (automounted)
automount -fstab [202] on /automount/Servers (automounted)
automount -static [202] on /automount/static (automounted)
...and diskutil list
/dev/disk0
#: type name size identifier
0: GUID_partition_scheme *111.8 GB disk0
1: EFI 200.0 MB disk0s1
2: Apple_HFS Macintosh HD 31.0 GB disk0s2
3: Microsoft Basic Data DATEN_FAT 31.6 GB disk0s3
4: Microsoft Basic Data Windows 49.0 GB disk0s4
...and the fdisk print
Disk: /dev/rdisk0 geometry: 14593/255/63 [234441648 sectors]
Offset: 0 Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
-----------------------------------------------------------------------
1: EE 0 0 2 - 25 127 14 [ 1 - 409639] <Unknown ID>
2: AF 25 127 15 - 1023 74 10 [ 409640 - 65011712] HFS+
3: 0B 1023 74 11 - 1023 254 63 [ 65421352 - 66247388] Win95 FAT-32
*4: 07 1023 0 1 - 1023 80 63 [ 131668740 - 102772908] HPFS/QNX/AUX

Beta3_3106.jpgis now officially an unsupported setup ;-(...I was hoping that this would be solved in a different way...but there is hope, because they say the current (beta? 3106) version is not supporting this...so which version will support this environment? Until then using Windows with bootcamp in the Apple way on startup...
...or is it possible to do something thru setup?
Anyway keep on the good work...and best regards...
 
any results?

Could you or anyone provide an update on this issue? I have precisely the same problem and it's debilitating. I would appreciate a full response from the Parallels team, but so far nothing forthcoming. :mad:

Any reply would be very much appreciated. Thanks, Tim


BillInSoBe said:
I'm very pleased to say that I'm up and running on the latest version. Not new issues as of yet.

It doesn't look like the Parallels team has made any effort on the issue where you can't configure a VM after you set it to start when you launch Parallels Desktop and Quit on Exit. In case anyone isn't following this, this is a pretty big problem.

How do you modify the configuration on these VMs??? You can't change settings while the VM is running and you can't modify them because Parallels quits when you shutdown the VM. I really hoped something like this would have been fixed in the new build.

We take part in the beta program to alert Parallels to functionality and usability issues. When no action is taken regarding issues it makes people wonder what's the point in participating. AT THE VERY LEAST the Parallels team should create a list of items they are tracking and items that have been fixed in the latest build.

Thanx!
 
Back
Top