Discussion:
RJS CD/DVD writer problem
(too old to reply)
Barry Landy
2016-03-02 11:15:17 UTC
Permalink
Inspired by the previous correspondence I am tempted to ask the
following.

When I changed hardware (2012!) I found that RSJ no longer worked
properly. No problem reading CDs; no problem creating the writable
drive; no problem writing data to the drive. However, whenever I tried
to finalize I merely got a series of reported writing errors in the log.

Basically I gave up and now do all my CD/DVD writing under windows.

The previous correspondence made me think it might well be due to the
cddrv.inf file (which, not surprisingly, is a decade out of date).

I installed and used cdrecord to find the SCSI data:
0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM

I used that to add to cddrv.inf

Brand Recorder FW SCSI-ID Compatible-ID Driver SyncTrans DAO-Mode RegKey
Dummy "dummy" N/A "dummy dummy" N/A cdatapi ATAPI CUESHEET N/A

TSSTcorp "CDDVDW SH-222AB" N/A "TSTcorp SB00" N/A cdatapi ATAPI CUESHEET N/A

(I tried both before and after he dummy line)

Basically no difference.

The RSJ related items in config.sys are

==================

REM [RSJ section
IFS=r:\CDWFS\CDWFS.IFS
RUN=r:\CDWFS\CDWFSD.EXE -p "R:/var/temp" -c20000 -b2048 -t2 -i3 -s0

REM *** RSJ CD-Writer File System ***


BASEDEV=OS2ASPI.DMD
BASEDEV=LOCKCDR.FLT /Q /D

DEVICE=r:\CDWFS\RSJSCSI.SYS

======================

and I have tried with and without the last three items and still get no
joy when finalizing

Any ideas welcomed - especially if the entry in the .inf file is wrong.
--
Barry Landy Email: Remove nospam in from address
192, Gilbert Road, Cambridge CB4 3PB
Andi B.
2016-03-02 11:34:38 UTC
Permalink
Post by Barry Landy
0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
I used that to add to cddrv.inf
Brand Recorder FW SCSI-ID Compatible-ID Driver SyncTrans DAO-Mode RegKey
Dummy "dummy" N/A "dummy dummy" N/A cdatapi ATAPI CUESHEET N/A
TSSTcorp "CDDVDW SH-222AB" N/A "TSTcorp SB00" N/A cdatapi ATAPI CUESHEET N/A
Isn't 'CDDVDW SH-222AB ' the correct SCSI-ID of your drive?

Did you check in the attach dialog the "Erkennen" button? No clue how
the button is called in the English version. It't the one at right of
the drive letter of the CD-ROM. The upper one, not right of the letter
you want to assign. Sometimes after clicking this button RSJ detects the
burner and shows the correct sting in the pop up.

Regards,
Barry Landy
2016-03-02 12:33:36 UTC
Permalink
On Wed, 2 Mar 2016, Andi B. wrote:

:>Barry Landy schrieb:
:>> I installed and used cdrecord to find the SCSI data:
:>> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>>
:>> I used that to add to cddrv.inf
:>>
:>> Brand Recorder FW SCSI-ID Compatible-ID Driver SyncTrans DAO-Mode RegKey
:>> Dummy "dummy" N/A "dummy dummy" N/A cdatapi ATAPI CUESHEET N/A
:>>
:>> TSSTcorp "CDDVDW SH-222AB" N/A "TSTcorp SB00" N/A cdatapi ATAPI CUESHEET N/A
:>
:>Isn't 'CDDVDW SH-222AB ' the correct SCSI-ID of your drive?
:>
:>Did you check in the attach dialog the "Erkennen" button? No clue how
:>the button is called in the English version. It't the one at right of
:>the drive letter of the CD-ROM. The upper one, not right of the letter
:>you want to assign. Sometimes after clicking this button RSJ detects the
:>burner and shows the correct sting in the pop up.
:>
:>Regards,
:>

The upper button is called "Detect" and the lower one "attach"

the detect button shows the same string TSSTcorp CDDVDW SH-222AB (ATAPI)
--
Barry Landy Email: Remove nospam in from address
192, Gilbert Road, Cambridge CB4 3PB
Pete
2016-03-02 15:54:14 UTC
Permalink
Hi Barry
Inspired by the previous correspondence I am tempted to ask the following.
When I changed hardware (2012!) I found that RSJ no longer worked
properly. No problem reading CDs; no problem creating the writable
drive; no problem writing data to the drive. However, whenever I tried
to finalize I merely got a series of reported writing errors in the log.
It might be an idea to post some of those errors as they might show
problems other than the below. It is a little unusual to be able to
write to disc but not Finalise.
Basically I gave up and now do all my CD/DVD writing under windows.
There are a few other apps that write CD/DVD that you might want to try:
cdrecord(2), dvddao, cdrtools, DVDToys
The previous correspondence made me think it might well be due to the
cddrv.inf file (which, not surprisingly, is a decade out of date).
0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
I used that to add to cddrv.inf
Brand Recorder FW SCSI-ID
Compatible-ID Driver SyncTrans DAO-Mode RegKey
Dummy "dummy" N/A "dummy dummy"
N/A cdatapi ATAPI CUESHEET N/A
TSSTcorp "CDDVDW SH-222AB" N/A "TSTcorp SB00"
N/A cdatapi ATAPI CUESHEET N/A
(I tried both before and after he dummy line)
Basically no difference.
The RSJ related items in config.sys are
==================
REM [RSJ section
IFS=r:\CDWFS\CDWFS.IFS
RUN=r:\CDWFS\CDWFSD.EXE -p "R:/var/temp" -c20000 -b2048 -t2 -i3 -s0
REM *** RSJ CD-Writer File System ***
BASEDEV=OS2ASPI.DMD
BASEDEV=LOCKCDR.FLT /Q /D
DEVICE=r:\CDWFS\RSJSCSI.SYS
======================
and I have tried with and without the last three items and still get no
joy when finalizing
Any ideas welcomed - especially if the entry in the .inf file is wrong.
Does LOCKCDR.FLT have /Q /D parameters? - I have 5.05 and do not see
those parameters listed.

The cdrecord line
0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
should end up similar to this in cddrv.inf
TSSTcorp "CDDVDW SH-222AB " "SB00" "CDDVDW SH-222AB "
N/A cdatapi ATAPI CUESHEET N/A
or possibly
TSSTcorp "CDDVDW SH-222AB " "SB00" "TSTcorpCDDVDW SH-222AB "
N/A cdatapi ATAPI CUESHEET N/A


Some of my burners have needed the Brand+Model and some have only needed
the Model in the column called SCSI-ID

Note the inclusion of any spaces involved within the quotes and the
position of the firmware level.


Alternatively try adding the burner to lockcdr.flt at boot:-

BASEDEV=LOCKCDR.FLT -I "CDDVDW SH-222AB "
or possibly
BASEDEV=LOCKCDR.FLT -I "TSTcorpCDDVDW SH-222AB "

Yet again note the inclusion of the space within the quotes.


Hope the above helps.

Pete
Lars Erdmann
2016-03-02 17:19:02 UTC
Permalink
On 02.03.16 16.54, Pete wrote:> Hi Barry
Post by Pete
The cdrecord line
0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
should end up similar to this in cddrv.inf
TSSTcorp "CDDVDW SH-222AB " "SB00" "CDDVDW SH-222AB "
N/A cdatapi ATAPI CUESHEET N/A
or possibly
TSSTcorp "CDDVDW SH-222AB " "SB00" "TSTcorpCDDVDW SH-222AB "
N/A cdatapi ATAPI CUESHEET N/A
Some of my burners have needed the Brand+Model and some have only needed
the Model in the column called SCSI-ID
Note the inclusion of any spaces involved within the quotes and the
position of the firmware level.
I think the SCSI ID in cddrv.inf is always the 8 byte Vendorstring with
the 16 byte device string concatenated. Therefore:

"TSSTcorpCDDVDW SH-222AB "

should be the correct string. Once that is specified LOCKCDR.FLT is no
longer needed anyways.
Post by Pete
Alternatively try adding the burner to lockcdr.flt at boot:-
BASEDEV=LOCKCDR.FLT -I "CDDVDW SH-222AB "
or possibly
BASEDEV=LOCKCDR.FLT -I "TSTcorpCDDVDW SH-222AB "
Yet again note the inclusion of the space within the quotes.
Very true. IF lockcdr.flt is used AND the drive is not detected then
it's basically inevitable to use the -I parameter to specify the SCSI ID
on the command line.

The biggest problem: I have the very same burner (funny enough) and I
could not get it to work. For me, the problem turned out to be the usage
of OS2AHCI.ADD instead of DANIS506.ADD and I only have one adapter and
therefore I cannot use both drivers (one driver for one adapter with the
hard disk attached and the other driver for the other adapter with the
CD-Writer attached).


Lars
Barry Landy
2016-03-02 22:28:10 UTC
Permalink
On Wed, 2 Mar 2016, Pete wrote:

:>Hi Barry
:>
:>Barry Landy wrote:
:>> Inspired by the previous correspondence I am tempted to ask the following.
:>>
:>> When I changed hardware (2012!) I found that RSJ no longer worked
:>> properly. No problem reading CDs; no problem creating the writable
:>> drive; no problem writing data to the drive. However, whenever I tried
:>> to finalize I merely got a series of reported writing errors in the log.
:>>
:>
:>
:>It might be an idea to post some of those errors as they might show problems
:>other than the below. It is a little unusual to be able to write to disc but
:>not Finalise.
:>
:>
:>> Basically I gave up and now do all my CD/DVD writing under windows.
:>>
:>
:>
:>There are a few other apps that write CD/DVD that you might want to try:
:>cdrecord(2), dvddao, cdrtools, DVDToys
:>
:>
:>> The previous correspondence made me think it might well be due to the
:>> cddrv.inf file (which, not surprisingly, is a decade out of date).
:>>
:>> I installed and used cdrecord to find the SCSI data:
:>> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>>
:>> I used that to add to cddrv.inf
:>>
:>> Brand Recorder FW SCSI-ID
:>> Compatible-ID Driver SyncTrans DAO-Mode RegKey
:>> Dummy "dummy" N/A "dummy dummy"
:>> N/A cdatapi ATAPI CUESHEET N/A
:>>
:>> TSSTcorp "CDDVDW SH-222AB" N/A "TSTcorp SB00"
:>> N/A cdatapi ATAPI CUESHEET N/A
:>>
:>> (I tried both before and after he dummy line)
:>>
:>> Basically no difference.
:>>
:>> The RSJ related items in config.sys are
:>>
:>> ==================
:>>
:>> REM [RSJ section
:>> IFS=r:\CDWFS\CDWFS.IFS
:>> RUN=r:\CDWFS\CDWFSD.EXE -p "R:/var/temp" -c20000 -b2048 -t2 -i3 -s0
:>>
:>> REM *** RSJ CD-Writer File System ***
:>>
:>>
:>> BASEDEV=OS2ASPI.DMD
:>> BASEDEV=LOCKCDR.FLT /Q /D
:>>
:>> DEVICE=r:\CDWFS\RSJSCSI.SYS
:>>
:>> ======================
:>>
:>> and I have tried with and without the last three items and still get no
:>> joy when finalizing
:>>
:>> Any ideas welcomed - especially if the entry in the .inf file is wrong.
:>>
:>
:>
:>
:>Does LOCKCDR.FLT have /Q /D parameters? - I have 5.05 and do not see those
:>parameters listed.
:>
:>The cdrecord line
:> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>should end up similar to this in cddrv.inf
:>TSSTcorp "CDDVDW SH-222AB " "SB00" "CDDVDW SH-222AB " N/A
:>cdatapi ATAPI CUESHEET N/A
:>or possibly
:>TSSTcorp "CDDVDW SH-222AB " "SB00" "TSTcorpCDDVDW SH-222AB " N/A
:>cdatapi ATAPI CUESHEET N/A
:>
:>
:>Some of my burners have needed the Brand+Model and some have only needed the
:>Model in the column called SCSI-ID
:>
:>Note the inclusion of any spaces involved within the quotes and the position
:>of the firmware level.
:>
:>
:>Alternatively try adding the burner to lockcdr.flt at boot:-
:>
:>BASEDEV=LOCKCDR.FLT -I "CDDVDW SH-222AB "
:>or possibly
:>BASEDEV=LOCKCDR.FLT -I "TSTcorpCDDVDW SH-222AB "
:>
:>Yet again note the inclusion of the space within the quotes.
:>
:>
:>Hope the above helps.
:>
:>Pete
:>
:>

Here is the last error log I got earlier today

*** Error no 152 at 02.03.2016 12:36:27
**************************************

Command: Write(24063, 30)
Sense key: Illegal Request
Adl. sense key: Invalid block address

Sense buffer:
00000000 70 00 05 00 00 00 00 00-00 00 00 00 21 02 00 00
p...........!...
00000010 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
................
00000020 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
................

(and they are all the same with different block addresses)
--
Barry Landy Email: Remove nospam in from address
192, Gilbert Road, Cambridge CB4 3PB
Pete
2016-03-03 15:23:01 UTC
Permalink
Hi Barry

Following Lars post I can only ask what drivers are in use: os2ahci or
danis506?


Regards

Pete
Post by Barry Landy
:>Hi Barry
:>
:>> Inspired by the previous correspondence I am tempted to ask the following.
:>>
:>> When I changed hardware (2012!) I found that RSJ no longer worked
:>> properly. No problem reading CDs; no problem creating the writable
:>> drive; no problem writing data to the drive. However, whenever I tried
:>> to finalize I merely got a series of reported writing errors in the log.
:>>
:>
:>
:>It might be an idea to post some of those errors as they might show problems
:>other than the below. It is a little unusual to be able to write to disc but
:>not Finalise.
:>
:>
:>> Basically I gave up and now do all my CD/DVD writing under windows.
:>>
:>
:>
:>cdrecord(2), dvddao, cdrtools, DVDToys
:>
:>
:>> The previous correspondence made me think it might well be due to the
:>> cddrv.inf file (which, not surprisingly, is a decade out of date).
:>>
:>> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>>
:>> I used that to add to cddrv.inf
:>>
:>> Brand Recorder FW SCSI-ID
:>> Compatible-ID Driver SyncTrans DAO-Mode RegKey
:>> Dummy "dummy" N/A "dummy dummy"
:>> N/A cdatapi ATAPI CUESHEET N/A
:>>
:>> TSSTcorp "CDDVDW SH-222AB" N/A "TSTcorp SB00"
:>> N/A cdatapi ATAPI CUESHEET N/A
:>>
:>> (I tried both before and after he dummy line)
:>>
:>> Basically no difference.
:>>
:>> The RSJ related items in config.sys are
:>>
:>> ==================
:>>
:>> REM [RSJ section
:>> IFS=r:\CDWFS\CDWFS.IFS
:>> RUN=r:\CDWFS\CDWFSD.EXE -p "R:/var/temp" -c20000 -b2048 -t2 -i3 -s0
:>>
:>> REM *** RSJ CD-Writer File System ***
:>>
:>>
:>> BASEDEV=OS2ASPI.DMD
:>> BASEDEV=LOCKCDR.FLT /Q /D
:>>
:>> DEVICE=r:\CDWFS\RSJSCSI.SYS
:>>
:>> ======================
:>>
:>> and I have tried with and without the last three items and still get no
:>> joy when finalizing
:>>
:>> Any ideas welcomed - especially if the entry in the .inf file is wrong.
:>>
:>
:>
:>
:>Does LOCKCDR.FLT have /Q /D parameters? - I have 5.05 and do not see those
:>parameters listed.
:>
:>The cdrecord line
:> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>should end up similar to this in cddrv.inf
:>TSSTcorp "CDDVDW SH-222AB " "SB00" "CDDVDW SH-222AB " N/A
:>cdatapi ATAPI CUESHEET N/A
:>or possibly
:>TSSTcorp "CDDVDW SH-222AB " "SB00" "TSTcorpCDDVDW SH-222AB " N/A
:>cdatapi ATAPI CUESHEET N/A
:>
:>
:>Some of my burners have needed the Brand+Model and some have only needed the
:>Model in the column called SCSI-ID
:>
:>Note the inclusion of any spaces involved within the quotes and the position
:>of the firmware level.
:>
:>
:>Alternatively try adding the burner to lockcdr.flt at boot:-
:>
:>BASEDEV=LOCKCDR.FLT -I "CDDVDW SH-222AB "
:>or possibly
:>BASEDEV=LOCKCDR.FLT -I "TSTcorpCDDVDW SH-222AB "
:>
:>Yet again note the inclusion of the space within the quotes.
:>
:>
:>Hope the above helps.
:>
:>Pete
:>
:>
Here is the last error log I got earlier today
*** Error no 152 at 02.03.2016 12:36:27
**************************************
Command: Write(24063, 30)
Sense key: Illegal Request
Adl. sense key: Invalid block address
00000000 70 00 05 00 00 00 00 00-00 00 00 00 21 02 00 00
p...........!...
00000010 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
................
00000020 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
................
(and they are all the same with different block addresses)
Barry Landy
2016-03-03 16:29:00 UTC
Permalink
On Thu, 3 Mar 2016, Pete wrote:

:>Hi Barry
:>
:>Following Lars post I can only ask what drivers are in use: os2ahci or
:>danis506?
:>

Both are in config.sys. Looking at the output (ibms506$ and atapi$) it
looks as though Dani software has claimed them.

AHCI claims the HDDs (actually SSDs)

:>
:>Regards
:>
:>Pete
:>
:>
:>
:>Barry Landy wrote:
:>> On Wed, 2 Mar 2016, Pete wrote:
:>>
:>> :>Hi Barry
:>> :>
:>> :>Barry Landy wrote:
:>> :>> Inspired by the previous correspondence I am tempted to ask the
:>> following.
:>> :>>
:>> :>> When I changed hardware (2012!) I found that RSJ no longer worked
:>> :>> properly. No problem reading CDs; no problem creating the writable
:>> :>> drive; no problem writing data to the drive. However, whenever I tried
:>> :>> to finalize I merely got a series of reported writing errors in the log.
:>> :>>
:>> :>
:>> :>
:>> :>It might be an idea to post some of those errors as they might show
:>> problems
:>> :>other than the below. It is a little unusual to be able to write to disc
:>> but
:>> :>not Finalise.
:>> :>
:>> :>
:>> :>> Basically I gave up and now do all my CD/DVD writing under windows.
:>> :>>
:>> :>
:>> :>
:>> :>There are a few other apps that write CD/DVD that you might want to try:
:>> :>cdrecord(2), dvddao, cdrtools, DVDToys
:>> :>
:>> :>
:>> :>> The previous correspondence made me think it might well be due to the
:>> :>> cddrv.inf file (which, not surprisingly, is a decade out of date).
:>> :>>
:>> :>> I installed and used cdrecord to find the SCSI data:
:>> :>> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>> :>>
:>> :>> I used that to add to cddrv.inf
:>> :>>
:>> :>> Brand Recorder FW SCSI-ID
:>> :>> Compatible-ID Driver SyncTrans DAO-Mode RegKey
:>> :>> Dummy "dummy" N/A "dummy dummy"
:>> :>> N/A cdatapi ATAPI CUESHEET N/A
:>> :>>
:>> :>> TSSTcorp "CDDVDW SH-222AB" N/A "TSTcorp SB00"
:>> :>> N/A cdatapi ATAPI CUESHEET N/A
:>> :>>
:>> :>> (I tried both before and after he dummy line)
:>> :>>
:>> :>> Basically no difference.
:>> :>>
:>> :>> The RSJ related items in config.sys are
:>> :>>
:>> :>> ==================
:>> :>>
:>> :>> REM [RSJ section
:>> :>> IFS=r:\CDWFS\CDWFS.IFS
:>> :>> RUN=r:\CDWFS\CDWFSD.EXE -p "R:/var/temp" -c20000 -b2048 -t2 -i3 -s0
:>> :>>
:>> :>> REM *** RSJ CD-Writer File System ***
:>> :>>
:>> :>>
:>> :>> BASEDEV=OS2ASPI.DMD
:>> :>> BASEDEV=LOCKCDR.FLT /Q /D
:>> :>>
:>> :>> DEVICE=r:\CDWFS\RSJSCSI.SYS
:>> :>>
:>> :>> ======================
:>> :>>
:>> :>> and I have tried with and without the last three items and still get no
:>> :>> joy when finalizing
:>> :>>
:>> :>> Any ideas welcomed - especially if the entry in the .inf file is wrong.
:>> :>>
:>> :>
:>> :>
:>> :>
:>> :>Does LOCKCDR.FLT have /Q /D parameters? - I have 5.05 and do not see those
:>> :>parameters listed.
:>> :>
:>> :>The cdrecord line
:>> :> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>> :>should end up similar to this in cddrv.inf
:>> :>TSSTcorp "CDDVDW SH-222AB " "SB00" "CDDVDW SH-222AB " N/A
:>> :>cdatapi ATAPI CUESHEET N/A
:>> :>or possibly
:>> :>TSSTcorp "CDDVDW SH-222AB " "SB00" "TSTcorpCDDVDW SH-222AB "
:>> N/A
:>> :>cdatapi ATAPI CUESHEET N/A
:>> :>
:>> :>
:>> :>Some of my burners have needed the Brand+Model and some have only needed
:>> the
:>> :>Model in the column called SCSI-ID
:>> :>
:>> :>Note the inclusion of any spaces involved within the quotes and the
:>> position
:>> :>of the firmware level.
:>> :>
:>> :>
:>> :>Alternatively try adding the burner to lockcdr.flt at boot:-
:>> :>
:>> :>BASEDEV=LOCKCDR.FLT -I "CDDVDW SH-222AB "
:>> :>or possibly
:>> :>BASEDEV=LOCKCDR.FLT -I "TSTcorpCDDVDW SH-222AB "
:>> :>
:>> :>Yet again note the inclusion of the space within the quotes.
:>> :>
:>> :>
:>> :>Hope the above helps.
:>> :>
:>> :>Pete
:>> :>
:>> :>
:>>
:>> Here is the last error log I got earlier today
:>>
:>> *** Error no 152 at 02.03.2016 12:36:27
:>> **************************************
:>>
:>> Command: Write(24063, 30)
:>> Sense key: Illegal Request
:>> Adl. sense key: Invalid block address
:>>
:>> Sense buffer:
:>> 00000000 70 00 05 00 00 00 00 00-00 00 00 00 21 02 00 00
:>> p...........!...
:>> 00000010 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
:>> ................
:>> 00000020 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
:>> ................
:>>
:>> (and they are all the same with different block addresses)
:>>
:>
--
Barry Landy Email: Remove nospam in from address
192, Gilbert Road, Cambridge CB4 3PB
Barry Landy
2016-03-03 16:33:55 UTC
Permalink
Just a progress report.

Apart from making one coaster, not much!

I looked at ibms506$ and atapi$ which made it seem that Dani software
had claimed the CD/DVD drive, so...

Reading again the doc files from the DANI installation, I added
/RSJ /A:1 /U:1 /TYPE=W
to daniatapi.flt

made no difference.....

I notice that

a) I can successfully erase the CD/DVD
b) if I write a small amount (<1Mb) to the CD or DVD I can finalise fine
c) If I write more (a few 100 Mb) it keeps getting errors and only a
reboot will terminate the process.

On Thu, 3 Mar 2016, Barry Landy wrote:

:>On Thu, 3 Mar 2016, Pete wrote:
:>
:>:>Hi Barry
:>:>
:>:>Following Lars post I can only ask what drivers are in use: os2ahci or
:>:>danis506?
:>:>
:>
:>Both are in config.sys. Looking at the output (ibms506$ and atapi$) it
:>looks as though Dani software has claimed them.
:>
:>AHCI claims the HDDs (actually SSDs)
:>
:>:>
:>:>Regards
:>:>
:>:>Pete
:>:>
:>:>
:>:>
:>:>Barry Landy wrote:
:>:>> On Wed, 2 Mar 2016, Pete wrote:
:>:>>
:>:>> :>Hi Barry
:>:>> :>
:>:>> :>Barry Landy wrote:
:>:>> :>> Inspired by the previous correspondence I am tempted to ask the
:>:>> following.
:>:>> :>>
:>:>> :>> When I changed hardware (2012!) I found that RSJ no longer worked
:>:>> :>> properly. No problem reading CDs; no problem creating the writable
:>:>> :>> drive; no problem writing data to the drive. However, whenever I tried
:>:>> :>> to finalize I merely got a series of reported writing errors in the log.
:>:>> :>>
:>:>> :>
:>:>> :>
:>:>> :>It might be an idea to post some of those errors as they might show
:>:>> problems
:>:>> :>other than the below. It is a little unusual to be able to write to disc
:>:>> but
:>:>> :>not Finalise.
:>:>> :>
:>:>> :>
:>:>> :>> Basically I gave up and now do all my CD/DVD writing under windows.
:>:>> :>>
:>:>> :>
:>:>> :>
:>:>> :>There are a few other apps that write CD/DVD that you might want to try:
:>:>> :>cdrecord(2), dvddao, cdrtools, DVDToys
:>:>> :>
:>:>> :>
:>:>> :>> The previous correspondence made me think it might well be due to the
:>:>> :>> cddrv.inf file (which, not surprisingly, is a decade out of date).
:>:>> :>>
:>:>> :>> I installed and used cdrecord to find the SCSI data:
:>:>> :>> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>:>> :>>
:>:>> :>> I used that to add to cddrv.inf
:>:>> :>>
:>:>> :>> Brand Recorder FW SCSI-ID
:>:>> :>> Compatible-ID Driver SyncTrans DAO-Mode RegKey
:>:>> :>> Dummy "dummy" N/A "dummy dummy"
:>:>> :>> N/A cdatapi ATAPI CUESHEET N/A
:>:>> :>>
:>:>> :>> TSSTcorp "CDDVDW SH-222AB" N/A "TSTcorp SB00"
:>:>> :>> N/A cdatapi ATAPI CUESHEET N/A
:>:>> :>>
:>:>> :>> (I tried both before and after he dummy line)
:>:>> :>>
:>:>> :>> Basically no difference.
:>:>> :>>
:>:>> :>> The RSJ related items in config.sys are
:>:>> :>>
:>:>> :>> ==================
:>:>> :>>
:>:>> :>> REM [RSJ section
:>:>> :>> IFS=r:\CDWFS\CDWFS.IFS
:>:>> :>> RUN=r:\CDWFS\CDWFSD.EXE -p "R:/var/temp" -c20000 -b2048 -t2 -i3 -s0
:>:>> :>>
:>:>> :>> REM *** RSJ CD-Writer File System ***
:>:>> :>>
:>:>> :>>
:>:>> :>> BASEDEV=OS2ASPI.DMD
:>:>> :>> BASEDEV=LOCKCDR.FLT /Q /D
:>:>> :>>
:>:>> :>> DEVICE=r:\CDWFS\RSJSCSI.SYS
:>:>> :>>
:>:>> :>> ======================
:>:>> :>>
:>:>> :>> and I have tried with and without the last three items and still get no
:>:>> :>> joy when finalizing
:>:>> :>>
:>:>> :>> Any ideas welcomed - especially if the entry in the .inf file is wrong.
:>:>> :>>
:>:>> :>
:>:>> :>
:>:>> :>
:>:>> :>Does LOCKCDR.FLT have /Q /D parameters? - I have 5.05 and do not see those
:>:>> :>parameters listed.
:>:>> :>
:>:>> :>The cdrecord line
:>:>> :> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>:>> :>should end up similar to this in cddrv.inf
:>:>> :>TSSTcorp "CDDVDW SH-222AB " "SB00" "CDDVDW SH-222AB " N/A
:>:>> :>cdatapi ATAPI CUESHEET N/A
:>:>> :>or possibly
:>:>> :>TSSTcorp "CDDVDW SH-222AB " "SB00" "TSTcorpCDDVDW SH-222AB "
:>:>> N/A
:>:>> :>cdatapi ATAPI CUESHEET N/A
:>:>> :>
:>:>> :>
:>:>> :>Some of my burners have needed the Brand+Model and some have only needed
:>:>> the
:>:>> :>Model in the column called SCSI-ID
:>:>> :>
:>:>> :>Note the inclusion of any spaces involved within the quotes and the
:>:>> position
:>:>> :>of the firmware level.
:>:>> :>
:>:>> :>
:>:>> :>Alternatively try adding the burner to lockcdr.flt at boot:-
:>:>> :>
:>:>> :>BASEDEV=LOCKCDR.FLT -I "CDDVDW SH-222AB "
:>:>> :>or possibly
:>:>> :>BASEDEV=LOCKCDR.FLT -I "TSTcorpCDDVDW SH-222AB "
:>:>> :>
:>:>> :>Yet again note the inclusion of the space within the quotes.
:>:>> :>
:>:>> :>
:>:>> :>Hope the above helps.
:>:>> :>
:>:>> :>Pete
:>:>> :>
:>:>> :>
:>:>>
:>:>> Here is the last error log I got earlier today
:>:>>
:>:>> *** Error no 152 at 02.03.2016 12:36:27
:>:>> **************************************
:>:>>
:>:>> Command: Write(24063, 30)
:>:>> Sense key: Illegal Request
:>:>> Adl. sense key: Invalid block address
:>:>>
:>:>> Sense buffer:
:>:>> 00000000 70 00 05 00 00 00 00 00-00 00 00 00 21 02 00 00
:>:>> p...........!...
:>:>> 00000010 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
:>:>> ................
:>:>> 00000020 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
:>:>> ................
:>:>>
:>:>> (and they are all the same with different block addresses)
:>:>>
:>:>
:>
:>
--
Barry Landy Email: Remove nospam in from address
192, Gilbert Road, Cambridge CB4 3PB
Pete
2016-03-03 21:08:03 UTC
Permalink
Hi Barry
Post by Barry Landy
Just a progress report.
Apart from making one coaster, not much!
I looked at ibms506$ and atapi$ which made it seem that Dani software
had claimed the CD/DVD drive, so...
Reading again the doc files from the DANI installation, I added
/RSJ /A:1 /U:1 /TYPE=W
to daniatapi.flt
made no difference.....
I notice that
a) I can successfully erase the CD/DVD
b) if I write a small amount (<1Mb) to the CD or DVD I can finalise fine
c) If I write more (a few 100 Mb) it keeps getting errors and only a
reboot will terminate the process.
I seem to recall similar behaviour years ago here with a CDRW...

