Article View: comp.os.msdos.programmer
Article #6141Re: How could I copy protect Borland C++ on a network ?
From: Dave Tutelman
Date: Mon, 21 Dec 1992 12:17
Date: Mon, 21 Dec 1992 12:17
48 lines
2727 bytes
2727 bytes
In article <shephard.724811384@sfu.ca> shephard@fraser.sfu.ca (Gordon Shephard) writes: >cyberman@exucom.com (Stephen R. Phillips) writes: >>Luc Bussieres (bussiere@garrot.DMI.USherb.CA) wrote: >>: Is there a way to protect Borland C++ from pirating on an nfs disk? >>: >>: Does novell as a copy protection feature that will work with Borland C++? > >1) Execute-Only on Novell is horrendous as you are no longer > able to back up the Execute Only files. Unacceptable. Who is "you"? The question is how to PREVENT the user from pirating the software. If the network (or application) administrator can't back it up, I agree that's unacceptable. But if the USER can't back it up (but rather has to run it from the network copy) that's exactly what was being requested. As a user, I might not be crazy about this, especially if the network is less than 100% reliable, but I could always buy my own (non-copy protected) copy. Remember that the legitimate owner of the software (the network or application administrator) still has the installation disks and whatever backup copies of it that they made, so the backup issue is really a non-issue. >3) Try experimenting with the Hidden attribute. A DOS Copy won't > work with a hidden files, but you can execute it. True, but it is more inconvenient for the user than the pirate. The user can't "dir" the files if he/she forgets the name of a command. But the pirate CAN type a hidden file. What's the effective difference between copy hidden.fil myfile and type hidden.file > myfile The latter does in fact work. BTW, I oppose copy-protected software in general, and will avoid buying any that I know is copy-protected. But that's not what is being requested here. The original poster, who has bought a legitimate copy of BC++, wants to make it available for USE by students taking a course. His/her agreement with Borland (I'm guessing here; I HOPE there's an agreement with Borland) allows this but insists that there be no copies of the software walking away with the students. Assuming Borland has indeed agreed to this, I see no problem with it. Dave
Technical Details
Message-ID:
<1992Dec21.121737.9882@cbnewsj.cb.att.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!cbnewsk!cbnewsj!davetReferences:
<BUSSIERE.92Dec17150727@garrot.DMI.USherb.CA> <1992Dec19.233247.12469@exucom.com> <shephard.724811384@sfu.ca>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.msdos.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!cbnewsk!cbnewsj!davet From: davet@cbnewsj.cb.att.com (Dave Tutelman) Subject: Re: How could I copy protect Borland C++ on a network ? Organization: AT&T Bell Labs - Lincroft, NJ Distribution: na Date: Mon, 21 Dec 1992 12:17:37 GMT Message-ID: <1992Dec21.121737.9882@cbnewsj.cb.att.com> References: <BUSSIERE.92Dec17150727@garrot.DMI.USherb.CA> <1992Dec19.233247.12469@exucom.com> <shephard.724811384@sfu.ca> Lines: 48