Hi Paul!
* Paul R Culmo writes:
I've been having some issues with CDrecord and cd burning in general
with cdrecord and redhat 7.3 with the 2.4.19 kernel but it happens with
the 2.4.18-3 kernel too.
I have a HP CD-RW 24x10x40 and when burning at speeds higher than 8x the
following error shows up
On Tue, 17 Sep 2002, Frederick Page wrote:
make[1]: Entering directory `/usr/local/src/cdrdao-1.1.6/utils'
toc2mp3.cc: In function `class string clean_string(string )':
toc2mp3.cc:426: no matching function for call to
`basic_stringchar,string_char_traitschar,__default_alloc_templatetrue,0
On Thu, Sep 19, 2002 at 12:33:08PM +0100, James Pearson wrote:
I'm trying to create DVD-sized powerpc ISO images of Debian Woody. For
thes to be bootable, they need to be HFS hybrid disks.
What is the total size of your input data? - although the output size will
most probably be a lot larger
On Thu, Sep 19, 2002 at 09:35:53PM -0500, Chris Lawrence wrote:
On Sep 19, James Pearson wrote:
However, there are probably limits in my code (and/or libhfs) that means
2Gb is the maximum.
Indeed; I encountered a similar problem building PowerPC DVDs and
found that it misbehaved due to the 2
[EMAIL PROTECTED] (Chris Lawrence) quoted and then wrote:
On Sep 19, James Pearson wrote:
However, there are probably limits in my code (and/or libhfs) that means
2Gb is the maximum.
Indeed; I encountered a similar problem building PowerPC DVDs and
found that it misbehaved due to the 2 GB
From: [EMAIL PROTECTED]
[EMAIL PROTECTED] (Chris Lawrence) quoted and then wrote:
On Sep 19, James Pearson wrote:
However, there are probably limits in my code (and/or libhfs) that means
2Gb is the maximum.
Indeed; I encountered a similar problem building PowerPC DVDs and
found that it
On Fri, Sep 20, 2002 at 02:29:02PM +0100, James Pearson wrote:
What is the total size of your input data? - although the output size will
most probably be a lot larger ...
Just over 4GB, ~8900 files
I would suspect anything over 2Gb will be problematic ...
The allocation block size is 64Kb as
I've worked around it by building -apple instead of -hfs images, but
it's hardly an ideal fix :-/
Imagine I'm completely ignorant of Mac / HFS issues (not difficult) -
what's the difference?
The -hfs option creates an HFS hybrid CD image.
The -apple option adds the Apple Extensions to the
I will attempt to see if I can sort out any 32-bit overflows that will
cause problems between 2Gb and 4Gb, but I guess going over 4Gb will require
major surgery ...
Yes, I can see that. Would it be possible / feasible to make the
hfs-hiding options allow 4GB sizes? The bits on the disk that we
9 matches
Mail list logo
