Page 1 of 1

Have you gotten OS X 10.2.x networked in PearPC?

Posted: Fri Feb 11, 2005 6:00 pm
by Mac Emu
Know any tutorial that targets Mac OS X 10.2 users?

Posted: Fri Feb 25, 2005 6:28 am
by prasys
Yes

On Linux , it is possible with the hacked 3COM Driver but on Windows...Its not possible

Tested on my friend's linux box , using SuSe 9.0 + Kernel 2.6.10..., PearPC 0.4pre (+ right mouse patch by thewer)...OSX 10.2.8

Posted: Fri Feb 25, 2005 10:22 pm
by Mac Emu
I'm pretty sure I got it working nearly a year ago.

I wasted a good 3 hours trying different things out last night to get networking working under 10.2.x on Windows (unsuccessfully). Then I installed Mandrake 10.1 and messed around with SheepShaver.

Posted: Sat Feb 26, 2005 3:31 am
by Maxwell Smart
Yeah its a shame. I run Windows XP Pro SP2 with PearPC .4pre and OSX 10.2 and I still have been unsucessful with installing the network. Unfortunately, thats one of the main reasons to have OSX on your PC :(

networking with pearpc and mac ox 10.2 on windows XP SP2

Posted: Sat Feb 26, 2005 10:55 am
by Cat_7
Hello,

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.

Configuration:
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 ;-)

Best wishes
Cat_7

Posted: Mon Feb 28, 2005 12:44 pm
by Mac Emu
See ... I knew I had done it nearly a year ago!

Thanks Cat_7, I hadn't thought to try out an older build. Geez, this sucks.

Posted: Sat Apr 30, 2005 4:08 am
by Mac Emu
Update: I just got Mac OS X 10.2.8 Jaguar on the Internet using the trick discussed on the PearPC.net Forum.

Image

Posted: Sat Apr 30, 2005 6:07 am
by Cat_7
Yeah, great!

But I believe the problem was solved at the pearpc side. Someone has rewritten the 3com driver support :lol:

Cat_7