try to find your card name in the daemon windows
I had the same pb with my XP SP1, netgear FA311, my system is french, the
name of my card is the french one under windows and the name scanned by
colinux was the english one..... replacing it and all goes nearly well
(there was also "(microsoft packet...)" in my card name found by colinux and
I had to cut it out to have bridge working)
----- Original Message -----
From: "Marko Bozikovic" <bozho@...>
To: "coLinux" <colinux-devel@...>
Sent: Tuesday, March 02, 2004 3:29 PM
Subject: [coLinux-devel] Bridged networking problem followup
> Regarding the STATUS_ACCESS_VIOLATION error some people get when using
> I have installed both Win2k and WinXP under VMWare, installed Winpcap and
> copied coLinux (with the Debian image I'm using) coLinux works fine on
> systems. The only relevant difference is the network cards used. Here's a
> short summary of systems I've tried running linux on:
> Win2k SP4 (native), SMC EZ Card 10/100 (SMC1255TX) ethernet card - works
> WinXP SP1 (native), SMC EZ 10/100 Fast Ethernet - doesn't work
> Win2k (VMWare), VMWare's virtual network card (don't have the name here) -
> works fine
> WinXP (VMWare), VMWare's virtual network card (don't have the name here) -
> works fine
> I get the same error and identical stack dump file when I use bridged
> networking and set a random name for the network card on a system that
> works. Could it be that there's a problem with detecting the network card?
> ICQ: 5990814
> I'm not under the alkafluence of inkahol
> that some thinkle peep I am.
> It's just the drunker I sit here the longer I get.
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> coLinux-devel mailing list