blog.macip.net

http://www.insentricity.com/a.cl/215/putting-your-retro-computer-on-the-line

Another conquest. A Macintosh ED. Sold as not working. Picked it up for 30 euro (around US $35,- )

 

What did I learn from this sale.

1) If sold as not working it will probably don’t work……

 

So what did I do. In a hurry to test I decied to test it at my mothers house who I was visiting. So I power it up and heared the monitor. Then the light went out. All of them. So it was not only not working but also giving a short circuit.

We had to find the place where we could enable the fuses agian with the light of my iPhone.

 

What to do after that. Yes I did brought my 15″ Tork. I had it in the car, just in case.Opend it up and looked insight.

And this is the inside. Not strange that it was not working.

So lesson number 2.

2) Open up the case first and do a visual inspection.

 

It is although an nice machine. A plaquete with DOVE enhanced is place on it. The SCSI cable is made in the battery compartment (battery is still in place….removed it right away of cource).

 

Here are the pictures.

 

 

 

 

 

 

 

 

 

 

Works beautiful. I tested first with a serial cable and Mac Terminal to see if it works. That was OK. I could see the console. So I was sure I have valid connection .

I checked with echo TEST > /dev/ttyS1 to see which tty I’m on….. TEST showed up in Mac Terminal on ttyS1

I set up ppp:

[root@station10 ppp]# cat /etc/ppp/options

asyncmap 0
proxyarp
lock

[root@station10 ppp]# cat /etc/ppp/options.ttyS1

# Baud rate of the connection. ElWhip uses 19200.
19200
# Don’t use the modem control lines.
local
# Try to reopen the connection it it is terminated.
persist
# Don’t require the peer to authenticate.
noauth
# Disable negotiation of Van Jacobson style IP header compression.
novj
# IP address to be given to peer.
:192.168.62.130
# IP address of the DNS server for the peer.
ms-dns 192.168.61.1
# Enables IP forwarding on linux
ktune
# Add an entry for the peer to this system’s ARP table.
proxyarp

Checked forwarding. My Red Hat / Centos system it is in /etc/sysctl

[root@station10 ppp]# cat /etc/sysctl.conf |grep forward

# Controls IP packet forwarding

net.ipv4.ip_forward = 1

Then run pppd

[root@station10 ppp]# pppd -d ttyS1

Then I started ElWhip and you this in messages log:

Jan 21 23:40:04 station10 pppd[5369]: pppd 2.4.4 started by root, uid 0
Jan 21 23:40:05 station10 pppd[5369]: Using interface ppp0
Jan 21 23:40:05 station10 pppd[5369]: Connect: ppp0 <–> /dev/ttyS1
Jan 21 23:40:23 station10 pppd[5369]: found interface eth0 for proxy arp
Jan 21 23:40:23 station10 pppd[5369]: local IP address 192.168.62.10
Jan 22 16:40:23 station10 pppd[5369]: remote IP address 192.168.62.130

That means you have a ppp connection to the 512K
I added a static route in my router

192.168.62.130 via 192.168.62.10 with netmask 255.255.255.255

192.168.62.10 is the ppp host where the pppd daemon is.

Start a browser and see this:

 

Some more pictures:

 

Read more about the project on Epooch page and M68kmla

http://apple-crapple.blogspot.nl/2015/01/elwhip-005-download.html

https://68kmla.org/forums/index.php?/topic/24508-web-server-for-macintosh-512k/

 