I think that was resolved by updating os2dasd.dmd - and possibly some
other related drivers.

It might be worth checking what the buildlevel of drivers involved are
ie os2dasd.dmd, danis506.add, daniatap(i).flt and comparing those with
the bldlevels Lars is using as he seems to have the same burner working.

It may also be worth checking the manufacturers website for a firmware
update - SB00 looks like an initial firmware release.

Regards

Pete
Post by Barry Landy
:>
:>:>Hi Barry
:>:>
:>:>Following Lars post I can only ask what drivers are in use: os2ahci or
:>:>danis506?
:>:>
:>
:>Both are in config.sys. Looking at the output (ibms506$ and atapi$) it
:>looks as though Dani software has claimed them.
:>
:>AHCI claims the HDDs (actually SSDs)
:>
:>:>
:>:>Regards
:>:>
:>:>Pete
:>:>
:>:>
:>:>
:>:>>
:>:>> :>Hi Barry
:>:>> :>
:>:>> :>> Inspired by the previous correspondence I am tempted to ask the
:>:>> following.
:>:>> :>>
:>:>> :>> When I changed hardware (2012!) I found that RSJ no longer worked
:>:>> :>> properly. No problem reading CDs; no problem creating the writable
:>:>> :>> drive; no problem writing data to the drive. However, whenever I tried
:>:>> :>> to finalize I merely got a series of reported writing errors in the log.
:>:>> :>>
:>:>> :>
:>:>> :>
:>:>> :>It might be an idea to post some of those errors as they might show
:>:>> problems
:>:>> :>other than the below. It is a little unusual to be able to write to disc
:>:>> but
:>:>> :>not Finalise.
:>:>> :>
:>:>> :>
:>:>> :>> Basically I gave up and now do all my CD/DVD writing under windows.
:>:>> :>>
:>:>> :>
:>:>> :>
:>:>> :>cdrecord(2), dvddao, cdrtools, DVDToys
:>:>> :>
:>:>> :>
:>:>> :>> The previous correspondence made me think it might well be due to the
:>:>> :>> cddrv.inf file (which, not surprisingly, is a decade out of date).
:>:>> :>>
:>:>> :>> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>:>> :>>
:>:>> :>> I used that to add to cddrv.inf
:>:>> :>>
:>:>> :>> Brand Recorder FW SCSI-ID
:>:>> :>> Compatible-ID Driver SyncTrans DAO-Mode RegKey
:>:>> :>> Dummy "dummy" N/A "dummy dummy"
:>:>> :>> N/A cdatapi ATAPI CUESHEET N/A
:>:>> :>>
:>:>> :>> TSSTcorp "CDDVDW SH-222AB" N/A "TSTcorp SB00"
:>:>> :>> N/A cdatapi ATAPI CUESHEET N/A
:>:>> :>>
:>:>> :>> (I tried both before and after he dummy line)
:>:>> :>>
:>:>> :>> Basically no difference.
:>:>> :>>
:>:>> :>> The RSJ related items in config.sys are
:>:>> :>>
:>:>> :>> ==================
:>:>> :>>
:>:>> :>> REM [RSJ section
:>:>> :>> IFS=r:\CDWFS\CDWFS.IFS
:>:>> :>> RUN=r:\CDWFS\CDWFSD.EXE -p "R:/var/temp" -c20000 -b2048 -t2 -i3 -s0
:>:>> :>>
:>:>> :>> REM *** RSJ CD-Writer File System ***
:>:>> :>>
:>:>> :>>
:>:>> :>> BASEDEV=OS2ASPI.DMD
:>:>> :>> BASEDEV=LOCKCDR.FLT /Q /D
:>:>> :>>
:>:>> :>> DEVICE=r:\CDWFS\RSJSCSI.SYS
:>:>> :>>
:>:>> :>> ======================
:>:>> :>>
:>:>> :>> and I have tried with and without the last three items and still get no
:>:>> :>> joy when finalizing
:>:>> :>>
:>:>> :>> Any ideas welcomed - especially if the entry in the .inf file is wrong.
:>:>> :>>
:>:>> :>
:>:>> :>
:>:>> :>
:>:>> :>Does LOCKCDR.FLT have /Q /D parameters? - I have 5.05 and do not see those
:>:>> :>parameters listed.
:>:>> :>
:>:>> :>The cdrecord line
:>:>> :> 0,1,0 1) 'TSSTcorp' 'CDDVDW SH-222AB ' 'SB00' Removable CD-ROM
:>:>> :>should end up similar to this in cddrv.inf
:>:>> :>TSSTcorp "CDDVDW SH-222AB " "SB00" "CDDVDW SH-222AB " N/A
:>:>> :>cdatapi ATAPI CUESHEET N/A
:>:>> :>or possibly
:>:>> :>TSSTcorp "CDDVDW SH-222AB " "SB00" "TSTcorpCDDVDW SH-222AB "
:>:>> N/A
:>:>> :>cdatapi ATAPI CUESHEET N/A
:>:>> :>
:>:>> :>
:>:>> :>Some of my burners have needed the Brand+Model and some have only needed
:>:>> the
:>:>> :>Model in the column called SCSI-ID
:>:>> :>
:>:>> :>Note the inclusion of any spaces involved within the quotes and the
:>:>> position
:>:>> :>of the firmware level.
:>:>> :>
:>:>> :>
:>:>> :>Alternatively try adding the burner to lockcdr.flt at boot:-
:>:>> :>
:>:>> :>BASEDEV=LOCKCDR.FLT -I "CDDVDW SH-222AB "
:>:>> :>or possibly
:>:>> :>BASEDEV=LOCKCDR.FLT -I "TSTcorpCDDVDW SH-222AB "
:>:>> :>
:>:>> :>Yet again note the inclusion of the space within the quotes.
:>:>> :>
:>:>> :>
:>:>> :>Hope the above helps.
:>:>> :>
:>:>> :>Pete
:>:>> :>
:>:>> :>
:>:>>
:>:>> Here is the last error log I got earlier today
:>:>>
:>:>> *** Error no 152 at 02.03.2016 12:36:27
:>:>> **************************************
:>:>>
:>:>> Command: Write(24063, 30)
:>:>> Sense key: Illegal Request
:>:>> Adl. sense key: Invalid block address
:>:>>
:>:>> 00000000 70 00 05 00 00 00 00 00-00 00 00 00 21 02 00 00
:>:>> p...........!...
:>:>> 00000010 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
:>:>> ................
:>:>> 00000020 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
:>:>> ................
:>:>>
:>:>> (and they are all the same with different block addresses)
:>:>>
:>:>
:>
:>
Barry Landy
2016-03-03 21:43:10 UTC
Permalink
Thanks for that. ISTR Lars did NOT get it working.

