edotto@ux1.cso.uiuc.edu (Ed Otto) (06/19/91)
I need a software implemented copy protection program for a PC/AT/386 that is compatible with MS Fortran Optimising Comp[iler rev 4.01. It has to be inexpensive; $90-150 is about all my clint can afford after he pays my bill. Please e-mail replies to me, and I will summarize for the net. ************************************************************************* ** Edward C. Otto III * Email: UIPSA::OTTO ** ** University of Illinois * UIPSB::OTTO ** ** Printing Division * edotto@uipsuxb.ps.uiuc.edu ** ** 54A E. Gregory * edotto@ux1.cso.uiuc.edu ** ** Champaign, IL * otto@uipsa.dnet.nasa.gov ** ** 217/333-9422 * ** ************************************************************************* "As knowledge is to ignorance, so is light unto the darkness." -- GO 'PODS! -- -- ************************************************************************* ** Edward C. Otto III * Email: UIPSA::OTTO ** ** University of Illinois * UIPSB::OTTO ** ** Printing Division * edotto@uipsuxb.ps.uiuc.edu **
mmccorm@d.cs.okstate.edu (McCormick Martin) (06/19/91)
Basically, copy protection programs are a waste of time. and resources.
There are a few tricks which make it impossible to use DISKCOPY to copy
a program, but many times copy protection just introduces problems for
honest users.
I am only half joking when I make the suggestion that one way to find
out how to copy protect a program would be to contact your local teen-
age hacker group, see what games they haven't cracked yet, and find out
what scheme was used to protect the games.
Martin McCormick
Amateur Radio WB5AGZ
Oklahoma State University
Computer Center
Data Communication sGroup
Stillwater, OKyanek@panix.uucp (Yanek Martinson) (06/20/91)
In <1991Jun18.212336.25372@ux1.cso.uiuc.edu> edotto@ux1.cso.uiuc.edu (Ed Otto) >I need a software implemented copy protection program for a PC/AT/386 that >It has to be inexpensive; $90-150 is about all my clint can afford after I once needed copy protection for a program, not for sale or general distribution but there had to be only ONE copy of the program. So what I did was make a little hole in the disk with a needle, and then wrote a program that would scan the disk to see which sector returns error when read, and then had my program check for that sector, to see if it was unreadable and check a few other sectors to make sure the entire disk was not damaged. It worked fine.