Hello, I could really use some help. After a crash on my iBook G4,
10.4.11, which occurred while my virtual PC machine was Paused, I can
not access this machine at all. At first it came up with a black, DOS-
like screen asking to find a boot drive or boot from a floppy, while
VPC 7.0.2 led me to the settings page for that machine wherein there
was nothing selected for Drive 1, and it would not allow me to select
my virtual PC disk image by name - it is greyyed out. Now when I ask
VPC to 'Open' the virtual PC via the File menu, nothing happens at
all. Nothing will appear in the Virtual PC list either.
Also, I tried to make a current copy of the virtual machine, but this
bombs out during the copy process in the Finder with either an
'unexpected error (-1309)', or more ominously a "The Finder cannot
complete the operation because some data in "UndoDrive1.vud" could not
be read or written. (Error code -36)."
Any ideas on how to access my original machine would be appreciated.
I've spent some time browsing the archives here, which included a
suggestion to set up a new virtual machine and try importing from the
old one. However I am having trouble with this too - I first purchased
Virtual PC 6 with Windows XP/H included, later I purchased VPC 7 as an
'upgrade' version. I can't get VPC 7 to create a new machine using the
Windows content on the VPC6 disks. Am I missing some discs for Windows
XP/Home? I seem to recall (four? years ago) that there were no
separate discs from Microsoft??? I have the Microsoft certificate
which includes the writing 'Connectix Corporation' on it, and the VPC6
install discs (2 of them) say on them "Includes WXP Home".
Am i going to have to set up a blank VPC6 machine, 'upgrade' or
'import' (?) it to VPC7, and then have an option to import an existing
VPC7 machine?
Brian - 17 Jan 2008 21:05 GMT
> Am i going to have to set up a blank VPC6 machine, 'upgrade' or
> 'import' (?) it to VPC7, and then have an option to import an existing
> VPC7 machine?
well this has been a long and boring day that isn't close to over yet.
I did make a VPC6 machine, converted it to a VP7 file, updated
Windows on it, installed VM additions, installed QuickBooks,
and finally was able to rescue the QB data from the original
virtual machine with the Transfer command.
I also looked at the package contents of the original machine,
which included a 'undodrive1.vud' in addition to a 'basedrive.vud',
but no where could I find a 'savedstate' file which is mentioned
in many of Paul Power's very helpful posts here. The undodrive1.vud
file is the one in particular that hangs up the copy process. I did
a repair permissions on the drive as a whole, but still can't get
the original virtual machine file to appear in the PC List.
But since I got my main QuickBooks file back without even resorting
to losing a little bit of work by using the back-up file, I'm not so
worried
about recovering the whole original machine. Only have to make it
through another few months before moving on to an Intel Mac.
Jeron - 18 Jan 2008 07:45 GMT
I have been error free for many years on my virtual pc 7. As of Jan 17, I no longer can access virtual pc. What has happened?
Mac G - 18 Jan 2008 08:22 GMT
> I have been error free for many years on my virtual pc 7. As of Jan 17, I no
> longer can access virtual pc. What has happened?
The first thing I'd do is run Disk Utility to Check the hard disk, then
if that is OK to repair permissions.
Fred Horvat - 18 Jan 2008 23:58 GMT
Also the PLIST file may be corrupt. Like Mac G stated I¹d run the Check
Disk and repair Permissions first and then see what happens.
On 1/18/08 2:45 AM, in article ee88f6c.1@webcrossing.caR9absDaxw, "Jeron"
> I have been error free for many years on my virtual pc 7. As of Jan 17, I no
> longer can access virtual pc. What has happened?
Paul Power - 22 Jan 2008 18:47 GMT
> Also the PLIST file may be corrupt. Like Mac G stated I¹d run the Check
> Disk and repair Permissions first and then see what happens.
[quoted text clipped - 5 lines]
>
> - Show quoted text -
OK. First of all, how is a plist file going to help open Windows?
Windows does not recognize plist files. He can't run Check Disk
because he can't get past the boot strap files. Check Disk runs from
'within'. And repairing Disk Permissions is a Mac utility. Has nothing
to do with Windows. The reason there is no 'savedstate' file is
because the virtual machine is not recognized. Windows is contained in
a package file under the name 'basedrive.vhd'
To get the original virtual machine to run, look for that
basedrive.vhd file. Move it to the desktop. Create an empty virtual
machine. Quit VPC. Move the basedrive.vhd file to the Windows package
and launch VPC. Works 80% of the time as long as there is no
corruption in the Windows file itself.
Fred Horvat - 23 Jan 2008 03:04 GMT
Well you are correct IF you are talking about once being in Windows. Since
the post was vague I offered suggestions to get VPC to launch into Windows.
So the suggestions I offered were strictly from the OSX side to get VPC to
launch. A corrupt PLIST file will keep VPC or any application from running.
This is a common issue with MS Office. Word may not run but all the other
apps in Office do. By deleted or moving the PLIST file and re-launching
Word will normally 99% of the time get Word to run just fine afterwards.
Needless to say File Permissions can also keep many apps from running
properly. Obviously once in Windows these things do not apply.
On 1/22/08 1:47 PM, in article
7af33f97-a93f-497c-b5ad-20c83f522d9d@t1g2000pra.googlegroups.com, "Paul
Power" <paulkpower@gmail.com> wrote:
>> Also the PLIST file may be corrupt. Like Mac G stated I¹d run the Check
>> Disk and repair Permissions first and then see what happens.
[quoted text clipped - 20 lines]
> and launch VPC. Works 80% of the time as long as there is no
> corruption in the Windows file itself.
Paul Power - 29 Jan 2008 18:33 GMT
> Well you are correct IF you are talking about once being in Windows. Since
> the post was vague I offered suggestions to get VPC to launch into Windows.
[quoted text clipped - 36 lines]
>
> - Show quoted text -
Look at the original post, Fred.
"Hello, I could really use some help. After a crash on my iBook G4,
10.4.11, which occurred while my virtual PC machine was Paused, I can
not access this machine at all. At first it came up with a black,
DOS-
like screen asking to find a boot drive or boot from a floppy"
This can ONLY happen if the VPC application is up and running. He is
trying to access his virtual machine (Windows). That is the reason for
my post. The other suggestions are for getting the VPC application to
launch. It already did at that point.
Fred Horvat - 30 Jan 2008 01:04 GMT
Gotcha
Thanks
On 1/29/08 1:33 PM, in article
0772b16e-67e3-45d7-af52-2b74400794e3@s19g2000prg.googlegroups.com, "Paul
Power" <paulkpower@gmail.com> wrote:
>> Well you are correct IF you are talking about once being in Windows. Since
>> the post was vague I offered suggestions to get VPC to launch into Windows.
[quoted text clipped - 50 lines]
> my post. The other suggestions are for getting the VPC application to
> launch. It already did at that point.
Brian - 30 Jan 2008 16:22 GMT
I too ran VPC error free for several years. I think my first crash was
a result of the internal hard disk in my iBook approaching 100%
capacity. Simultaneously, my virtual Windows machine was slowly
filling up. I'm not sure it was actually 'emptying' the Recycle Bin
completely; I'm no Windows expert at all. I was estimating it was
using up a total of maybe 7 gigs so I didn't think about it too much
as the VPC machine file had 15 gigs allocated to it.
My new crash I think may have been caused by trying to update
QuickBooks 2006 without ever updating Windows XP/Home from what I
bought back in about 2003. I did not realize that first you have to
update the Windows Update software and then you can update Windows.
Just a hunch though.
Anyway I did not realize you could change the title of the threads
here, I thought my original thread had somehow gone to the great bit-
bucket in the sky. Nothing suprises me working with Windows though I
know that had nothing to do with it, but I couldn't figure out what
happened to my original post here for several weeks.