Cdrecord help?

[Stryfe]

I was attempting to create a bootable disc using cdrecord, when I ran into this issue.

My input:

Code: Select all

C:\Bootdreams\Tools>cdrecord.exe -dev=1,7,0 -blank=minimal -speed=4

The ouput:

Code: Select all

Cdrecord-ProDVD-ProBD-Clone 2.01.01a36 (i686-pc-cygwin) Copyright (C) 1995-2007 Jörg Schilling
cdrecord: No realtime priority class possible.
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '1,7,0'
scsibus: 1 target: 7 lun: 0
Using libscg version 'schily-0.9'.
cdrecord: Cannot do inquiry for CD/DVD/BD-Recorder.
cdrecord: Invalid argument. test unit ready: scsi sendcmd: fatal error
CDB:  00 00 00 00 00 00
cmd finished after 0.000s timeout 40s

I used the erase function as an example, but this happens when I try to burn as well. This prevents me from ever using Bootdreams to burn images.

BTW - I also made sure that I had the latest version of the ASPI layer installed as well.

Any ideas as to what is preventing Cdrecord from running correctly?

.

[curt_grymala]

What version of Windows are you using?

[Stryfe]

I've received the same error on a PC running Win2000, and Win Vista.

[curt_grymala]

Do you know for sure if CDRecord is configured properly on your computer? Apparently that error sometimes infers that your burner wasn't recognized by CDR.

[Stryfe]

I'm using the Cdrecord that came with Bootdreams 1.0.6c distribution. How would I do a configuration?

I downloaded and installed the 4.17a2 ASPI package, and installed it. I ran the "-scanbus" command for the "1,7,0" location I used in the example.

Usually I create images through Bootdreams, and burn through Alcohol 120. I wanted to know why I couldn't burn, so I finally decided to try manually using the Cdrecord to see if I could figure it out.

And if I remember correctly, I couldn't get it to work with my other old PC running Win ME either.

[curt_grymala]

If you ran scanbus and got a valid response, that means that it's configured properly.

I'm not sure what else might be going on. I haven't really used BootDreams (or even burned a DC disc) in quite a while.

[Stryfe]

Thanks for asking.

I did get it figured out though. I tried to many things at once, so I'm not sure what did it.

It was either deactivating all of my "virtual" drives, and/or my reversion to the 4.6 ASPI layer. Which I installed through the ForceASPI 1.7 package, apparently it has a higher compatibility.