Thread
Need help connecting PowerBook 230 to a LAN and to the Web
Hi! I'm new to this forum, and new to old Macintosh machines, but not new to networking and computers. I was recently given the following equipment, and now I have a challenge for you:
Apple PowerBook 230
Duo Dock
AsanteTalk Ethernet to LocalTalk Bridge
All of the equipment works, as far as I can tell. Right now I have the PowerBook in the Duo Dock, a LocalTalk cable connecting the Duo Dock's "printer" port to the AsanteTalk device, and a standard ethernet cable connecting the AsanteTalk device to my 10/100 mbps LAN (which has a variety of Linux and Windows machines on it).
That's where I am. Here are some things I'd like to be able to do, if possible:
1. Print from the PowerBook in its dock to a printer on my LAN. Note that the printers on my LAN have no idea what a Macintosh is, or what LocalTalk is... they expect to be printed to by Linux or Windows machines.
2. Transfer files between the PowerBook and Linux or Windows computers on my LAN
3. Install browser software on the PowerBook and somehow connect it to the Internet, so it can be used to browse the Web.
Are any of these things possible?
Any suggestions?
Please forgive that I really, really don't know anything about Macs. I really, really wanted one back in the early 1990's but couldn't afford one. So I became a Windows and eventually a Linux enthusiast. But it would be really cool to get this cute little Apple machine doing real stuff!
Dave
Apple PowerBook 230
Duo Dock
AsanteTalk Ethernet to LocalTalk Bridge
All of the equipment works, as far as I can tell. Right now I have the PowerBook in the Duo Dock, a LocalTalk cable connecting the Duo Dock's "printer" port to the AsanteTalk device, and a standard ethernet cable connecting the AsanteTalk device to my 10/100 mbps LAN (which has a variety of Linux and Windows machines on it).
That's where I am. Here are some things I'd like to be able to do, if possible:
1. Print from the PowerBook in its dock to a printer on my LAN. Note that the printers on my LAN have no idea what a Macintosh is, or what LocalTalk is... they expect to be printed to by Linux or Windows machines.
2. Transfer files between the PowerBook and Linux or Windows computers on my LAN
3. Install browser software on the PowerBook and somehow connect it to the Internet, so it can be used to browse the Web.
Are any of these things possible?
Any suggestions?
Please forgive that I really, really don't know anything about Macs. I really, really wanted one back in the early 1990's but couldn't afford one. So I became a Windows and eventually a Linux enthusiast. But it would be really cool to get this cute little Apple machine doing real stuff!
Dave
What kind of Linux machine?
The quickest start with be
(a) install "netatalk" on the Linux box and used "papd" for printing. You could use ghostprint to pretend to the Mac that you are really a networked laserwriter. You would also be able to configure an AppleShare server on the Linux box. The Linux kernel needs AF_APPLETALK support enabled.
( B) workout how to use the localtalk/ethernet bridge, they can be pedantic, best results seem to be if you power up that device last.
© getting TCP going on the Mac would be the hardest, as you need a Mac-IP gateway running somewhere. I run one on my NetBSD gateway box which does the packing and unpacking of IP packets from DDP.
Hopefully that helps.
The quickest start with be
(a) install "netatalk" on the Linux box and used "papd" for printing. You could use ghostprint to pretend to the Mac that you are really a networked laserwriter. You would also be able to configure an AppleShare server on the Linux box. The Linux kernel needs AF_APPLETALK support enabled.
( B) workout how to use the localtalk/ethernet bridge, they can be pedantic, best results seem to be if you power up that device last.
© getting TCP going on the Mac would be the hardest, as you need a Mac-IP gateway running somewhere. I run one on my NetBSD gateway box which does the packing and unpacking of IP packets from DDP.
Hopefully that helps.
Once you do get the thing networked, here are some suggestions for suitable browsers. As you might suspect, your choices are somewhat limited. Don't expect modern webpages to render well.
A fast, text-only browser is wannabe68k. I have used it on my Duos on dialup.
If you must browse with pictures, then consider netscape (versions 2 and 3). It will function, for suitably generous definitions of "function." Perhaps even version 4 will run, but its large memory footprint will pose a challenge.
The oldest functioning version of iCab presumably will also run on a 230, as long as you're running system 7.5 or above. I've never tried this myself, however, so I do not know for certain.
A fast, text-only browser is wannabe68k. I have used it on my Duos on dialup.
If you must browse with pictures, then consider netscape (versions 2 and 3). It will function, for suitably generous definitions of "function." Perhaps even version 4 will run, but its large memory footprint will pose a challenge.
The oldest functioning version of iCab presumably will also run on a 230, as long as you're running system 7.5 or above. I've never tried this myself, however, so I do not know for certain.
My PowerBook 230 is running "System 7.1". I have no idea how or where to find "System 7.5". I don't have any system floppy disks or anything like that for the PowerBook. What is "iCab"?
Even browsing through my LAN's connection to the internet from the PowerBook 230 without pictures would be an accomplishment! Right now I have *no way at all* to move files between the PowerBook and other computers, except possibly by use of the PowerBook's analog modem.
On my Linux machines I am running ubuntu 8.10, variously 32-bit and 64-bit. I will look into the "netatalk" and "papd" programs.
I wonder if there is a "Mac-IP gateway" that will run on ubuntu?
Even browsing through my LAN's connection to the internet from the PowerBook 230 without pictures would be an accomplishment! Right now I have *no way at all* to move files between the PowerBook and other computers, except possibly by use of the PowerBook's analog modem.
On my Linux machines I am running ubuntu 8.10, variously 32-bit and 64-bit. I will look into the "netatalk" and "papd" programs.
I wonder if there is a "Mac-IP gateway" that will run on ubuntu?
I'm certainly willing to attempt compilation of code, but if the compilation is to be on the PowerBook 230 running System 7.1, I may need some help figuring out how to do it. Forgive my ignorance, porter, but what code have you written?
My recent compilation experience is primarily with Microsoft C, Visual Basic, and Visual C++ running on Windows. I have done some compilation on Linux machines also, but mostly following "cookbook" instructions when doing so.
This week I hope to find time to install and get netatalk running.
My recent compilation experience is primarily with Microsoft C, Visual Basic, and Visual C++ running on Windows. I have done some compilation on Linux machines also, but mostly following "cookbook" instructions when doing so.
This week I hope to find time to install and get netatalk running.
It's a Mac-IP gateway that runs on a netatalk enabled UNIX host. It's a C daemon that uses AF_APPLETALK sockets to talk DDP, then uses a secondary process to translate those IP packets to the UNIX host. I run mine on NetBSD, it compiles on Linux, but has not been tested.I may need some help figuring out how to do it. Forgive my ignorance, porter, but what code have you written?
What's wrong with Netatalk?Depends how keen you are to try and compile my code.I wonder if there is a "Mac-IP gateway" that will run on ubuntu?![]()
As for transferring files: You have a Duo Dock - therefore you have SCSI (for external SCSI drives - like a ZIP for example, and a matching parallel or USB ZIP for a PC) and a floppy drive - the Mac can read PC-formatted floppies. If you download compressed files on the PC and put the compressed file on a floppy, then uncompress them on the Mac, you should be fine.
I unfortunately do not possess any cables that connect to the SCSI port on the Duo Dock. I have some SCSI CD-ROM drives, hard disks, and even a few tape drives, but all SCSI cables I have are for the "Centronics"-style or IBM-style SCSI connectors.
I am encouraged to read that the Macintosh can read "PC-formatted" (1.44MB?) 3.5" floppy disks... I didn't know this was possible.
I presume from porter's last post that I will need to get netatalk working before I attempt to add his gateway. I hope to work on this soon.
I am encouraged to read that the Macintosh can read "PC-formatted" (1.44MB?) 3.5" floppy disks... I didn't know this was possible.
I presume from porter's last post that I will need to get netatalk working before I attempt to add his gateway. I hope to work on this soon.
Yes, I use netatalk's name binding daemon, on IRIX I use KTalk and Darwin/MacOSX/AUX I use the native OS nbp. Alas on AUX there is no simple way of programmatically getting IP packets in and out of the UNIX box itself.I presume from porter's last post that I will need to get netatalk working before I attempt to add his gateway. I hope to work on this soon.
I hope this thread doesn't turn into "how to setup netatalk", but I must admit after perusing the "manual" for the program and playing around a bit without success I am unsure what to do. On my Linux box (ubuntu 8.10 64-bit) I have netatalk installed. lsmod shows the "appletalk" module loaded. The Linux box is connected to a 10/100 switch alongside my AsanteTalk module, which in turn is connected via a mini-DIN8 cable to the "printer" port on the Duo Dock. The "link integrity" LED on the AsanteTalk is glowing green, and the switch "sees" the link to it as well.
The printer I would like to allow the PowerBook 230 (System 7.1) in the Duo Dock print to is on the same subnet of the LAN as the above two devices. The Linux box can print to it, of course. When I invoke "Chooser" on the PowerBook, and then click on "AppleShare" I am shown an empty box in which to "select a file server", and below that a radiobutton indicating that AppleTalk is Active.
I do not know how to:
- tell netatalk to share the printer that it knows how to print to with a LocalTalk network
- determine if netatalk is even aware of the AsanteTalk box and its attached LocalTalk network
- tell the PowerBook to try to print to a printer on the LocalTalk network, or even that a printer exists on it
The other options I seen in Chooser are:
AppleTalk ImageWriter
ImageWriter
LaserWriter
LQ AppleTalk ImageWriter
LQ ImageWriter
Personal LaserWriter SC
Personal LW LS
StyleWriter
Each of them leads to a similar blank list in which I am to "select an AppleTalk ImageWriter" or something similar.
My guess is that I need to somehow configure netatalk to advertise the availability of a printer to the LocalTalk network as if it was some kind of printer that the PowerBook knows how to print to. I further guess that I need to put a line or two into atalkd.conf and/or papd.conf, but I am clueless about what lines I need. I know the details of the printer I would like to share:
Brother DCP-9040CN color laser printer
lpd://192.168.1.213
Brother offers drivers for MacOS X on its website, for what that is worth.
The printer I would like to allow the PowerBook 230 (System 7.1) in the Duo Dock print to is on the same subnet of the LAN as the above two devices. The Linux box can print to it, of course. When I invoke "Chooser" on the PowerBook, and then click on "AppleShare" I am shown an empty box in which to "select a file server", and below that a radiobutton indicating that AppleTalk is Active.
I do not know how to:
- tell netatalk to share the printer that it knows how to print to with a LocalTalk network
- determine if netatalk is even aware of the AsanteTalk box and its attached LocalTalk network
- tell the PowerBook to try to print to a printer on the LocalTalk network, or even that a printer exists on it
The other options I seen in Chooser are:
AppleTalk ImageWriter
ImageWriter
LaserWriter
LQ AppleTalk ImageWriter
LQ ImageWriter
Personal LaserWriter SC
Personal LW LS
StyleWriter
Each of them leads to a similar blank list in which I am to "select an AppleTalk ImageWriter" or something similar.
My guess is that I need to somehow configure netatalk to advertise the availability of a printer to the LocalTalk network as if it was some kind of printer that the PowerBook knows how to print to. I further guess that I need to put a line or two into atalkd.conf and/or papd.conf, but I am clueless about what lines I need. I know the details of the printer I would like to share:
Brother DCP-9040CN color laser printer
lpd://192.168.1.213
Brother offers drivers for MacOS X on its website, for what that is worth.
First step with netatalk is "is it running?" It starts with a daemon
eg on my box this is
which is normally self configuring.
The first program to see what else is on the appletalk network is
This will probe the network to see what names have been registered.
eg, mine, with nothing else running on the net says
The ADSP is my ADSP terminal server so you can log onto the gateway using the "ADSP Tool". IPADDRESS and IPGATEWAY are my macipd ready for duty. The last two are registered by netatalk itself, here on the echo socket.
You need to go through a configuration phase with any file sharing to say what you want shared.
eg on my box this is
Code:
/usr/pkg/libexec/netatalk/atalkd
The first program to see what else is on the appletalk network is
Code:
/usr/pkg/bin/nbplkup
eg, mine, with nothing else running on the net says
Code:
$ nbplkup
gateway:ADSP 65280.94:128
10.1.3.1:IPADDRESS 65280.94:72
10.1.3.1:IPGATEWAY 65280.94:72
gateway:netatalk 65280.94:4
gateway:Workstation 65280.94:4
You need to go through a configuration phase with any file sharing to say what you want shared.
At present my netatalk configuration files (atalkd.conf and papd.conf) contain nothing but commented-out lines. When I execute the commands atalkd and nbplkup on my Linux box, this is what I get:
dave@quad:/$ atalkd
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/$ nbplkup
quad:AFPServer 65280.8:128
quad:netatalk 65280.8:4
quad:Workstation 65280.8:4
dave@quad:/$
dave@quad:/$ atalkd
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/$ nbplkup
quad:AFPServer 65280.8:128
quad:netatalk 65280.8:4
quad:Workstation 65280.8:4
dave@quad:/$
Sounds like it's up and ready for business, unless your running atalkd killed the one that is already running.dave@quad:/$ nbplkupquad:AFPServer 65280.8:128
quad:netatalk 65280.8:4
quad:Workstation 65280.8:4
dave@quad:/$
If you go to the Chooser on a mac and select file server it should at least list "quad".
Does "netstat -a" list the appletalk sockets?
Eg on my NetBSD box I get
Code:
Active ATALK connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
ddp 0 0 65280.94.128 *.*.*
ddp 0 0 65280.94.72 *.*.*
ddp 0 0 65280.94.1 *.*.*
ddp 0 0 65280.94.2 *.*.*
ddp 0 0 65280.94.4 *.*.*
ddp 0 0 65280.94.6 *.*.*
ddp 0 0 *.*.1 *.*.*
ddp 0 0 *.*.2 *.*.*
ddp 0 0 *.*.4 *.*.*
ddp 0 0 *.*.6 *.*.*
Well, Chooser still shows me nothing. I also do not see the appletalk sockets:
dave@quad:/home$ netstat -i
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 51182 60 0 0 33413 0 0 0 BMRU
lo 16436 0 851 0 0 0 851 0 0 0 LRU
dave@quad:/home$ netstat -a | grep ddp
dave@quad:/home$ netstat -a | grep DDP
dave@quad:/home$ netstat -a | grep ATALK
dave@quad:/home$ atalkd
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/home$
Possibly I should add the line "eth0" to my atalkd.conf file?
dave@quad:/home$ netstat -i
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 51182 60 0 0 33413 0 0 0 BMRU
lo 16436 0 851 0 0 0 851 0 0 0 LRU
dave@quad:/home$ netstat -a | grep ddp
dave@quad:/home$ netstat -a | grep DDP
dave@quad:/home$ netstat -a | grep ATALK
dave@quad:/home$ atalkd
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/home$
Possibly I should add the line "eth0" to my atalkd.conf file?
"atalkd" is the netatalk daemon so should only be run once, and it should keep going.Possibly I should add the line "eth0" to my atalkd.conf file?
If you only have one network interface atalk should work things out, how many do you have?
Also, if you have other macs on the network, running "nbplkup" should show up those other macs.
Here is "nbplkup" run from my gateway, and sees another netatalk box..
Code:
$ nbplkup
gateway:ADSP 65280.94:128
10.1.3.1:IPADDRESS 65280.94:72
10.1.3.1:IPGATEWAY 65280.94:72
gateway:netatalk 65280.94:4
gateway:Workstation 65280.94:4
saxon:AFPServer 65280.152:128
saxon:netatalk 65280.152:4
saxon:Workstation 65280.152:4
"saxon" is Ubuntu, neither ifconfig or netstat show ddp sockets.
Whereas on NetBSD you get
Code:
rtk1: flags=8843 mtu 1500
media: Ethernet autoselect (none)
status: active
......
atalk 65280.94 range 1-65534 phase 2 broadcast 65280.94
I'm beginning to wonder if the problem is either in the AsanteTalk device or in the PowerBook or Duo Dock.
I added "eth0" to my atalkd.conf file and restarted my Linux box. Now I get:
dave@quad:/etc/netatalk$ atalkd
eth0: Operation not permitted
Can't configure multicast.
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/etc/netatalk$ nbplkup
quad:AFPServer 65280.108:128
quad:netatalk 65280.108:4
quad:Workstation 65280.108:4
dave@quad:/etc/netatalk$ aecho quad:Workstation
22 bytes from 65280.108: aep_seq=0. time=0. ms
22 bytes from 65280.108: aep_seq=1. time=0. ms
22 bytes from 65280.108: aep_seq=2. time=0. ms
^C
----65280.108 AEP Statistics----
3 packets sent, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
dave@quad:/etc/netatalk$
Can you help me figure out how to diagnose the LocalTalk portion of my system?
I added "eth0" to my atalkd.conf file and restarted my Linux box. Now I get:
dave@quad:/etc/netatalk$ atalkd
eth0: Operation not permitted
Can't configure multicast.
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/etc/netatalk$ nbplkup
quad:AFPServer 65280.108:128
quad:netatalk 65280.108:4
quad:Workstation 65280.108:4
dave@quad:/etc/netatalk$ aecho quad:Workstation
22 bytes from 65280.108: aep_seq=0. time=0. ms
22 bytes from 65280.108: aep_seq=1. time=0. ms
22 bytes from 65280.108: aep_seq=2. time=0. ms
^C
----65280.108 AEP Statistics----
3 packets sent, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
dave@quad:/etc/netatalk$
Can you help me figure out how to diagnose the LocalTalk portion of my system?
The best bet is to....Can you help me figure out how to diagnose the LocalTalk portion of my system?
Make sure you are using proper LocalTalk cabling to the AsanteTalk box, not just a serial/printer cable.
Switch off the AsanteTalk box.
Start the linux box with netatalk.
Start the mac with LocalTalk/AppleTalk enabled on the printerport
Then once the machine has started up, powerup the AsanteTalk box.
Try nbplkup from the linux box.
Go the the control panel and select AppleTalk or Network depending on if you are OpenTransport or classic and see if that says anything different.
I've had varying success with the AsanteTalk box, it seems to work best when there is an appletalk router already on the network.
If you already have a Mac with ethernet, the control panel "LocalTalk Bridge" seems to work better than the AsanteTalk box.
Here is a good example:
Which shows
(a) Macintosh Classic running System 6 on 40000.16
( B) Compaq running W2K server on 41384.136
© gateway running NetBSD on 40215.94
(d) AsanteTalk on 40000.15
Note MacTCP running with gateway as server, and classic allocated an address.
Code:
$ nbplkup
gateway:ADSP 40215.94:128
10.1.3.1:IPADDRESS 40215.94:72
10.1.3.1:IPGATEWAY 40215.94:72
gateway:netatalk 40215.94:4
gateway:Workstation 40215.94:4
EVO:DceDspRpc DynEpt 638.1 41384.136:136
EVO:DceDspRpc DynEpt 114.1 41384.136:129
EVO:DceDspRpc Endpoint Mapper 41384.136:130
EVO:AFPServer 41384.136:131
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Prt 44318.148:2
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Rtr 43497.215:2
Asant?Talk 94AFE828:AsantTalk 40000.15:252
10.1.3.2:IPADDRESS 40000.16:72
porter:Macintosh Classic 40000.16:253
(a) Macintosh Classic running System 6 on 40000.16
( B) Compaq running W2K server on 41384.136
© gateway running NetBSD on 40215.94
(d) AsanteTalk on 40000.15
Note MacTCP running with gateway as server, and classic allocated an address.
I have an interesting catch-22.
I can't use AsanteTalk unless I have an AppleTalk seed/router on the ethernet. I'm using my win2k box to do that.
I can use MacTCP from Classic thru AsanteTalk to NetBSD to my MacIP gateway. (tested with Browser6 of course).
But my Ubuntu box refuses to start netatalk when the win2k box is up claiming
when I start atalkd.
Now you may be able to start atalkd on the Linux box as a seed on the network to get the AsanteTalk box to grab an address in a reasonable range. Perhaps I should try that.
I can't use AsanteTalk unless I have an AppleTalk seed/router on the ethernet. I'm using my win2k box to do that.
I can use MacTCP from Classic thru AsanteTalk to NetBSD to my MacIP gateway. (tested with Browser6 of course).
But my Ubuntu box refuses to start netatalk when the win2k box is up claiming
Code:
Jan 28 19:18:43 saxon kernel: [ 992.358470] Too many routes/iface.
Now you may be able to start atalkd on the Linux box as a seed on the network to get the AsanteTalk box to grab an address in a reasonable range. Perhaps I should try that.
I shutdown the win2k box and the gateway.
Okay, now I have started up the Linux box first then started up the classic with the AsanteTalk.
I get a weird looking output from nbplkup on linux...
Note, the classic can now see the Linux box in the Chooser.
When I startup the NetBSD one I get
Which looks alot nicer, and classic can still see Linux box in Chooser.
Now when I fireup the win2k box with the seed the Linux box disappears from the Chooser, and nbplkup fails with
Now we can see that the AsanteTalk box has correctly switched address now the network has been seeded. The NetBSD box didn't, and the Linux box has collapsed in a heap.
I'm happily able to mount the win2k share from the Chooser.
However now the MacTCP gateway is broken until I reset the gateway box.
So, gateway is reset...
And bingo the MacIP gateway works...
Upshot is I think the Ubuntu netatalk is shagged.
Okay, now I have started up the Linux box first then started up the classic with the AsanteTalk.
I get a weird looking output from nbplkup on linux...
Code:
root@saxon:/etc/init.d# nbplkup
saxon:AFPServer 65280.249:128
saxon:netatalk 65280.249:4
saxon:Workstation 65280.249:4
AsantéTalk 94AFE828: porter:Macintosh Classic 65397.152:253
When I startup the NetBSD one I get
Code:
bash-3.00# nbplkup
gateway:ADSP 65280.94:128
10.1.3.1:IPADDRESS 65280.94:72
10.1.3.1:IPGATEWAY 65280.94:72
gateway:netatalk 65280.94:4
gateway:Workstation 65280.94:4
saxon:AFPServer 65280.249:128
saxon:netatalk 65280.249:4
saxon:Workstation 65280.249:4
porter:Macintosh Classic 65397.152:253
Asant?Talk 94AFE828:AsantTalk 65397.151:252
Now when I fireup the win2k box with the seed the Linux box disappears from the Chooser, and nbplkup fails with
Code:
nbp_lookup: Cannot assign requested address
Code:
bash-3.00# nbplkup
gateway:ADSP 65280.94:128
10.1.3.1:IPADDRESS 65280.94:72
10.1.3.1:IPGATEWAY 65280.94:72
gateway:netatalk 65280.94:4
gateway:Workstation 65280.94:4
EVO:DceDspRpc DynEpt 114.1 41384.136:129
EVO:DceDspRpc Endpoint Mapper 41384.136:130
EVO:AFPServer 41384.136:131
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Prt 44318.148:2
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Rtr 43497.215:2
porter:Macintosh Classic 40000.112:253
Asant?Talk 94AFE828:AsantTalk 40000.111:252
However now the MacTCP gateway is broken until I reset the gateway box.
So, gateway is reset...
Code:
bash-3.00# nbplkup
gateway:ADSP 43797.94:128
10.1.3.1:IPADDRESS 43797.94:72
10.1.3.1:IPGATEWAY 43797.94:72
gateway:netatalk 43797.94:4
gateway:Workstation 43797.94:4
EVO:DceDspRpc DynEpt 614.1 41384.136:136
EVO:DceDspRpc DynEpt 114.1 41384.136:129
EVO:DceDspRpc Endpoint Mapper 41384.136:130
EVO:AFPServer 41384.136:131
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Prt 44318.148:2
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Rtr 43497.215:2
porter:Macintosh Classic 40000.112:253
Asant?Talk 94AFE828:AsantTalk 40000.111:252
Code:
Asant?Talk 94AFE828:AsantTalk 40000.111:252
porter:Macintosh Classic 40000.112:253
10.1.3.2:IPADDRESS 40000.112:72
See comments below, interspersed in a message porter sent earlier... my text is hopefully in italics.
The best bet is to....
Make sure you are using proper LocalTalk cabling to the AsanteTalk box, not just a serial/printer cable.
I have only one mini-DIN8 cable. I hope it is the correct type. It was given to me along with the PowerBook, and had been used to connect the PowerBook to a LaserWriter printer in the past. I could check continuity of the cable with an ohmmeter, but I suspect it is OK. Note I do not have "terminating resistors" on either the PowerBook end or the AsanteTalk end of this cable, in case that likely matters.
Switch off the AsanteTalk box.
Done
Start the linux box with netatalk.
Done
Start the mac with LocalTalk/AppleTalk enabled on the printerport
Here's where I may need help confirming I have this step done correctly. When I power on the PowerBook, and then click Control Panels | Network, I see only one item, an icon labeled "LocalTalk Built-In". Clicking on this icon does nothing. When I open Chooser, and then click on "AppleShare", on the right hand side of the window I see: "Select a file server:" above a blank rectangle, above an OK button, above a pair of radiobuttons... "AppleTalk" is "Active".
Then once the machine has started up, powerup the AsanteTalk box.
When the AsanteTalk device is powered up, the PWR and Li (link) LEDs immediately turn green, and the TX and RX LEDs begin flashing irregularly, as if the AsanteTalk is communicating with something.
Try nbplkup from the linux box.
nbplkup returns exactly the same response as it did before I powered on the AsanteTalk device:
dave@quad:/$ nbplkup
quad:AFPServer 65280.108:128
quad:netatalk 65280.108:4
quad:Workstation 65280.108:4
dave@quad:/$
Go the the control panel and select AppleTalk or Network depending on if you are OpenTransport or classic and see if that says anything different.
Clicking on Control Panels | Network produces the same result as it did before I turned on the AsanteTalk device. I do not see an icon in Control Panels called "AppleTalk".
I've had varying success with the AsanteTalk box, it seems to work best when there is an appletalk router already on the network.
Sadly, I do not have such a thing, unless that's what my Linux box is providing.
If you already have a Mac with ethernet, the control panel "LocalTalk Bridge" seems to work better than the AsanteTalk box.
I do not have any other Macintosh computers, either with or without ethernet. I also do not have any LocalTalk printers.
The best bet is to....
Make sure you are using proper LocalTalk cabling to the AsanteTalk box, not just a serial/printer cable.
I have only one mini-DIN8 cable. I hope it is the correct type. It was given to me along with the PowerBook, and had been used to connect the PowerBook to a LaserWriter printer in the past. I could check continuity of the cable with an ohmmeter, but I suspect it is OK. Note I do not have "terminating resistors" on either the PowerBook end or the AsanteTalk end of this cable, in case that likely matters.
Switch off the AsanteTalk box.
Done
Start the linux box with netatalk.
Done
Start the mac with LocalTalk/AppleTalk enabled on the printerport
Here's where I may need help confirming I have this step done correctly. When I power on the PowerBook, and then click Control Panels | Network, I see only one item, an icon labeled "LocalTalk Built-In". Clicking on this icon does nothing. When I open Chooser, and then click on "AppleShare", on the right hand side of the window I see: "Select a file server:" above a blank rectangle, above an OK button, above a pair of radiobuttons... "AppleTalk" is "Active".
Then once the machine has started up, powerup the AsanteTalk box.
When the AsanteTalk device is powered up, the PWR and Li (link) LEDs immediately turn green, and the TX and RX LEDs begin flashing irregularly, as if the AsanteTalk is communicating with something.
Try nbplkup from the linux box.
nbplkup returns exactly the same response as it did before I powered on the AsanteTalk device:
dave@quad:/$ nbplkup
quad:AFPServer 65280.108:128
quad:netatalk 65280.108:4
quad:Workstation 65280.108:4
dave@quad:/$
Go the the control panel and select AppleTalk or Network depending on if you are OpenTransport or classic and see if that says anything different.
Clicking on Control Panels | Network produces the same result as it did before I turned on the AsanteTalk device. I do not see an icon in Control Panels called "AppleTalk".
I've had varying success with the AsanteTalk box, it seems to work best when there is an appletalk router already on the network.
Sadly, I do not have such a thing, unless that's what my Linux box is providing.
If you already have a Mac with ethernet, the control panel "LocalTalk Bridge" seems to work better than the AsanteTalk box.
I do not have any other Macintosh computers, either with or without ethernet. I also do not have any LocalTalk printers.
Then it might be an idea to get one, no? IIRC, the Dock has the Honda HDI-50 square Powerbook style SCSI port.I unfortunately do not possess any cables that connect to the SCSI port on the Duo Dock.
Another option is to mount a bare SCSI drive internally in the Dock - there is space for one. Format it using the Duo, pull it, transfer to a SCSI-equipped PC with MacDrive or some other HFS/HFS+ read/write software on it, drag the files you want over, pull it, remount it in the Dock.
Some Duo Docks came with built-in Ethernet, but it may be a socket type that is unfamiliar to you, called AAUI. Symbol: If there is one, you need an Apple AAUI to Cat-5 adapter to use it.
There are also two Nubus expansion card slots in the Dock, and Nubus ethernet cards are readily available on evilbay, as are the Powerbook SCSI cables and AAUI adapters.
Other than that, see first line of sig below.
It does have to be a pair of LocalTalk connector boxes with localtalk cabling between them, and ideally terminators on each end. A serial cable alas does not work. The little boxes contain an isolating transformer and turn the cabling into a bus.Make sure you are using proper LocalTalk cabling to the AsanteTalk box, not just a serial/printer cable. I have only one mini-DIN8 cable. I hope it is the correct type. It was given to me along with the PowerBook, and had been used to connect the PowerBook to a LaserWriter printer in the past.
Try changing your atalk.conf to say something likeI've had varying success with the AsanteTalk box, it seems to work best when there is an appletalk router already on the network. Sadly, I do not have such a thing, unless that's what my Linux box is providing.
Code:
eth0 -phase 2 -seed -net 20000-30000 -addr 20000.10
Code:
man atalkd
I just tested this with a Macintosh Classic running System 6.0.8, but it did have the latest AppleTalk installed.Do you think it would help for me to try to upgrade the OS on the PowerBook 230 from "System 7.1" to something newer?
System 7.5 is a major advance.
System 7.6.1 is the end of the road for System 7 and starts assuming you want OpenTransport.
And if you feel the need to use Open Transport, skip all of the early versions and go straight to OT 1.1.1. OT 1.1.1 will run happily on System 7.1 if you have 8MB of system RAM.System 7.6.1 is the end of the road for System 7 and starts assuming you want OpenTransport.
OK... lots to respond to. First of all, the Duo Dock I have is, I believe, the "first generation" Duo Dock. It has 2 NuBus slots (both currently empty). It has a SCSI port with an "HDI-30" connector... nothing is connected to this. It has an Apple Desktop Bus port, to which a keyboard/mouse is attached. It has a "Printer" port (mini-DIN8), which I assume to be an AppleTalk/LocalTalk port. It does not have any kind of ethernet port... neither an RJ-45 jack nor an AAUI socket.
If the mini-DIN8 cable I have is not actually a "LocalTalk" cable, then I do not understand the difference between that and a "serial" cable. The cable is about 2 meters long, and does not appear to have any termination built into it... it is simply a "straight-through" cable connecting the "printer" port of the Duo Dock to the AsanteTalk device I have. As I have indicated in earlier posts, the LEDs on the AsanteTalk device seem to indicate that there is both transmission and reception happening on the line.
I do not know how to determine what version of AppleTalk is running on the PowerBook. "About This Macintosh" indicates:
PowerBook Duo 230
Total memory 4,096K
System Software 7.1
I do not know what Open Transport is.
I see lots of files on this website:
http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/Macintosh/System/
but I'm not sure which I might need. My guess is that I can download a file, put it onto a 1.44M FAT-formatted floppy disk, and then somehow install it onto the PowerBook, perhaps with help from experts here.
Where should I start?
If the mini-DIN8 cable I have is not actually a "LocalTalk" cable, then I do not understand the difference between that and a "serial" cable. The cable is about 2 meters long, and does not appear to have any termination built into it... it is simply a "straight-through" cable connecting the "printer" port of the Duo Dock to the AsanteTalk device I have. As I have indicated in earlier posts, the LEDs on the AsanteTalk device seem to indicate that there is both transmission and reception happening on the line.
I do not know how to determine what version of AppleTalk is running on the PowerBook. "About This Macintosh" indicates:
PowerBook Duo 230
Total memory 4,096K
System Software 7.1
I do not know what Open Transport is.
I see lots of files on this website:
http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/Macintosh/System/
but I'm not sure which I might need. My guess is that I can download a file, put it onto a 1.44M FAT-formatted floppy disk, and then somehow install it onto the PowerBook, perhaps with help from experts here.
Where should I start?
Well, although I find trying to get old equipment to work a pleasurable pasttime, I'm not particularly inclined to spend much money on this PowerBook project. If I could find a Nubus ethernet card for $10 or less, I might jump on it, but my experience with eBay in recent months is that shipping alone is usually about $10.
Anyone on this forum have a NuBus ethernet card collecting dust?
Anyone on this forum have a NuBus ethernet card collecting dust?
Yes, the major advantage is the Mac will use TCP/IP natively on ethernet rather than having to do the MacIP packing-unpacking-gateway.Update... I found for $20 (including shipping) a Daynaport NuBus ethernet card, which hopefully will arrive in the next week or two. Possibly this will work better than the AsanteTalk device.
While I wait for my NuBus ethernet card to arrive, I'd like to upgrade the system software on my PowerBook 230 to the best version that was produced for it, in hopes that it by doing so I will increase my chances of success in getting the PowerBook "networked".
My PowerBook 230 has a 68K processor, not a "PowerPC"... I am trying to figure out if I should attempt to install "System 7.5 Version 7.5.3" which is apparently available from an Apple software archive:
http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/Macintosh/System/Older_System/System_7.5_Version_7.5.3/
According to a text file on the site, "System 7.5.3 requires an Apple Macintosh or PowerBook computer with at
least 4MB of RAM."
I do not think I have any way to restore System 7.1 if I screw this upgrade up, so I am a bit worried about attempting it. I'm also not sure if I will gain anything by moving from System 7.1 to System 7.5.3.
Any advice?
My PowerBook 230 has a 68K processor, not a "PowerPC"... I am trying to figure out if I should attempt to install "System 7.5 Version 7.5.3" which is apparently available from an Apple software archive:
http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/Macintosh/System/Older_System/System_7.5_Version_7.5.3/
According to a text file on the site, "System 7.5.3 requires an Apple Macintosh or PowerBook computer with at
least 4MB of RAM."
I do not think I have any way to restore System 7.1 if I screw this upgrade up, so I am a bit worried about attempting it. I'm also not sure if I will gain anything by moving from System 7.1 to System 7.5.3.
Any advice?
4MB isn't enough for 7.6.1 or 7.5.3/7.5.5 really. It's going to be sluggish. Browsing the web on 4MB...not going to happen, unless we're talking about text-only.
If you want to make it useful, try and find a 20MB module for it.
Here's one which is cheap:
http://www.memoryx.net/pb21020.html
On another website the same 20MB module was $99!
If you want to make it useful, try and find a 20MB module for it.
Here's one which is cheap:
http://www.memoryx.net/pb21020.html
On another website the same 20MB module was $99!
I have plenty of machines with which to browse the web. It would be fun to get a text-only browser running on the PowerBook, but really my primary goals are to be able to move files between it and other machines on my ethernet LAN and to be able to print from it to one of the printers on my ethernet LAN.
Thanks for the link to the memory module, tho. I'll think about it.
Nice to know that I need not bother to upgrade from System 7.1 unless I have more memory than I currently do.
Thanks for the link to the memory module, tho. I'll think about it.
Nice to know that I need not bother to upgrade from System 7.1 unless I have more memory than I currently do.
I've given up on the AsanteTalk device. I never did see it show up on an nbplkup listing, although it certainly seems to be functional, and reportedly was functional when it was last used years ago.
I also never saw it show up on Chooser. I don't know if it should have, tho.
I'm planning to list it on eBay, but if anyone here wants to buy it for $20+shipping, let me know. I'd also consider a trade, for something else that might be useful to me, as the proud owner of a 4MB Powerbook 230 Duo.
I also never saw it show up on Chooser. I don't know if it should have, tho.
I'm planning to list it on eBay, but if anyone here wants to buy it for $20+shipping, let me know. I'd also consider a trade, for something else that might be useful to me, as the proud owner of a 4MB Powerbook 230 Duo.
Hmmm. I have machines on my LAN running WinXP Home, WinXP Pro, Vista Home Premium, and various flavors of Linux. I could probably get a Win98 machine running. But I don't have any WinNT or Win2K machines. Do the "Server Services for Macintosh" run on something other than Win2K?
I've never seen IRIX and would not have any idea where to get it.
I never did try putting a 10 mbps-only hub between the Linux machine running netatalk and the AsanteTalk device... do you suppose this could really work when a 10/100 mbps switch did not?
I've never seen IRIX and would not have any idea where to get it.
I never did try putting a 10 mbps-only hub between the Linux machine running netatalk and the AsanteTalk device... do you suppose this could really work when a 10/100 mbps switch did not?
It's worth a try because switches do have to negotiate link speed and the Asante device is pre 100Mbs and does not participate in the negotiation.I never did try putting a 10 mbps-only hub between the Linux machine running netatalk and the AsanteTalk device... do you suppose this could really work when a 10/100 mbps switch did not?
I must truly be obsessed with this goose chase, because here I am back at it.
I now have my PowerBook 230 Duo connected to my AsanteTalk device which in turn is connected to a Netgear EN108 (10BASE-T) ethernet hub. All cable connections have green lights. The only other device connected to the hub is my ubuntu 8.10 64-bit machine "quad", which is set up to request an address from a DHCP server, but there is no DHCP host in the system. As a result, ifconfig does not report that there is an eth0 interface active. It seems worrisome that when I run the atalkd command, quad returns "eth0: Operation not permitted" and "atalkd: zero interfaces, exiting." nbplkup on quad returns "nbp_lookup: Cannot assign requested address".
So I then tell quad to use a fixed IP address. ifconfig reports that there is an eth0 interface active, as expected. atalkd now returns "eth0: disabled", and nbplkup returns the same "error" message as above.
I've tried a variety of different lines in atalkd.conf, including just "eth0" and nothing at all (all lines commented out). All produce essentially the same result (either "eth0; disabled" or "eth0: Operation not permitted"), although some lead to atalkd also reporting "Can't configure multicast."
My suspicion is that I still do not understand how to get netatalk to work. Do I need to put a second ethernet connection into quad, so I can try to configure netatalk on something other than eth0?
I now have my PowerBook 230 Duo connected to my AsanteTalk device which in turn is connected to a Netgear EN108 (10BASE-T) ethernet hub. All cable connections have green lights. The only other device connected to the hub is my ubuntu 8.10 64-bit machine "quad", which is set up to request an address from a DHCP server, but there is no DHCP host in the system. As a result, ifconfig does not report that there is an eth0 interface active. It seems worrisome that when I run the atalkd command, quad returns "eth0: Operation not permitted" and "atalkd: zero interfaces, exiting." nbplkup on quad returns "nbp_lookup: Cannot assign requested address".
So I then tell quad to use a fixed IP address. ifconfig reports that there is an eth0 interface active, as expected. atalkd now returns "eth0: disabled", and nbplkup returns the same "error" message as above.
I've tried a variety of different lines in atalkd.conf, including just "eth0" and nothing at all (all lines commented out). All produce essentially the same result (either "eth0; disabled" or "eth0: Operation not permitted"), although some lead to atalkd also reporting "Can't configure multicast."
My suspicion is that I still do not understand how to get netatalk to work. Do I need to put a second ethernet connection into quad, so I can try to configure netatalk on something other than eth0?
Before running 'atalkd' do you ever check to see if it is already running? 'atalkd' isn't just some random program, it's a daemon that is supposed be run once at startup, sit there and manage alot of the appletalk protocol.As a result, ifconfig does not report that there is an eth0 interface active. It seems worrisome that when I run the atalkd command, quad returns "eth0: Operation not permitted" and "atalkd: zero interfaces, exiting." nbplkup on quad returns "nbp_lookup: Cannot assign requested address".
So I then tell quad to use a fixed IP address. ifconfig reports that there is an eth0 interface active, as expected. atalkd now returns "eth0: disabled", and nbplkup returns the same "error" message as above.
My suspicion is that I still do not understand how to get netatalk to work. Do I need to put a second ethernet connection into quad, so I can try to configure netatalk on something other than eth0?
My ubuntu box has exactly one ethernet port and the atalkd.conf is basically empty, and netatalk is run automatically at startup.
If running "nbplkup" returns your local machines names but nothing else then netatalk is at least configured and doing stuff. If nbplkup fails with cannot use address or similar then netatalk is down.
OK, here's a status update.
I've acquired and installed into my PowerBook's Duo Dock a Daynaport NuBus ethernet card. I have an ethernet cable connecting the NuBus ethernet card to a 10/100 switch, which in turn is conencted to the rest of my LAN and ultimately to the Internet. The machine I am typing this message on is also connected to the Internet through this same 10/100 switch.
On my Linux machine "quad", also connected to this same switch, I have netatalk running. I can ping addresses on the Internet from quad without problems. nbplkup on quad returns this:
quad:AFPServer 65280.154:128
quad:netatalk 65280.154:4
quad:Workstation 65280.154:4
Apple PowerBook 230 in Duo Dock:AFPServer 65337.1:251
Apple PowerBook 230 in Duo Dock
PCToolBox 65337.1:252
Apple PowerBook 230 in Duo Dock
owerBook Duo 230 65337.1.253
Apple PowerBook 230 in Duo Dock:Workstation 65337.1:4
On the Powerbook, in Control Panels | Network, I now see a new icon, "Ethertalk". Unfortunately, when I try to select it as my AppleTalk Connection, the Powerbook gives this error message:
"You cannot choose a zone at this time because no internet router is available."
What should I do next?
I've acquired and installed into my PowerBook's Duo Dock a Daynaport NuBus ethernet card. I have an ethernet cable connecting the NuBus ethernet card to a 10/100 switch, which in turn is conencted to the rest of my LAN and ultimately to the Internet. The machine I am typing this message on is also connected to the Internet through this same 10/100 switch.
On my Linux machine "quad", also connected to this same switch, I have netatalk running. I can ping addresses on the Internet from quad without problems. nbplkup on quad returns this:
quad:AFPServer 65280.154:128
quad:netatalk 65280.154:4
quad:Workstation 65280.154:4
Apple PowerBook 230 in Duo Dock:AFPServer 65337.1:251
Apple PowerBook 230 in Duo Dock
PCToolBox 65337.1:252Apple PowerBook 230 in Duo Dock
owerBook Duo 230 65337.1.253Apple PowerBook 230 in Duo Dock:Workstation 65337.1:4
On the Powerbook, in Control Panels | Network, I now see a new icon, "Ethertalk". Unfortunately, when I try to select it as my AppleTalk Connection, the Powerbook gives this error message:
"You cannot choose a zone at this time because no internet router is available."
What should I do next?
It looks like you are on a simple non-routed AppleTalk network (eg all the network addresses are 65xxx., hence would not have multiple zones. Hence no zones to choose from.On the Powerbook, in Control Panels | Network, I now see a new icon, "Ethertalk". Unfortunately, when I try to select it as my AppleTalk Connection, the Powerbook gives this error message:
"You cannot choose a zone at this time because no internet router is available."
What should I do next?
Does the icon for Ethertalk stay highlighted within the Network window? Can you close it with the Ethertalk icon highlighted? Does it then say "Switching AppleTalk connections..."?
Oops. It turns out all I needed to do was wait a bit. I returned to the PowerBook just now, and amazingly I was able to see "quad" in Chooser and browse files on quad from my PowerBook!!
Now, of course, I want to figure out how to print from the Powerbook to a printer on the LAN which does not know anything about AppleTalk.
Now, of course, I want to figure out how to print from the Powerbook to a printer on the LAN which does not know anything about AppleTalk.
The tools you may or may not need are netatalk's papd, CUPS, ghostscript and Samba.Now, of course, I want to figure out how to print from the Powerbook to a printer on the LAN which does not know anything about AppleTalk.
Papd may default to printing on the Linux boxes lpr. So if you have CUPS or whatever you can use a redirected printer. Samba would be needed to print to a window's printer. The best solution is to make the Apple box use the LaserWriter 8 driver and print using postscript. Then you may need ghostscript to do the appropriate rendering.
I have papd installed, but its .conf file is currently empty. I will install ghostscript. CUPS is already running on quad, and I believe Samba is as well (but I'll check).
Meanwhile, a new question... I warned that I was a complete Macintosh noob.
I would like to install some new programs on the PowerBook, now that I actually can do so without trying to burn floppies. Unfortunately, all files I find for System 7 have the file extension .hqx, which my Powerbook apparently lacks the program to uncompress (Stuffit?). I looked for "Stuffit Expander", but the only versions of it that I can find are downloadable as .hqx files. A wonderful "Catch 22". The only software on my PowerBook at present is System 7 and a copy of Microsoft Word.
How can I find a version of Stuffit that runs on System 7 and is delivered as a self-extracting executable, or as something directly executable?
Meanwhile, a new question... I warned that I was a complete Macintosh noob.
I would like to install some new programs on the PowerBook, now that I actually can do so without trying to burn floppies. Unfortunately, all files I find for System 7 have the file extension .hqx, which my Powerbook apparently lacks the program to uncompress (Stuffit?). I looked for "Stuffit Expander", but the only versions of it that I can find are downloadable as .hqx files. A wonderful "Catch 22". The only software on my PowerBook at present is System 7 and a copy of Microsoft Word.
How can I find a version of Stuffit that runs on System 7 and is delivered as a self-extracting executable, or as something directly executable?
Hopefully someone will PM you with a copy. In fact PM me and I'll send you what I have. Of course, without being compressed passing through different platforms, you run the risk of the application losing attributes System 7 needs in order to run it. Another option for you is to set up something like Basilisk II on your Linux machine and run a virtual Classic Mac. That way you can run a later OS with more options for expanding Mac software. Often new archive compression schemes are incompatible with software which runs under System 7, though most of the vintage software is compressed under a native OS application.How can I find a version of Stuffit that runs on System 7 and is delivered as a self-extracting executable, or as something directly executable?
The Duo line was one of the greatest products Apple ever developed. Unfortunately it did not impress the average consumer, probably because all of the extras began to add up and weigh the average traveler down, because as you discovered, without a dock of some sort, the Duo is practically useless (not to mention having the appropriate software on hand). I wish Apple would re-visit this technology, but it goes against their marketing model (one computer for each location), particularly now that they have the network "Cloud". Today's technology would make a modern Duo an incredibly practical device.
I have written a version of binhex/unbinhex that will also run on Windows NT with Services for Macintosh. So if you have a folder shared from Services For Macintosh you can unbinhex from the windows command line and both forks plus type and creator will be unpacked.
Sadly, I don't have any Windows NT machines, so I don't think I can take advantage of a version of binhex/unbinhex that runs on Win NT.
I do have "macutils" (includes macunpack, hexbin, and binhex, if I only knew how to properly use them) installed on a Linux machine. Documentation of this Linux package seems pretty poor.
I don't understand exactly what an .hqx file should open up (uncompress, decode, etc.) into. A single executable file? A directory? Multiple files?? I remember hearing once that all Macintosh executable files were actually in multiple parts, or "forks"...
I do have "macutils" (includes macunpack, hexbin, and binhex, if I only knew how to properly use them) installed on a Linux machine. Documentation of this Linux package seems pretty poor.
I don't understand exactly what an .hqx file should open up (uncompress, decode, etc.) into. A single executable file? A directory? Multiple files?? I remember hearing once that all Macintosh executable files were actually in multiple parts, or "forks"...
Back to printing. On my Linux machine, I have CUPS, papd, Samba (which I'm not certain I need), and ghostscript installed. I am not sure, however, how to tell my Linux machine to represent itself as if it was a LaserWriter printer.
At present, Chooser on my Powerbook sees "quad" as a file server choice in the AppleShare window, but does not see anything as being present on the LAN in the LaserWriter window.
I do not know how to tell if I have the "LaserWriter 8" driver on my PowerBook.
At present, Chooser on my Powerbook sees "quad" as a file server choice in the AppleShare window, but does not see anything as being present on the LAN in the LaserWriter window.
I do not know how to tell if I have the "LaserWriter 8" driver on my PowerBook.
I think you need those things on your Mac. Your printer has to be network accessible on your Linux machine and your Mac has to be able to see the printer via the network. Unfortunately I don't know how to do any of that below System 8.1.On my Linux machine, I have CUPS, papd, Samba (which I'm not certain I need), and ghostscript installed. I am not sure, however, how to tell my Linux machine to represent itself as if it was a LaserWriter printer.
The way I handle printing on my 128K Mac is to print a PostScript file to disk, transfer that to my OS X Mac and then print it from there. That's the easiest way to do it without having any specific software and instruction more than you have.
The problem you're going to run into is finding an open-source CUPS-type software that runs under System 7. It's that software that knows how to look for a generic printer on the network and print to it. The idea is to set up a macro that your LaserWriter 8 software prints to a temporary file that is then sent via CUPS to the Linux printer driver, at least that's how I've done it under OS 8 to a printer I did not have a driver for at all under OS X.
No, no, no, you have netatalk, so use papd to present a LaserWriter in the network, then to print to it you simply use the Chooser.... on *any* macintosh with LaserWriter printer driver installed.The problem you're going to run into is finding an open-source CUPS-type software that runs under System 7. It's that software that knows how to look for a generic printer on the network and print to it. The idea is to set up a macro that your LaserWriter 8 software prints to a temporary file that is then sent via CUPS to the Linux printer driver, at least that's how I've done it under OS 8 to a printer I did not have a driver for at all under OS X.
The mapping that papd uses should treat the data as Postscript, so you need to work out how to print pure postscript from 'quad' first.
Samba is needed if you are using a networked windows printer.
The printer I would like to have my PowerBook ultimately able to print to is on my LAN, serving both Linux and Windows clients. Linux machines (including "quad") print to it via CUPS, and Windows machines print using Windows drivers over TCP/IP. Basically, the printer is on a fixed IP address on my LAN, and any computer that needs to print to it just needs to be set up to send its print output to the IP address. In case it helps, the printer is a Brother DCP-9040CN color laser printer... it comes with Windows, Mac OS X, and Linux drivers, and supports "PCL6" and "BR-Script 3" (Brother's version of PostScript). I am not certain, but I suspect that if I can get output from the PowerBook intended for a Postscript printer routed to the DCP-9040CN, it may simply print.
My guess is that I need to put a line or two into my papd.conf file, but I am unsure of what syntax I need. Currently my papd.conf file is empty (all lines commented out). Any suggestions here?
As seen on my LAN by my Linux machines, the printer currently has this URI:
lpd://192.168.1.213
My guess is that I need to put a line or two into my papd.conf file, but I am unsure of what syntax I need. Currently my papd.conf file is empty (all lines commented out). Any suggestions here?
As seen on my LAN by my Linux machines, the printer currently has this URI:
lpd://192.168.1.213
http://netatalk.sourceforge.net/2.0/htmldocs/papd.conf.5.htmlMy guess is that I need to put a line or two into my papd.conf file, but I am unsure of what syntax I need. Currently my papd.conf file is empty (all lines commented out). Any suggestions here?
OK. So I'm terminally slow. I've been able figure out how to do many things in Linux, but "papd" has me basically stumped.
In my /etc/netatalk directory, I have an atalkd.conf file and a papd.conf file, but I do not have a netatalk.conf file. Do I need a netatalk.conf file if my goal is simply to have my Linux box pretend to be a LaserWriter? Note I already have file sharing working (even without a netatlk.conf file), so I believe the contents of my atalkd.conf file are good. I've tried a couple of different things in papd.conf, but none seem to have any discernable effect.
The printer I would like my Linux box to share as an LaserWriter is described in this file:
/etc/cups/ppd/DCP9040CN.ppd
the printer is located at this URI on my LAN:
lpd://192.168.1.213
I am hoping someone can help me identify the bare minimum number of lines to add (presumably to my /etc/netatalk/papd.conf file) to accomplish the sharing of the printer via AppleTalk.
Is there a way on Linux to see a list of printers being shared via AppleTalk? I can see my printer in the Printer configuration window, and adjust Settings, Policies, Access Control, Printer Options, and Job Options. The Printer configuration window does not seem to know anything about AppleTalk, however.
What I do know is that on my PowerBook 230 Duo I see "quad" in Chooser only as a file server and not as any kind of printer. My guess is that I am not properly sharing my printer via AppleTalk.
In my /etc/netatalk directory, I have an atalkd.conf file and a papd.conf file, but I do not have a netatalk.conf file. Do I need a netatalk.conf file if my goal is simply to have my Linux box pretend to be a LaserWriter? Note I already have file sharing working (even without a netatlk.conf file), so I believe the contents of my atalkd.conf file are good. I've tried a couple of different things in papd.conf, but none seem to have any discernable effect.
The printer I would like my Linux box to share as an LaserWriter is described in this file:
/etc/cups/ppd/DCP9040CN.ppd
the printer is located at this URI on my LAN:
lpd://192.168.1.213
I am hoping someone can help me identify the bare minimum number of lines to add (presumably to my /etc/netatalk/papd.conf file) to accomplish the sharing of the printer via AppleTalk.
Is there a way on Linux to see a list of printers being shared via AppleTalk? I can see my printer in the Printer configuration window, and adjust Settings, Policies, Access Control, Printer Options, and Job Options. The Printer configuration window does not seem to know anything about AppleTalk, however.
What I do know is that on my PowerBook 230 Duo I see "quad" in Chooser only as a file server and not as any kind of printer. My guess is that I am not properly sharing my printer via AppleTalk.
Slight update. Since I added a few lines to papd.conf I am able to see my printer in Chooser (as a LaserWriter), but attempts to print to it fail. They look like they should work, and there is even a dialog box indicating that something is being sent to the print spooler, but then after a long delay, I get a message indicating that printing has failed.
Here are the non-commented-out lines in my /etc/netatalk/papd.conf file:
Brother DCP-9040CN:\
r=|lpr -P Brother_DCP9040CN:\
d=/etc/cups/ppd/DCP9040CN.ppd:
Since putting in these lines, I see the printer as a choice in the "LaserWriter" section of Chooser on my PowerBook 230 Duo.
Brother DCP-9040CN:\
r=|lpr -P Brother_DCP9040CN:\
d=/etc/cups/ppd/DCP9040CN.ppd:Since putting in these lines, I see the printer as a choice in the "LaserWriter" section of Chooser on my PowerBook 230 Duo.
It's been a while since I updated. Sadly, I've made little progress.
My biggest problem at the moment is that I cannot expand .hqx files on my PowerBook (running System 7.1). I am absolutely stuck, because I can't find a copy of Stuffit that I can install.
I can find Stuffit as an .hqx file, but I can't open the file successfully. I've even tried opening the file using Stuffit running on Windows. The unpacking process seems to fail on Windows.
I found a program called binUnpk at this site, which supposedly can "unpack files in MacBinary format":
http://minivmac.sourceforge.net/extras/binunpk.html
I unzipped the file on my Linux machine, into a directory that I can see (via sharing) on my PowerBook. The file I want to run on the PowerBook is called "binunpk-1.0.1.dsk", and is supposedly a "zipped hfs disk image". When I double click on it on the PowerBook I get the same message I do when I click on an .hqx file:
"The program.... could not be opened because the the application program that created it could not be found."
How do you "install" a program on a Mac, anyway? Is there some trick to it?
My biggest problem at the moment is that I cannot expand .hqx files on my PowerBook (running System 7.1). I am absolutely stuck, because I can't find a copy of Stuffit that I can install.
I can find Stuffit as an .hqx file, but I can't open the file successfully. I've even tried opening the file using Stuffit running on Windows. The unpacking process seems to fail on Windows.
I found a program called binUnpk at this site, which supposedly can "unpack files in MacBinary format":
http://minivmac.sourceforge.net/extras/binunpk.html
I unzipped the file on my Linux machine, into a directory that I can see (via sharing) on my PowerBook. The file I want to run on the PowerBook is called "binunpk-1.0.1.dsk", and is supposedly a "zipped hfs disk image". When I double click on it on the PowerBook I get the same message I do when I click on an .hqx file:
"The program.... could not be opened because the the application program that created it could not be found."
How do you "install" a program on a Mac, anyway? Is there some trick to it?
Use:
http://macintroid.tripod.com/downloads/stuffit351.zip
To extract:
http://macintroid.tripod.com/downloads/stuffit402.zip
Just take them out of the zip and you have the .bin. There is most of the time no installer, They are just the executable when they are extracted.
http://macintroid.tripod.com/downloads/stuffit351.zip
To extract:
http://macintroid.tripod.com/downloads/stuffit402.zip
Just take them out of the zip and you have the .bin. There is most of the time no installer, They are just the executable when they are extracted.
It's a catch 22. A "xxxx.bin" file means nothing to a Macintosh that has no application installed that will unpack binhex, macbinary or whatever.Just take them out of the zip and you have the .bin. There is most of the time no installer, They are just the executable when they are extracted.
You need some kind person to give you a 1.44mb raw disk image (not a disk copy image) of a Mac format disk containing unstuffit. Then you can use a PC to write the floppy.
http://www.macgeek.org/downloads/index.html
Get the PC-Mac program. You can run it on a PC, it then gives you an unstuffed version of Stuffit 4.0.2 on a Mac formatted floppy disk.
Get the PC-Mac program. You can run it on a PC, it then gives you an unstuffed version of Stuffit 4.0.2 on a Mac formatted floppy disk.
PC-Mac worked well for me!
I was able to install Stuffit 4 with PC-Mac, and then was able to install Stuffit 5 from an .hqx file. I apparently can't use a more advanced version of Stuffit, however, as I am only running System 7.1
With Stuffit 5 I was able to install an old classic Mac game, CaveFox. It's slow, but it runs.
So I now have a PowerBook 230 with 24M RAM, sitting in an Ethernet-equipped Duo Dock, talking to an AppleShare created by a Linux machine on my network. My next challenge is printing to my network printer from the PowerBook (when docked).
I was able to install Stuffit 4 with PC-Mac, and then was able to install Stuffit 5 from an .hqx file. I apparently can't use a more advanced version of Stuffit, however, as I am only running System 7.1
With Stuffit 5 I was able to install an old classic Mac game, CaveFox. It's slow, but it runs.
So I now have a PowerBook 230 with 24M RAM, sitting in an Ethernet-equipped Duo Dock, talking to an AppleShare created by a Linux machine on my network. My next challenge is printing to my network printer from the PowerBook (when docked).
