🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.amiga.tech
Article #8090

Re: Help --> How to prevent the visit from the dreaded guru

#8090
From: Dave Schreiber
Date: Sat, 12 Jan 1991 21:05
58 lines
3126 bytes
In article <1991Jan12.034631.18571@marlin.jcu.edu.au> glmwc@marlin.jcu.edu.au (Matt Crowd) writes:
>In article <22567@well.sf.ca.us> farren@well.sf.ca.us (Mike Farren) writes:
>>glmwc@marlin.jcu.edu.au (Matt Crowd) writes:
>>
>>>Anyway, as most games don't even multitask, if the
>>>program quit from a state of no OS it may as well crash.
>>
>>Please be sure and tell us all when you finish your game.  I'd like to warn
>>all of my friends in advance about it.  I sure wouldn't want any of them
>>to support such idiocy as you're putting into it.

I agree totally.  I've usually got too much going on my 3000 to risk
losing it all because some programmer is out for blood.

>Did I say my game killed the OS?

You used the "as most games don't even multitask" statement as justification
for crashing the machine if the user messed up the copy-protection.  If your
game doesn't throw out the OS, and in fact multitasks perfectly, then you're
arguing that, because OTHER games that throw out the OS effectively crash
when the copy protection scheme says "TROUBLE!", it's all right for YOUR
game to do so even though it doesn't throw out the OS.

>Did I say my game didn't multitask perfectly?
>Did I say my game isn't hard drive installable and doesn't
> come with a HD install program to help?
>Did I say my game doesn't work on the Amiga 3000?
>Did I say my game doesn't work with 2.0 and doesn't use
> the standard file requester if running on 2.0?
>
>NO! Because all of the above is not true. 

I don't remember anybody claiming that your game didn't multitask, couldn't
be installed on a hard drive, wouldn't work on a 3000, or wouldn't work
under 2.0.  _You_ implied that the game threw out the OS.

>>Mike Farren 				     farren@well.sf.ca.us

>As for crashing the machine after the password fails....

>well I'm still thinking about it.

Think about this:  if you crash the machine, you will drive away legitimate
users (me for one).  You will not stop pirates, however;  an unprotected
version of your software will be floating around "out there" within days of
it's release.  The net result will be a lower number of sales.  If that's the
way you want it, fine;  nobody's forcing you to make money :-).

>Colin Adams.

Followups to comp.sys.amiga.misc

-- 
Dave Schreiber                                    davids@slugmail.ucsc.edu 
                                or (but not both) davids@ucscb.ucsc.edu
"It was fun learning about logic, but I don't see where or when I will ever
use it again."
Technical Details
Message-ID: <10981@darkstar.ucsc.edu>
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!samsung!sdd.hp.com!usc!apple!agate!darkstar!ucscf.UCSC.EDU!davids
References: <1991Jan9.092435.10710@marlin.jcu.edu.au> <22567@well.sf.ca.us> <1991Jan12.034631.18571@marlin.jcu.edu.au>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!samsung!sdd.hp.com!usc!apple!agate!darkstar!ucscf.UCSC.EDU!davids
From: davids@ucscf.UCSC.EDU (Dave Schreiber)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Help --> How to prevent the visit from the dreaded guru
Message-ID: <10981@darkstar.ucsc.edu>
Date: 12 Jan 91 21:05:45 GMT
References: <1991Jan9.092435.10710@marlin.jcu.edu.au> <22567@well.sf.ca.us> <1991Jan12.034631.18571@marlin.jcu.edu.au>
Sender: usenet@darkstar.ucsc.edu
Followup-To: comp.sys.amiga.misc
Organization: University of California, Santa Cruz
Lines: 58