X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: "arizvi" <ahmadwaris AT hotmail DOT com>
Newsgroups: comp.os.msdos.programmer,comp.os.msdos.djgpp
Subject: Re: Creating a copy protected floppy
Date: 12 Jul 2005 18:09:13 -0700
Organization: http://groups.google.com
Lines: 38
Message-ID: <1121216953.861570.248110@g43g2000cwa.googlegroups.com>
References: <1121199731 DOT 361001 DOT 326030 AT g43g2000cwa DOT googlegroups DOT com>
   <42d445d0$1_1 AT spool9-west DOT superfeed DOT net>
NNTP-Posting-Host: 66.156.48.81
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1121216959 17498 127.0.0.1 (13 Jul 2005 01:09:19 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Wed, 13 Jul 2005 01:09:19 +0000 (UTC)
User-Agent: G2/0.2
Complaints-To: groups-abuse AT google DOT com
Injection-Info: g43g2000cwa.googlegroups.com; posting-host=66.156.48.81;
   posting-account=Se-Idg0AAAC00LEpjdiQS7ZeyWGDYpCA
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


>
> Give up.
>
> Copy protection is an extremely disgusting thing for users.
>
I quite agree, but this is one of those things which I have to do for
reasons outside my control. As a purely academic question also the
technique(s) are interesting (for me at least).
>
> But, to discuss your subject, you'd need to directly access the floppy
> controller.  You'd need to feed it the appropriate commands and bytes.
>
> You'll need to look at the specs for the floppy disk format.  There is a
> certain number of bytes required before sectors, between sectors, etc.
>
A pointer to the floppy disk format and disk controller specs will be
very helpful for me. I tried to search but could not find it. Please
send me a link if you can .. If someone has some sample code for
accessing the floppy disk controller, that would be awesome.
>
> You also have to allow for the possibility that not every floppy controller
> will read the data the same way....

Thanks for the tip. I guess I will just have to experiment on this one.
>
> Now, having said that...  Do you know how long it'll take somebody to crack
> it?
>
> Probably less time than it took you to write it.
>

I understand that the program can easily be cracked. All I am looking
for is to delay/stop the casual user of the program.

Thanks for the help!
Ahmad