Eureka! It's printing!
The printer wasn't showing up at all in anything - Terminal, Desktop Printer Utility or Apple Printer Utility, so I Googled "laserwriter not showing up in Apple Printer Utility" and found that somebody on another forum had had this problem (different printer, different Mac) but the printer had become visible when connected to the router, as opposed to the Mac. So, I connected it to the router and restarted it - and the IP address changed again, to a network address. I pinged (well 'arped') and that IP addess was now there against the printer's Mac address.
I put that IP address into the
Desktop Printer Utility and hey presto, there it was. It didn't showed up in the
Apple Printer Utility at any stage. Skipped back to OS X and successfully printed.
Many thanks to Jerry and others here.
------------------------
So for anyone else, here's my recap of what I did.
First of all I tried using Telnet to get to the printer, as per the manual for the 8500, but I couldn't get anywhere with that. I also tried the TCP/IP thing on a windows laptop, but that wouldn't work either. I don't have any other Macs so after a fair bit of Googling, decided that the SheepShaver/Classic emulator was the way to go.
I installed SheepShaver 2.3 because reports were that that version was stable. It crashes a lot but it's still better than 3 which crashed on startup every time. It wasn't intuitive to me, and I found two helpful guides:
http://theappleblog.com/2006/07/01/classic-on-intel-macs-courtesy-of-sheepshaver / and
http://emaculation.com/doku.php/sheepshavermac_os_xsetup which spelled out the obvious things such as the need to initialise the disc during SheepShaver Setup (sadly, not obvious to me).
You need a working ROM file. The catch 22 is that most ROM files need to be extracted - and that can only be done under Classic. If you google newworld86.rom you'll find a pre-extracted working ROM file.
Then you need a working system. I tried all the systems I have (all 8.x) but SheepShaver crashed on start up. Then I read that 7.5.3 up to 9.0.1 were acceptable but they have to be independent of hardware - all mine were PowerBook or iMac systems. Then I tried to download the only one that Apple provides free, 7.5.3, but couldn't combine it - the utility needs Classic. I put a call out for OS 8.5-9.0.4 on Freecycle and somebody came to my rescue, and today I got hold an installation disc of 9.0.4.
For the first time SheepShaver actually opened and stayed open. At this stage I wasted more time becuase I didn't realise I had to initialise the disc (I get scared when I see the word 'erase' and didn't take it all in). But following the instructions in the guides above, I finally got it. The original volume I created (as per the first set of instructions above) wasn't big enough to install the system which then crashed during installation, so I had to do it again. This time I created a volume of 500mb. Volume created, disc initialised, and the installation disc finally agreed to install Mac OS 9.0.4.
So now I had Classic running on the MacBook.
Next, I copied the Apple Printer Utility into a folder on the new disk. It still wouldn't open. In my googling I then discovered that the
Desktop Printer Utility seemed as important, so I found that it had been installed as part of 9.0.4 (Apple Extras/Apple Laserwriter Software). Nothing showed up the Appletalk Zone as I would have expected so I spent ages faffing about with cables, swapping them around and so forth. And I tried the pinging that Jerry suggested in his last post. Then I realised that Jerry had said to download the Apple Print Utility from within Classic, so I did that, and yes indeed it opened - but showed no printer!
Eventually I found a post elsewhere saying that the printer should be connected to the router, not the computer, so I switched that and suddenly it appeared when I pinged, and the Desktop Printer Utility connected it. (Still invisible in the Apple Printer Utility)
It looks like perhaps all this hassle with Classic wasn't necessary; I don't know if it would have connected without the Desktop Printer Utility. Either way, I'm just happy that it's all working now.
Hope this helps somebody else.
Thanks all,
Debbie