[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MDK9.1 CD1 - no good burn yet



Ken & Mike,

Does adding a BS=2048 (or other reasonable value) allow you to read the CD
without errors?

WRT WiFi, this is a great technology that's not quite ready for prime time
on the Linux side of the house. For example, I have an 802.11a (54 Mbps)
card and AP from D-Link that work beautifully with That Other OS, but
D-Link stubbornly refuses to release detailed the technical information
required to create Linux drivers. When in Linux I have to downshift to
802.11b (11 Mbps) with my Orinico Gold card.  Annoying, to say the least.

--Doc

> I'm not familiar with checksumming of CD's and so forth, but I was able
> to install MDK 9.1 on my server and my laptop. It seems to have gone
> smoothly, I'm really hoping the new WiFi support will work on my laptop.
> I hope that helps. If you tell me how to run the tests, I'll try it on
> my machines. Unfortunately, it doesn't look like getting my WiFi working
> is going to be a simple task...
>
> -Ken
>
> -----Original Message-----
> From: silug-discuss-owner@silug.org
> [mailto:silug-discuss-owner@silug.org] On Behalf Of
> mike808@users.sourceforge.net
> Sent: Saturday, March 29, 2003 2:37 AM
> To: discuss@sluug.org; silug-discuss@silug.org; luci-discuss@luci.org
> Subject: MDK9.1 CD1 - no good burn yet
>
> The MDK 9.1 CD1 is 682164224 bytes (i.e. 333088 2K blocks)
> and has an MD5 checksum of 6f1581974e12420fef87868ed6caa31f.
>
> I've burned it at several speeds with some "Precision" brand (BestBuy)
> CDRs that claim to be 40x speed and to hold 700MB.
>
> When I've burned it at 24x, 12x, 8x, and 4x, I get 333088 blocks written
> reported by KonCD (with Burn-Proof enabled).
>
> But, when I read back the CD and calculate the md5sum, I don't get back
> the md5sum of the ISO.
>
> Has anyone else been able to write a verified CD1 for the new MDK 9.1?
>
> If the last 24 blocks (48K) are junk, why did they make the ISO that big
> to begin with?
>
> Mike808/
>
> Here's the details...
>> 24x burn (default block size and read until error)
>> dd: reading `/dev/cdrom': Input/output error
>> dd if=/dev/cdrom | md5sum
>> 1332248+0 records in
>> 1332248+0 records out
>> 2b18c29cea96d28ad15d2b5b68e88516  -
>>
>> 16x burn
>> dd if=/dev/cdrom bs=2048 count=333088 | md5sum
>> dd: reading `/dev/cdrom': Input/output error
>> 333062+0 records in
>> 333062+0 records out
>> 2b18c29cea96d28ad15d2b5b68e88516  -
>>
>> # 8x burn (tried sample Lite-ON 700MB CDR media)
>> dd if=/dev/cdrom bs=2048 count=333088 | md5sum
>> dd: reading `/dev/cdrom': Input/output error
>> 327304+0 records in
>> 327304+0 records out
>> 1c4e08e11f4d0fe76b4e3f540e3457d5  -
>>
>> # 4x burn
>> dd if=/dev/cdrom bs=2048 count=333088 | md5sum
>> dd: reading `/dev/cdrom': Input/output error
>> 333062+0 records in
>> 333062+0 records out
>> 2b18c29cea96d28ad15d2b5b68e88516  -




-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.