From: Hal MacArgle <haltec@kvinet.com>
To: linux-newbie@vger.kernel.org
Subject: Debian Sarge Install??
Date: Sat, 8 Apr 2006 14:13:07 -0400 [thread overview]
Message-ID: <20060408181307.GA1328@lnx2.kvinet.com> (raw)
Debian Sarge; two single layer DVD set bought on eBay.. Packed well
with very nice printed labels and both mounted and read easily with
two separate machines and DVD devices; a HP DVD-300i and Plextor
PK-708A, both relatively new and not overworked..
Tried installing, twice, on a Cyrix III/600mHz CPU; 256mB SDRAM; 8gB
freshly partitioned HD and a c.2000 BIOS.. Both trys stalled on
DVD#1, so I used the distributions "Check the CDRoms Integrity"
program and both failed at different points in the run.. Thought;
must be bad burns???
Not wanting to complain if there is another reason I tried on another
machine: Duron 1.3gHz CPU; 512mB SDRAM; freshly partitioned 12gB on a
40gB HD, this one with the Plextor PK-708A device and c.2000 BIOS...
DVD#1 passed the Integrity run but #2 failed at around 90% of the
checksum run... So no install that machine either.. I got to thinking
that I didn't want to complain to the vendor if the problem was a
single file that I would never need anyway, but how to work around
this; if possible??
Could it be that all files must be perfect to install Debian Sarge??
The vendor charged only pennies above what the blanks cost so can I
really complain?? Are single layer DVD's that critical with data??
TIA...
--
Hal - in Terra Alta, WV/US - Slackware GNU/Linux 10.1 (2.4.29)
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next reply other threads:[~2006-04-08 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 18:13 Hal MacArgle [this message]
2006-04-08 22:00 ` Debian Sarge Install?? Ray Olszewski
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=20060408181307.GA1328@lnx2.kvinet.com \
--to=haltec@kvinet.com \
--cc=linux-newbie@vger.kernel.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