MY OS2DASD DANIxxx etc are all from ECS2.2 beta so are well up to date
(no later changes to those that I am aware of)

On Thu, 3 Mar 2016, Pete wrote:

:>Hi Barry
:>
:>Barry Landy wrote:
:>> Just a progress report.
:>>
:>> Apart from making one coaster, not much!
:>>
:>> I looked at ibms506$ and atapi$ which made it seem that Dani software
:>> had claimed the CD/DVD drive, so...
:>>
:>> Reading again the doc files from the DANI installation, I added
:>> /RSJ /A:1 /U:1 /TYPE=W
:>> to daniatapi.flt
:>>
:>> made no difference.....
:>>
:>> I notice that
:>>
:>> a) I can successfully erase the CD/DVD
:>> b) if I write a small amount (<1Mb) to the CD or DVD I can finalise fine
:>> c) If I write more (a few 100 Mb) it keeps getting errors and only a
:>> reboot will terminate the process.
:>>
:>
:>
:>I seem to recall similar behaviour years ago here with a CDRW...
:>
:>I think that was resolved by updating os2dasd.dmd - and possibly some other
:>related drivers.
:>
:>It might be worth checking what the buildlevel of drivers involved are ie
:>os2dasd.dmd, danis506.add, daniatap(i).flt and comparing those with the
:>bldlevels Lars is using as he seems to have the same burner working.
:>
:>It may also be worth checking the manufacturers website for a firmware update
:>- SB00 looks like an initial firmware release.
:>
:>Regards
:>
:>Pete
:>
--
Barry Landy Email: Remove nospam in from address
192, Gilbert Road, Cambridge CB4 3PB
Barry Landy
2016-03-04 07:07:59 UTC
Permalink
On Thu, 3 Mar 2016, Barry Landy wrote:

