closing, discarding, saving, undo disks, oh my...

[michael sorens]

Consider this scenario:
I run a VirtualPC that uses an undo disk, setup the session with various
windows, then close it by selecting "Save state and save changes" and
checking "commit changes to virtual hard disk". So my changes are saved on
the undo disk, the undo disk gets merged to the main disk, plus I get a saved
state file (.vsv).

Now I would like to be able to return to this exact state after each of many
subsequent runs of the VPC. But I find no closing options that will do this.
What I want is something like "turn off, discard changes, but retain the .vsv
file that was in place when I started".

So I thought of this:
(1) Save a copy of the .vsv file from above.
(2) Launch the VPC, do whatever, then close with "turn off and discard
changes". This deletes the .vsv and the .vud files.
(3) Now put the saved .vsv file back in place.

Unfortunately, the VPC console does not recognize this situation. It shows
the VPC as "not running" rather than "saved". I even tried removing the VPC
and re-adding it to the console. Any workarounds for this?

[FACE]

On Wed, 23 Jul 2008 08:46:15 -0700, in microsoft.public.virtualpc,
michael sorens <m_j_s...@newsgroup.nospam>, wrote

It appears that you are looking for a 'repeatable resume' feature. There
may be more there now than you think and possibly all that you need.
Check out http://ts2blogs.com/blogs/donroe/archive/2005/12/19/513.aspx and
see if that is useful.

If not, or you want to bypass that, AND you are not averse to batch files,
it can be done with a batch file -- what i call a 'file shuffle' -- that
is, removing one set of files and shuffling a set of 'template' files in
for use from a hold area.

FACE

[michael sorens]

The pointer to the "repeatable resume" you provided is just what I needed.
From reading that, I see I was on the right track, but I should have saved
the .vmc and the .vsv instead of just the .vsv.
Out of curiousity I compared the saved .vmc file with that left after
"discarding changes" and I see that the saved .vmc has the critical xml
element indicating that the state is saved.

Thanks!