Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

50G: "Print Screen" keystroke?

83 views
Skip to first unread message

Dave

unread,
Jul 5, 2009, 5:11:14 PM7/5/09
to
Does the 50G have some kind of Print Screen keystroke that's
equivalent to ON+1 on the 48G? I tried a bunch of different key
combinations, but haven't found it yet.

-Dave Britten

TW

unread,
Jul 5, 2009, 7:45:03 PM7/5/09
to
> Does the 50G have some kind of Print Screen keystroke that's
> equivalent to ON+1 on the 48G? I tried a bunch of different key
> combinations, but haven't found it yet.

ON-UP_ARROW

All the 'hidden' key combinations can be found in the AUR.

TW

Dave

unread,
Jul 5, 2009, 8:25:45 PM7/5/09
to

Okay, got it working. Thanks. However, I'm seeing some weird behavior
regarding the DELAY setting in PRTPAR when printing graphics. When I
use the typical 1.8, nothing prints, then when I cancel with ON a few
times, the printer spits out a few bytes of the current display
(usually "RAD XYZ HEX" or some such). When I set the delay to 0, it
seems to behave like my 48GX does with the delay set at 1.8, but this
mucks up text printing (lots of buffer overruns). How odd. Is this a
known bug in printing to the 82240A/B with the 50G? Any fixes?

-Dave Britten

TW

unread,
Jul 5, 2009, 8:52:35 PM7/5/09
to
> Okay, got it working. Thanks. However, I'm seeing some weird behavior
> regarding the DELAY setting in PRTPAR when printing graphics.

Well i was giving the keystroke that prints to the computer. I didn't
know that works for a printer as well since I've never used one.
Perhaps someone else knows. :-)

TW

Dave

unread,
Jul 5, 2009, 9:23:23 PM7/5/09
to

Well, turns out it's the keystroke for printing to an 82240 as well!
Ha ha. Assuming you've got the proper flags set, of course. The
strange thing is that it prints graphics fine if DELAY is set to 0. It
makes me think the print routines are incorrectly inserting the delay
after every byte for graphics printing, rather than after every line.
For printing text, I have to use 1.8, or else I get buffer overruns.
For graphics, I have to use 0, or else it will probably take an hour
to finish.

Also, if I use the PRLCD command, rather than On-Up, pressing On to
cancel causes the calculator to crash and reboot. No data loss that
I'm aware of, thankfully...

For the record, I'm using ROM 2.15.

-Dave Britten

0 new messages