I recommend using a 32GB card at the minimum so that you have lots of space for game ROMs however, a smaller SD card will also work.
Use Raspberry Pi Emulator Free To UseThe SSH Client is robust, easy to install, easy to use, and supports all features supported by PuTTY, as well as the following: It is developed and supported professionally by Bitvise. dynamic port forwarding through an integrated proxy Bitvise SSH Client is free to use. Step 2: Enable USB boot mode. Now that we have Raspbian on a microSD card, we can enable the Raspberry Pi’s USB boot mode. First, we’ll have to add a config option, and then we’ll have to reboot the Pi. This will set a bit in the Raspberry Pi’s OTP (One Time Programmable) memory, allowing the device to be booted from a USB mass storage.It is robust, easy to install, easy to use, and works well with a variety of SSH clients, including Bitvise SSH Client, OpenSSH, and PuTTY. The SSH Server is developed and supported professionally by Bitvise.You can download Bitvise SSH Server here. PuTTY is open source software that is available with source code and is developed and supported by a group of volunteers.Enable snaps on Raspberry Pi and install hatari-emulator. Whether its Windows, Mac, iOs or Android, you will be able to download the images using.Below suggestions are independent of the authors of PuTTY.![]() A DB9 Female to Mini Din-8 Male serial cable. A newer computer to create write the Raspian image to the SD card Since the older Pi didn’t have internal WiFi, I used a small TP Link usb Wifi adapter. My Pi was an older “Model B” running Raspian. In my case, it was an SE FDHD with 4mb of ram. There are wiring schematics to do this, but with everything else that has to come in place, I figured why risk messing that up. These are also fairly common and cheap to come by.As a side note, some people have successfully made their own serial cable by cutting into a Mac serial cable (a printer, AppleTalk, cable etc) and splicing it with a USB cable. This adapts the cable coming from the Mac to the USB port on the Pi. A DB-9 RS-232 to USB 2.0 serial cable. This connects to the Mac modem/printer serial port. Mac TCP 2.0.4 – this should have been installed with 7.5 Mac PPP version 2.1.1SD (includes an extension and control panel, System 6 I had better luck with PPP 2.0.1) System 7.5 (I chose this version in order to run MacWeb, but I’ve also got this working under 6.0.8) telnetd (not required, more about this later!) Raspian, which I used Apple Pi baker (via a MacBook Pro) to install to my SD card Next, open up a command line. Then, attach the Pi to a monitor/keyboard/mouse and make sure the Pi can see the internet. I used Apple Pi Baker to install Raspian onto my SD card. Wireless printer for mac iosJust remember which one you pick. On the Mac I used the modem port, but you can use the printer port if you’d like. On the MacBook I used to set this up, you would open the terminal application and type: ssh Plugging InUsing your serial cable(s), attach the Mac to the Pi. Test that you are able to SSH over to the Pi. In my setup, the Pi’s hostname is “raspi” and the user is “pi”. Interfacing Options” I would also advise setting a new password while you’re in there. Note the “9600” is the baud rate of the serial port, and 9600 was about as fast as my SE could cut it. If you type the following you should see your usb port listed: dmesg | grep ttyIn my case, I saw my USB cable was set up here: usb 1-1.3: pl2303 converter now attached to ttyUSB0.meaning “ttyUSB0” is the console I’ll work with.To configure Linux to use this port as a console, we have to edit the file /boot/cmdline.txt, so type in: sudo nano /boot/cmdline.txtAt the very beginning of the line, add a new console by typing: console=ttyUSB0,9600Make sure there’s a space after this to separate it from the other consoles in this file. We need to identify what the name of the console is. We’re essentially setting up the Pi so it will listen on the serial (usb) port for the Mac, allow it to log in, and serve PPP.To install the SLiRP software which is key to this process, type the command: sudo apt-get install slirpNext, we need to figure get the Pi to use the serial port as a console. Again, open a terminal and type “ssh or ssh few things need to be set up on the Pi. We installed the SLiRP software that will provide PPP services to the Mac, and finally set up a script that the Mac’s PPP client will run once it connects in. To summarize, we set up a console on the serial port the USB cable is attached to. Then, make the script executable with: chmod +x ~/slirp.shStill with me? Great! That’s pretty much it for the Pi at this point. What we’ll do here is create a shell script on the pi the Mac can call which will start up SLiRP with the appropriate settings.Open the nano text editor with the name of your script specified: nano ~/slirp.shThen, include the following into this file: #!/bin/bashSlirp -S -b 9600 -P "host addr 10.0.2.1" "dns 10.0.2.3" "asyncmap 000a0000" "debugppp debugppp.log" "debug 1" "mru 500" "mtu 500"Note again, I’m setting my baud rate to 9600 for my SE, but faster Macs can try out higher values.I’ve also specified some IP addresses that I’ll be using in MacTCP, remember these!Hit CTRL+0 to save and then CTRL+X to exit nano. But now, we need the Mac to be able to start it once it makes the connection over the serial port. When you’re done here, hit CTRL+O to save the file and then CTRL+X to exit the nano text editor.Enable the console with: sudo systemctl enable sudo systemctl start wouldn’t hurt to reboot the Pi at this point: sudo reboot 0At this point, we have the PPP server (SLiRP) and the Pi is set up to use the serial port as a console. (MacTCP and Config PPP)In Mac TCP, select PPP, click more and set the values as shown in the screenshots:We’re manually setting the IP based on the configuration the Raspberry Pi is set up with. Again, remember this is specific to my Mac SE, later 68k Macs would have OpenTransport which would be a slightly different process.Once you have everything installed there are two control panels we’ll need to jump into. I had to play around with finding the right combination of versions that worked for me, and the ones I listed above were what I got working. You can install Mac TCP and PPP after the fact as well. If you’re fresh-installing the Mac OS, make sure you include Mac TCP. If you need to download anything, check out the resources page. There are many more screens of configuration here, so look at my settings carefully: Next is the Configure PPP control panel. Other tutorials I’ve read used the SLiRP DNS which should be 10.0.2.3, based on our setup… but that didn’t work for me whereas this did.Ok that’s it for MacTCP. ![]() If you are experimenting with different speeds, remember to change it here on the Mac, and the two locations it’s set on the Pi. This makes a total of 3 places we set that baud rate. Also note the port speed is set on the main config window also. Finally, the “slirp.sh” script may be located someplace else for you if you don’t want it sitting in your home directory like I did earlier. The password I blanked out, you’ll have to enter yours, of course. This will help troubleshoot from the Pi side.Ok, so if everything’s set up right, you should be able to click the “Open” button in the PPP control panel and see it run through the connect script and show two happy faces indicating the Mac and the Pi are happily connected:At this point, any time you open an application that requests a TCP connection (web browsers, telnet, etc) the Mac will open the PPP window and go through the connection process. In linux, you can actually read and write from the /dev/ttyUSB0 with the cat and echo commands respectively. You should be able to see stuff come back from the Pi here to confirm your baud rate and other settings are correct. There is a “Terminal Window” checkbox which can be useful for troubleshooting. In other words, reboot the Pi before trying to connect. If you connect or partially connect and need to establish your connection, you’ll have to reboot the Pi so the console can go back to the login. Don’t expect anything to be fast. Note that MacWeb has a patch to solve background color issues on black & white macs. You can always try connecting via an IP address. Try accessing google.com through MacWeb! If you aren’t connecting right away don’t panic, it might just be your DNS settings. Now that you’re up and running…
0 Comments
Leave a Reply. |
AuthorEugene ArchivesCategories |