#Defender.lzh
9 messages in this thread
Denny, I tried it under the 68000, still no go. Any other ideas, or is it
just a waste of disk space?
Gene
Gene, Defend runs on my 3000 under 1.3. I have not tried it on any other
machine. It does not run under 2.04.
Steve, I have a 2500HD ('020), 5 megs ram, 1 meg chip, running 1.3 as well.
It doesn't run at all. The program appears to load, and then the system
crashes completely. I have to reboot to get it back. I tried it under the
68000, but that didn't work either. Any ideas (Anyone?).
Gene
Gene,
I had no luck getting the Defender program to run either. Same symptoms:
would seem to load and then crash. The only thing not stock about my 2000
system is 1M chip RAM, unless it's something in my startup-sequence. I gave
up on it.
Karl
– via Whap!
Yeah, I gave up on it too. I have better things to do than debug some one
else's faulty software (or installation instructions or whatever..). I have
my own faulty software (or installation or…) to debug first. 🙂
Too bad, tho', it sounded like it might have been fun, I enjoyed the arcade
version.
While I'm not familiar with the Defender program that you are speaking of,
I have found the following to be true for most crashing programs. Either
they are unable to handle >512K of memory, unable to handle >512K chip ram,
or the default STACK is too small.
I've found that setting the STACK to 50000, cures a lot of programs.
NoFastMem helps programs that don't like fast memory, and a little utility
called KillChip, will make the 2000 look like a 512K chip ram machine.
Defender will not run (at least on my machine) when using a 68020. I have
to boot with the 68000 or the program will crash. I assume somebody didn't
play by the rules.
Peter
Peter, It does run on my 3000, under 1.3.
Alex,
That KillChip sounds handy for testing stuff before inclusion into a
user-group library. I've had people clobber me because things wouldn't run
on their original-Agnus machine.
Karl
– via Whap!