Hi, Dieter.

[chomp]

DM> FM> Mine started
DM> FM> playing up a few weeks ago, would randomly go into a power-on sequence
DM> FM> and spit out the test page. Then it totally shat its memory and reset
DM> FM> the pages printed from ~2000 back to 1. Finally on Thursday (with
DM> FM> Caroline's school assignment due) it gave up entirely and won't print.
DM> FM> Anything. Except the test page with the // lines.

DM> Hmmm....

DM> FM> The power-on test sequence (flashing power light) is unusually short
DM> FM> and no sample page is produced. The last few randomly produced sample
DM> FM> pages before the final problem showed it communicating at 538,977,664
DM> FM> baud. Let's hope I can still get that speed when it's fixed!

DM> Yeah, you wish. :-)

DM> FM> Any clues? Presumably some NVRAM has lost its guts. Might try and find
DM> FM> a battery in the innards and remove it for a few hours. Who fixes
DM>them?

DM> I forget - AWA i think. In Talavera Rd, Nth Ryde.

Yeah, that's right - I'll call them.

DM> Any luck at getting it going ?  Any sense of the settings ? I

No luck. It's been powered off for about a week, turned it on when I
read your message. The p/o sequence took the normal long time, but no
sample page at the end.

DM> did have a problem with the very short active time, and nothing
DM> would print, unless it was a very short text page. I obtained
DM> the following from QMS:

DM> serverdict begin 0 exitserver
DM> statusdict begin
DM> 25 9600 0 setsccbatch
DM> setdefaulttimeouts 0 60 30
                       ^^^^^^^ Shouldn't the parameters come before
                               the command, PostScript being a stack
                               machine?
DM> end

I told it that, no response. I think it's not receiving anything,
certainly the light's not flashing. If I can't think of anything
else I'll get AWA to look at it.

Regards, FIM.

 * * Reality is a crutch for people who can't handle BBS'ing
@EOT:

---