I am writing to you from Mac OS X 10.2 on pearpc on windows XP SP2 through the 3com driver.
So it seems it IS possible to network 10.2 on XP. The only caveat is that I am using pearpc 0.2.0 So it's rather slow.
host network adapter
10.10.10.11, default gw 10.10.10.10, with ISP dns'
tap device: 10.10.10.12. gateway 10.10.10.10
These two are bridged so I have a bridge like this:
10.10.10.10, default gateway 10.10.10.1 (my windows 2003 server) with ISP dns'
Mac OS X:
10.10.10.12 default gw 10.10.10.10, with ISP dns'
I had to change the name of the tap device in the registry, because pearpc 0.2.0 still searches for "tapxxxx", and "tapxxxx" has to be an exact predefined value. Thats why for a long time pearpc only worked with only one version of the tap device. You can look the old development list messages up about this.
The newer versions of pearpc simply search for "tap". So I changed tap0801 to tap (after configuring the network)
So the problem is in Pear. The same goes for the linux version.
Packets are recognized and sent, but not received in Pear.
I'll see if this also works with higher version of Pear,
EDIT: no it doesn't: mac osx gives me a kernel panic when using pearpc 0.4 pre
When using Pearpc 0.3 Mac OSX doesn't crash, but also doesn't connect