Megalextoria
Retro computing and gaming, sci-fi books, tv and movies and other geeky stuff.

Home » Archive » net.micro.atari16 » Bugs/Annoyances in TOS, Developers kit, ...
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Bugs/Annoyances in TOS, Developers kit, ... [message #282994] Mon, 10 March 1986 14:44 Go to next message
Anonymous
Karma:
Originally posted by: johnf

<pre>
Article-I.D.: apollo.2c69fde5.917
Posted: Mon Mar 10 14:44:00 1986
Date-Received: Wed, 12-Mar-86 21:43:27 EST
Organization: Apollo Computer, Chelmsford, Mass.
Lines: 35

I just got my developers kit, and so have at last started to play with my ST.
A few bugs and annoyances have cropped up, so I thowght I would share them
with the net.

My hardware configuration is:
Vanilla 520ST (no 1meg upgrade, no TOS in ROM, ...)
One Single-Sided and one Double-Sided floppy drive.
Both B/W & RGB monitors (although only one at a time, sigh...)

o Eight-Character folder names do not seem to work. I created B:\EXAMPLES\
and tried to move APSKEL.C and ACCSKEL.C into it. All I got was an error
message saying "This application is unable to open the folder you named".
Everything worked just fine if the folder name was B:\DOC\

o BATCH.TTP gives up at once (with no error messages) if you supply less
parameters then it expects. I had created a generic batch script to
compile, load, and run a C program. As the C program took parameters I
had a line in the batch script of the form "B:%1.PRG %2". When I tried
to use this same batch script to test another C program which did not
take parameters I only supplied the first parameter, and BATCH.TTP gave
up after printing its banner line. Supplying a dummy second parameter
made BATCH.TTP happy.

* o There is no easy way to make a double-sided bootable system disk.
The only way I can see is to write a C program myself to create a
boot sector on the disk.

* o It would be really nice if there was a simple application to display
a source file. I know that MicroEmacs will let me look at a file, but
I would really like to be able to scroll through a document using
scroll bars!

If anybody has source code for either of the last two items (flagged with *)
I would love to hear from them. If not, then when I get round to writing them
myself I will post the sources to the net.
</pre>
Re: Bugs/Annoyances in TOS, Developers kit, ... [message #283003 is a reply to message #282994] Tue, 11 March 1986 08:18 Go to previous messageGo to next message
Anonymous
Karma:
Originally posted by: sscalsk

<pre>
Article-I.D.: ucbvax.8603111322.AA13828
Posted: Tue Mar 11 08:18:45 1986
Date-Received: Fri, 14-Mar-86 03:34:19 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 8

I have had similiar problems with folders with names equal to 8 chars. The
difficulty even extends to not being able to delete any folder with an
8 character name.

There is an easy way to create a double-sided bootable system disk. A
utility is already available called WBOOT.PRG and it is listed in the
bloomington st users group PD software catalog that they publish here
on the net 03/10/86.
</pre>
Re: Bugs/Annoyances in TOS, Developers kit, ... [message #283041 is a reply to message #282994] Thu, 13 March 1986 15:07 Go to previous messageGo to next message
Anonymous
Karma:
Originally posted by: steven

<pre>
Article-I.D.: boring.6829
Posted: Thu Mar 13 15:07:13 1986
Date-Received: Sun, 16-Mar-86 10:45:27 EST
Reply-To: steven@mcvax.UUCP (Steven Pemberton)
Organization: CWI, Amsterdam
Lines: 32
Apparently-To: rnews@mcvax

johnf@apollo.UUCP said:
> I just got my developers kit, and so have at last started to play with my ST.
> A few bugs and annoyances have cropped up, so I thowght I would share them
> with the net.
[...]
> * o It would be really nice if there was a simple application to display
> a source file. I know that MicroEmacs will let me look at a file, but
> I would really like to be able to scroll through a document using
> scroll bars!

I agree. It would be much nicer if when you double clicked a file, instead
of getting that terrible 'more', you just got a window on the file which you
could scroll. And that warning thet you can only show or print the file is a
pain too. It would be nicer to select the icon, and then select a print menu
item.

> If anybody has source code for either of the last two items (flagged with *)
> I would love to hear from them. If not, then when I get round to writing them
> myself I will post the sources to the net.

What would be very nice is a version of MicroEmacs that opens real windows
instead of imitating them like it does. Then you could use the scroll bar
instead of ^V, ^X-^N, etc.

Another point altogether: some of the example programs use routines
beginning rc_. An example is apskel.c which uses rc_intersect to see if two
rectangles overlap. I can't find these documented anywhere (or even
mentioned in any header file). Anyone got any documentation? Has anyone
already dismembered the libraries to see if there are any other goodies
hiding in there, and would like to share it with us?

Steven Pemberton, CWI, Amsterdam; steven@mcvax.uucp
</pre>
Re: Bugs/Annoyances in TOS, Developers kit, ... [message #283057 is a reply to message #282994] Mon, 17 March 1986 03:02 Go to previous message
bammi is currently offline  bammi
Messages: 27
Registered: January 1986
Karma: 0
Junior Member
<pre>
Article-I.D.: cwruecmp.1434
Posted: Mon Mar 17 03:02:09 1986
Date-Received: Tue, 18-Mar-86 08:37:07 EST
References: <6829@boring.UUCP>
Organization: CWRU Dept. Computer Eng., Cleveland, OH
Lines: 33

>
> What would be very nice is a version of MicroEmacs that opens real windows
> instead of imitating them like it does. Then you could use the scroll bar
> instead of ^V, ^X-^N, etc.
>
We thought of that when we did the port of microEmacs here.
(that was posted to the net a while ago). The problem is that Vdi
text (v_gtext) is soooo slloooow. For the same reason a window (Vdi/Aes)based
browser would not be very useful.

> Another point altogether: some of the example programs use routines
> beginning rc_. An example is apskel.c which uses rc_intersect to see if two
> rectangles overlap. I can't find these documented anywhere (or even
> mentioned in any header file). Anyone got any documentation? Has anyone
> already dismembered the libraries to see if there are any other goodies
> hiding in there, and would like to share it with us?
>
> Steven Pemberton, CWI, Amsterdam; steven@mcvax.uucp

Almost all the rc_XX routine I have seen were written by Tim
Oren and are fully described in his Professional GEM seminar series
on Antic online. Another place to see the rc_XX routines are in the
Doodle source (which is where they originate from, also writen by Tim
Oren). I highly recommend the Professional Gem series and the
associated sources. If there is enough interest I can post them
(I have parts 1-10 and the associated sources), but i guess most
people have downloaded them by now.
--
Jwahar R. Bammi
Usenet: .....!decvax!cwruecmp!bammi
CSnet: bammi@case
Arpa: bammi%case@csnet-relay
CompuServe: 71515,155
</pre>
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: CPM on ST
Next Topic: ST color monitor as a TV?
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Nov 28 12:22:41 EST 2021

Total time taken to generate the page: 0.02391 seconds