howto stop Parallels quits on stop/boots on launch
|
|
|
May 19, 2007, 12:50 PM
|
|
|---|---|
catmistake Junior Member Join: Jun 2006 Posts: 27 |
howto stop Parallels quits on stop/boots on launch This... is driving me... absolutely... nuts. (1) If I double click a pvs file (vm), it launches Parallels. Great. But it also automatically boots the vm. I've set it NOT to auto boot on launch from the configuration editor (under Options/Booting/Start VM automatically when it is opened is UNCHECKED), and it doesn't when I start from Parallels, then load the pvs, but not when I just double-click the pvs file. I don't want it to boot yet because I want to change some something in the configuration editor, which I can't do when the vm is running. (2) So I hit the stop button... and Parallels just quits! ARRRAAGH! That's even more annoying than part (1). How do I prevent the vm from booting when I double click the pvs (again, I've already configured it not to in the editor)? How do I keep Parallels running, and get to the vm configuration, after stopping the vm (if Parallels just quits on stop)? Thanks. |
|
May 20, 2007, 11:40 AM
|
||
|---|---|---|
catmistake Junior Member Join: Jun 2006 Posts: 27 |
Quote:
Regardless of how you open the VM, it should abide by the settings you make in the VM config. Namely, if you set it not to automatically boot, then it shouldn't. |
|
|
May 23, 2007, 10:06 PM
|
|
|---|---|
catmistake Junior Member Join: Jun 2006 Posts: 27 |
Thanks. Sorry. Too... much .... coffee... |
|
Jun 16, 2007, 04:17 PM
|
||
|---|---|---|
wingdo Senior Member Join: Nov 2006 Posts: 291 |
Quote:
__________________ 2.33GHz C2D MacBook Pro 3GB Ram OS X 10.4.9 XP SP2 Guest OS 768MB RAM, 32GB plain HD Vista Guest OS 1GB RAM, 16GB Expandable HD |
|
|
Jun 16, 2007, 05:38 PM
|
||
|---|---|---|
coumerelli Junior Member Join: Jan 2007 Posts: 6 |
Quote:
wingdo, I think more inline with what catmistake is saying, it seems many people (including me, obviously) think of the "VM Configuration" screen as the preverbal word document, and 'auto starting' as a macro. In word, you can say DON'T RUN MACROS, BUDDY!" and it won't. But you can later if you choose. This is true if you double click the document or the App icon and then go to File > Open... Here's another voice requesting that in order to edit a particular config for a VM that it not be required to choose it from first launching Parallels outright. And further, that having launched said vm from double clicking the .pvs file directly, it not quit the Parallels program after shutting down the OS if I've set the preference to not act that way. :) |
|
|
Jun 16, 2007, 06:02 PM
|
|
|---|---|
wingdo Senior Member Join: Nov 2006 Posts: 291 |
I understand your point of view completely. I would not mind seeing Parallels offer a switch allowing the choice of how one wants to run. I ask for a switch because I use the *.pvs file when I want the whole VM to just auto startup and I use the actual parallels application when I need to edit a config before booting. I've always viewed it as double clicking the actual application means 'ok, let's go and play around a bit' and double clicking the VM's pvs file as 'ok, i've got work to do, let's run this sucker'. :)
__________________ 2.33GHz C2D MacBook Pro 3GB Ram OS X 10.4.9 XP SP2 Guest OS 768MB RAM, 32GB plain HD Vista Guest OS 1GB RAM, 16GB Expandable HD |
|
May 23, 2007, 11:24 PM
|
||
|---|---|---|
dkp Senior Member Join: May 2006 Posts: 1,415 |
Quote:
|
|
|
Jun 8, 2007, 04:11 AM
|
|
|---|---|
catmistake Junior Member Join: Jun 2006 Posts: 27 |
No... it makes some sense, but not perfect sense. It would make perfect sense if that setting whether to auto-launch the vm on opening the vm (which is a pref tied to the vm not the app) was honored regardless of how the machine was opened, from the app or by double-clicking it. See my metaphor above. Just because I want to open the vm 'document' from the finder doesn't mean that I want to start it. I was already aware that I could get the behavior I want from lauching Parallel's first... the issue is that the behavior is inconsistent when lauching by double-clicking the vm... it should follow its set preference, and not automatically do something ignoring the pref setting. |
|
Jun 9, 2007, 05:11 AM
|
|
|---|---|
TRIX Junior Member Join: Jun 2007 Posts: 2 |
First stop Parallels / VM. Once it is stopped hold down the Apple/Command key while you click on the Icon to launch Parallels. It should boot and stop at the opening screen of the VM so you can now go in and change the auto launch option in the Configuration Editor (CE). Double click Hard Disk 1 or one of the other line items to open the CE. Now click on Options - Booting Tab - and uncheck the box for Start VM automatically when opened. |
|
Jun 9, 2007, 06:31 AM
|
|
|---|---|
 Andrew @ Parallels Parallels Team Join: Apr 2006 Posts: 1,557 |
Guys, It is intended design. When Parallels is started via double click on particular PVS file - it forces autostart and autoclose features. It was done to allow out-of-the box running VM in one click. If you want to edit PVS - you should start Parallels alone and choose appropriate VM from catalogue. __________________ Best Regards, Andrew @ Parallels |
|
Jun 9, 2007, 04:38 PM
|
|
|---|---|
TRIX Junior Member Join: Jun 2007 Posts: 2 |
It's fine that it was an intended design, that's great and this feature functions exactly like what I wanted, but I think you are missing the point. Without reading through the manual an end user would not know how to stop this auto boot / auto close feature once enabled. I enabled it and then went through Hell trying to figure out how to stop it because every time I went to try an edit the VM a warning would come up saying you have to stop the VM in order to edit it. So I would stop the VM and it would completely disappear. I finally had to go to the manual, which I hate doing, to figure out how to stop the auto boot / auto shut down so I could edit the VM. I have no idea what the following statement means: If you want to edit PVS - you should start Parallels alone and choose appropriate VM from catalogue. How do we edit the PVS, what is the PVS, and what is the VM catalogue? Not all end users are up on these terms and what they mean. Instructions are best if they are step by step so that anyone on any level of understanding can follow them step by step. Thank you. |
|
Jun 16, 2007, 12:36 PM
|
||
|---|---|---|
catmistake Junior Member Join: Jun 2006 Posts: 27 |
Quote:
when launching from the pvs file also. Thanks, & sorry I'm too obtuse to read carefully |
|
|
Jun 16, 2007, 03:54 PM
|
|
|---|---|
bgt Junior Member Join: Jun 2007 Posts: 9 |
I'm with you catmistake. Even more annoying is when you're trying to edit a VM's config. You can't without stopping the VM. So you stop it, and Parallels closes, even if the config is set to NOT close Parallels after stopping the VM! This may not be a "bug" because it's intended design, but if that's the case the design is bad. It's totally unintuitive and frustrating to realize you have to have started Parallels via it's app icon (rather than via a VM icon) in order to edit a VM's config. Parallels, maybe you should add a app level preference setting to override this irritating behavior? |
« Previous Thread | Next Thread »
| Search this thread | Forum jump |
|---|---|
| Thread tools | Display modes |
|---|---|
|
Hybrid Mode
|