Basilisk with Appletalk support; ML and upwards
Posted: Sat Jun 22, 2013 8:59 am
Hi,
NOTE: these are not our suggested BasiliskII builds and the links no longer work. You can find the suggested builds at:
http://www.emaculation.com/forum/viewto ... f=6&t=7361
CAUTION: Use these builds only when you need easy Appletalk support. These builds do not stem from the official source code repository and will most likely not be updated when the official source code changes.
The links below provide BasiliskII builds with greatly simplified support for Appletalk through the "etherhelper" (thanks to dsumorok!). This will only work in Mountain Lion and upwards. Appletalk will only work with WIRED ethernet connections. All builds also support "normal" slirp based networking. (source code at: https://github.com/dsumorok/macemu)
1. 64 bit BasiliskII with JIT, SDL-based, etherhelper.
http://www.open.ou.nl/hsp/downloads/Bas ... 7-2013.zip
2. 64 bit BasiliskII, SDL-based (No JIT), etherhelper.
http://www.open.ou.nl/hsp/downloads/Bas ... 7-2013.zip
3. 64 bit Basilisk, XQuartz-based (No JIT), with extended support for the ASC (Apple Sound Chip), etherhelper.
http://www.open.ou.nl/hsp/downloads/Bas ... 7-2013.zip
4. 32 bit Basilisk, SDL and Ethernethelper, no jit.
http://www.open.ou.nl/hsp/downloads2/Ba ... er-SDL.zip
How to run these builds:
Appletalk support is achieved by bridging your WIRED network connection with a tap driver. This will only work in Mountain Lion or higher, as Apple only added support for bridging network connections from Mountain Lion onwards. If you don't run Mountain Lion or higher, you can refer to our Appletalk guide at:
http://www.emaculation.com/doku.php/app ... heepshaver
1. Backup you current version of BasiliskII.
2. Installation:
-Install tuntap_20111101.pkg from the folder "tuntap_20111101".
(http://tuntaposx.sourceforge.net, created by Mattias Nissler <mattias.nissler@gmx.de>).
Install both the drivers and the startup items.
Note on Yosemite this updated tuntap packages is needed: https://sourceforge.net/projects/tuntap ... /20141104/
-Dowload the desired BasiliskII build from the links above. Rename the BasiliskII build in the download to "BasiliskII".
Please note that if you want to run the XQuartz build, you will need to download and install the XQuartz environment. This will happen automatically on the first time you run a XQuartz-based application.
-Use the BasiliskII GUI (BasiliskIIGUI) to set the required ethernet settings. Go to the Serial/Network tab and enter at Ethernet Interface:
"etherhelper/tap0/bridge0/en0" (without the quotes) (see below for correct determination of the last parameter (enX)
Explanation of the parameters:
etherhelper: signals Basilisk to use the etherhelper tool in the current package.
tap0: The tap driver supports 16 tap devices (from tap0 to tap15). You would normally only use "tap0".
bridge0: OSX supports multiple bridges between network connections. You would normally only use "bridge0"
en0: You need to find the OSX internal name of your WIRED ethernet connection. If you have a wireless connection, this most often uses "en0", so your wired connection would be "en1". You can find out the name of your wired connection by opening system information (about this mac -> more info -> system report) and clicking "Network". In the Active Services list on the right, find "Ethernet" and use the BSD Device name.
Save the basilisk_ii_prefs file by clicking "Save". This concludes the installation.
You can revert to normal slirp networking by entering "slirp" at the "Ethernet Interface". If you set TCP/IP to manual in the Mac OS TCP/IP Control panel, please set it back to using DHCP.
3. Running BasiliskII:
-Click "Start" in the BasiliskIIGUI (this will only work if your BasiliskII program is called "BasiliskII"), or start BasiliskII by double-clicking the application. You will then need to enter your password and click/press OK.
-Go to the TCP/IP control panel and either set Configure to "Using DHCP Server" or to "Manually".
If set to "Manually", set IP address to a free address in your network, set Subnet mask, Router address, Name server addr. to the same values your network uses. (See System Preferences/Network for the correct values)
4. Advanced usage: Connection a Basilisk and SheepShaver instance on the same machine through Appletalk.
SheepShaver doesn't support the automated setup of appletalk support. You can, however, start SheepShaver through the manual solution provided at http://www.emaculation.com/doku.php/app ... heepshaver. By using a second tap device (e.g., "tap1") and manually adding it to the same bridge BasiliskII uses you can connect both through Appletalk.
5. Known issues:
-Sometimes the DHCP server in your network can get "confused". This results in a longer wait before the Mac OS desktop shows in BasiliskII. This, however, doesn't affect Appletalk working. A solution is to set TCP/IP to "Manually" (see above).
-If TCP/IP is not set to be always active, a system error might occur on start-up and shut down might hang. Set TCP/IP to always active in the TCP/IP control panel (first select user mode "advanced" and then use the Options button to uncheck "load only when needed"
Best,
Cat_7
NOTE: these are not our suggested BasiliskII builds and the links no longer work. You can find the suggested builds at:
http://www.emaculation.com/forum/viewto ... f=6&t=7361
CAUTION: Use these builds only when you need easy Appletalk support. These builds do not stem from the official source code repository and will most likely not be updated when the official source code changes.
The links below provide BasiliskII builds with greatly simplified support for Appletalk through the "etherhelper" (thanks to dsumorok!). This will only work in Mountain Lion and upwards. Appletalk will only work with WIRED ethernet connections. All builds also support "normal" slirp based networking. (source code at: https://github.com/dsumorok/macemu)
1. 64 bit BasiliskII with JIT, SDL-based, etherhelper.
http://www.open.ou.nl/hsp/downloads/Bas ... 7-2013.zip
2. 64 bit BasiliskII, SDL-based (No JIT), etherhelper.
http://www.open.ou.nl/hsp/downloads/Bas ... 7-2013.zip
3. 64 bit Basilisk, XQuartz-based (No JIT), with extended support for the ASC (Apple Sound Chip), etherhelper.
http://www.open.ou.nl/hsp/downloads/Bas ... 7-2013.zip
4. 32 bit Basilisk, SDL and Ethernethelper, no jit.
http://www.open.ou.nl/hsp/downloads2/Ba ... er-SDL.zip
How to run these builds:
Appletalk support is achieved by bridging your WIRED network connection with a tap driver. This will only work in Mountain Lion or higher, as Apple only added support for bridging network connections from Mountain Lion onwards. If you don't run Mountain Lion or higher, you can refer to our Appletalk guide at:
http://www.emaculation.com/doku.php/app ... heepshaver
1. Backup you current version of BasiliskII.
2. Installation:
-Install tuntap_20111101.pkg from the folder "tuntap_20111101".
(http://tuntaposx.sourceforge.net, created by Mattias Nissler <mattias.nissler@gmx.de>).
Install both the drivers and the startup items.
Note on Yosemite this updated tuntap packages is needed: https://sourceforge.net/projects/tuntap ... /20141104/
-Dowload the desired BasiliskII build from the links above. Rename the BasiliskII build in the download to "BasiliskII".
Please note that if you want to run the XQuartz build, you will need to download and install the XQuartz environment. This will happen automatically on the first time you run a XQuartz-based application.
-Use the BasiliskII GUI (BasiliskIIGUI) to set the required ethernet settings. Go to the Serial/Network tab and enter at Ethernet Interface:
"etherhelper/tap0/bridge0/en0" (without the quotes) (see below for correct determination of the last parameter (enX)
Explanation of the parameters:
etherhelper: signals Basilisk to use the etherhelper tool in the current package.
tap0: The tap driver supports 16 tap devices (from tap0 to tap15). You would normally only use "tap0".
bridge0: OSX supports multiple bridges between network connections. You would normally only use "bridge0"
en0: You need to find the OSX internal name of your WIRED ethernet connection. If you have a wireless connection, this most often uses "en0", so your wired connection would be "en1". You can find out the name of your wired connection by opening system information (about this mac -> more info -> system report) and clicking "Network". In the Active Services list on the right, find "Ethernet" and use the BSD Device name.
Save the basilisk_ii_prefs file by clicking "Save". This concludes the installation.
You can revert to normal slirp networking by entering "slirp" at the "Ethernet Interface". If you set TCP/IP to manual in the Mac OS TCP/IP Control panel, please set it back to using DHCP.
3. Running BasiliskII:
-Click "Start" in the BasiliskIIGUI (this will only work if your BasiliskII program is called "BasiliskII"), or start BasiliskII by double-clicking the application. You will then need to enter your password and click/press OK.
-Go to the TCP/IP control panel and either set Configure to "Using DHCP Server" or to "Manually".
If set to "Manually", set IP address to a free address in your network, set Subnet mask, Router address, Name server addr. to the same values your network uses. (See System Preferences/Network for the correct values)
4. Advanced usage: Connection a Basilisk and SheepShaver instance on the same machine through Appletalk.
SheepShaver doesn't support the automated setup of appletalk support. You can, however, start SheepShaver through the manual solution provided at http://www.emaculation.com/doku.php/app ... heepshaver. By using a second tap device (e.g., "tap1") and manually adding it to the same bridge BasiliskII uses you can connect both through Appletalk.
5. Known issues:
-Sometimes the DHCP server in your network can get "confused". This results in a longer wait before the Mac OS desktop shows in BasiliskII. This, however, doesn't affect Appletalk working. A solution is to set TCP/IP to "Manually" (see above).
-If TCP/IP is not set to be always active, a system error might occur on start-up and shut down might hang. Set TCP/IP to always active in the TCP/IP control panel (first select user mode "advanced" and then use the Options button to uncheck "load only when needed"
Best,
Cat_7