From wulf@cip.physik.uni-stuttgart.de Mon Jun 28 05:06:30 1993 Received: from calvin.sfasu.edu by umaxc.weeg.uiowa.edu (5.61.jnf/930523) on Mon, 28 Jun 93 05:06:27 -0500 id AA02096 with SMTP Received: from OSCAR.PHYSIK.UNI-STUTTGART.DE ([129.69.74.11]) by calvin.sfasu.EDU with SMTP (5.59/25-eef) id AA19119; Mon, 28 Jun 93 05:00:41 CDT Return-Path: Received: by cip.physik.uni-stuttgart.de (MX V3.1C) id 891; Mon, 28 Jun 1993 12:01:33 +0200 Date: Mon, 28 Jun 1993 12:02:00 +0200 From: Wulf Hofbauer To: hyperc-l@calvin.sfasu.edu Message-Id: <0096EB34.7F1E0920.891@cip.physik.uni-stuttgart.de> Subject: Restricting the scrolling window Status: R >Is there any way to emulate the Applesoft > >POKE 33,: POKE 34,: POKE 35,: POKE 36, > >commands in HyperC (i.e., is there any way to limit where printf will print >on the screen, "make a window")? These locations seem only to be used by >Applesoft. I don't know of a way to restrict the scrolling window that will work for all setups. Opsys uses a mixture of Pascal/BASIC entries into the video firmware, assuming fixed entry points - contrary to all conventions about how to access interface cards. They're even using self-modifying code... If I'm not completely off, there's no easy way to accomplish what you want with Opsys. Opix lets you install your own console driver. If it calls the BASIC entries, as the standard driver does, you should have no difficulties in restricting the scrollinmg window, in exactly the same way as under BASIC. I won't recommend however to trust in this specific set up - there are also reasons to use the Pascal driver routines, and you're completely free in writing your own drivers. One more complex solution would be: - for Opsys: install your own assembly-written driver, using the hook in page 3, that supports restricting the window. If your driver is part of your application and installs itself automatically, you can get around different setups. - for Opix: it is not very clean, but you may install a similar driver by changing the console driver vector at 0x1ff0. - for both systems: write a C or assembly function to display characters, taking care of windowing etc. You can use it then with xprintf(), which is identical to printf(), only you can specify the output routine. Doing all output with xprintf() is however slow. On the other hand, this is probably the safest way to do it. >This message is also to see whether I am actually ON hyperc-l, as I >have yet to get any messages from it. Does it really exist still? If I am >not actually on it, I would appreciate it if I somehow appeared on it... Onbviously, it still exists. - Wulf "Though this be madness, there is method in it." (Shakespeare) +-------------------------------------+-----------------------+ ! wulf@cip.physik.uni-stuttgart.de ! Apple // Enthusiast ! +-------------------------------------+-----------------------+ ! Wulf Hofbauer * Heilbronner Str. 12 * 71732 Tamm * Germany ! ! Tel. 07141/602518 ! +-------------------------------------------------------------+