:>Thanks for that. ISTR Lars did NOT get it working.
:>
:>MY OS2DASD DANIxxx etc are all from ECS2.2 beta so are well up to date
:>(no later changes to those that I am aware of)
:>


I checked for firmware changes. Turns out it is a Samsung box and
thatthere is just one firmware upgrade (from June 2011). Made no
difference!

:>On Thu, 3 Mar 2016, Pete wrote:
:>
:>:>Hi Barry
:>:>
:>:>Barry Landy wrote:
:>:>> Just a progress report.
:>:>>
:>:>> Apart from making one coaster, not much!
:>:>>
:>:>> I looked at ibms506$ and atapi$ which made it seem that Dani software
:>:>> had claimed the CD/DVD drive, so...
:>:>>
:>:>> Reading again the doc files from the DANI installation, I added
:>:>> /RSJ /A:1 /U:1 /TYPE=W
:>:>> to daniatapi.flt
:>:>>
:>:>> made no difference.....
:>:>>
:>:>> I notice that
:>:>>
:>:>> a) I can successfully erase the CD/DVD
:>:>> b) if I write a small amount (<1Mb) to the CD or DVD I can finalise fine
:>:>> c) If I write more (a few 100 Mb) it keeps getting errors and only a
:>:>> reboot will terminate the process.
:>:>>
:>:>
:>:>
:>:>I seem to recall similar behaviour years ago here with a CDRW...
:>:>
:>:>I think that was resolved by updating os2dasd.dmd - and possibly some other
:>:>related drivers.
:>:>
:>:>It might be worth checking what the buildlevel of drivers involved are ie
:>:>os2dasd.dmd, danis506.add, daniatap(i).flt and comparing those with the
:>:>bldlevels Lars is using as he seems to have the same burner working.
:>:>
:>:>It may also be worth checking the manufacturers website for a firmware update
:>:>- SB00 looks like an initial firmware release.
:>:>
:>:>Regards
:>:>
:>:>Pete
:>:>
:>
:>
--
Barry Landy Email: Remove nospam in from address
192, Gilbert Road, Cambridge CB4 3PB
ivan
2016-03-04 16:34:15 UTC
Permalink
Post by Barry Landy
:>Thanks for that. ISTR Lars did NOT get it working.
:>
:>MY OS2DASD DANIxxx etc are all from ECS2.2 beta so are well up to date
:>(no later changes to those that I am aware of)
:>
I checked for firmware changes. Turns out it is a Samsung box and
thatthere is just one firmware upgrade (from June 2011). Made no
difference!
:>
:>:>Hi Barry
:>:>
:>:>> Just a progress report.
:>:>>
:>:>> Apart from making one coaster, not much!
:>:>>
:>:>> I looked at ibms506$ and atapi$ which made it seem that Dani software
:>:>> had claimed the CD/DVD drive, so...
:>:>>
:>:>> Reading again the doc files from the DANI installation, I added
:>:>> /RSJ /A:1 /U:1 /TYPE=W
Shouldn't that be BASEDEV=DANIATAPI.FLT /A:1 /U:1 /RSJ if you are
applying the rsj backdoor for the first unit on adapter 1 ?
Post by Barry Landy
:>:>> to daniatapi.flt
:>:>>
:>:>> made no difference.....
:>:>>
:>:>> I notice that
:>:>>
:>:>> a) I can successfully erase the CD/DVD
:>:>> b) if I write a small amount (<1Mb) to the CD or DVD I can finalise fine
:>:>> c) If I write more (a few 100 Mb) it keeps getting errors and only a
:>:>> reboot will terminate the process.
:>:>>
:>:>
:>:>
:>:>I seem to recall similar behaviour years ago here with a CDRW...
:>:>
:>:>I think that was resolved by updating os2dasd.dmd - and possibly some other
:>:>related drivers.
:>:>
:>:>It might be worth checking what the buildlevel of drivers involved are ie
:>:>os2dasd.dmd, danis506.add, daniatap(i).flt and comparing those with the
:>:>bldlevels Lars is using as he seems to have the same burner working.
:>:>
:>:>It may also be worth checking the manufacturers website for a firmware update
:>:>- SB00 looks like an initial firmware release.
:>:>
:>:>Regards
:>:>
:>:>Pete
:>:>
:>
:>
Here is a copy from some of my notes that I keep in the RSJ backup
folder.

