dobbs@marlin.UUCP (Lynn B. Dobbs) (06/14/86)
The HARDWARE: Atari 520ST with color monitor, two SS disk drives
and tos in ROM.
The PROBLEM: None of the code I have received on the net runs.
It doesn't seem to matter what type of code,
either. I have compiled c retreived with the ch
shell stripping off the extra and by hand copying
the lines of code. I have also uudecoded several
binaries for the ST using three different uudecode
programs on two different machines. Also, I
recently received the "starters kit" (and a
wonderfull package it is, too. Four disks packed
to the hubs with great stuff.) but find that most
of the programs tend to produce two mushroom
clouds. Just like the programs I write. :-)
The METHOD: I save the net articles to my home directory on
the UNIX machine at work using an IBM PC-XT
running a h19 terminal emulator. Then I access
the UNIX machine at home with the ATARI running
ST-TALK. I use the capture mode. I don't seem to
understand the xmodem feature of the UNIX machine
and I can't get the kermit in the 520ST developer's
package to work at all.
The QUESTION: Is it just my machine?
The DISCLAIMER: I speak only for mayself. At least my wife
says I don't speak for her. :-)
The THANKS: Thanks.dobbs@marlin.UUCP (06/15/86)
Well, it never fails, or at least it never fails me :-), once a
silly question is asked, the answer pops up. I posted questions concerning
pulling programs off the net and finding I couldn't run them. Fixed that
one by using a few more synapse connections.
Capturing files with ST-TALK also captures the command to list the
file on the host. Once I stripped the extranious header and footer, the
programs ran fine.
I also said that some of the programs in the "STARTER KIT" wouldn't
run. Fixed that, too. Bad disk drive.
Shortly after buying the 520, I bought a second SS drive. It was
quieter and had a slightly easier-to-use disk release mechanism. The drive
had a wide release button directly under the disk openning. The drive
became real flaky lately and was eventually replaced by the retailer. The
replacement is the same as the orignal, small button, noisy drive; BUT it
works and so do all the programs.
Still don't know the answer to my basic question. What is the
"Too many FOR loops" error in Atari Basic mean?
Disclaimer: Speech for myself, by myself, and of myself.
Thanks.JDavidson.WBST@XEROX.COM (06/16/86)
The fault lies not with your machine or even you. The two bombs
indicate that the problem is a bus error. What it means is that the
program you are trying to run expects TOS in RAM not ROM. To see if
this is the problem trying booting your machine with a TOS boot disk and
then trying to run a program that has previously chrashed with 2 bombs.
I had a similar problem with a package I bought on Saturday. It
wouldn't work with TOS in ROM but when TOS was in RAM it ran great.
{John}franco@iuvax.UUCP (06/18/86)
The only piece of software in the STarter Kit that produces two mushrooms
in normal use is the mushroom analyser. Reasons for mushrooms on other
programs might be
1. the program requires the machine to be in low resolution and your
machine is in medium or high resolution.
2. the program requires the machine to be in medium or high resolution
and your machine is in low resolution.
3. the program requires your machine to have TOS in RAM and you have
TOS in ROM
4. the program requires your machine to have TOS in ROM and you have
TOS in RAM
Actually I could continue the list but you get the idea - you have to
experiment a little, putting the machine in different modes, before
giving up on a piece of software.demillo@uwmacc.UUCP (Rob DeMillo) (06/19/86)
In article <860616-081851-1400@Xerox> JDavidson.WBST@XEROX.COM writes: > > The fault lies not with your machine or even you. The two bombs >indicate that the problem is a bus error. What it means is that the >program you are trying to run expects TOS in RAM not ROM. I have a question that I think might be related to this... I am trying to do some things with the BIOS and XBIOS using an assembler. Specifically, I am trying to monkey around with the screen resolution and physical/logical screen addressing. As far as I can tell, I am doing nothing wrong - yet the program results in a double bomb and hangs the system. I have GEMDOS in ROM --- could the above explanation be the culprit? (I'll try booting with GEMDOS in RAM and see if I get the same error.) If this is the culprit, it bites the big one...anyone know any way around it? -- --- Rob DeMillo Madison Academic Computer Center ...seismo!uwvax!uwmacc!demillo "If you can't trust wimp lawyers anymore, who can you trust...?" -- Mildred Krebs
bammi@cwruecmp.UUCP (Jwahar R. Bammi) (06/22/86)
> > I am trying to do some things with the BIOS and XBIOS using an assembler. > Specifically, I am trying to monkey around with the screen resolution and > physical/logical screen addressing. > > As far as I can tell, I am doing nothing wrong - yet the program results > in a double bomb and hangs the system. I have GEMDOS in ROM --- could the > above explanation be the culprit? (I'll try booting with GEMDOS in RAM > and see if I get the same error.) If this is the culprit, it bites the > big one...anyone know any way around it? > > > -- > --- Rob DeMillo > Madison Academic Computer Center > ...seismo!uwvax!uwmacc!demillo Sounds like you are not in Super Mode before trying the operations. See Supexec (xbios(38)) or Super (gemdos(20)). Hope that helps. -- Jwahar R. Bammi Usenet: .....!decvax!cwruecmp!bammi CSnet: bammi@case Arpa: bammi%case@csnet-relay CompuServe: 71515,155