Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 02 Sep 2014, 06:39
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge » Multi-session live-CD/DVD
Separate Multisession iso?
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [19 Posts]   Goto page: 1, 2 Next
Author Message
Kelly
Guest


PostPosted: Tue 17 May 2005, 14:11    Post subject:  Separate Multisession iso?  

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
Back to top
Flash
Official Dog Handler


Joined: 04 May 2005
Posts: 11034
Location: Arizona USA

PostPosted: 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.
Back to top
View user's profile Send private message 
Kelly
Guest


PostPosted: Tue 17 May 2005, 18:34    Post subject: Thanks  

Thanks, I missed that page.
Back to top
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: 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.
Back to top
View user's profile Send private message Visit poster's website 
Rich

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

PostPosted: Fri 20 May 2005, 16:31    Post subject:  

BarryK wrote:

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.



I don't know about how to access the 'flag or whatever',(or If i can be classed as a clever person ) but I've just thought of a simple way to do it.

Using a small script, write the word 'Test' to the CD in a hidden file './puppytest' ( for example ). Then read the file from the cd. If it's not found then the CD can't be written to. Suppress the error message and replace with something like 'CLOSED CD'. If the file can be read successfully, delete the file, and look for it again. If the file is still there then it's an OPEN CD. If it's gone then it's OPEN and REWRITEABLE.

It's probably quite a naive way of doing it - and I apologise for that. But it wouldn't take more than a dozen lines of text to accomplish.

Rich
Back to top
View user's profile Send private message 
Flash
Official Dog Handler


Joined: 04 May 2005
Posts: 11034
Location: Arizona USA

PostPosted: 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?
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Sat 21 May 2005, 05:14    Post subject:  

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


Very early on.
The detection is supposed to happen in /etc/rc.d/rc.sysinit, the first boot script, and if it detects the cd is multisession it is then supposed to execute /etc/rc.d/rc.sysinit-cd instead id rc.sysinit. In other words, it jumps out of rc.sysinit.
Back to top
View user's profile Send private message Visit poster's website 
mmc

Joined: 19 May 2005
Posts: 1

PostPosted: Sat 21 May 2005, 23:18    Post subject: Cd multisession info  

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 ...

Quote:
.... It's written in C++ for Linux and FreeBSD but the intention is to allow it to work on other systems. The device interface works at a fairly low-level by sending ATAPI commands directly to the CDROM.


Excerpt from the docs ...

Quote:
Here's what you can do:

* Read each sector of data on the disk. You can arrange to have an md5 checksum computed and saved for each sector. Any information that can be read from the sector (such as what track it is in, the type of data, if there were any data errors, etc) is saved. Usually, the data itself (more than 600MBytes over an entire CD) is discarded.
* Find out information about the CD-ROM drive itself. Items such as does it support reading and writing CDs, the manufacturer, model numbers, etc.
* Read the table of contents for the CD. You can also construct a table of contents based on the sectors read from the disk. You can compare several the Mode 0 and Mode 2 table of contents. Finally, you can try and lookup the artist and album on the network.
* Finally, there are a number of tests that can be run. These can be repeatedly run and just work on whatever data has already been collected. For example, if no table of contents has been read, then those tests don't do anything significant. Similarly, of only a few sectors of data are read, then the tests are only for those sectors.


what say?

--
mmc
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: 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!
Back to top
View user's profile Send private message Visit poster's website 
edwin

Joined: 23 May 2005
Posts: 4

PostPosted: Mon 23 May 2005, 05:10    Post subject:  

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
Back to top
View user's profile Send private message 
FrankA

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

PostPosted: Tue 24 May 2005, 07:22    Post subject: finalized info on iso  

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

Last edited by FrankA on Wed 25 May 2005, 10:39; edited 1 time in total
Back to top
View user's profile Send private message 
Jesse

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

PostPosted: Wed 25 May 2005, 07:42    Post subject: possible solution  

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
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: 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"
Back to top
View user's profile Send private message Visit poster's website 
Guest
Guest


PostPosted: Wed 25 May 2005, 20:52    Post subject:  

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
Back to top
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: 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.
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 2 [19 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge » Multi-session live-CD/DVD
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0822s ][ Queries: 12 (0.0044s) ][ GZIP on ]