0Working with the 8-block overburn-.4

;

Working with the 8-block overburn

4



Description

DThere seems to be a problem burning CD-R's using the HP6020, and theBPhilips CDD2600 burners, and possibly others. The problem shows up@as a burned CD-R that has 8 blocks more on the platter than were?physically written. As an example, I have a container file thatCends at block 23016. After burning the CD-R, there are really 23024Eblocks on the platter. I have verified that the writer program reallyDwrote 23016 blocks, then the TOC. The extra 8 blocks contain zeroes.LThe problem reportedly has also been seen using cdrecord instead of cdwrite.2The problem also reportedly is not always present.

GUnfortunately, I have no solution for this problem at this time. I willHupdate this page if a solution is found. So for now, the only thing that*can be done is a fairly clumsy workaround.



The Workaround

There are two steps:
    6
  1. badblock the last 8 blocks of the ods-2 containter"before writing any data to it
    2. 
    
    .
    $ genrealfile :== $odstools:gen_real_file$ show dev lda4:J   -- look at total blocks, subtract 8, call this number Q, example: 23016*   -- Compute Q-8 and Q-1, use as follows:*$ genrealfile 23008 23015 badblk.sys lda4:
    
    
    "
  2. just before burn, use the FILE)utility to lop off the last 8 blocks
    3. 
    
    $ set command odstools:file0   -- Use Q-8 from the previous step as follows:.$ file /end_of_file=23008 /first_free_byte=512
    
    
    
Then burn as normal. The 8-blockFoverburn will exactly match the 8 blocks that were badblock'd, and theplatter will analyze clean.
#

Better ideas? Suggestions?

EIf you come across an explanation or a better solution, I'd very much&appreciate you dropping me some email.

4

<odsiso@tditx.com
99.07.013
© Copyright 1999, TECSys Development, Inc.