[Libburn] libisofs issues

[Derek Foreman]

I'm confused as to what does and does not work.

libisofs is creating a broken iso image, but libburn is capable of 
burning an mkisofs created iso image to make a functional cd?

If that's the case, it would be quite useful to use libisofs to create an 
iso on an x86 machine, and another on a PPC (exact same files, in same 
order, with same options, etc etc), and compare the two.

On Sat, 25 Sep 2004, Bryan Forbes wrote:

> No, it doesn't work.
>
> On Sat, 2004-09-25 at 00:17 -0500, Derek Foreman wrote:
>> On Tue, 21 Sep 2004, Bryan Forbes wrote:
>>
>>> Alright, burning an iso from disk works on PPC.  Creating the iso's on
>>> the fly is another problem.  Attached is a test program adapted from
>>> burniso.c in the test directory.  I have also attached the test text
>>> files I use with this test file (you'll have to change the paths to the
>>> files in the source).  Here is the output of the program running for me:
>>>
>>> bryan at mxpxppc:~/Projects/tests/test-libburn$ ./isoburn-c
>>> Initializing library...Success
>>> Scanning for devices...Done
>>> /
>>>  TEST1.TXT;1
>>>  TEST2.TXT;1
>>>  TEST3.TXT;1
>>> ignored nwa: 0
>>>
>>> ctladr|trno|indx|form|scms|  msf
>>> ------+----+----+----+----+--------
>>> 4  1 | 00 | 00 | 01 | 00 |00:00:00
>>> 4  1 | 01 | 00 | 10 | 00 |00:00:00
>>> 4  1 | 01 | 01 | 10 | 00 |00:02:00
>>> 4  1 | AA | 01 | 01 | 00 |00:02:1D
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>> S: 0/1 T: 0/1 L: -26: 5/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: -26: 29/29
>>> S: 0/1 T: 0/1 L: 0: 0/0
>>>
>>> As you can see, it writes the 0's that should be put at the end of the
>>> disc at the front of the disc.  Does this happen on x86?  Thanks in
>>> advance!
>>
>> Nah the first pile of 0s are when it's writing the lead in.
>>
>> Does the disc work?
> -- 
> ======================================================================
> Bryan Forbes
> bryan at reigndropsfall.net
> http://www.reigndropsfall.net
>
> "It does not take a majority to prevail, but rather an irate, tireless
> minority keen to set brush fires in people's minds."
>        - Samuel Adams, an architect of the Constitution
>
> Key fingerprint = 3D7D B728 713A BB7B B8B1  5B61 3888 17E0 70CA 0F3D
>