I hope someone can help me since I didn't find any help on the whole internet.
I used cdrtfe for some time now and everything worked perfect. Now I got a new corporate notebook with XP installed and the burner isn't available anymore.
Here are all relevant informations that might help to find a solution:
Burner: HL-DT-ST DVDRAM_GSA-T20N
I'm not sure but I think it's a IDE (no SATA) burner
I tried InfraRecorder and the burner isn't available there, too
Error-Msg in cdrtfe: No CD writer found. Nevertheless, images (data CD, XD) can be created.
cdrecord.exe -scanbus lists my hd and thumbdrives but no burner
Version of cdrecord: 2.01.01a36 and some stable (older) release
I tried the cdrtfe on another machine (it's portable) and it worked
Finally I installed some ASPI drivers from adaptec cause I thougt that might help, but also didn't
The drive is available in other application (cdex, windows, dvdfab)
I have local admin-rights
I really have no idea what else to check and it looks like it's a cdrtools problem but I doubt that a dvd-burner which is manufactured Sept. 2007 isn't complatible to standards.
Any other idea what might be the problem?
Thanks in advance!
Oliver :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thanks alot for your answer. Unfortunatly I saw this hint in another post. I forgot to mention, that I checked that too and it was enabled by default. All other apps (even burner-apps) can access the device so I start to think that it's a cdrtools bug. I already tried to contact the developer but with no reaction.
Do you know of any cdrtools-forum? I saw several post with issues similar to mine but with different burners. But no solution anywhere.
Thanks in advance!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So to be honest: I have no idea why it won't show up on a standard "-scanbus" but with the "dev=ASPI:" parameter it show under the same ID where at first the HD showed up.
However I get to see it, but only on commandline-level. Not in cdrtfe.
Hope that helps a bit to solve the issue.
Thanks again!
oliver
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are two ways to access SCSI devices (like CD/DVD writers) under Win2k/XP, via SPTI and via ASPI (if installed). Under these operating systems cdrecord uses the SPTI by default (and so does cdrtfe).
Obviously the SCSI access via the built-in SPTI fails on your system for unknown reasons.
I'll add the possibiliy to cdrtfe to set the SCSI interface used by cdrecord.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I hope someone can help me since I didn't find any help on the whole internet.
I used cdrtfe for some time now and everything worked perfect. Now I got a new corporate notebook with XP installed and the burner isn't available anymore.
Here are all relevant informations that might help to find a solution:
I really have no idea what else to check and it looks like it's a cdrtools problem but I doubt that a dvd-burner which is manufactured Sept. 2007 isn't complatible to standards.
Any other idea what might be the problem?
Thanks in advance!
Oliver :-)
With cdrtfe 1.2.8 (package 'cdrtfe test') it is now possible to specify the SCSI interface: dialog 'Settings' -> tab sheet 'Drives'.
Please check, if the local CD drives are accessible for the users:
You can change the settings with the "Local Security Policy" console.
To open it:
Start Menu -> Control Panel -> Administrative Tools -> Local Security Policy.
Open the section "Local Policies" and select "Security Options".
Change "Devices: Restrict CD-ROM access to locally logged-on user only." to ENABLED.
If this wasn't the reason, why cdrecord -scanbus failed, then there is perhaps another program/driver that interferes with cdrecord.
Hey kerberos :-)
thanks alot for your answer. Unfortunatly I saw this hint in another post. I forgot to mention, that I checked that too and it was enabled by default. All other apps (even burner-apps) can access the device so I start to think that it's a cdrtools bug. I already tried to contact the developer but with no reaction.
Do you know of any cdrtools-forum? I saw several post with issues similar to mine but with different burners. But no solution anywhere.
Thanks in advance!
Looks like I got a bit closer to a solution:
When I do a "cdrecord -scandisk" I get:
scsibus0:
0,0,0 0) *
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) HOST ADAPTOR
scsibus1:
1,0,0 100) 'WDC WD80' '0BEVS-07RST0 ' '04.0' Disk
1,1,0 101) *
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) HOST ADAPTOR
scsibus2:
2,0,0 200) *
2,1,0 201) *
2,2,0 202) *
2,3,0 203) *
2,4,0 204) *
2,5,0 205) *
2,6,0 206) *
2,7,0 207) HOST ADAPTOR
but when I do "cdrecord dev=ASPI: -scanbus"
I get the drive listed:
scsibus0:
0,0,0 0) 'WDC WD80' '0BEVS-07RST0 ' '04.0' Disk
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) HOST ADAPTOR
scsibus1:
1,0,0 100) 'HL-DT-ST' 'DVDRAM_GSA-T20N ' 'WF08' Removable CD-ROM
1,1,0 101) *
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) HOST ADAPTOR
scsibus2:
2,0,0 200) *
2,1,0 201) *
2,2,0 202) *
2,3,0 203) *
2,4,0 204) *
2,5,0 205) *
2,6,0 206) *
2,7,0 207) HOST ADAPTOR
So to be honest: I have no idea why it won't show up on a standard "-scanbus" but with the "dev=ASPI:" parameter it show under the same ID where at first the HD showed up.
However I get to see it, but only on commandline-level. Not in cdrtfe.
Hope that helps a bit to solve the issue.
Thanks again!
oliver
There are two ways to access SCSI devices (like CD/DVD writers) under Win2k/XP, via SPTI and via ASPI (if installed). Under these operating systems cdrecord uses the SPTI by default (and so does cdrtfe).
Obviously the SCSI access via the built-in SPTI fails on your system for unknown reasons.
I'll add the possibiliy to cdrtfe to set the SCSI interface used by cdrecord.