Unable to burn CD on a RX2600 running OVMS 8.2

[Paul Goslin Rae McCarth]

Programmer reports they are unable to burn a cd using an in-house written script that calls cdrecord.com in Sys$Manager.
Commands being issued by script are:
@Sys$Manager:CdRecord.com Setup DKA0:[MAKEVMSCD]MANTIS030.DSK LDA1: MANTIS03
0 1269504

And
@Sys$Manager:CdRecord.com Write DKA0:[MAKEVMSCD]MANTIS030.DSK LDA1: DQA0: 0
0 5 Y

Results:

Writing disk image to CD...
%DCL-I-ALLOC, _ARCHER$DQA0: allocated
Cdrecord 1.10 (Alpha/VAX-CPQ-VMS/OpenVMS) Copyright (C) 1995-2001 Jörg Schilling
archer$dka0:[sys0.syscommon.][sysexe]cdrecord.exe;1: WARNING: If buffer underrun
s occur, you might want to increase process priority.
archer$dka0:[sys0.syscommon.][sysexe]cdrecord.exe;1: Fifo not supported.
scsidev: '8,0,0'
scsibus: 8 target: 0 lun: 0
Using libscg version 'schily-0.5'
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'TEAC '
Identifikation : 'DW-224E-B '
Revision : 'E.6F'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : SWABAUDIO
archer$dka0:[sys0.syscommon.][sysexe]cdrecord.exe;1: CD/DVD-Recorder not ready.
archer_sofpac$
--------------------------

[Steven Schweda]

I normally use a newer version of cdrecord,
and only on Alpha these days, but after the
"Driver flags :" line, it seems to be trying
to check the medium in the drive. You might
try throwing in some "-v" and/or "-V"
options to see if you can get more/better
info about why it's unhappy. What _is_ the
medium in the drive?

Clearly, the program is communicating with
the drive well enough to get the ID data
back, and I assume that the drive was
working fine for normal MOUNT and read
purposes, so it's probably not some
completely trivial hardware problem.

[Ian Miller.]

Check the media is suitable (e.g some drives only work with CD-R).

[Paul Goslin Rae McCarth]

The media in the drive is simply a blank recordable CD. They have also reported problems mounting it with a recorded CD in the drive:

$ mount/foreign dqa0:
%MOUNT-F-DRVERR, fatal drive error

[Steven Schweda]

> $ mount/foreign dqa0:
> %MOUNT-F-DRVERR, fatal drive error

Well, duh. You think maybe the drive is bad?

I'd look into that possibility.

[Ian Miller.]

i have seen that with CD-RW media in a drive that only handles CD-R.

Also you could have a broken drive.

Anything in the error log?

[Paul Goslin Rae McCarth]

The drive is only about a year old and has had very little use.....(and we don't have any hardware support at the moment).

an analyze/error results in:

%DCL-W-ACTIMAGE, error activating image SYS$SYSTEM:ERF.EXE
-CLI-E-IMAGEFNF, image file not found ARCHER$DKA0:[SYS0.SYSCOMMON.][SYSEXE]ERF.EXE;

which is another issue I need to resolve somehow...

[Volker Halle]

Hi,


%DCL-W-ACTIMAGE, error activating image SYS$SYSTEM:ERF.EXE
-CLI-E-IMAGEFNF, image file not found ARCHER$DKA0:[SYS0.SYSCOMMON.][SYSEXE]ERF.EXE;


This one is easy. There is no ANAL/ERROR support in OpenVMS Alpha since V7.1-2 and in OpenVMS I64 since the beginning.

You now need to use ELV (available since V7.3-2):

$ ANAL/ERROR/ELV

but don't expect it to be able to translate CD errors.

Volker.

[Volker Halle]

To further diagnose the DQA0: drive, I would suggest to use an OpenVMS I64 system DVD and try to mount it. If that fails, you can be pretty sure, that the drive is bad.

Volker.

[Steven Schweda]

> i have seen that with CD-RW media in a
> drive that only handles CD-R.

And this drive is what, a DVD and CD-R/RW
drive? So this comment is _how_ irrelevant?

> we don't have any hardware support at the
> moment

If the warranty has expired, take $50 to the
local PC store, and buy something which says
DVD and CD-RW on the front.