Puppy Linux Discussion Forum

Kelly · Guest

Puppy release 1.0.0 had a separate iso for the multisession cd. Is this no longer necessary? Is burning the regular iso to a cd using the multisession option all that is necessary now for the 1.0.2 release?

Thanks

Flash · Posted: Tue 17 May 2005, 16:12 Post subject:

Hi Kelly.

The best answer I can give is to refer you to Barry's release notes on the News page.

Kelly · Guest

Thanks, I missed that page.

BarryK · Posted: Tue 17 May 2005, 21:05 Post subject:

Yeah, but read the bit on the News page, about how got strange effects at bootup with the "-msinfo" option of cdrecord.
That has stuffed things up a bit.

Is there a clever person who can think how to ask the inserted CD if it was burnt "closed" or "open"?
"Open" means that another track can be added.

I can't find anything in /proc with that info.
The only application I can find that determines that, is the abovementioned cdrecord.
Surely it must be possible to write a little C program that can read that info off the CD? ...because, obviously it must be there somewhere on the CD/DVD, some little flag or whatever.

...anyone reading this who thinks they might know how to tackle it, it will be greatly appreciated. This little problem is holding up the multisession project.
We need to access the drive as a plain ATAPI, ie as /dev/hdx, not use any scsi stuff.

Rich · Joined: 04 May 2005 Posts: 278 Location: Middlesbrough - UK

Flash · Posted: Fri 20 May 2005, 21:42 Post subject:

How soon in the boot process does Puppy need to know that it is booting from a multisession CD?

BarryK · Posted: Sat 21 May 2005, 05:14 Post subject:

mmc · Joined: 19 May 2005 Posts: 1

I think this might be what you are looking for (might need to cull out the portions of the code we need)

http://www.interhack.net/news/cdverity.html
src : http://www.interhack.net/projects/01media/cdverity-1.08.tgz

Excerpt from site ...

BarryK · Posted: Sun 22 May 2005, 01:31 Post subject:

Ah, now that is promising: "works at a fairly low-level by sending ATAPI commands directly to the CDROM"

I'm downloading it right now!

edwin · Joined: 23 May 2005 Posts: 4

Please see my two replies in the following regarding success with puppy-1.0.2 burned as multisession using Gcombust method from the "News Page"

http://www.murga.org/~puppy/viewtopic.php?t=223

Great Job! Smile

FrankA · Joined: 05 May 2005 Posts: 29 Location: Germany, Europe

parallel in wiki:

http://www.goosee.com/puppy/wikka/MultiSessionBoot

http://www.goosee.com/puppy/development/developer.htm and homepage

info on multisession is in the lead-in 9MB = 4500 sectors which also keeps TOC. if cd is not finalized, only then there is a pointer to the next writable address. so one can read this out in raw mode.

this way a multisession CD can be identified

Jesse · Joined: 08 May 2005 Posts: 465 Location: Auckland, NZ

Hello,

I have a very likely candidate for a solution to this problem.

It works for my computers limited environment, it correctly identifies one particular multisession cdrom I have as multisession, and a comercial stamped cd as closed, but I don't currently have a burner to make my own test cases.

It really really should work Rolling Eyes

, the program uses the linux kernel "uniform cdrom driver interface" which dates back to kernel 2.1.x. Which is why I am quite happy to post the source code in a public forum.

What I don't know:
1) is if it correctly identifies a multisession disc with only one track (one session of writing on it).

2) if a multisession disc that gets closed, is still identified as "multisession".

Can people who want to test this, have a go and post back to this thread. With either success or failure for cases #1 and #2.
If you have a problem with it, please send me the "-d" debug output from it.

Run with -h flag for info.
Puppy Binary and source code inside archive.

Jesse

BarryK · Posted: Wed 25 May 2005, 11:59 Post subject:

Jesse,
Sorry to be the bearer of bad tidings, but it isn't working for me.
Yes, it works if the CD has more than one track, but I have a multisession CD newly burned, only one track, and cdrominfo returns "Closed".

I just checked the CD with "cdrecord -msinfo dev=/dev/hdd"
and it returns "0,42579"
whereas a closed CD returns "cdrecord: Cannot read first writable address"

Guest · Guest

Hi Barry,

Here this one might do it Smile

the numbers for "singe track open multisession" that you get from cdrecord should be the same numbers that you get on this MULTI line (from debug output):
MULTI: 18008, 330701
though for single track the first number will be 0.

The reason that I don't know if its right yet is I can't find a definition of what is "multisession open".

this is from my two track open multisession cd disc:

# ./cdrominfo -d -p
CDROM INFO version 0.0.3
opening drive
get slots
found 1 slots
DriveStatus: Disc
DiscStatus: Data 1
Capabilities: closable_tray ejectable_tray lockable programmable_speed multisession Medium_Catalog_Number Media_Changed Audio_Functions resetable (has custom ioctls) (driver implements drive status) (driver implements generic packets) [drive is a DVD]
MULTI: 18008, 330701
MULTI: is XA
MULTI: addr format is LBA
TOC: 1-2
toc-e: track 1, adr 1, ctrl 4, format 1 datamode 0, LBA addr 0.
toc-e: track 2, adr 1, ctrl 4, format 1 datamode 0, LBA addr 18008.
device:/dev/cdrom|DVD|RO|1|SW_CLOSE|SW_OPEN|closed|Data|2|LBA|Multisession|

Jesse

BarryK · Posted: Thu 26 May 2005, 02:27 Post subject:

A normal closed Puppy CD returned this:
MULTI: 0, 31184
MULTI: is not XA
MULTI: addr format is LBA
TOC: 1-1

A multisession CD with only one track returned this:
MULTI: 0, 31183
MULTI: is not XA
MULTI: addr format is LBA
TOC: 1-1

...so, it remains elusive!
The solution to the problem is the error message that cdrecord returns when it determines that a CD is not multi-session. It somehow determines that beyond the first track is not writable.