HDTenEightyP/NetNews huggingface dataset:
From: max@neumann.cba.csuohio.edu (Max Polk)
Subject: Re: LASER C PRINTING
Summary: Short explanation of IO and fprintf (stdprt, ...)
Organization: Cleveland State University
Date: Fri, 4 Sep 1992 14:53:36 GMT

From what I can tell, Atari and LASER C run things this way:

 LEVEL OF COMMUNICATION  IMPLEMENTATION    TYPICAL CALLS
   Device                   BIOS        Bconin, Bconout
   File descriptor         GEMDOS       Fopen, Fread, Fwrite, Cconin, Cconout
   Stream                  LASER C      fopen, fread, fwrite, printf, fprintf

Each higher level uses the previous level to accomplish their tasks.
For example, printf calls Fwrite, (yes, even for screen output!), and
Fwrite within the operating system calls Bconout at some point.

An array of 20 _iob structures are standard for LASER C programs, which
are used for the fread, fwrite, printf, etc.  The first three are
already used when your program runs, much like UNIX does things.  These
are _iob[0], _iob[1], and _iob[2], which are structures whose addresses
are stdin, stdout, and stderr, and represent buffered file IO, called
streams.

In UNIX, the first three _iob structures use file descriptors 0, 1, and
2.  But in LASER C, it is 0, 1, and 1.  Writing to stderr is really the
same as stdout.  In UNIX, programs know to write to any one of three files
whose descriptors are 0, 1, or 2.  But in Atari, there is only 0 and 1.

Even if you can manage to Fdup the console output and change the
association of stderr to it, programs executed with this in place won't
care about what you did, because only file descriptors 0 and 1 have
significance.

Furthermore, in UNIX, opening a file results in file descriptor 3, the
next consecutive number, being used, wherease in Atari, it is number 6.
(Let me use "fd" to mean file descriptor.)  This is because Atari is
different than UNIX as far as standard devices is concerned.  UNIX uses
your /dev/tty?? as your single device.  Atari likewise has the console input
and output like UNIX but also has a serial port (fd 2), printer port (fd 3),
and two other devices open (fd 4 and fd 5) when your program begins.

LASER C has no such thing as stdprt, that is, a pre-opened stream
connected with the printer.  However, the printer device is ready and has
fd 3, so you can simply associate a stream with it as follows:

#include <stdio.h>

FILE *stdprt;

main ()
{
    stdprt = fdopen (3, "w");	/* make a stream for the printer */

    fprintf (stdprt, "This goes to the printer");

    ....
}
From: patterson@koal.enet.dec.com (Jim Patterson)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Stero Glasses on the ST
Date: 2 Sep 92 21:29:17 GMT
Distribution: usa
Organization: Digital Equipment Corporation


In article <1992Sep2.175847.2300@natinst.com>, glens@natinst.com
(Glen Sescila) writes...
> 
>	Could somebody please at least tell me what port the old 'Stereo-
>Tek' glasses plugged into on the ST?  I have a pair of chopper glasses

	There is a special cartridge they plug into.

                                 Jim Patterson
                          (Patterson@vfovax.dec.com)

    Programmer on: VAX/VMS, Atari STe, Atari ST, Atari 8-bit, Commodore 64
    Programming in: Pascal, VAX MACRO, 68000, C, 6502, Basic, Action, Forth
Newsgroups: comp.sys.atari.st.tech
From: jcy2@engr.uark.edu (YOCKEY J CALVIN)
Subject: Use an Atari color monitor with a PC?
Keywords: monitor
Organization: University of Arkansas
Date: Tue, 1 Sep 1992 15:14:22 GMT

I was just wondering if this is possible.  If so, can it support VGA?

Thanks for any replies.

Calvin Yockey
cjy@uafhp.uark.edu
Newsgroups: comp.sys.atari.st.tech,comp.sys.atari.st
From: healy@nosc.mil (Mike Healy)
Subject: Re: Zmodem 1.62 (J. Bammi version) compiling problems.
Organization: Naval Ocean Systems Center, San Diego
Date: Wed, 2 Sep 1992 00:13:38 GMT


