PB100 & Cap Replacements Gold Mine over on 'fritter ...

[Trash80toHP_Mini]

. . . maybe the joint ain't on critical life support quite yet! [] ]'>

http://www.applefritter.com/node/7308

It'd be a shame if their forums died, some of our valuable comrades still post over there . . .

I've even seen some of the MIA comrades lurking here . . .

. . . and cross-pollination of info & ideas is a GOOD THING! [] ]'>

 

[Hrududu]

AppleFritter was the first Mac community I joined. When they switched to the new (current) forums, the place lost a lot of its life. I still check in every now and again, and some of the most knowledgeable people on legacy hardware are over there. You'll get a lot more help on forums like this one and Fritter than you will on one like MacRumors.

 

[Mars478]

than you will on one like MacRumors.

Ergh, MacRumors... they are all just self obsessed pricks there. I was on there for a while as Marsman478 but I rarely post (save for the apple collectors sub forum)

 

[Trash80toHP_Mini]

Well, I'VE got a PB100 trick up MY SLEEVE too!

It seems, in their infinite idiocy, that Epson left out support for the 68000 when they wrote the drivers for the original Epson Stylus Color Printer, the very FIRST of the successful art/photo oriented (as well as business graphics oriented) Color InkJet Printers.

It drove me BONKERS for a while that I could sometimes get it to print just fine and sometimes the system would lock up tighter than a virgi . . . uhhhm . . . drum! [] ]'>

I finally figured out that if you "set up" to print and then hit "Cancel" and THEN hit "print" again, everything worked great! Forget, and you were locked up tight! So I installed a debugger for the times I goofed and then reported the bug and the workaround to Epson.

To no avail, the arrogant S.O.B.s said they didn't support the 6800 OR the OS I was using and NEVER FIXED THE CODING ERROR!

Short sighted MORONS!!!! }

 

[Bunsen]

reported the bug and the workaround to Epson.
To no avail

This was last year, right?

 

[Trash80toHP_Mini]

reported the bug and the workaround to Epson.
To no avail

This was last year, right?

:lol: