Internal build 1910 for Mac Pro and iMac Core 2 Duo
|
|
|
Sep 23, 2006, 10:15 AM
|
|
|---|---|
 STim Parallels Team Join: Mar 2006 Posts: 831 |
Internal build 1910 for Mac Pro and iMac Core 2 Duo Hello everyone, We are continuing our efforts to deliver a Parallels Desktop for Mac version that fully supports Mac Pro and iMac Core 2 Duo. There's an updated internal build that is available for early testing which can be downloaded from here. Please don't forget to backup any sensitive data on your Mac before proceeding to evaluation. This version introduces a number of important fixes: * VM crash on restart on huge memory MacPros in VT-x mode. * Several VMs simultaneous work. * Win98 guest 100% CPU usage * WinNT not being able to start fix * Several other fixes We're still extremely interested in your feedback about this build and any issues you might face. Best regards, Tim |
|
Sep 23, 2006, 10:32 AM
|
|
|---|---|
awilliamsny Junior Member Join: Sep 2006 Posts: 9 |
Sweet! Mac Pro here, 3ghz, 4gb RAM. Was running 1848, installed 1910 over it, and it works beautifully. No KPs, tools work, nicely done, ||s :) |
|
Sep 23, 2006, 11:25 AM
|
|
|---|---|
thorby Member Join: Sep 2006 Posts: 33 |
Quick Start Guide broken In the 1910 .dmg the Parallels Desktop for Mac Quick Start Guide.pdf file produces an error message when you try to open it. Preview.app says "File Error. Couldn't open the file" Adobe Acrobat Reader 7 says "There was an error opening this document. The file is damaged and could not be repaired." The full User Guide.pdf opens correctly. Also, the Quick Start .pdf from build 1908 opens correctly. |
|
Sep 23, 2006, 11:42 AM
|
|
|---|---|
pastrychef Junior Member Join: Sep 2006 Posts: 27 |
So far, so good!!! One question, though... Do I need to re-install Parallels Tools after Windows boots up? Thanks for the great work!!! __________________ Mac Pro 3GHz. 5GB. ATI X1900. AP+BT. |
|
Sep 23, 2006, 11:48 AM
|
|
|---|---|
pastrychef Junior Member Join: Sep 2006 Posts: 27 |
By the way, DVD Shrink seems to be working now, too! :) Ooops... Spoke too soon... Worked with one disc and not the other... __________________ Mac Pro 3GHz. 5GB. ATI X1900. AP+BT. |
|
Sep 23, 2006, 02:44 PM
|
||
|---|---|---|
BlueSkyISdotCOM Member Join: Aug 2006 Posts: 67 |
Quote:
Mac Pro 2.66 Ghz 3 GB RAM. So far, so good. I didn't have any problems with 1908, except for the disabled VT-X. I haven't seen that message yet, so maybe that is fixed too. My method: 1. Download Parallels 2. Use downloaded uninstaller to uninstall previous version 3. Install new version 4. Start new version (got the warning to reboot my mac, which I did and returned to this step) 5. Start existing Win XP SP2 VM 6. Immediately install Parallels Tools and reboot VM. |
|
|
Sep 23, 2006, 02:58 PM
|
|
|---|---|
SiskoKid Junior Member Join: Sep 2006 Posts: 28 |
Ok, I didn't do all the necessary steps because I was in a hurry. By that I mean, I didn't uninstall, restart, install, restart etc. So I used it again and it crashed but this is what Activity Monitor said: Parallels not responding - CPU % 2.20 - #Threads 16 - Real Memory 75.04MB - Virtual Memory 2.25GB - Kind Intel Read In: 47151 Read Out: 18075 Data Read: 828.82 MB Data Written: 276.63MB 41 IO/sec I'm gonna go through the whole process of uninstalling, but does that tell you guys anything so far? BRB in a few. |
|
Sep 23, 2006, 11:53 AM
|
|
|---|---|
WickDC Junior Member Join: Sep 2006 Posts: 9 |
Upgraded from 1898 (working fine except for the memory reduction). Reinstalled Parallel Tools fine in XP Pro, no problems at all except the Quick Start Guide PDF has an error as mentioned above. Memory is back up to 2GB from 1.95GB with 1898. Mac Pro 3Ghz, 2GB, AP+BT |
|
Sep 23, 2006, 12:12 PM
|
|
|---|---|
thorby Member Join: Sep 2006 Posts: 33 |
"poof" - no improvement from 1908 I did the uninstall - install 1910 thing and launched the WinXP VM I described in this post. Just as before the VM starts, shows the initial Win splash screen, expands to the desired window resolution but before it can display anything else, it vanishes and we are back to the property display. As before no message or diagnostic, and nothing in the os x console window. This is the last time I'm gonna offer: I'd be happy to download a trace-enabled version or do any other kind of debugging you want that would get some traction on this problem which MAKES PARALLELS USELESS TO ME. Sorry, patience running a little thin there... or if you want I can quote the .pvs file here, or whatever would help. I have the developer tools installed... let me just add, the only thing I can think of that would make my setup any different from typical is, both the .pvs file and the .hdd virtual disk are on a different volume (on a different physical drive) from the volume that contains /Applications and /Users. So not in the usual default location in ~/Documents. |
|
Sep 23, 2006, 12:30 PM
|
|
|---|---|
controller Junior Member Join: Apr 2006 Posts: 20 |
I am having no problems with 1910 either on my Mac Pro 2.66 x1900 w/4GB of RAM (all RAM active.) I installed right over 1908. I even ran Vista RC1 57xx and XP at the same time with no issues. My PVS file is on my main drive, but my HDDs are on another drive. I have yet to see the crashes when restarting VMs that I saw before, but it is still too early to tell. Nice work so far! One bug: Running a VM sets my Mac's volume pretty high. I have to manually turn it down. |
|
Sep 23, 2006, 01:27 PM
|
||
|---|---|---|
kgregc Member Join: Sep 2006 Posts: 73 |
Quote:
|
|
|
Sep 23, 2006, 05:40 PM
|
||
|---|---|---|
artpease Junior Member Join: Aug 2006 Posts: 9 |
"poof" - no improvement from 1908 Quote:
I had the same "poof" that you describe, except it was the BIOS splash screen that returned to the Parallels Property Screen. It started in 1892 after the reboot of a Windows Update that crashed everything. There was nothing that I could do to get that VM running again. When Parallels released 1898, I uninstalled 1892 and installed 1898 and the result was the same "poof" with that VM. The exact same think happed with 1908, but others were running 1908 fine. I finally decided that the VM was hopelessly trashed. I didn't want to rebuild it because it had a lot of software installed. The build of a new VM under 1908 went just fine along with all of my other software and all of the Windows and Office updates. Sometimes you just need to start over with Beta software. I think you need to give up on your VM. It may also be hopelessly trashed. Art |
|
|
Sep 23, 2006, 09:02 PM
|
|
|---|---|
spullara Junior Member Join: Apr 2006 Posts: 28 |
I uninstalled and reinstalled 1910. I created a new set of VM settings and pointed it at an old install of WinXP and it crashed the computer most of the way through the boot up sequence. No reported KP just a freeze. Are most of the people on here installing from scratch? |
|
Sep 24, 2006, 02:22 PM
|
||
|---|---|---|
webdeck Junior Member Join: Aug 2006 Posts: 21 |
Quote:
|
|
|
Sep 24, 2006, 02:13 PM
|
||
|---|---|---|
thorby Member Join: Sep 2006 Posts: 33 |
Quote:
* I have an Ubuntu VM that has twice "poofed" but most of the time comes up and runs. * The WinXP VM never crashed on its own, it was running fine thru several Windows reboots and Parallels launches before it started "poofing". The first time it vanished was after Win had come up and was setting up my "personal settings". The next time and every succeeding time, it is very early in boot -- early enough that the next time, Win doesn't know it failed to come up (doesn't offer "safe mode"). Then there's the question, What exactly would be "trashed"? Either the contents of the .hdd, or the contents of the .pvs. The .pvs file is editable. In the prior build I made a new Win VM (this one) and while it was working, I used BBEdit to compare its .pvs to the .pvs of a previous Win VM that poofed every time up. There was only one diff, I think it was Enable write-back disk cache, and I changed the old bad one to match the new, then-good one, and it still failed. So it wasn't the .pvs. Now I'm trying to imagine what Parallels (or Windows) could have done to the contents of the hdd such that Windows would not crash but the emulator just stops with no message of any kind from either Windows or Parallels. If Windows is corrupted, it would produce some kind of diagnostic, if only a BSOD. Or maybe it would loop or hang but in any case, the VM display screen would remain! And this magical disk corruption, with Ubuntu sometimes fails and sometimes doesn't. Thus I just don't think that .hdd corruption is a credible explanation. To me the explanation is a bug in Parallels itself, probably a wild memory store, that makes it erroneously think the VM has halted or that the user has clicked the red button. That's the only way I see to account for no message of any kind -- which to me is the most significant symptom of the whole thing! (The dog that didn't howl in the nighttime...) I think there's a software flag "VM is running" and somehow it is getting set to "false" and so Parallels just cleans up and stops. Speculatively, maybe it gets hit based on the value of some random location in the VM's memory -- which would explain why a Win VM will run great until one day it changes the magic bytes of its disk image to some innocent value that triggers the Parallels bug. And from then on, it poofs. |
|
« Previous Thread | Next Thread »
| Search this thread | Forum jump |
|---|---|
| Thread tools | Display modes |
|---|---|
|
Hybrid Mode
|