The Early Mac Serial Number Decoder (http://macfaq.org/serial.html) says it is a 512K…but it is a genuine 128K. It is build in week 21
( monday 21 may till sunday 27 may).
512K was relesead in september 10th 1984

Your European Macintosh 512 (M0001P), with serial number F42103PM0001P, was the 125th manufactured during the 21st week of 1984 in Fremont, CA.

 

I recently bought a AsantéTalk box.

It is not so simple to get it working in my network:

A Macinstoh SE, Basilisk II emulation, Netatalk on FreeBSD.

 

I think it has to do with the way you start up everything, but I didn’t find the correct way to do it. Sometimes I see the box ( and the Mac SE it is connected to) but most times not.

The only time it really worked was when I started up Netatalk first and then the AsantéTalk box, but I first had pull of the power plug and put it back on….. then I did see them. I attach a picture.

My question is:

 

– What is happening here?

– How to start up everything so it will work right away?

 

SOLUTION:

 

I first boot the Netatalk instance and then the AsanteTalk. Then of it doesn’t show up I power down and power up again the AsanteTalk box.
Then I see it!

I found a better manual today. It has a FAQ with this power up power down problem mentioned.

It can be found on:

 

http://www.asante.co…ls/ATALK_UM.pdf

 

 

 

A compilation of the post on 68kmla

 

 

I recently bought a EtherWave Mac/PB Adapter and would like to connect my old school Mac’s to the Internet. I have seen some posting that these devices support TCP/IP. Is there someone out there who has a manual? Or an idea how to do this?
I got it working for LocalTalk. Not easy because I first had to solder a cap out and change it!

This is the device:

 

 

Now that is an interesting question.

http://lowendmac.com…rk/bridge.shtml

I am not sure myself. However, if you have a Mac that can boot OS X 10.2, and another than runs 10.3 or 10.4, you can find out pretty easily if they do. Either that adapter will work just like a regular AFP bridge or it will function like a FastPath 5 TCP/IP router, which I doubt but until I get reports that it does in fact then I’ll remain skeptical.

You’ll also need a driver for it. I’m not sure if it will work with OT systems — you’ll have to find out if that is the case.

 

 

Check out this link for the drivers:

http://www.markyb.or…-version-2-2-1/

I’ve found that the Farallon EN install works for the majority of that era Farallon network hardware, including the etherwave. I’ve managed to get TCP/IP working on 7.1.1 and 7.5.3 – but it seems dependent on working PRAM. The driver will install an “Alternate Ethernet” adapter, use that for IP networking.

Hope it works!

Alex

 

 

I use an Asante EN/SC adaptor myself but I’m sure this advice will work for the EtherWave

You first want to get a netgear 10mbps switch. This will take the information from your modern 100 mbps router and make it more compatible with the classic mac. So you would run ethernet cable from your modern router, to the netgear switch and then to the EtherWave.

After installing the drivers, you’ll want to use MacTCP which you should have installed on the mac to then select Ethernet Built in, then manually set up the gateway settings for dhcp.

I’ve had good luck with MacTCP but you can also use Open Transport to just set TCP/IP settings to automatic.

 

Have you been able to get it working? I’ve added references to this type of adapter in the Guide (it’ll show up next minor update) but there doesn’t seem to be many similar models on eBay, other than AAUI adapters *yawn*.

EDIT: I’d love to have one of those things around. Probably much, much better than a regular AFP bridge. Also: viewtopic.php?f=16&t=1428

 

http://www.welovemacs.com/pn801a.html

appears to be the older version, although I cannot verify. (PN801)

HIs version is a PN840ADB

 

Farallon uses external clocking in its EtherMac and EtherWave PowerBook adapters to push data through the serial port roughly three times faster than usual. This makes an excellent way to add an older PowerBook to an ethernet network. (BTW, these adapters do not support Open Transport.) Source

I was looking for an article/post/blog/something that mentioned the difference between the Modem and Printer ports, saying something technical about one versus the other. I can’t remember where it was and it’s not in my bookmarks or history. Something to do about xfering data without as much interference from the CPU or thereabouts. Maybe it was a reference to something described in Inside Macintosh…dunno.

 

A possibly relevant thread on modem vs printer ports

 

 

I downloaded the driver, but it is in a image format I cannot open. Could anyone change it to a format I can open on an Old Mac. I have Disk Copy 6.3 and it is not able to mount this image what is inside the zip…

Thanks for your help!

See attachment (zip file):

[attachment=0]Farallon221.zip[/attachment]

 

You may have seen this post: viewtopic.php?f=7&t=21226
Also this IIgs technote mentions the interrupt A as being special: http://www.umich.edu… … N.IIGS.018

In practice, there is no difference, just two serial ports hanging off of the Zilog SCC. Apple just switches the communication mode to SDLC to whatever port Localtalk is being used on. The Etherwave likely uses the same transfer mode that Localtalk networking uses (230kbps) to achieve that breakneck speed. Out of the box the SCC is capable of 115kbps with standard RS-232 signaling, the real question is if the host machine can handle it as most aren’t fast enough.

It really doesn’t matter which port you use. Apple’s software gives you the option to use either the printer port or the modem port for Localtalk. The same port flexibility exists on the slower Apple IIgs too.

 

 

Ok I found EN Card Installer 2.3. Installed it on a 7.5 System. ( Booted with extentions off).
Still no luck…

This is what I see when I run the diagnostic tool. It somehow sees the Etherwave Adapter ( I guess…)

[attachment=1]screen-after-install.JPG[/attachment]

I see also two green lights and orange blinking.

[attachment=0]card.JPG[/attachment]

It doesn’t show up in Network Control Panel and not in MacTCP….. What to try next?

 

 

I put together a disk image with the latest version of the files you should need to run an Ethernet adapter on a PB 100 for System 7.1.x (with the exception of the actual Ethernet adapter drivers, since those are specific to the Ethernet adapter in question). I’ve tested all the enclosed files on 7.1.x personally and I know they absolutely work. You can either write the image to disk or mount it using Disk Copy. Either way should work. Hopefully you’ll find it useful.

http://www.sendspace.com/file/dl0uum

 

BIG SUCCESS!!!!!

IT WORKS!!!

On advice from one of our members I used Shrinkwrap to mount the disk. Then, with Extentions off, I installed the drivers with success.
Now the PB Adapter can have a own IP adres from the normal Ethernet range I use in my house. So no macIPgw….

My PowerBook will be online tonight on:

http://mac.vanegten.com

Comming week I will make some screen shots to show how it works.

 

 

 

To round it up.
I bought the EtherWave adapter in June 2013. I didn’t work. A red light was burning. When I opened it up I found out that one of the capacitors was getting much to warm. I replaced it and I had green lights all over!

When I connected it without any driver it worked like a normal hardware LocalBridge. You see the AppleTalk network, but cannot use it as an Alternative Ethernet card or switch to it in network or MacTCP control panel.

Thanks to all our community I got the drivers. Many thanks for that again. I will attach the image I used for this on this post.

The rest is simple. Just mount this disk and install the drivers on 7.1 or 7.5. Startup with Extentions Off (hold shift when booting).

You see two images how the network control panel looks and the MacTCP control panel.

[attachment=1]1.jpg[/attachment]

[attachment=0]2.jpg[/attachment]

This is the image for the version 2.2.2.

http://files.max1zzz… … .image.sit

No… the problem was that I copied the Installer files to a floppy. That didn’t work…. Even with the correct floppy name.
I had to mount the disk image and install it from there.
And yes…then a successful installation is also only possible with extensions off.

The adapter is working fine now for several days. I noticed that the PowerBook and adapter work better under System 7.5 than under 7.1.
My web server responds even when screen is almost off and HD is off. It wakes up and serves a page…

 

You’ll want to grab this version of MacTCP, 2.0.6, the very last version of MacTCP:

 

http://staticky.com/…/MacTCP.sit.hqx

 

All you need is the 2.0.6 control panel from that SIT file, nothing else.

I recently bought a AsantéTalk box.

It is not so simple to get it working in my network:

a mac SE, Basilisk II emulation, Netatalk on FreeBSD.

 

I think it has to do with the way you start up everything, but I didn’t find the correct way to do it. Sometimes I see the box ( and the Mac SE it is connected to) but most times not.

The only time it really worked was when I started up Netatalk first and then the AsantéTalk box, but I first had pull of the power plug and put it back on….. then I did see them. I attach a picture.

 

My question is:

 

– What is happening here?

– How to start up everything so it will work right away?

 

Just blow’n away some dust and started up my Mac 128K. Booting alright with Finder 1.0! But I noticed a strange behaviour of my keyboard, a M0110 B. The qwerty range and second row are allright, but the last row has shifted one character!

So the \ is a z, the x a c, the c is a v, etc.
Is there some kind of keyboard setting I’m missing?

Yes! There is! You can change local settings for another keyboard.So here is the solution also for future generations….

This is what I did. I downloaded disk image Utilities 2 from the Boston Computer Society.
http://www.n-1.nl/mac/bcs/index.html
This was done on my Baselisk II virtual machine. I mounted the disk an copied Localizer to my Quadra over Appletalk. There I copied it on a 800K disk, because all my 400K disk gave a copy error -2….
The 800k disk was put in a SE and Localizer copied to the hard disk. The finaly I copied Localizer to the 400K disk with Finder 1.0.

Localizer runs fine in System 1.0. When opening it says:

The Macintosh Localizer 1.2

You can use the Localizer to change the keyboard routine and the intrenational resources that are part of the System file on the application disk.

After you select the options the Localizer, in my case United Kingdom, the system disk ejects and you will be asked to insert the disk which has to be localized.
You can just insert the same system disk and click on OK. It will be localized and you can insert another one, if you want. You can also stop Localizer if you click on Quit.

http://68kmla.org/forums/viewtopic.php?f=7&t=21207

One of the most intriging Mac related pieces of hardware for me are the LocalTalk PC cards. They where used to connect a LocalTalk network to a DOS or Windows 3.11 network. Apple made the first one in 1986/87. I acquired a model 630-5306 Vintagemacword.com has information about this card:

Apple’s official LocalTalk PC card: Half-size ISA card, contains a 6502 processor and Zilog 8530 controller. Set of eight dip swiches for setting IRQ and IO address. LocalTalk (RS-422 serial) interface is a 9 pin D socket, using the same LocalTalk/PhoneNet box as the Mac 128/512. Card is silk screened as “AppleTalk PC Card”, copyright date 1986. Model number 630-0113. The card labelled 630-5306 appears to be identical.

http://www.vintagemacworld.com/pc_hardware.html

An other source of excelent information is:

http://www.the4cs.com/~corin/localtalk/

My first mission was to get it running in a DOS and Windows 3.11 enviroment. This was relative easy. But it required some special equipment. First of all you need an old PC, because of the ISA slot. ISA is not in computers which are build after the year 2000. Futhermore you need a set of DOS and Windows floppy’s to install the operating system. ISA card require fideling around with dipswitches and correct settings in the BIOS. In my case I had to put the card on IRQ 9 and let the BIOS know that IRQ 9 is handeled by the ISA slot. Installation was straigt forward and I could start the Chooser with the DOS command da. Here are some pictures:

When I was Google-ing around I found out that these card where also officialy supported by the Linux kernel. This was very good news for me because I have a Linux box which is central in my AppleTalk network. It runs Netatalk and is one of the central file servers. It would be great to connect to this machine by LocalTalk too!

To be honnest. This is not a job for the fainth at hearth….
I’m very comfortable in a Linux environment but I really had to work hard to get it running.
First of all. AppleTalk and the LocalTalk PC card are not part of a standard Linux instalation. To get it running you have to recompile the kernel to make it a loadable module. I tried it first with my modern Red Hat Linux distribution with a 2.6 kernel. After I got it finaly working (Red Hat has a special way of making a new kernel…) the Netatalk service would couse a kernel panic when it had to use the LocalTalk device. I tried it with many configuration changes in the atalkd.conf..but it didn’t work.
Then I decided to take a Linux distribution which fitted more to the historical situation. I read that ISA support was standard in the 2.4 kernel and not anymore in the 2.6 kernel. So I switched to Debian Woody with a 2.4.19 kernel update. This update was straigt forward. I used the config-2.2.20-idepci file in the /boot directory to create a .config file. With the use of the command make menuconfig I added AppleTalk and the LocalTalk PC card. After that I did the following commands:

make
make install
make modules
make modules_install

and…reboot

The card is only seen by Linux if you have booted first in DOS and have seen dat the card is working. Then reboot in Linux and a the system will actualy see the card.

You can use the card if you edit /etc/modules and add ltpc.

# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with
# a "#", and everything on the line after them are ignored.

af_packet
8139too
dummy
ltpc

and also in /etc/modutils/arch/i386

alias ltpc lt0

Then I installed Netatalk:

 Package: netatalk
 Version: 1.4b2+asun2.1.3-6
 Section: net
 Priority: optional
 Architecture: i386
 Depends: netbase, libpam-modules, libc6 (>= 2.1), libpam0g, libwrap0
 Conflicts: netatalk-asun, libatalk14g, libatalk1
 Replaces: netatalk-asun, libatalk14, libatalk1
 Installed-Size: 604
 Maintainer: David Huggins-Daines <dhd@debian.org>
 Description: Appletalk user binaries
  Netatalk is an implementation of the AppleTalk Protocol Suite for
  BSD-derived systems.  The current release contains support for
  EtherTalk Phase I and II, DDP, RTMP, NBP, ZIP, AEP, ATP, PAP, ASP, and
  AFP.

The biggest fight to get it working was the configuration of atalkd. I got it finaly working when I just entered lt0 in the /etc/netatalk/atalkd.conf. Netatalk will fill in the correct addresses itself. Mine (/etc/netatalk/atalkd.conf ) looks now like this.

lt0 -phase 2 -net 0-65534 -addr 65280.105

If you do a ifconfig you see the lt0 as a network device:

If you do a nbplkup you see this:

I now can download stuff to the macintosh Plus without any problem.

Here are two pictures how it loks on my Mac.

This operation costs me about two month of blood, sweet and tears…. But I had also a lot of fun!

Next challenge is to get more of these cards and see if I get them up and running in a moderne Linx enviroment!

DOS Software 3005006-EB7D:

http://macintosh.vanegten.com/pccard01.dd
http://macintosh.vanegten.com/pccard02.dd

Discussion in m68kla:

Post

Hietrbij mijn aantekeningen uit /etc/netatalk/atalkd.conf

###############

##let op hij doet het door eerst te booten met MSDOS

## daarna direct door naar Debian. Dan HD71 aan en netatalk starten. Hij vult dan eth0 in. Daarna die uitcomm. en vervangen door alleen    lt0    Dan netatalk weer starten en go!

lt0

debian:/home/tjabring# vi /etc/netatalk/atalkd.conf

debian:/home/tjabring# /etc/init.d/netatalk  stop

Stopping AppleTalk Daemons: afpd atalkd.

debian:/home/tjabring# /etc/init.d/netatalk  start

Starting AppleTalk Daemons (this will take a while): atalkd afpd.

debian:/home/tjabring# nbplkup

debian:netatalk                           65280.29:4

debian:Workstation                        65280.29:4

debian:AFPServer                          65280.29:128

debian:/home/tjabring# nbplkup

debian:AFPServer                          65280.29:128

debian:netatalk                           65280.29:4

debian:Workstation                        65280.29:4

plus:Macintosh Plus                     0.92:250