From: hubby@nather.net (Markus Weber)
Subject: [TUHS] Quasijarus.Z problem
Date: Sat, 28 Feb 2004 20:08:17 -0600 [thread overview]
Message-ID: <PMEAIMBALAHKECEIMJFGEEJIMMAA.hubby@nather.net> (raw)
In-Reply-To: <0402281704.AA01091@ivan.Harhan.ORG>
> -----Original Message-----
> From: Michael Sokolov [mailto:msokolov at ivan.Harhan.ORG]
> Subject: Re: [TUHS] Quasijarus.Z problem
>
> Not sure which two do you mean, but keep in mind that the current
> release is 4.3BSD-Quasijarus0c [...]
I just updated the SIMH installation tape and pre-installed disk images to
Quasijarus0c. See www.itsecuritygeek.com, Downloads, Retrocomputing.
Markus
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.593 / Virus Database: 376 - Release Date: 2/20/2004
next prev parent reply other threads:[~2004-02-29 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 17:04 Michael Sokolov
2004-02-29 2:08 ` Markus Weber [this message]
2004-02-29 7:18 ` Wesley Parish
-- strict thread matches above, loose matches on Subject: below --
2004-02-28 10:47 Wesley Parish
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=PMEAIMBALAHKECEIMJFGEEJIMMAA.hubby@nather.net \
--to=hubby@nather.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;
as well as URLs for NNTP newsgroup(s).