Are there any guidelines regarding when it'd be better to shut down the VM (via Start / Turn Off) vs. just closing and suspending the VM? It seems to take a lot less time to start the VM if it's suspended - presumably because it doesn't have to go through all the boot logic. So is that the preferred strategy? Are there times when you'd want to go through the Windows shutdown process?
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
When to suspend vs. when to shut down?
- Thread starter jgarbers
- Start date
I hope someone with knowledge on this topic replies to this post. To avoid problems, I’ve routinely shut down Windows, and rebooted it when I need it again -- a process that in some instances I wind up repeating several times a day.
I’ve avoided “suspend†for two reasons: (1) I really don’t quite understand it, or the ramifications of using it consistently; (2) I use Windows only because of my job, and it’s mission-critical. I absolutely can’t have unexpected behavior that I can’t solve very, very quickly.
Still, I’d very much like to (safely) speed up my process, and thus would love if someone could shed some light on all this!
Thanks.
------
What I’m Using:
Leopard 10.5.2
Parallels Build 5584
3 GB Ram
Windows XP2
I’ve avoided “suspend†for two reasons: (1) I really don’t quite understand it, or the ramifications of using it consistently; (2) I use Windows only because of my job, and it’s mission-critical. I absolutely can’t have unexpected behavior that I can’t solve very, very quickly.
Still, I’d very much like to (safely) speed up my process, and thus would love if someone could shed some light on all this!
Thanks.
------
What I’m Using:
Leopard 10.5.2
Parallels Build 5584
3 GB Ram
Windows XP2
I use suspend feature almost every day with no problem at all, besides the UNMOUNTABLE_BOOT_VOLUME problem after a ForceQuit or a powerdown.
I also use this VM as a mission-critical part of my work. What I did to avoid downtime was to create a separate disk to store my data, and made a copy in DVD of my "system" disk. This way, every time Windows get screwed, I just have to restore my backup and get back in bussines in 30min or so.
I also use this VM as a mission-critical part of my work. What I did to avoid downtime was to create a separate disk to store my data, and made a copy in DVD of my "system" disk. This way, every time Windows get screwed, I just have to restore my backup and get back in bussines in 30min or so.
I use suspend feature almost every day with no problem at all, besides the UNMOUNTABLE_BOOT_VOLUME problem after a ForceQuit or a powerdown.
I also use this VM as a mission-critical part of my work. What I did to avoid downtime was to create a separate disk to store my data, and made a copy in DVD of my "system" disk. This way, every time Windows get screwed, I just have to restore my backup and get back in bussines in 30min or so.
Victor Espina
Leopard 10.5.2
Parallels Build 5582
3 GB RAM
Windows XP SP2, 512 MB RAM
I also use this VM as a mission-critical part of my work. What I did to avoid downtime was to create a separate disk to store my data, and made a copy in DVD of my "system" disk. This way, every time Windows get screwed, I just have to restore my backup and get back in bussines in 30min or so.
Victor Espina
Leopard 10.5.2
Parallels Build 5582
3 GB RAM
Windows XP SP2, 512 MB RAM