Path: utzoo!attcan!uunet!peregrine!elroy!ames!mailrus!tut.cis.ohio-state.edu!ucbvax!ukc.ac.UK!FTP From: FTP@ukc.ac.UK (UKC FTP Daemon) Newsgroups: comp.sys.atari.st Subject: Failure of your mail. Message-ID: <8903130152.AA20940@mcvax.cwi.nl> Date: 13 Mar 89 09:39:16 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 115 Your mail to uk.co.stc.idec failed when the file was transferred. The mail at this host was to be sent to the follow addresses. stuser%uucp.cel@uk.co.stc.idec This was due to an error at uk.co.stc.idec. The reason given was: File access denied The body of your mail follows. Received: from nss.cs.ucl.ac.uk by kestrel.Ukc.AC.UK via Janet (UKC CAMEL FTP) id aa28569; 12 Mar 89 5:21 GMT Received: from NSS.CS.UCL.AC.UK by NSS.Cs.Ucl.AC.UK via List-Channel id aa01222; 12 Mar 89 2:40 GMT Received: from score.stanford.edu by NSS.Cs.Ucl.AC.UK via Satnet with SMTP id aa01209; 12 Mar 89 2:38 GMT Date: Sat 11 Mar 89 12:08:55 PST Subject: Info-Atari16 Digest V89 #76 From: Info-Atari16 Digest Original-Sender: Info-Atari16-request@edu.stanford.score Errors-to: Info-Atari16-request@Score.Stanford.EDU Maint-Path: Info-Atari16-request@Score.Stanford.EDU To: Info-Atari16 Distribution List: ; Reply-to: Info-Atari16@edu.stanford.score Sender: info-atari16-request@uk.ac.ucl.cs.nss Info-Atari16 Digest Saturday, March 11, 1989 Volume 89 : Issue 76 This weeks Editor: Bill Westfield Today's Topics: Re: Atari ST Screen Dump Info Sought Re: Adding A Floppy Drive Re: Debugger/Monitor missing files from poplib archive mouse problems in London! Re: Atari ST Screen Dump Info Sought OSS Personal Pascal ST COBOL Re: Atari ST Screen Dump Info Sought Re: CompuClub and Atari repair policy Re: NeoDesk / GEM replacements question Re: NeoDesk / GEM replacements question ---------------------------------------------------------------------- Date: 4 Mar 89 06:49:36 GMT From: hermes!jpexg@BLOOM-BEACON.MIT.EDU (John Purbrick) Subject: Re: Atari ST Screen Dump Info Sought To: info-atari16@score.stanford.edu > ... for the Atari Laser Printer (SLM804) there's a screen dumper that > steals the Alt-Help and outputs the correct data over the DMA to print > to the laser printer... > --Kenneth Soohoo (soohoo@cory.Berkeley.Edu) How does a program do this? Presumably terminate-and-stay-resident, but how does it intercept keypresses? A couple of years ago Moshe Braner (where's he gone?) posted a program which did this but it shoved the screen into a reserved area of memory he called the "barrel"; then you could dump the barrel to a Degas file. I'd like to try writing a program which instead created a .TNY format screen file every time alt-help was hit. ------------------------------ Date: 4 Mar 89 07:02:59 GMT From: mcdchg!chinet!saj@gatech.edu (Stephen Jacobs) Subject: Re: Adding A Floppy Drive To: info-atari16@score.stanford.edu In article <9148@mhuxu.UUCP>, cbz@mhuxu.UUCP (Craig B. Ziemer) writes: > Does anyone have any experience using the ST/PC Drive Cable from E. Arthur > Brown Co.? This cable supposedly allows you to hook up any IBM compatible > 3.5" or 5.25" floppy drive to the ST. Is this something that I can easily > make myself? Can I run the second drive off of my existing power supply > somehow? Any comments appreciated. Very much in the same vein: I just got a NEC Multispeed MS-DOS laptop (used-- mostly for use as a second terminal to do debugging on the ST). It has a funny connector on the back, and there is a claim that it can pretend to be external floppy drives on a desktop MS-DOS machine. Can the same thing be arranged with an ST? Believe me, it would be the steal of the century if that portable could pretend to be a pair of double sided drives for my ST. ------------------------------ Date: 3 Mar 89 15:21:10 GMT From: brunix!rjd@uunet.uu.net (Rob Demillo) Subject: Re: Debugger/Monitor To: info-atari16@score.stanford.edu In article <8751@polyslo.CalPoly.EDU> jriegel@polyslo.CalPoly.EDU (Jeff Riegel) writes: > > Can anyone recommend a good PD assembly language debugger or monitor? >I have Laser C but its in-line assembly code is difficult to debug. > >-Jeff Riegel jriegel@polyslo.calpoly.edu If you have Laser C, you should seriously consider getting the upgrade to the newst version, and then get the Laser C Source Debugger. It's an excelllent debugging tool, and it works flawlessly in the Laser C environment. (It also works well from Gulam) - Rob DeMillo Brown University - Planetary Science Group **** Rest omitted - too long!