From: Andrew Warkentin <andreww591@gmail.com>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: [TUHS] Re: 5ESS UNIX RTR Reference Manual - Issue 10 (2001)
Date: Tue, 11 Jun 2024 23:43:13 -0600 [thread overview]
Message-ID: <CAD-qYGoUd=7rP5bN+refyUBg+XeJXWY6-MOru1Q2Pz5H--_Hmg@mail.gmail.com> (raw)
In-Reply-To: <QgRYSpCpQYi1JqaoiGEk2F0XR9AXTs6Ka4e4IgRZDBMtUBmOXBsgcrGyR5_PwU5uCQb2OQAq3ZnAnpNzn9Jd6mYBgDuK85LREdgrOS6W6es=@protonmail.com>
On Tue, Jun 11, 2024 at 9:41 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
>
> What would you suggest? My main point of reference is years and years of being in the console video game scene, bin/cue is the most accessible of the high fidelity formats I've seen for things, compared with say cdi and mdf/mds. Does a plain old iso suffice for all relevant data from the media? Frankly I've never done dumps on a UNIXy computer with an optical drive, only Windows boxen, so can't say I'm hip to the sort of disc image you get doing a dd from an optical /dev entry, maybe I just need to get a UNIX of some kind on my old beater game machine with an optical drive to do these dumps going forward.
>
The vast majority of non-game software was distributed on discs that
were formatted with a single data track and no special formatting.
These can be safely imaged in flat (ISO) format. The main reason to
use the lower-level formats is for discs with disc-based copy
protection or multiple tracks (usually one data track and multiple
audio tracks), both of which are very uncommon for non-game software.
BeOS install CDs are the one exception I can think of; these have an
ISO-format boot track followed by one or two BFS-format system tracks
(separate system tracks are used for x86 and PPC), although even these
aren't actually dependent on multiple tracks and can be run from a CD
with just the system track if a boot floppy is used.
Most dumping programs should be able to show you how the discs are
formatted; if they only have a single track each, ISO format should be
sufficient.
next prev parent reply other threads:[~2024-06-12 5:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 6:06 [TUHS] " segaloco via TUHS
2024-06-11 6:59 ` [TUHS] " Kevin Bowling
2024-06-12 1:37 ` Jim Carpenter
2024-06-12 3:34 ` segaloco via TUHS
2024-06-12 5:43 ` Andrew Warkentin [this message]
2024-06-12 7:01 ` Wesley Parish
2024-06-12 8:12 ` Ralph Corderoy
2024-06-12 8:41 ` Arno Griffioen via TUHS
2024-06-12 16:30 ` segaloco via TUHS
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='CAD-qYGoUd=7rP5bN+refyUBg+XeJXWY6-MOru1Q2Pz5H--_Hmg@mail.gmail.com' \
--to=andreww591@gmail.com \
--cc=tuhs@tuhs.org \
/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).