Prev: Virtual XP & Hardware
Next: VPC On VMWare
From: Karl E. Peterson on 19 Nov 2009 13:30
In my ongoing travails doing a P2V, I managed to get the machine up and running with
some difficulty and a Windows repair. This was an XP/SP3 box, that probably has/had
some registry corruption. (The physical box still boots fine, though.) I use
Acronis to back it up, then used Universal Restore to restore that to a new VHD.
Created the machine, and it just sorta hung at a black screen for me. So I ran the
XP setup's Repair option, which took hours (overnight). I honestly thought it'd
gone past the point of getting anything done.

This morning, I find that the machine is up and running - yea!!! So I give it a new
IP address to connect to the network, rename the machine to avoid the name conflict,
install the virtual machine additions, and restart it. BAM! I can't get past the
"Preparing Network Connections" dialog without the VM wanting to reset itself with
the Subject error message.

I've tried every copy of HAL that I can put my fingers on. Most just hang at a
blackscreen before ever doing the Windows flag. HALACPI.DLL (renamed HAL.DLL) from
the SP3 disc gets me back to the error in question.

What to do? Rerun the Repair?

Thanks... Karl
--
..NET: It's About Trust!
http://vfred.mvps.org


From: Bo Berglund on 19 Nov 2009 14:58
On Thu, 19 Nov 2009 10:30:42 -0800, "Karl E. Peterson"
<karl(a)exmvps.org> wrote:


>What to do? Rerun the Repair?
>
Maybe try VMWare Converter and Player 3????

--

Bo Berglund (Sweden)
From: Karl E. Peterson on 19 Nov 2009 15:54
Bo Berglund wrote:
>>What to do? Rerun the Repair?
>
> Maybe try VMWare Converter and Player 3????

Update... I moved the VHD onto a Windows 7 machine, and fired it up there as a new
VM. It's working again!

I'm not sure if it simply wouldn't run on the same host machine from which it was
cloned? Or if the Win7 XP Mode version of VPC is somehow able to avoid that
processor error?

The plot thickens!

I have not yet reconfigred the TCP/IP so that it can connect to the network. That
was the last thing I did before the problems began the one and only time I got it to
load successfully. I think I'll tweak and test a bit before I go down that road
again. :-)
--
..NET: It's About Trust!
http://vfred.mvps.org


From: Steve Jain [MVP] on 19 Nov 2009 16:38
On Thu, 12 Feb 2004 17:16:43 +0100, "Bluetooth"
<szymon_dot_slupik(a)cdn.com.pl> wrote:

>I've just checked again and running "hinstall.exe -i" to install HASP dongle
>drivers by Aladdin results in VPC reporting "unrecoverable processor error".
>Should we consider it as a VPC bug?
>
>Best,
>Szymon

Or a bug in the HASP. There are and have been some known
incompatibilies between VPC and HASP dongles. The design of the two
isn't compatible, and one of them needs to be completely redesigned
from a low level.

Windows VPC might work, since it's based off Virtual Server and the
fork from VPC200x might be enough, otherwise you'll probably need to
go with a non-MS VM solution.

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/
http://smudj.wordpress.com/
From: Karl E. Peterson on 19 Nov 2009 16:59
Was this reply posted to the right thread?

Fwiw, the second paragraph seems to be germaine. (When you say "Windows VPC", you
mean the version you can download to run XP Mode in Windows 7 with, right?) Moving
the VHD to w7 and firing it up there seems to have gotten it going again.

But I'll be darned if I can figure out the differences in network card settings, and
why using the same IP address on one of the Intel cards isn't working anymore. (Now
there are two VMWare "cards" and two Intel cards, and I didn't actually add any
myself.) One of the Intel cards shows a connection, while the other says the cable
is unplugged. The host can see the guest and the guest can see the host, but the
guest can't see the rest of the network at all. Very very odd for a guy only now
starting to move to w7!
--
..NET: It's About Trust!
http://vfred.mvps.org


Steve Jain [MVP] wrote:
> On Thu, 12 Feb 2004 17:16:43 +0100, "Bluetooth"
> <szymon_dot_slupik(a)cdn.com.pl> wrote:
>
>>I've just checked again and running "hinstall.exe -i" to install HASP dongle
>>drivers by Aladdin results in VPC reporting "unrecoverable processor error".
>>Should we consider it as a VPC bug?
>>
>>Best,
>>Szymon
>
> Or a bug in the HASP. There are and have been some known
> incompatibilies between VPC and HASP dongles. The design of the two
> isn't compatible, and one of them needs to be completely redesigned
> from a low level.
>
> Windows VPC might work, since it's based off Virtual Server and the
> fork from VPC200x might be enough, otherwise you'll probably need to
> go with a non-MS VM solution.



 | 
Pages: 1
Prev: Virtual XP & Hardware
Next: VPC On VMWare