One last thing on your make problem:

You do have the dependency for the executable, don't you? e.g.

OBJECTS = foo.o bar.o

foo: $(OBJECTS)
	$(CC) $(CFLAGS) -o foo $(OBJECTS) $(LIBS)

or something like that (all symbols previously defined)


Mike Healy

healy@cod.nosc.mil

Xref: sparky comp.sys.atari.st.tech:4623 comp.sys.atari.st:12982
From: mforget@ersys.edmonton.ab.ca (Michel Forget)
Newsgroups: comp.sys.atari.st.tech,comp.sys.atari.st
Subject: Re: Zmodem 1.62 (J. Bammi version) compiling problems.
Date: Sat, 29 Aug 92 12:57:04 MDT
Organization: Edmonton Remote Systems #1, Edmonton, AB, Canada

gs32+@andrew.cmu.edu (Geoffrey Spear) writes:

- Excerpts from netnews.comp.sys.atari.st: 28-Aug-92 Zmodem 1.62 (J. Bammi
- > versi.. Michel Forget@ersys.edmo (1164)
- 
- > There are repeated references to a PD MAKE tool.  I do not have this 
- tool, and have never been able to locate it.  Is it GNU Make? 
- 
- 	     There is a "make" tool out that is included with Sozobon C.  It
- has no docs with it (which is really annoying), but it is supposedly
- very similar to the UNIX make program.  I don't use it myself, I prefer
- to compile everything by hand (although with really BIG programs typing
- > in a cc line for each source file takes a while.)
- 
- 
- > Last question:  The DLIBS library is mentioned in the docs, in
- > association with Alcyon C.  I thought DLIBS was meant for Sozobon C?  I
- > have a version of DLIBS, but now I'm not sure at all what I should be
- > doing to get Zmodem compiled.
- 
- 	The dLibs library is a PD C library which is generally considered to be
- better than the libraries included with Alcyon.  And as Sozobon C was
- developed as a replacement for Alcyon, and is for the most part
- Alcyon-compatible, dLibs works for both.  As a matter of fact, dLibs was
- ORIGINALLY created for use with Alcyon, and the people who wrote Sozobon
- used it.

Okay, but how do I get Alcyon to use DLIBS instead of the library it uses 
now (which seems to be nothing special).  My only experiences with "make" 
so far have been ones of total anger, since I can not get it to do what I 
need.  For a while I thought I was on the right track, but then it told 
me that all of the files were up to date.  No matter how I changed the 
dates on the files, it held to that position...


<<  ------------------------------------------  >>
<<        mforget@ersys.edmonton.ab.ca          >>
<<  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  >>
<<               Michel Forget                  >>
<<   The Key:  Spirit over mind over matter.    >>
<<  ------------------------------------------  >>
From: micro@imada.ou.dk (Klaus Pedersen)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: DSP in the Falcon
Date: 3 Sep 92 18:08:45 GMT
Organization: Dept. of Math. & Computer Science, Odense University, Denmark

hrs@aber.ac.uk (Herbert Martin Sauro) writes:

>I assume that the 56001 can only deal with integers (i.e no floating
>point), is this true?

It uses 24/48/56 bit fixed point arithmetic(sp?).
There is a fast floating point lib. available if a S/N of 144 dB (24bit) to 
350 dB (56 bit) isn't enough.

-Klaus
From: chu@acsu.buffalo.edu (John C. Chu)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: GNU make 3.62 at atari.archive
Date: 3 Sep 92 17:57:17 GMT
Organization: UB

Frank Ridderbusch has re-ported GNU Make 3.62. At his request, I
uploaded it to atari.archive a little while ago. It is in the new
directory with the name:

gmake362.zoo

I've been using this version for a while now and it works fine.

					john
				chu@acsu.buffalo.edu
From: gs32+@andrew.cmu.edu (Geoffrey Spear)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: LASER C PRINTING
Date: 31 Aug 92 14:05:16 GMT
Article-I.D.: andrew.IecdSQO00aw6IR31Es
Organization: Freshman, CIT general, Carnegie Mellon, Pittsburgh, PA


	The standard file for your printer in C is "stdprn", not "stdprt". 
That should work for any C compiler.
Newsgroups: comp.sys.atari.st.tech
From: bammi@acae127.cadence.com (Jwahar R. Bammi)
Subject: Re: format of object files in gcc
Organization: Cadence Design Systems
Date: Sat, 15 Aug 1992 08:52:55 GMT

> In <bnell.714159659@ferrari> bnell@siemens.com. (Bill Nell) writes:
> 
> >Can anyone tell me where to find the format of the .o files used by gcc?
> >I don't feel like wading through the source or anything like that.  I would

Bill Nell,
	what is your address anyway? bnell@siemens.com bounces back.
(this happened what i tried to reply to this message yesterday, and
had happened in the past, maybe a mont ago when you asked about the
startup files)

to answer your question, gcc .o's are in unix a.out format. the
details of the format may be found in utilsrc/gnu-out.h, the
symbol table stuff in <stab.h> and <stab.def>, and a paper that may
help to (if you are not familiar with a.out) in
documentation/aout.ms.

cheers,
--
--
bang:   uunet!cadence!bammi			jwahar r. bammi
domain: bammi@cadence.com
GEnie:	J.Bammi
CIS:    71515,155
Newsgroups: comp.sys.atari.st.tech
From: bbs.ruscal@tsoft.sf-bay.org (Russel Mar)
Subject: Older ROMs ok in Mega STE ?
Organization: The TSoft BBS and Public Access Unix, +1 415 969 8238
Date: Thu, 27 Aug 1992 11:46:32 GMT

I am having problems running the Hybrid Arts ADAP 1 software on a Mega
STE.  On a regular ST, I can zoom a window and then evelope a small
section of a waveform.  On a Mega STE, the window zooms back out.  I have
eliminated software as a variable, and now look to the ROM routines as
the probable culprit.  So the question is, can I load TOS 1.x ROMS in
place of the 2.x ?

Please E-Mail response direct;  I'll re-post appropriate info.

Thanks!

--
Russel Mar (bbs.ruscal@tsoft.sf-bay.org)
Newsgroups: comp.sys.atari.st.tech
From: kinzel@ibr.cs.tu-bs.de (Jens Kinzel)
Subject: atari emacs and ^M
Summary: making emacs handle ^M's
Keywords: emacs
Organization: TU Braunschweig, Informatik, Bueltenweg, Germany
Date: Thu, 3 Sep 1992 16:42:40 GMT

Hi !

I just managed to pass the dungle installing emacs under MiNT (and
after a short period of happiness), I feel it's nasty that atari-emacs
can't handle '^M' EOL charakters by default. This editor isn't vewry
useful, when can't handle EOL's (or when it should be too difficult to
handle 'em). So I think there must be someone who wondered about this
problem like me, or has just solved it!
							bye, Jens
----------------------------------------------------------------------
Jens Kinzel                                            God is real
Institut fuer Betriebssysteme und Rechnerverbund       unless he is integer
kinzel@ibr.cs.tu-bs.de
----------------------------------------------------------------------
Newsgroups: comp.sys.atari.st.tech
Subject: 1.44Mb floppy problem on TT, problem solved
From: mboom@mswe.dnet.ms.philips.nl
Date: 25 Aug 92 11:22:11 +0100
Organization: Philips Medical Systems Nederland

I wrote:
> Keyword: Help needed with 1.44 Mb floppy in TT
> 
> The problem is that the TT is not able to write a 1.44Mb floppy but it
> can read one. I have already replaced the WD1772 chip with a AJAX one,
> which didn't solve the problem.
> 
> Anyone?

I bought an external 1.44Mb drive on the Atari Messe last weekend and it worked!
I then concluded that it must be the drive it self which was the problem.

After a long time of discussions with a friend of mine, I reopened the TT's case
and replaced the drive. It still wouldn't work, which gives me the creeps,
because the external one did. When we looked at the time, around 1:30 AM :-(,
we gave up and closed everything again. We couldn't resist a last try, and.....

it worked. It seems that it is very important to close the case. Interference
of the monitor? who knows,

Anyway, I am now the happy owner of two 1.44Mb drives.

Thanks to everyone who posted or mailed some help.

Marcel Boom


email: mboom@mswe.dnet.ms.philips.nl
voice: +31 40 762007 / +31 4408 3531
Newsgroups: comp.sys.atari.st.tech
From: d89-sla@cyklop.nada.kth.se (Stefan E Larsson)
Subject: Asking questions (Re: Tape drive for ATARI ST)
Organization: Royal Institute of Technology, Stockholm, Sweden
Date: Wed, 2 Sep 1992 02:43:39 GMT

>> Please respond by E-mail as I usually don't read this group.
>
>> Regards,
>> -Roger
>
>Once again: if you don't read this group, don't ask questions in it:
>it is not just a hot-line: it is a conference !

Not to flame anyone, but I don't agree.
If someone doesn't read a group they may have good reasons for not doing 
so. How could anyone else know? Even if they were just lazy, why shouldn't
they be allowed to ask an occasional question? Nobody is obliged to
answer them anyway. 

And considering the large flow of news, nobody could be expected
to participate in more than a few newsgroups. Still they may very well
come upon questions that can't be answered in their native groups. 
So why not ask about it in the appropriate group and use the huge
source of knowledge that Usenet is?
-- 
--------------------------------------------------------------------------
 Stefan E Larsson // d89-sla@nada.kth.se // Royal Institute of Technology
--------------------------------------------------------------------------
Newsgroups: comp.sys.atari.st.tech
From: aweder@iiic.ethz.ch (Andreas Michael Weder)
Subject: Star Trek Font?
Organization: Dept. Informatik, Swiss Federal Institute of Technology (ETH), Zurich, CH
Distribution: local,ch,ger,uk,na
Date: Tue, 1 Sep 1992 17:26:24 GMT



Hi

sorry, this is probably a FAQ. Nevertheless, I am looking
for a STAR TREK FONT for the Atari ST (preferably GDOS
and/or Signum/Script 2).


Thanks
-- Andrew
   aweder@inf.ethz.ch
From: neil@cs.hw.ac.uk (Neil Forsyth)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Intterrupts for screen saver ... OOOOOOPS
Date: 26 Aug 92 09:06:14 GMT
Organization: Dept of Computer Science, Heriot-Watt University, Scotland

In article <1992Aug25.114326.2044@prl.dec.com> amos@prl.dec.com (Samos) writes:
>For the keyboard test, replace the tst.b $fffffc02.w by
> tst.b $fffffc02.w
> bmi.s .No_key
> clr.l pointer
>.No_key:
> addq #1,pointer
>
>because when you bash a key, a byte between 0 and $7f is sent back
>and when you remove your hand from the key (!) the same code+$80
>is sent back..

What is going on here? If you want to write a screen saver you should
intercept the IKBD vetcor at $118 but the code that does so should not touch
$FFFFFC02 at all! The fact that the interrupt has occurred is all the
information that is required. Basically you could intercept the 200Hz clock
vector ($114?) and just add 1 to your own private clock variable. When your
clock var hits a predetermined limit you blank the screen. The IKBD intercept
code just needs to zero the clock var and restore the screen if it's
currently blanked. As long as there is IKBD activity (mouse or keyboard) then
the clock will never reach the limit.

Bung in XBRA's before your intercepts and put a cookie in the Cookie Jar so
that the delay can be altered and well you've got something very similar to
Ken Badertscher's Maccel3.

+----------------------------------------------------------------------------+
! DISCLAIMER:Unless otherwise stated, the above comments are entirely my own !
!                                                                            !
! Neil Forsyth                      JANET:  neil@uk.ac.hw.cs                 !
! Dept. of Computer Science         ARPA:   neil@cs.hw.ac.uk                 !
! Heriot-Watt University            UUCP:   ..!ukc!cs.hw.ac.uk!neil          !
! Edinburgh, Scotland, UK           "That was never 5 minutes!"              !
+----------------------------------------------------------------------------+
From: lynbech@daimi.aau.dk (Christian Lynbech)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: atari emacs and ^M
Keywords: emacs
Date: 4 Sep 92 08:19:07 GMT
Organization: DAIMI: Computer Science Department, Aarhus University, Denmark

kinzel@ibr.cs.tu-bs.de (Jens Kinzel) writes:

>Hi !

>I just managed to pass the dungle installing emacs under MiNT (and
>after a short period of happiness), I feel it's nasty that atari-emacs
>can't handle '^M' EOL charakters by default. This editor isn't vewry
>useful, when can't handle EOL's (or when it should be too difficult to
>handle 'em). So I think there must be someone who wondered about this
>problem like me, or has just solved it!
>							bye, Jens
>----------------------------------------------------------------------
>Jens Kinzel                                            God is real
>Institut fuer Betriebssysteme und Rechnerverbund       unless he is integer
>kinzel@ibr.cs.tu-bs.de
>----------------------------------------------------------------------

Actually there is.

I guess that you have the MiNT version of emacs. There is another port, based
on the most recent version (18.58) of emacs.

Included in this is a little elisp-package which will automatically remove the
^M characters while visiting a normal atari file. They are of course reinserted
before the file is saved.

I can't remember the path on atari.archive right now, but try checking the
gnustuff directory and/or the editor directory. This little package is worth
the entire download.

Don't forget that the appearance of the ^M characters is actually a feature.
One of the advantages of emacs is the ability to handle arbitrary
control-characters as ordinary characters that can be searched and replaced and
whatever. Then if the characters is not desired, it is small trouble to hook up
functions to delete/reinsert them when loading/saving the file.



------------------------------------------------------------------------------
Christian Lynbech

DAIMI						office: R0.32   phone: 5034
University of Aarhus,DK-Denmark                 email: lynbech@daimi.aau.dk
------------------------------------------------------------------------------
			  EMACS, The One True Editor                       


Hit the philistines three times over the head with the Elisp reference manual.

                                        - petonic@hal.com (Michael A. Petonic)
From: hrs@aber.ac.uk (Herbert Martin Sauro)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: DSP in the Falcon
Date: 1 Sep 92 10:27:48 GMT
Organization: University of Wales, Aberystwyth

In article <469@muller.loria.fr> eker@loria.crin.fr (Steven Eker) writes:
>Well the best thing about a 56001 is that it has a hardware multipler which can
>do a multiply & add step in 1 instruction cycle (= 2 clock cycles).
>This is much faster than your typical microprocessor and in fact the 56001
>does shifting via multiplication rather than the other way arround.
>Other goodies:
>	3 memory areas (1 program, 2 data) which can be simultaneosly accessed.
>	With most instructions you get 1 or 2 move instructions free.
>	Fancy adressing modes for fast circular queues, FFTs etc
>	Fast interupts
>	Hardware looping
>
>Things which the 56001 should be useful for include software sound synthesis
>& matrix*vector multiplcation (the basis of 3D vector games).
>
........
>
>Steven

I assume that the 56001 can only deal with integers (i.e no floating
point), is this true?

Herb
-- 
/******************************************************************************
Herbert Sauro                                   e-mail: hrs@aber.ac.uk
Biological Sciences                              phone: +44 970 622353
Univesity College of Wales                                                    
Newsgroups: comp.sys.atari.st.tech
From: bammi@acae127.cadence.com (Jwahar R. Bammi)
Subject: Re: Reopen an ACCs window
Organization: Cadence Design Systems
	<BAMMI.92Aug13222840@acae127.cadence.com> <mfg.714118058@gmd.de>
Date: Fri, 14 Aug 1992 03:22:25 GMT

In article <mfg.714118058@gmd.de> mfg@gmd.de (Martin Gergeleit) writes:

> I AM using MiNT and it is fine, but as long as there is no MultiTOS available
> I _have_ to use ACCs in order to get a sensible Window-System with terminals.
> BTW even Eric Smith uses TOSWIN._ACC_ to use terminal sessions and GEM-

	thats funny, i call it TOSWIN.PRG and start it up from mint.cnf

cheers,
--
--
bang:   uunet!cadence!bammi			jwahar r. bammi
domain: bammi@cadence.com
GEnie:	J.Bammi
CIS:    71515,155
Newsgroups: comp.sys.atari.st.tech
From: bq035@cleveland.Freenet.Edu (Brian Jepson)
Subject: Minit and echo * problem
Reply-To: bq035@cleveland.Freenet.Edu (Brian Jepson)
Organization: Case Western Reserve University, Cleveland, OH (USA)
Date: Wed, 26 Aug 92 15:49:25 GMT


Hi. I've just experimented with minit.ttp on one of my small partitions to see
if it was something I'd like. But I'm having trouble getting all the filenames
recognized by a shell. I've used init, ksh, bash, and tcsh, and so far, the
only shell that will correctly return all the full length filenames when I
echo * is tcsh. Using ls from the futils is no problem, I get all the files
listed. But if I were to ls *, I would have a problem. The expansion seems to
only be correct in tcsh. However, I have noticed that in the root directory,
the shells seem to do ok, and even with init, bash, and ksh, *some* filenames
get expanded okay, even in subdirs. I use mfsconf to set all short name 
replacements to neither (-l n -s n -d n -x n ? I can't remember if it's a n, but
you get the jist, I'm not at my Atari now), so as to always have the full names.

Has anyone else dealt with this? Is it some subtle thing I'm missing? Any help
is greatly appreciated.
-- 
*********************
* "Nothing is true; Everything is permitted" - Hassan i Sabbah *
                                         ***********************
Brian Jepson = iby223@uriacc.uri.edu || bq035@cleveland.freenet.edu
Newsgroups: comp.sys.atari.st.tech
From: hohr@dxcern.cern.ch (Roger Hoh)
Subject: Re: 24 pin screen dumps
Organization: CERN European Laboratory for Particle Physics
Date: Thu, 27 Aug 1992 06:06:11 GMT

 Direct mail bounced. So I send it here.

 Hi Brian,

 I did write (a long time ago:-)) a utility for screen dumps  with  my  24
pins printer.  Here's it's READ_ME file:

-------------------------cut here---------------------

				HC24_H12.PRG

    This utility replaces the internal hard-copy routine (for 9 pin printers)
 by an other one for LQ500 compatible 24 pin printers (high resolution only).

    In addition, it respects the x/y ratio (circles on the  screen  are  also
 circles on the paper) and it will give you a realy good  printout  of  about
 180x115 mm. in horizontal format.

    The negative parts are that you need a printer spooler of 128kb, and that
 it will thake about 23 seconds on a Mega STE (at 16Mhz+cache) before you get
 the hand back, even if it is, like this version, compiled  with  the  Pure-C
 compiler (Thanks Ulf).

    To be put in your \AUTO\ folder. Use it at your own risk: it's absolutely
 free. If modified, please let me know. Not to be sold or for commercial use.
 I just hope it works for you too.

    Enjoy!

    Roger               email: hohr@cernvax.cern.ch

-------------------------cut here---------------------

 It's on a.a.u.e in the directory printing.

 Have a nice day.

 Roger          hohr@dxcern.cern.ch
-- 
   email: hohr@cernvax.cern.ch or hohr@cernvax.UUCP or hohr@cernvax.bitnet
	     smail:  Roger Hoh ,P.S. Div., CERN,
		     1211 Geneva 23, Switzerland