🚀 go-pugleaf

>11/17/88 16:31 zimerman@phoenix.Princeton.EDU
>(Jacob Ben-david Zimmerman):

>... A whileback, I caught the tail end of a discussion
>about Imagewriter II or LQ problems.  Here are mine:           
>
>1) My imagewriter occasionally prints lines of text 'squashed', i.e.
>   about 1 pin shorter than they should be.

Check to see if your paper is catching on the bail assembly.
(The bar over the printhead.)
Sometimes it becomes rough and the fold rubs just enough to slow
the paper down. Also check the rest of the paper path for rubbing
on cables, the backplane, ect. And see if you can back off on the
impression lever a click or two. The idea is to remove as much
pressure on the paper as possible.

>2) Occasionally, when I send output to my Imagewriter, the darn thing
>   just starts spitting out reams of hex code in neat little columns.

Rumour has it that this is caused by accidently bumping the
select switch when turning on the printer.

>I used to program a lot, in BASIC (shudder) and finally in assembler
>and machine code for my Apple II+.  When I began using macs, I
>stopped programming, as I had no idea how to go about it.  I find myself 
>wanting to learn how to program the Macintosh, but I *still* have
>no idea how to go about it.  I know a little bit of C (not much) and
>nothing else.  My question is:  What language should I learn (if any)
>and do I NEED the APDA kit or whatever?  How does all this work? I
>would prefer to keep learning C to starting something else, but if I h
>to, well...

I, also, gave up BASIC when I moved to the Mac. There just didn't
seem to be any point to it. How could I duplicate the windows,
menus, buttons, icons, and other graphics?

HyperCard lets me reproduce all that and more. I've made $500
selling custom stacks in the past two months. Try it. You'll like it.



Jeff Gitchel