> It certainly sounds like a driver problem to me. I am surprised that you
> are still using Netbeui. I thought almost everyone was on TCP/IP now. What
> other machines are on the network?

>I just started testing Virtual PC 2004 SP1 and no matter which OS I install
> (Win9.x, Win2k and XP), as soon as I enable NetBEUI the host computer blue
> screens. It's a stop error, with a Driver_IRQL_Not_Less_or_Equal and the
> minidump points to the NIC driver for my motherboard. It's an Intel
> board, a
> D945GTP, with the integrated Pro1000 NIC chipset. Of course if I change
> the
> VPC networking to NAT, all is well but then I can't access the other PC's
> on
> my network.
>
> I'm on the latest version of all of the drivers and BIOS firmware from
> Intel
> so if it's some sort of issue with the Intel driver I'll have to contact
> them. But in the meantime I'm wondering if perhaps I'm doing something
> wrong
> or if anyone else is seeing this sort of problem.
>

> Make sure any offloading is turned off for the NIC on the host. I don't
> know if that specific adapter has that capability, but it has been known to
> cause problems.

> "Robert Comer" wrote:
>
>> Make sure any offloading is turned off for the NIC on the host. I don't
>> know if that specific adapter has that capability, but it has been known
>> to
>> cause problems.
>
> Thanks Bob. I dug around a bit more last night after posting my
> original message and saw the thing about offloading. This chipset does
> have
> that and I unchecked all four items under the offloading section. Still
> get
> the blue screen as soon as NetBEUI loads.

> How about trying an older version of the NIC's driver?
>
> I know VPC doesn't generally have a problem with NetBEUI, as I run that
> config a lot, so it has to be related to drivers on your PC.
>
> --

> I just started testing Virtual PC 2004 SP1 and no matter which OS I
> install (Win9.x, Win2k and XP), as soon as I enable NetBEUI the host
> computer blue screens. It's a stop error, with a
> Driver_IRQL_Not_Less_or_Equal and the minidump points to the NIC
> driver for my motherboard. It's an Intel board, a D945GTP, with the
> integrated Pro1000 NIC chipset. Of course if I change the VPC
> networking to NAT, all is well but then I can't access the other PC's
> on my network.
>
> I'm on the latest version of all of the drivers and BIOS firmware
> from Intel so if it's some sort of issue with the Intel driver I'll
> have to contact them. But in the meantime I'm wondering if perhaps
> I'm doing something wrong or if anyone else is seeing this sort of
> problem.

> Well, looks like I've reached a dead end. I found older drivers for this
> NIC
> but they also blue screen with NetBEUI loaded.
>
> Intel says since the host PC runs fine with NetBEUI and their drivers,
> it's
> Microsoft's fault and they can't help me.
>
> "JimGill" wrote:
>
>> "Robert Comer" wrote:
>>
>> > How about trying an older version of the NIC's driver?
>> >
>> > I know VPC doesn't generally have a problem with NetBEUI, as I run that
>> > config a lot, so it has to be related to drivers on your PC.
>> >
>> > --
>>
>> It's actually been difficult to find the older driver for this particular
>> chipset but I may just try one that's for the NIC that this one replaced.
>> I
>> suspect they're close enough.
>>
>> As for NetBEUI, right, I've used it for a couple of years on the
>> Connectix
>> version on a Dell but it immediately started having problems when I
>> switched
>> to a system with this Intel motherboard. I switched to VPC 2004 in case
>> there was some change made since the final Connectix release, but it
>> exhibited the exact same problem. It made sense that it was the Intel
>> driver
>> but I just wanted to come here to make sure there was no workaround or
>> obscure setting that I may have missed.
>>
>> In the meantime I've submitted a trouble ticket to Intel support, maybe
>> they'll be able to work with me to find the root cause and fix their
>> drivers.
>> Now that VPC is a free product I suspect that problems like this will be
>> a
>> lot more visible.

> Bummer. I don't suppose you could drop another NIC in and disable that one?