really need help please!

Ok, I really have some annoying problems:

-I'm running 5160 on my bootcamp partition (leopard 10.5.1 / windows XP pro; Imac 20", 2.4, 3 GB)-

1a. When I only use Boot Camp, I cannot access the shared parallels folder: (in dutch) "\\.psf is not accesible. You don't have rights..."

1b. The software I installed perfectly in parallels -for instance Corel- is in BC now asking for registration and activation -I have to install it all over again, cause it's says my evaluation version is over. (I bought the damn thing) When I do that everything's fine again, but when I switch over to parallels, the software doesn't work anymore, again it's asking for activation/registration. And vice versa it goes:
Installing software in BC I only can use in BC -not in parallels and installing software in parr. I only can use in parr., not in BC -I just can't work like this!

2. Running parallels coherence I cannot open a windowsfile in a mac application:
'to use your windows files directly in Mac you should reinstall parallels Desktop'.
-I can however, open a mac file in a windows application.- ...This problem has already been posted, but with no answer from the paralells team.
[and yes, I have the latest macFuse and 'connected server is checked']

please, can someone help me solve these issues?
thanks a lot

 

ad 2. I mean this thread:
http://forum.parallels.com/showthread.php?t=17760&highlight=error+you+should+reinstall+parallels+desktop

please can someone from the parallels team reply?

 

Hello,

1a. could you please specify - do you use Bootcamp natively or you run a Bootcamp partition in Parallels?

1b. it seems that software is hardware changes sensitive so it sees the difference in configuration between BC and Parallels and requires reactivation. So it's the unavoidable cost of using two different configuration I think.

2. Please, try to reinstall Parallels Tools. Will it help?

Best regards,
Alicia.

 

Hi, thanx for the quick reply

re1a+b. I wrote: -I'm running 5160 on my bootcamp partition (leopard 10.5.1 / windows XP pro; Imac 20", 2.4, 3 GB)-
The whole idea of using the BC partition is so you can have it both ways: natively and through parallels. Why else using the BC partition in the first place? Now it's useless because I cannot run my software properly. I expect when I install software in Boot Camp, -so I have it on my hard disk- Parallels recognize it (it uses the BC partition); I don't need different configuration-issues. Again: why using the BC partition for parallels otherwise?

re2. As several (all) posts (see link above) about this problem tell: that doesn't help.

 

I mean is this phrase, "When I only use Boot Camp, I cannot access the shared parallels folder", implied that it happens while you use bootcamp natively?

As for software reactivation, it is the normal behaviour for it actually because it takes BC and Parallels as different machines. And using just BC is sometimes worthwhile as it doesn't require any secondary software to run Windows.

Have you tried to reinstall Parallels Desktop?

Best regards,
Alicia.

 

thank you again for replying

-yes, that is correct. (happens when I use bc natively). When I am in parrallels I don't have this error.

-ok, so it is the normal behaviour...Can you enlighten me please, because maybe I'm totally misinformed -I have found nothing in any documentation-: what then in heavens name is the adventage of using BC-partition (32 gigs!) for parallels?? If I can't run the software like office 2007 and heavy corel products: have to reinstall this kind of applications over and over again including losing all my preference/configurationsettings?? Are you sure it is not a path-thing, which can be fixed? I mean, parallels behaves well/does recognize for instance my AVG-virusprotection software which I installed in (native) Bootcamp. No signs of taking BC and PD as different machines at all, exactly as it supposes to do...I just want to have a -ONE- (not two or three whatever) working and stable windows xp, rather I boot in with BC or run parallels on mac os.

-reinstalling PD doesn't help (see link posts same problem): cannot open windows files directly in mac.

 

- Parallels Shared Folder is a special feature that allows Windows to communicate with Mac OS; that is why it is nessecary to run Mac OS to use it. While running bootcamp you disable Mac OS. In other words, this feature is available for a running VM, not bootcamp.

- The feature of running a bootcamp partition as a VM was added because of many users requests. Not all software doesn't accept new hardware parameters, but EULA of others are rather strict.

- How exactly do you open files? Clicking them and pressing "Open with..." or running applications and pointing out the path to file?

Best regards,
Alicia.

 

re first part: ..I see. I guess then I honestly don't understand what
'running the BC partition as a VM' means accept
not having to reinstall windows xp and wasting
diskspace for nothing. To me it makes no sense at all
if I can't launch my windows software also natively if I want to.
This is what the feature 'running the BC partition as a VM' implies.
That they work together! Well, they don't at this point.
It looks like I'm better of getting rid of/ uninstalling Bootcamp
and run just a general VM with PD? Or is using a BC-partition
for Parallels the better choise; that is: runs more stable, faster,
less buggy etc.? Which option is to be preferred?

re last part: I'm opening files like for example a picture in my pictures:
right click -> open with->





get the error:






Other way around (mac files directly in windows) no problem.

When I open 'applications' I notice smartselect/shared is grey -don't know if it means something-:






I really appreciate your replies, thanks

 

Hello,

for the coherence issue, please, try to stop the VM, open the VM folder (Mac HD->Users->Your username->Documents->Parallels->Your VM folder) and delete the folder "Windows application" there. Then start the VM again and check if it solved the issue.

And as for bootcamp question, there are some functions that are fulfilled in a bootcamp but not in Parallels (DirectX 9 support for example). Then, not all users need so tight integration with MacOS. And when they already have a BC partition, they prefer to use it as a VM.
But in my opinion, if there's no severe need in BC, it's more convenient to simply run a Parallels VM - there's no neccessity to reboot for using Windows.

Best regards,
Alicia.

 

Hi Alicia, thanks again for your reply,
>>I will try that.
In the mean time, is there a solution for this yet?:

 

The Leopard compatible update for Parallels, which is coming very soon (possibly today), has that fixed.

 

That is good news!
thanx

 

Unfortunately, it's not helping... still can't open directly in mac.

 

Please update Parallels and see if it fixes your issues.

 

...is this the official update/fix for 5160? I can't find any info..? Why is it not happily announced by the parr. team, for all off us having trouble with 5160? When I check for updates running parallels auto-update comes up with nothing.
And, if I do, can I install this one savely over my licensed 5160 (no trial) -so it just updates, keeping all my content and settings of all my windows software? -I just installed about 30 plugins, I don't want to do that all over again- *confused*

 

It usually takes about a day before Parallels Desktop will see the update. As for why no one from Parallels is actively promoting the update on the forums yet, I have no idea, but there is a mention of the update on the official Parallels blog. It is meant to be installed directly over build 5160, so you won't lose anything and your Parallels license will still work.

 

thank you, brkirch!

 

No, not working: it says my license is invalid! Had to reinstall 4560 again and then update to 5160 again.

 

AFAIK that will only happen if you are getting a copy of Parallels which has the wrong localization (when your license is for a localization other than US/UK). Assuming that is the problem, you will either need to find the Parallels web page for your localization and download the new build there or wait until the new build shows up in Parallels Desktop's auto update.

 

...you mean I'm from Holland
guess I'll wait for the auto-date; with 5160 update though I managed to install manually, -auto-update then gave me a continue colored ball and I had to close my VM with a forced shut down. Hope this auto-update will work.

thanks for your replies -much appreciated!