On May 09, 2006, at 6:06 PM, [EMAIL PROTECTED] wrote:
That's what I thought, but my G4 desktop with both Ethernet and
FireWire active as network devices causes RB apps in Windows XP SP2
in VPC7 to show the Ethernet device normally, and the FireWire
device with an IP Address of 0.0.0.0
Not to say that VPC is at all perfect, but it's nice to dream.
Realistically, I believe that this behavior is likely to be caused
by VPC not being able to translate FireWire into something that
Windows can understand without Windows having FireWire drivers for
itself.
Does VPC support the use of IP over Firewire ?
I was sure I'd seen a reply to a message much like yours recently
Jon Johnson replied to this
On Mar 22, 2006, at 8:43 PM, Christian Miller wrote:
I ran into an interesting issue with my laptop today. I was not
connected to any network while airport was on, and I had the same
issue when airport was turned off...
System.NetworkInterfaceCount returned zero, and
System.GetNetworkInterface(0).MACAddress raised an OutOfBounds error.
Why is this?
The current design of System.NetworkInterface is to hand back
interfaces that sockets can be bound to. It would be undefined
behavior to bind a socket to an interface that isn't actually
connected.
If you're looking for something else, please file a feature request.
Thanks,
Jon
_______________________________________________
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
