From: Antonio Vargas <wind@cocodriloo.com>
To: "Pravin Nanaware , Gurgaon" <pnanaware@ggn.hcltech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Copy protection of the floppies
Date: Tue, 25 Nov 2003 21:18:42 +0100 [thread overview]
Message-ID: <20031125201842.GC30083@wind.cocodriloo.com> (raw)
In-Reply-To: <5F0021EEA434D511BE7300D0B7B6AB530CA67677@mail2.ggn.hcltech.com>
On Tue, Nov 25, 2003 at 11:07:29AM +0530, Pravin Nanaware , Gurgaon wrote:
> Hi All,
>
> 1> Could somebody suggest me the way to protect floppy from copying it's
> contents.
> 2> If not possible, will it be possible to make the copied floppy unworkable
> (The copied floppy shouldn't work).
> For this I have constraint, I don't want to change the platform, which
> reads this floppy.
>
>
> The contents of the floppy could be anything like text file, exe file or
> encrypted file.
>
> Regards,
> Pravin.
Usual PC floppy controllers are not very flexible, so you just need
some more-flexible controller to do the trick. A popular choice
for creating master disks is to get an Amiga with an 1.44 floppy
(any A4000 will do), make some scratched disks and then duplicate
them with some fine 1990-ish hardware disk copier.
--
winden/network
1. Dado un programa, siempre tiene al menos un fallo.
2. Dadas varias lineas de codigo, siempre se pueden acortar a menos lineas.
3. Por induccion, todos los programas se pueden
reducir a una linea que no funciona.
next prev parent reply other threads:[~2003-11-25 20:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 5:37 Copy protection of the floppies Pravin Nanaware , Gurgaon
2003-11-25 9:07 ` Murray J. Root
2003-11-25 9:12 ` Måns Rullgård
2003-11-25 9:28 ` YOSHIFUJI Hideaki / 吉藤英明
2003-11-25 9:40 ` Måns Rullgård
2003-11-25 10:55 ` Matthias Andree
2003-11-25 16:07 ` Ricky Beam
2003-11-25 18:37 ` Nick
2003-11-25 20:07 ` Richard B. Johnson
2003-11-25 20:52 ` Ricky Beam
2003-11-26 3:55 ` Gene Heskett
2003-11-25 10:47 ` Helge Hafting
2003-11-25 20:18 ` Antonio Vargas [this message]
2003-11-25 20:32 ` Måns Rullgård
2003-11-26 3:58 ` Gene Heskett
2003-11-27 6:07 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031125201842.GC30083@wind.cocodriloo.com \
--to=wind@cocodriloo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pnanaware@ggn.hcltech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).