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"
> <> 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.