Required drivers:
BASEDEV=DANIS506.ADD /VL
BASEDEV=DANIATAPI.FLT
BASEDEV=OS2DASD.DMD
BASEDEV=OS2ASPI.DMD /ALL
DEVICE=C:\os2\ASPIROUT.SYS
DEVICE=c:\os2\ASPINKK.SYS

rem ***RSJ***
DEVICE=D:\CDWFS\RSJSCSI.SYS
IFS=D:\CDWFS\CDWFS.IFS
RUN=D:\CDWFS\CDWFSD.EXE -p "e:/temp" -c20000 -b2048 -t2 -i3 -s0

Note: Add the RSJ backdoor to Daniatapi.flt depending on writer
adapter and unit.

------------------------------------

Notes taken from rsj readme

* If the DANIATAPI.FLT driver is installed, the user can choose if he
wants to install our RSJIDECD.FLT driver, since DANIATAPI provides
a similar functionality for enabling write access to IDE recorders.

Background:
DANIATAPI.FLT also has the ability to emulate SCSI devices. Since
our LOCKCDR.FLT driver does - among other things - the same, it is
possible to not use LOCKCDR.FLT if DANIATAPI is properly installed.
Again, please read the information in the DANIATAPI.DOC file to
find out how.

NOTE:
LOCKCDR.FLT performs dynamic recorder detection during boot time. If
you
do not use it, you have to manually edit the cddrv.inf file.

Note: Copy the Dummy entry in cddrv.inf (use epm with mono font to get
the spacing). Paste it in position for the drive and fill in the
information (keep correct spacing!!!!)

------------------------------------------------------------

End of notes.

I don't know if this will help but it works for my 5.05 retail
version.

ivan
--

Loading...