From: Jim Hartley <xjimh@worldnet.att.net>
To: linux-msdos@vger.kernel.org
Subject: Re: your mail
Date: Sat, 05 Jul 2003 23:06:16 -0500 [thread overview]
Message-ID: <3F07A038.8080608@worldnet.att.net> (raw)
In-Reply-To: <1057435822.2023.49.camel@tamriel.terranforge.com>
DOS 7.10? I guess that's one of those "M$-hidden-under-Windoze-DOS"
versions? It gets confusing, since M$ used 7.x for those, while there is
also an IBM PC-DOS 7.0 which is a "real" DOS and that's the one I always
think of when DOS 7 is mentioned. That one is my favorite, I still have
copies around, especially in the form of quick-boot utility diskettes. I
guess one reason I like it is because I got it LEGALLY for free - a
reward for participating in the Beta test. (Then again, those who know
me know I will go to great lengths to avoid using ANY Micro$quish products.)
Jim Hartley
Lyvim Xaphir wrote:
>I agree with Jim Hartley. This is pretty much a nonissue. Dos isn't
>even supported by M$ any more as far as I know, and I've never heard of
>any case where M$ has gone after an individual for such a thing in the
>past anyway. Their only concern are large scale pirates selling on the
>black market or corporations doing *current* release software on a
>significant basis. They pretty much leave the individuals alone.
>
>And I don't think anyone will ever mistake this place as a site for
>swapping of illegal software. This isn't anywhere near that class and
>to suggest that it might be is kind of edging over into the pinhead
>arena.
>
>On another note, if I was going to share a copy of Dos it would be
>version 7.10 because of it's superior memory management and stability.
>7.10 was partially a response in 98 to gamer's claims of
>incompatibilities in winblows with some of the more sophisticated Dos
>games like Elder Scrolls Arena, Duke Nukem 3d and others. It was the
>last best version of Dos.
>
>
>On Sat, 2003-07-05 at 10:53, Ged Haywood wrote:
>
>
>>Hi there,
>>
>>On Sat, 5 Jul 2003, Jim Hartley wrote:
>>
>>
>>
>>>I think this one is WAY, WAY under the radar.
>>>
>>>
>>I'd agree if this weren't a public mailing list.
>>
>>I'm more concerned with the reputation of the list. If it earns a
>>reputation as a place for swapping pirate copies of software, that
>>might not be a Good Thing.
>>
>>There has to be a way for the guy to get what he wants done without
>>broadcasting a technical infringement of a copyright owned by a ten
>>billion dollar potential adversary.
>>
>>73,
>>Ged.
>>
>>
>
>--LX
>
>
>
next prev parent reply other threads:[~2003-07-06 4:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 11:51 some problems (1.1.5 and 1.1.4) Will Styles
2003-06-30 17:39 ` Justin Zygmont
2003-07-01 10:19 ` Will Styles
2003-07-01 11:16 ` Bart Oldeman
2003-07-01 22:49 ` Justin Zygmont
2003-07-04 3:32 ` Justin Zygmont
2003-07-04 18:10 ` (unknown) Darryl Perry
2003-07-04 18:21 ` your mail Ged Haywood
2003-07-05 14:48 ` Jim Hartley
2003-07-05 14:53 ` Ged Haywood
[not found] ` <1057435822.2023.49.camel@tamriel.terranforge.com>
2003-07-06 4:06 ` Jim Hartley [this message]
2003-07-06 11:20 ` Jochen Reinwand
2003-07-06 11:56 ` Ged Haywood
2003-07-06 16:26 ` Jochen Reinwand
2003-07-06 19:03 ` Eemeli Kantola
2003-07-06 23:10 ` Jochen Reinwand
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=3F07A038.8080608@worldnet.att.net \
--to=xjimh@worldnet.att.net \
--cc=linux-msdos@vger.kernel.org \
--cc=linuxjim@programmer.net \
/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