Reading and writing via ASPI

vbimport

#1

Hi,

I’ve got a few questions regarding the CD reading/writing via ASPI, hope you’ll enlighten me :wink:

  1. I’ve been using SFF-8020i as an ATAPI CD-ROM instructions reference for some time now, but this document is a little bit dated (it originates back in 1996) and of course doesn’t contain any cd writing instructions - that is why I’m looking for some other resource. I suspect such command set is located somewhere on http://www.t13.org or http://www.t10.org but unfortunately there are so many other standards on these sites, that I was unable to find what I was looking for. Most importantly, I’d like to know how to perform a block write - a counterpart of READ instructions.
  2. A few years ago Adaptec released an ASPI SDK for free. Later the SDK disappeared from the site only to be replaced after some time with a driver pack containing parts of the SDK. So the SDK remains free and you can use it in your projects - provided you have it :wink: Do you know of any place where I could get the SDK? Or maybe some of you still have it in your archives? In addition if you know of any other ASPI drivers which are distributed as a statically linked library (lib, not dll) I’d appreciate some names and links.
  3. I’d like to play a little bit with TOC, but unfortunately the information about it is so scarce that I’m not even sure where TOC is located. I’ve read somewhere that TOC has it’s copy 13 seconds or so from the lead-in of the CD, which is later copied to it’s real location. Still, no idea how to read or write it. I guess Clone can alter the TOC, but I haven’t managed to change much when tinkering with ccd file - the file format has no documentation, so it’s hard to do anything advanced with it.

thanks :bow: :wink:
SM


#2
  1. Look on http://www.cdrlabs.com/articles/ there you can find something

2.Use google, i was also looking for it recently :stuck_out_tongue:

3.Sorry can’t help


#3

Believe it or not, I had looked up both the Labs and Google before posting here, but couldn’t find anything. But when you had suggested doing these simple steps, the results popped out in a minute :o Quite embarrassing, to say the least :wink:
I just wait for someone to post an answer to the 3rd question - “The answer is on the main page of Google, stupid!” :bigsmile:

Thanks for your help :bow: :wink:


#4
  1. Go to ftp://ftp.t10.org/t10/drafts/ and get all mmc*, sbc*, spc* docs.
    The corresponding blocks commands are READ(10), READ(12), etc see sbc*.pdf

  2. try http://www.zianet.com/jgray/dat/files/ASPISDK.exe

  3. The TOC is stored in the lead-in, but it is indeed first stored in
    a temporary location (PMA) before being copied there during finalization
    (except in DAO mode). I could explain you the TOC structure, but I doubt
    you really need it now (and I’m a bit lazy to do so to be honest :)).
    I suggest you play first a bit with the READ_TOC command and maybe
    cue sheets, then ask again if you need details. Also CCD file format
    is very straightforward, just look at the file in some hex editor
    and at the same time in cdmage, and all will be clear. If you need
    help for strange burning experiments, Truman is our specialist :slight_smile:


#5

[B]1. Go to ftp://ftp.t10.org/t10/drafts/ and get all mmc*, sbc*, spc* docs.
The corresponding blocks commands are READ(10), READ(12), etc see sbc*.pdf

It’s a true jungle of pdfs out there :wink:

  1. try http://www.zianet.com/jgray/dat/files/ASPISDK.exe

Thanks. Anyway, I thought that the SDK contained a statically linked library (a lib file) - that’s at least what I could deduce from the manual, but it differs from the recent driver package only in some included examples. Any idea if there is such a statically linked library somewhere to get?

  1. The TOC is stored in the lead-in, but it is indeed first stored in
    a temporary location (PMA) before being copied there during finalization
    (except in DAO mode). I could explain you the TOC structure, but I doubt
    you really need it now (and I’m a bit lazy to do so to be honest :)).

:bigsmile: I’ll delve into the mage & the .ccd and see if I can get any results.


#6

When you read the Ecma 130 document you will see a lot of abreviations which Clonecd also uses in its .ccd file.


#7

Why would you want to use a statically linked aspi layer? :slight_smile:
If you want to do something funky, use SPTI :smiley: