Error upgrading to 5600

Still present here. I had this for the last few weeks, and had given up on the hasle of manually upgrading parallels.

Unfortunately, it runs worse and worse on my machine (MBPro, tiger), so I want to see if an upgrade may fix it (fat chance, upgrades never fixed anything) and downloaded the dmg manually from dd1.parallels.com

The corrupted file is 92217344 bytes long, and its md5 is 92673b1e4d421b407d69342adb424019

The correct file is 92219354 bytes long, with an md5 of 74a14a5f611d3f225c39c8a96bd57db4

I suggest that parallels should take notice that failing to add any kind of CRC control to an automatic update is very very dumb. Even checking just the size of the download would be enough.


Now, if I were you, I wouldn't waste my and other's time by pretending to "check with ISPs" and all. The auto-downloader in Parallels checks the following URL:

http://download.parallels.com/v3/en/updater.ini

which in turn tells parallels to download from http://download.parallels.com/v3/en/GA/Parallels-Desktop-5608-Mac-en.dmg

Such a download work perfectly well with wget, I checked that, thank you.


The issue is in the Parallels update code. Knowing that 92217344 is exactly 11257*2^13 and that the first 92217344 bytes of the correct file match the corrupted one, it doesn't take a lot of time to see that the issue is whith the last read.

Please fix that. Having a broken update reflects very badly on the general quality of parallels.

Hint: http://download.parallels.com/v3/en/updater.ini seems the perfect place to add the CRC to check the correctness of the download.

 

yes, as I mentioned on another threads we are checking problem and found several issues from both sides , and we are working to correct them,
Thank you for checksum idea, we will discuss this, and probably will implement

 

Thank you f54280.

I wish Parallels Team would've been as diligent and competent at identifying and stating the problem.
Unfortunately, the problem reveals too much amateurism from Parallels developers for my taste.

 

fixed

thanks for the suggestions,
i am not a computer s/w or h/w literate guy but after having got beachballed and disk not mounted/recognized errors with the auto updates, multiple times for the last 2months, i tried today to install the trial version from the downloads section of the parallels website to see if it was a dmg problem. Guess what the trial version installed perfectly and UPgraded my existing s/w and recognized the license key etc etc and things are back to nml again!

 

Update 5608 Failed

Beach ball after multiple attempts to update for over a month. Restarting only fixes problem temporarily. Any suggestions would be greatly appreciated. I have the screen flickering problem as well.

iMac 10.5.5; 2.4 ghz, 4 gig ram, parallels build 5600 3.0 desktop for Mac, running windows XP home edition service pack 3

 

http://download.parallels.com/v3/en/GA/Parallels-Desktop-5608-Mac-en.dmg

and reinstall Parallels Desktop as described in kb
http://kb.parallels.com/en/4790

Performance problem:
1. Set memory for Virtual Machine to less than 1 GB
2. Perform Mac and Windows side disk defragmentation http://www.xvsxp.com/system/system_tools_defrag.php
3. Set Adjust memory limit from Auto to Manual at Parallels Desktop -Preferences-Memory, and set limit a bit more higher than VM memory
4. Disable Themes in Windows XP serives.msc stop Themes service
5. If you are running in Coherence, try to switch to Single Window, or lower Mac resolution
6. Some antivirus software can load CPU when Heuristic Prediction is set, or Tamper protection (Symantec, MacAffey), adjust settings to risk you are supposed, high security settings is not always good idea, as it can also affect software running
7. Run msconfig , and disable unneeded startup items
See http://www.netsquirrel.com/msconfig/msconfig_xp.html
8. Make sure that no VNC,or remote desktop connection is established to Mac, this can slowdown Parallels Desktop
9. Optimize computer experience for best performance
10. Make sure that at least 1.25 GB of Memory is free for Mac OS (it is Total Memory - Virtual Machine Memory)
11. Make sure that at least 2 GB +Virtual Machine assigned memory *2 is available on Mac OS partition where VM is located

 

Considering an Upgrade to Build 5608

Been running Parallels 3.0 (Build 5160) since July 2008. Regularly experience problems, such as inability to log out from Windows XP causing me to "Force Quit." Also receive messages that read, "..Please shut or Halt your computer by turning off the power and restarting..." This message appears in several languages and takes hold of the OS so that your only recourse is to power down the MacBook. I have upgraded my memory to 4.0 GB and manually adjusted my memory settings accordingly. My thought was to upgrade to Build 5608, but after reading all of these posts, I'm concerned that I will encounter serious problems and lose everything that I installed under the Parallels VM. What level of assurance, if any, can Parallels provide me that the upgrade to Build 5608 will proceed smoothly. Incidentally, I am running Mac OS X 10.5.3.

 

Stop dragging your feet and upgrade Parallels to 5608, and OS X to 10.5.5.

 

I was running build 5584 and have requested the 5608 update several times. After every successful download I receive the error message: "not recognized". I downloaded the 5604 .dmg which successfully upgraded my build, then I ran the 5608 .dmg.

Tell your users that this approach should work.