http://discussions.info.apple.com/WebX?13@@.efc404a/13>. My intentions in creating this page is to simply flesh out in more detailed, step-by-step fashion, the wealth of information he and others have kindly provided." />
 



According to the last post on this page, Epson now provides direct support for the Axis 1440 print server. I have closed this page for comments, but am leaving it up for historical reasons. Here are notes from Hal:

I got the driver from this page:

I see now that it doesn’t say anything about the Axis 1440, but it worked for me. It is called “Macintosh OS X (v10.1) epson10396.sea.hqx – 3.4MB – posted on 08/06/02”

I have only been using OS X (10.2. for a couple of days now but I think that once the driver was downloaded and installed, I went to the “print center”, clicked on Add, and chose EPSON Appletalk from the topmost pulldown menu. I suppose printing to an IP address would be faster; the Appletalk on
Ethernet is not so bad.

If Epson no longer offers this driver, I will try to post one here.

The origin of these instructions are the quite detailed notes Bernard Saar contributed to the Macintosh support forums <http://discussions.info.apple.com/WebX?13@@.efc404a/13>. My intentions in creating this page is to simply flesh out in more detailed, step-by-step fashion, the wealth of information he and others have kindly provided.

If you are an X-windows user on your Mac, you may want to try setting your Mac up for printing using "gimp-print" instead. It offers a highly polished interface, and full feature implementation for monitoring and configuring your Epson.

I also need to make it clear that even though I am trying to make these instructions as clear as possible, they cannot stand in for a basic understanding of the *NIX command line. That should not dissuade you; it should only mean that you spend some hours learning how to move around a *NIX file system, enter path names and do some basic commands. You should also understand what su and sudo mean (and how dangerous they are). Taking the time before you begin to get the basic concepts down is invaluable. With the power to make these kinds of modifications comes a certain responsibility to self-education. Look for online tutorials on BSD and "tcsh". Or you can go to the MacOSX.org command line interface tutorial.

Downloads Needed

I recommend you start the downloads right away, and let them finish in the background while you look over this document. If you decide you don’t want to go through with this operation after all, you can just delete what you’ve downloaded. But starting now will speed things up when you do decide to get going.

Setting the IP of the Print Server

  1. In your terminal application, type
    atlookup and hit return. After a few seconds, depending on the size of your network, you will get a list in which you should find the AppleTalk name of your AXIS print server, something like this:
    ...
    ff68.e0.80 AXIS3F8C75_LPT1:EPSONLQ2
    ...

    Make a note of this information. You will use this later.
  2. Set your AXIS 1440 to configuration mode. You should be able to do this simply by turning your AXIS 1440 off, and then on again. However, I was not able to get the configuration to work without resetting the AXIS. To reset the AXIS,do the following (as described in the AXIS 1440 manual):
    1. Unplug the external power supply
    2. Press and hold down the test button [small button located on the side of the unit] while you plug the external power supply back in. Continue to hold down the test button until the network indicator begins to flash at one second intervals. (This should take at least 5 seconds. [It took almost 10 seconds for me])
    3. Release the test button and wait until the network indicator flashes at least five times.
    4. Press and hold down the test button again for at least five seconds until the network indicator remains lit.

    The AXIS 1440 is not reset to its factor default settings. Restart the AXIS 1440 by turning it off and then on again.

    Whichever method you use (simply turning off, or resetting), you will now have 60 minutes in which to complete the next 2 steps.

  3. Open the Chooser. If you are currently in Mac OS X, just start up a Classic application, and when it is open, use the Apple Menu to get to the Chooser. Select LaserWriter as your network printer driver. Select the printer port whose name ends with “_CFG”. Close the Chooser.
  4. Create the following text file in SimpleText (we’re still in the Classic environment), and send it to the printer simply by printing it (cmd-P):

    APRINT_1     :AXIS3F8C75_LPT1;
    INT_ADDR     :192.168.1.100

    Obviously, you will want to substitute your own values here, as explained just below. If you are still within the 60 minute time limit from when you restarted your AXIS print server, the printer will respond to this document as a configuration command rather than a print command. In other words, if the printer prints your file, something isn’t right, and you should go back to step 2.

    APRINT_1 is the AppleTalk network name of your printer. Do not use the name above, but enter the name you found when you did your atlookup in the terminal.

    INT_ADDR is the IP address you want to assign to the printer. In my case, 192.168.1.100. You can enter any IP address you need to fit in with how your network is set up. You may decide to have the IP dynamically allocated via your router’s DHCP, or your Mac’s IP assigning functions, but in that case your printer IP will be reset every time you restart your computer or, in the case of using a router, the power goes down. Instructions for configuring your AXIS if you want the IP dynamically assigned is a task for someone else. (If someone does this, please let me know where such documentation exists, so I can link to it here. Or just send me the instructions, and I’ll include them in my documentation).

    The space before the colon (:) is a tab.

    Your printer should now have an IP address permanently assigned to it. If you want to look into this more, check the section called Basic Configuration in the Setting Up Macintosh Computers chapter of your AXIS manual.

Installing GhostScript

  1. If you’ve already downloaded the Fink Package Manager installer, double click on the installer image and, once it’s mounted, double click on the package installer (Fink X.X.X Installer.pkg).Click the lock at the bottom of the first screen to authenticate yourself, and enter your administrator password. Follow the prompts, and install the package.
  2. During the install you will be shown the installer’s Read Me file. Do not skip it; read it through. If you don’t follow it’s simple directions, your installation will not work. It will direct you to create or modify your home directory’s shell login file (.cshrc) so that your shell will be able to find the needed binaries in the future.
  3. After you’ve modified your .cshrc file as per the instructions in the installer Read Me, quit your terminal application and restart it so that you are logged in with the new .cshrc directives you just added. Then, in a terminal window, type the following
    like this:
    sudo apt-get update

    The update should take less than a minute. Essentially, Fink is just asking it’s servers for a listing of the latest available compiled packages for the Mac OS X. Once your listing has been updated, issue the following command:
    sudo apt-get install ghostscript-nox

    If you follow Mr. Derry and Fink’s instructions and do everything as root, you will likely run into the following error message later in the install:
    dpkg: `install-info' not found on PATH.
    dpkg: `update-rc.d' not found on PATH.
    dpkg: 2 expected program(s) not found on PATH.
    NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin.

    E: Sub-process /sw/bin/dpkg returned an error code (2)

    Since most of us have not configured the root user account to include all the binary paths, it’s probably better to issue all the commands using sudo You’ll be prompted for your administrator password as usual.

    Using sudo over and over again before every command is a little more typing, it’s true, but it does save you the hassle of having to configure the root user’s PATHs, as well as the danger of being logged in as root and being able to completely trash your system in a moment of forgetfulness.

    The GhostScript package will now download and be installed and configured automagically by the Fink Package Manager. You can stare at its progress in the terminal window, or you can just come back to these instructions and move ahead while the download progresses in the background.

Configuring NetInfo

Now is a good time to familiarize yourself with Jim Derry’s Network Inkjet configuration package. If you haven’t already done so, download it now. (It’s listed in the downloads section above). It includes a rather stunning amount of documentation about the steps we’ve just taken as well as excellent in-depth material for learning more about how Mac OS X handles printing. I recommend you read it from start to finish. However, for the purposes of a quick installation, you can start on page nine of the PDF document. Mr. Derry has done a fabulous job of giving very clear, easy-to-follow instructions on these pages, so I will leave the next steps to the documentation in his package, with only a few comments of my own as they pertain to changes we will have to make in order to apply his directions to the Epson printer family rather than his Hewlett-Packard DeskJet.

Follow the directions on pages 9-10 of Mr. Derry’s instructions. However, make sure to change the name of the printer in the NetInfo Manager to something that will work for you. Mr. Derry recommends the name be all lowercase, and with no spaces. For example, my settings in the NetInfo Manager are as follows:

name    stylusphoto700
 
if      /usr/local/lib/lpd.filter
 
lo      lock
 
sd      /Volumes/X/caching/PrintSpool/lpd/stylusphoto700
 
ppdurl  /Library/Printers/PPDs/Contents/Resources/en.lproj/GS_HP_LaserJet.ppd
 
lp      /dev/null

The more ways in which your installation differs from the one documented in Mr. Derry’s instructions, the more holes there will be for you to troubleshoot should something go wrong. I recommend you only differ from the documented values in naming your printer, although as you can see, I did not heed my own good advice here and created my own printer spool directory, and put the PPD file in the OS X Library with the others. Again, just make sure to name your printer something that works for you, and remember what you named it.

Also, you have the choice here of whether to use AppleTalk printing or not. Setting things up for AppleTalk printing is simpler in that you can skip the set up of the "LP" printer in the NetInfo Manager. However, if your network does not run AppleTalk, or if you simply don’t want to use AppleTalk for your printing, you will have to follow instructions in setting up both the actual printer and the "LP" device, as Mr. Derry describes.

For some reason, I have only been successful in printing to AppleTalk so far. If anyone would like to contribute notes on how to successfully set the filters and the "LP" printer for non AppleTalk printing, I would love to be able to add them to the documentation here.

Now, we are going to create the "filter", which is really just a file containing a "bash" shell script which will send commands to the GhostScript engine, specifying what printer descriptor to use, what input to process, how to process it, and where to send it.

Creating and Configuring Your "Filters"

First, following the section titled "Use The Terminal to Build the Filter" on page 10 of Mr. Derry’s documentation, we are going to copy his filter files to the Input Filter directory we just specified in the NetInfo Manager. (Check to see what directory you entered for the "if" parameter for your printer, and copy the files to this directory.)

Please be aware that if you haven’t been tinkering with your BSD subsystem as much as Mr. Derry has, you probably won’t have the directory /usr/local/lib/lpd. No big deal, just make the directory first:
cd /usr/local
sudo mkdir lib
sudo CD lib
sudo mkdir lpd

That should do it. Now you can copy the files as instructed. I know it’s a little weird to be using the LaserJet PPD file for an Epson printer (or whatever model
you may have), but just do it. As for the lpd.filter file, we will start monkeying with it in a bit.

It is a good idea to review some additional documentation at this point, so you can customize the steps that follow. Please read up on the UNIPRINT driver, documentation available at <http://www.ghostscript.com/doc/AFPL/7.03/Devices.htm#Uniprint>. It will cover most cases of ink jet printers. [Thanks again to Bernard Saar for pointing me to this documentation. The GhostScript Web site is a nightmare to navigate. Thanks also to the developers who have spent so much time creating the drivers!]

  1. Choose which Uniprint driver you want to use for your Epson model.

    Unfortunately the Uniprint driver does not contain a driver specific to my Stylus Photo 700. What to do? I decided to use the stcany.upp driver, since that is the most "generic" of all the Epson drivers and stands the most chance of succeeding with my unsupported model. If you are at all unsure of which format to choose, choose stcany.upp. You can always change your mind later. For right now, we just want to make sure we can get some kind of output to the printer.

  2. Make sure you are in the directory you copied the lpr.filter to, then open the lpr.filter file in pico, vi, or whatever text editor you prefer.
    pico lpr.filter

    You should have the following contents in your text editor window:

    #!/bin/sh
     
    GS=/SW/bin/gs
     
    GS_FONTPATH=/SW/share/ghostscript/fonts:/SW/share/ghostscript/7.02/lib
     
    export GS GS_FONTPATH
     
    #exec $GS -dNOPAUSE -q -dBATCH -sDEVICE=cdj550 -r600 -sOutputFile=\|"/usr/bin/lpr -v -h -Plp" -
     
    #exec $GS -dNOPAUSE -q -dBATCH -sDEVICE=cdj550 -r600 -sOutputFile=\|"/usr/bin/atprint deskjet970:DeskWriter" -

  3. If you are going to print to AppleTalk, remove the pound sign (#) from the beginning of the last line. This will allow the line to be executed when the script runs. If you are configuring your filter for IP printing, you will want to remove the pound sign and modify the penultimate line.
  4. Change the rest of the line to work with your printers and set up. In my case, I made the following substitutions on the last line:
    I replaced -sDEVICE=cdj550 with @stcany.upp, and
    deskjet970:DeskWriter with AXIS3F8C75_LPT1:EPSONLQ2 (which I got from the atlookup we did at the very start, remember?). So my first generation command line for the GhostScript interpreter looks like this:

    exec $GS -dNOPAUSE -q -dBATCH @stcany.upp -sOutputFile=\|"/usr/bin/atprint AXIS3F8C75_LPT1:EPSONLQ2" -

You should now be able to print something. It’s a good idea to keep your first test simple. Open TextEdit, type "Print test" in the window and print it to your newly defined printer. If it doesn’t work, the most likely cause is either a typo in your NetInfo Manager, or an inconsistency in terms of where you have placed your various filter files etc. and where you have told your computer they are. It is very helpful to write down the directory paths and file locations you are making your configurations with, as it can quickly get confusing—especially if you’re not already very familiar with the file structure of a *NIX operating system.

If your test was successful, congratulations! It should have taken you much much less time than it did me. You will probably want to experiment with building more filters, and creating separate NetInfo printers using the different filters. For example, you can create a filter with a higher resolution, and one with a lower resolution. Again, study the Uniprint documentation for ideas of how to modify your filters to fit your needs.

I am also interested in posting filters that have worked well for achieving various tasks on their Epson printers. [Perhaps they would be better posted on the Apple discussion boards?] If you want to contribute a filter to this page, use my contact form.

Good Luck!
Kristofer Widholm


NOTES

  1. The instructions are for Mac OS X v 10.1 and firmware AXIS 1440 firmware v. 5.52
  2. It should theoretically be possible to do all this using the Mac OS X print center and an OS X text editor. However, I was unable to get it to work until I did it following the Classic OS techniques above. If you want to try to do it entirely in OS X, the steps would be something like the following:
    1. Open up the Print Center (Applications/Utilities/Print Center). Click “Add Printer”. After a few seconds, you should see something like: AXIS3F8C75_CFG. Leave the printer model as “Auto Select” and click “Add”. Ignore the fact that the system thinks it is driven by LaserWriter; we’ll take care of this later. There should automatically appear a little dot next to the AXIS in the listing, signifying that it is now the active printer. You can leave the print center open if you like.
    2. Prepare a text file in TextEdit with the same information as above, and print the file.
  3. The AXIS 1440 manual is available here in PDF form: <http://www.axis.com/documentation/usermanual/1440/1440um.pdf>
  4. Ghostscript Documentation is available at <http://www.ghostscript.com/doc/index.htm>. I recommend you read it, too. You can never be too informed.

One Comment to “Setting up your AXIS 1440 with Mac OS X v 10.1”  

  1. 1 Hal Pridgen

    Hi, I have an Axis 1440 print server that I use with my Photo 1200. Epson has a driver on it’s web page that is listed for osx 10.1. I downloaded it and tried it on my system – 10.2.8 – and the printer is visible in the Print Center. You probably know all this by now, but I thought I would mention it in case you wanted to update your web page.

    [Kristofer: Thank you. Yes, this post is happily very obsolete by now.]