burncd block size
slave-mike at rv1.dynip.com
Fri Nov 7 21:05:30 PST 2003
Does this *fix* atapicam?
Or is atapicam still only about 50% operational?
I can't get atapicam to work with my atapi tape drive at all.
And power calibrations malfunction via atapicam with cdrdao and cdrecord.
And if I blank a cd-rw, the atapicam'ed programs return after like 2S,
*THEN* it seems the commands make it to the cd burner and *THEN* it
Soren Schmidt wrote:
> It seems Jeremy Messenger wrote:
>>On Fri, 07 Nov 2003 10:10:40 +0100, Dag-Erling Smørgrav <des at des.no> wrote:
>>>I've been having a variety of problems burning CDs with atang:
>>> - burncd consistently failing in exactly the same spot in the ISO,
>>> and reporting "only wrote 0 of 32768 bytes: Unknown error: 0"
>>> - burncd failing right at the start with "only wrote -1 of 32768
>>> bytes: Input/output error" (this generally happens after a couple
>>> of the previous, and once it starts happening I have to reboot)
>>Whew, glad that I am not only one.. I *just* have wasted two of my blank
>>CD in like fifteen minutes ago, I keep wondering if I created the ISO
>>files in the wrong way or was it burncd's fault.. Until now here..
> This is fallout from getting atapi-cd under GEOM. GEOM wasn't designed
> to handle medias of size 0 and where the sizes can change during an
> open. I just committed a fix that has solved the issue here (and its ugly).
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current