-=PCTechTalk=- Re: For Don - Silent Installers
- From: "don101" <don101@xxxxxxxxxx>
- To: <pctechtalk@xxxxxxxxxxxxx>
- Date: Mon, 21 Jan 2008 21:35:36 -0500
Finally got around to the VM again. Started it up. Ran updates, saved
state, rebooted ran update again repeat etc etc about 3 or 4 times to get
all the updates to install. (Remember back in the good old days update used
to tell you certain updates could not be installed unless certain others
were installed first and the system rebooted).
After the last run I I did a save state, started it again and did a shut
down without save. Rebooted and everything is just like you said it would
be.
I've started having some problems with one of my dual boot installations and
need to go take a fresh look at the slipstream I created. Maybe add or take
away a few things. Wednesday is my next day off. With luck I'll have the
time.
As to silent installers... gotta go look at them too. All I gotta do is
remember which website had them... Ryan, Nlite or somewhere else. Good
thing I got a private archive of the group to find such things. :-))
Don
----- Original Message -----
From: "GMan" <gman.pctt@xxxxxxxxx>
To: <pctechtalk@xxxxxxxxxxxxx>
Sent: Tuesday, January 15, 2008 4:57 PM
Subject: -=PCTechTalk=- Re: For Don - Silent Installers
> Don,
> You're getting VERY warm. Shared folders is the place to go, but you
> MUST have the VM Additions extension installed (If you've already
> installed
> them, they only need to be installed once for each VM you create). Also,
> Virtual PC has to know which VM to apply them to. When you first fire up
> VPC, none of them are active, so you won't be able to add any shared
> folders
> just yet. You have to fire one up, let it load and then get your mouse to
> escape the VM (Press the right ALT key) so you can go to Edit > Settings
> in
> Virtual PC's main menu at the top of the window. Shared folders are then
> immediately available to the VM.
>
> Resist the urge to share your entire boot drive with a VM. While they
> are designed to isolate the VM from the rest of your main system, sharing
> a
> real drive means you can now delete things from it. Since you're working
> within a VM, Recycle Bin won't help to bring back and mistakes. As a
> result, I only share what I need.
>
>
> There are TONS of useful things available for bot silent installation
> and for adding to custom WinXP installation CDs. I've been trolling
> several
> resources for these things lately and will provide links and what little
> guidance I can whenever you're ready. Just know that it's very easy to
> get
> overwhelmed by all of these seemingly conflicting options (some are not
> compatible with others), so you might be better off mastering the VMs
> before
> branching out too far.
>
>
> VPC uses the original VM file to load up your virtual OS and whatever
> you had installed into it. From that point on, it doesn't touch that
> original file. Instead, it works from within that Hibernation-like file
> to
> keep the current session in isolation. When you shut down a VM and choose
> to NOT save its current state, you're telling it to forget about the
> session
> you just had. In that case, the Hibernation-like file is simply discarded
> (deleted). If you save it, it will merge the two (the one you originally
> opened plus the changes you made) so that any changes will be there when
> you
> next fire up that VM. It's only like Hibernation until they are merged,
> except that you're actually using the second file throughout the entire
> session. After than, the Hibernation-like file is gone and all that's
> left
> is the VM as it was when you shut it down.
>
> So, you'll want to save the session whenever you do something you wish
> to preserve. If you install an app, update definition files or make
> changes
> to how the OS and apps work, you'll want to save the changes when asked
> after you shut down the VM. This is why I previously suggested that you
> fire it up, let it update all of the critical updates, definition files,
> etc. and then shut it down, saving the changes. THEN, fire it back up and
> run whatever experiments you want to try. When you're finished playing,
> shut it down and DON'T save those changes. The next time you fire it up,
> it
> will have retained the updates, but forgotten about the experiments.
>
> Just to be clear, the Save option I'm discussing is NOT found within
> the
> VM. It only comes up after you Start > Shut Down > Shut Down the
> operating
> system inside the VM. I would imagine it would also come up if you
> completely destroy the OS inside the VM and have to shut it down manually
> (Right ALT to escape the VM window and then go to Action > CTRL+ALT+DEL)
> OR
> (Action > Close or Reset will also allow you to recover).
>
> Peace,
> GMan
> http://reddit.com
> "The only dumb questions are the ones we fail to ask!"
---------------------------------------------------------------
Please remember to trim your replies (including this sentence and everything
below it) and adjust the subject line as necessary.
To unsubscribe or change your email settings:
//www.freelists.org/webpage/pctechtalk
To access our Archives:
http://groups.yahoo.com/group/PCTechTalk/messages/
//www.freelists.org/archives/pctechtalk/
To contact only the PCTT Mod Squad, write to:
pctechtalk-moderators@xxxxxxxxxxxxx
---------------------------------------------------------------
Other related posts:
