Forum unknown
· Games
#Starglider
3 messages in this thread
Jez,
Just a small suggestion, mayhaps in the future you could look to see if
there is enough memory (lots of extra megabytes on Amigas over here) before
you trash AmigaDOS. I understand you're dislike of multi-load programs, I
don't like them either, but I DON'T like programs more that destroy
everything else that's going on in the machine. I'll prolly get the game
anyway since my son rarely, if ever, does more than one thing at a time on
his Amiga.
Vic, hiya pal!! Long time no see!!
Even if the user had plugged more memory into the machine, all our code
requires CHIP memory, and very very little of it could sit in FAST memory,
so we didn't bother checking for any extra available memory.
I agree with your sentiments, however… and our next program will probably
system friendlier (no guarantees, tho!). For performance code, I
personally feel that ANYTHING, and EVERYTHING is acceptable to get the
hardware running as fast as it possibly can. That includes trashing the
OS, as long as the computer itself is not damaged in any way…… and
since we dont instruct any Robot Arms to HIT the computer, we assumed
things would be okay after a REBOOT.
We considered adding a menu option 'R" to reboot the machine, but since the
user can do this quicker, and more thoroughly with CTRL-Amiga-Amiga we
decided this was unnecessary and overcomplicated.
How's MetaScope these days? I can't remember how the saying goes, but I
think its "Copying is the best form of flattery"….. or something like
that. Anyhow, we wrote an in-house remote Amiga monitor, such that one
Amiga remote controls (and debugs) another TARGET Amiga. We styled our
user interface on yours, since it was the cutest and friendliest we had
seen! (congrats!)
Ours is not a commercial product, so don't be disturbed or start talking to
your lawyer (grin!) Its simply for our own use.
— Jez.
Vic, hiya pal!! Long time no see!!
Even if the user had plugged more memory into the machine, all our code
requires CHIP memory, and very very little of it could sit in FAST memory,
so we didn't bother checking for any extra available memory.
I agree with your sentiments, however… and our next program will probably
system friendlier (no guarantees, tho!). For performance code, I
personally feel that ANYTHING, and EVERYTHING is acceptable to get the
hardware running as fast as it possibly can. That includes trashing the
OS, as long as the computer itself is not damaged in any way…… and
since we dont instruct any Robot Arms to HIT the computer, we assumed
things would be okay after a REBOOT.
We considered adding a menu option 'R" to reboot the machine, but since the
user can do this quicker, and more thoroughly with CTRL-Amiga-Amiga we
decided this was unnecessary and overcomplicated.
How's MetaScope these days? I can't remember how the saying goes, but I
think its "Copying is the best form of flattery"….. or something like
that. Anyhow, we wrote an in-house remote Amiga monitor, such that one
Amiga remote controls (and debugs) another TARGET Amiga. We styled our
user interface on yours, since it was the cutest and friendliest we had
seen! (congrats!)
Ours is not a commercial product, so don't be disturbed or start talking to
your lawyer (grin!) Its simply for our own use.
— Jez.