kamath@reed.UUCP (Sean Kamath) (04/23/86)
[grunch grunch grunch grunch grunch gruncc grunch gruch grunch grunch...] Well, here's the scoop... I got a //c and imagewriter // (actually _I_ have a //e and Prowriter...) and I'm in the process of writting some more fantastic PD software (yay!) for all of yoose guys... BUT! Yes, needless to say, I'm having a problem... It seems that after I print out about 96 graphics bytes, I get a return and line feed. Well, there goes the neigherhood! I tried to set the line length to 255 by "^I255N" but then I get the same thing. I tried it with the printer in debug mode (hex dump) and I got two things. If I just powered up, I get 8D 8A about once every 96 characters. With ^I255N I get 8D 8A and 80 or so character I get 0D 0A. This makes me wonder if perhaps the printer itself is sending these nasty CR and LF's.... to illustrate my point, run this... 1 ONERR GOTO 100 10 PRINT CHR$(4);"PR#1" 20 DATA 1,1,1,1,2,2,2,2,3,3,3,3,4,4,4,4,5,5,5,5,6,6,6,6 30 READ K : PRINT CHR$(27);"K";K; : PRINT CHR$(27);"G0009"; : REM 0=zero 40 FOR X = 1 TO 9 : CALL 768 : NEXT : REM ML PROGRAM FOLLOWING 50 GOTO 30 100 PRINT: PRINT: PRINT: PRINT CHR$(4);"PR#0" 300: A9 7F LDA #$7F 302: 20 ED FD JSR $FDED 305: 60 RTS What this should do is print nine bytes of one color, then move on to the next. It's pretty simple. What really icks me off is that this sample program ran just fine at 2 am this morning, but not now...now I get those damn line feeds. wel, I've rambled on long enough. If you're just dying to help me, like ou can't sleep at night because you know the answer, or even might know the answer, then by all means, send me mail. help! sean kamath ihnp4,decvax,ucbcad,teneron!tektronix!reed!kamath
werme@alliant (05/01/86)
I have a Apple][+ in [sort of] network involving a Commodore 64, Heath H89 and another CP/M system. The biggest headache I had was trying to figure out the [not-so] Super Serial card. What saved me days of time was essentially to give up on its ROM. I call ROM routines to intialize the port, from from there on out I do everything by talking directly to the uart. Your problems sound like the sort of thing that convinced me to roll my own. Talking to the uart only takes a little code, so that shouldn't make your driver too much bigger.