cdrtfe cannot recognize cd-writer.
Burn optical discs in various formats
Brought to you by:
kerberos002
Menu
▾
▴
I downloaded the 1.3pre1 version this morning and cdrtools no longer recognizes my cd-writer. I used version 1.2 without this problem. What suggested step(s) should I try to resolve this?
C:\Documents and Settings\carol smith>cd c:\Program files\cdrtfe
C:\Program Files\cdrtfe>cdrecord -scanbus
Cdrecord-ProDVD-Clone 2.01.01a22 (i586-pc-cygwin) Copyright (C) 1995-2006 Jörg
chilling
Using libscg version 'schily-0.9'.
scsibus0:
0,0,0 0) 'ST380011' 'A ' '8.16' 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) 'SAMSUNG ' 'DVD-ROM SD-616E ' 'F501' Removable CD-ROM
1,1,0 101) 'HL-DT-ST' 'CD-RW GCE-8483B ' 'B105' Removable CD-ROM
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
C:\Program Files\cdrtfe>cdrecord dev=0,0,0 -prcap
Cdrecord-ProDVD-Clone 2.01.01a22 (i586-pc-cygwin) Copyright (C) 1995-2006 Jörg
chilling
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Using libscg version 'schily-0.9'.
Device type : Disk
Version : 0
Response Format: 0
Vendor_info : 'ST380011'
Identifikation : 'A '
Revision : '8.16'
Device seems to be: Generic CCS Disk.
C:\Program Files\cdrtfe>
Hi again.
That was the problem. I edited the cygwin path back to cygdrive and all is well again.
The only cygwin installations on our pc were associated with the cdrtfe installations...
Thanks!
Just a question:
Does the problem occur with cdrtfe or just with the cdrtools from the DOS command prompt?
In your commandline you use dev=0,0,0, but the output of cdrecord -scnabus indicates that the device ID should be 1,1,0 for the CD-RW device.
If this behaviour occurs with cdrtfe:
Any error messages?
The new package includes cdrecord 2.01.01a22. You could try to use the older version 2.01.01a19. Or the other way, does this error occur with cdrtfe 1.3pre1 and cdrecord 2.01.01a19?
You can also try this special version of cdrtfe, which will write a log file (<cdrtfe program folder>\log.txt) with some additional information. Post it here or send it via eMail to the address mentioned in the readme_en.txt.
http://home.arcor.de/artemis002/download/cdrtfe-1.3pre1_deb.zip
(Download is only available temporarily)
It also happened with cdrtfe. An error message appeared that there was no cd-writer available and when I looked up at the drop-down box, sure enough, it was blank.
Instead of attempting to move forward against the tide, I did the following:
I uninstalled all copies of cdrtfe and reinstalled v1.2, then 1.3x and all was well again. I closed the program and reopened it. The problem was back (no CD-write drive recognized). When cdrtfe is opened, the error message reads:
A Win32 API error has occurred:
Code : 5
Message: Access is denied
Info : CreateProcess()
"C:\Program Files\cdrtfe\cdrecord" -version
Removed any saved settings, uninstalled all versions of cdrtfe again, deleted the cdrtfe folder in C:\Program Files, and reinstalled v1.2 and left as-is. CD-write drive is recognized once again. Added mpgs to the vcd playlist and attempted to burn VCD:
"C:\Program Files\cdrtfe\vcdimager" -p -v --type=vcd2 --cue-file=/cygrive/C/DOCUME~1/CAROLS~1/LOCALS~1/Temp/image.cue --bin-file=/cygrive/C/DOCUME~1/CAROLS~1/LOCALS~1/Temp/image.bin "/cygrive/C/Documents and Settings/carol smith/Desktop/YouTube Downloads/SuperConversions/Super Tears For Fears/Cold.MPG"
**ERROR: packet length beyond buffer...
--DEBUG: initializing libvcd 0.6.2rc2 [cygwin/i586]
INFO: scanning mpeg track #0 for scanpoints...
Execution completed.
"C:\Program Files\cdrtfe\cdrecord" gracetime=5 dev=1,1,0 driveropts=burnfree -dao cuefile=/cygrive/C/DOCUME~1/CAROLS~1/LOCALS~1/Temp/image.cue
scsidev: '1,1,0'
scsibus: 1 target: 1 lun: 0
Cdrecord-ProDVD-Clone 2.01.01a19 (i586-pc-cygwin) Copyright (C) 1995-2006 Jörg Schilling
Using libscg version 'schily-0.8'.
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identifikation : 'CD-RW GCE-8483B '
Revision : 'B105'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-2 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
/cygrive/c/Program Files/cdrtfe/cdrecord: No such file or directory. Cannot open '/cygrive/C/DOCUME~1/CAROLS~1/LOCALS~1/Temp/image.cue'.
Execution completed.
This is where I am now. I am not familiar enough with cygwin to understand the nuance of "cygrive" in the path or if I need to delete the cygwin file folder when I uninstall cdrtfe versions prior to reinstallation. There is no cdrecord folder in C:\Programs\cdrtfe. Of course, cdrecord.exe is there.
The only additional error message is:
**ERROR: packet length beyond buffer...
Even when I had v1.2 up and running before installing v1.3, I found it necessary to merge the mpg files that I wanted to record into a single long mpg file using TMPGEnc in order to create a reasonable VCD, but of course this negated the ability to have tracks. Simply adding individual mpg files to the recording list, the padding done by the cdrtfe program package left too many sound distortions on the resulting VCD
Regards,
Robert
This is a really strange error ...
> [no devices]
Well, the error message 'Access denied' indicates, that for some reason cdrtfe cannot execute the cdrecord command. Either it doesn't have the previleges to do so or the acces to cdrecord.exe is somehow blocked (e.g. a running instance of cdrecord).
Did I understand it right, that cdrtfe 1.3pre1 works directly after an installation but stops working after restarting the program? Does a reboot help?
What happens, if you use cdrtfe 1.3pre1 with the files from a cdrtfe 1.2 installation and cdrtfe 1.2 with the new files delivered along with cdrtfe 1.3pre1?
What about cdrtfe 1.2.1 and cdrtfe 1.2.2? Are these versions affected, too?
Does it help, if you install cdrtfe into another folder which does not begin with 'cdr'. On some Windows systems there is a strange bug regarding ambiguous file or folder names.
BTW, which is you OS?
> [cygdrive]
In the cygwin environment paths normally have another format. So a path like d:\program\test\test.exe would be /cygdrive/d/program/test/test.exe. cdrtfe automatically uses this format where necessary. So the occurence of 'cygdrive' is correct.
> [VCDImager error]
I would guess that the mpeg file is corrupted or that it doesn't have the right format to be used as input for VCDImager. See section '(S)VideoCD' in readme_en.txt for details. You could also try a more recent version of VCDImager.
> [sound problems with VCDImager]
If such problems occur, they are cause by VCDImger or mpeg files with a wrong format. cdrtfe passes the files over to VCDImager without any change.
I don't know if I will have the time to work with the program today. I'll get back to you tomorrow on this.
The only comments I have to make are:
"cygdrive" would intuitively make sense to me. But the error message is showing it as "cygrive". I don't know if that error in the path is making any difference or not.
Is the WinAPI error "....\cdrecord -version" was when v1.3 was installed. After reinstalling v1.2, I assume that cdrecord is running again because it's the program responsible for detecting the CD-Writer (and it does), but then can't write the files. At first glance of the bottom line, it does appear to be a permissions problem running cdrecord, but it operated using -scanbus before. My guess is that the only difference between the two instances is the cygwin path employed to call the write process.
I will work on your suggestions after one more attempt to reinstall v1.2. This time, I'm going to remove the both the \cdrtfe and \cygwin folders prior to reinstallation.
I'm using WinXP...
Oh, sorry, I didn't notice the missing 'd' in 'cygrive'. This is very interesting. cdrtfe reads the cygwin path prefix from the registry, either from
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
or
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin\mounts v2
If the program cannot find anything in the registry it uses the standard '/cygdrive'. If on your system the path prefix is 'cygrive' then something seems to be wrong with your installation of the cygwin environment.
Which version of the cygwin1.dll is installed on your PC (in \cygwin\bin)? Perhaps the problems are the strange results of a version incompatibility between the DLL of your cygwin installation and the DLL delivered with cdrtfe which do not occur with the older cdrecord 2.01.01a19?