Re: I just got a IIc.....HELP?

[nparker@cie-2.uoregon.edu (Neil Parker)]

In article <5afhm8$eik$1@europa.frii.com> shack@deimos.frii.com (Randy
Shackelford) writes:
}In article <5afdec$ket@login.freenet.columbus.oh.us>,
}Dave Althoff <dalloff@freenet.columbus.oh.us> wrote:
}>Randy Shackelford (shack@onyx.southwind.net) wrote:
}>: crazyblake (crazyblake@earthlink.net) wrote:
}>: : 50 HOME
}>: : 100 PRINT "PRINTING ON SCREEN"
}>: : 110 PR#1
}>: : 120 PRINT "PRINTING ON SCRIBE"
}>: : 130 PR#0
}>: : 140 PRINT "PRINTING ON SCREEN AGAIN"
}>: : 150 END
}>
}>: Dunno about the Print Shop problem, aside from whether it supports the Scribe
}>: or whether you have it configured properly, but I see problems with the
}>: Applesoft program up there. If you use Applesoft's PR# statement instead
}>: of BASIC's, you'll disconnect BASIC and bad stuff will happen. Change PR#1
}>: to print chr$(4)"pr#1" and the same for PR#0 except use 0 instead of 1
}>: of course.
}>
}>Actually, under DOS 3.3, it is DOS that gets disconnected; and under
}>ProDOS, it is BASIC.SYSTEM that gets disconnected.  Under DOS 3.3, you can
}>reconnect things with a CALL 1002; I think that under ProDOS you can just
}>hit <RESET>...or the CALL 1002 should also work under ProDOS, unless Apple
}>violated their own rules and moved that vector around.  (It wouldn't
}>suprise me...).
}
}Yep but the original poster said ProDOS 1.0.1. Note the nomenclature I use:
}Applesoft is that stuff in ROM, and BASIC is the SYS program usually found
}in a file named BASIC.SYSTEM. Call 1002, aka 3D0G, works in BASIC as well
}as in DOS.

"Ya know what's wrong with these kids today?  They can't do their decimal/hex
conversions, that's what!"

CALL 1002, which is 3EAG (not 3D0G) in the Monitor, is a DOS 3.3-ism.  It
doesn't work under ProDOS.

CALL 976, aka 3D0G, works in both DOS 3.3 and ProDOS.  Unfortunately, it
also exits back to the ] prompt if called from inside a running BASIC program.


In any event, since the program only says "PR#1" and "PR#0", and doesn't
include any IN# statements, it never fully disconnects DOS.  The next time
anything tries to read from the keyboard, DOS will notice that its output
vector was disconnected, and reconnect it.  This means that after running
the above program, everything magically returns to normal as soon as the ]
prompt reappears.

But I have to agree with all the other posters who have pointed out that
unless you're running without any DOS at all, it's best to use
PRINT CHR$(4)"PR#1".  Don't depend on the magic-reconnect feature.

                - Neil Parker
-- 
Neil Parker                       | Unsolicited commercial e-mail to my
nparker@cie-2.uoregon.edu         | address is not welcome, and will be
nparker@cie.uoregon.edu           | discarded unread.
http://cie-2.uoregon.edu/~nparker |