Audio-Data/CD-Creator - problems scanning the bus

[Dariusz Piatkowski]

I figured I would do a clean-up pass through my multimedia apps and configuration during the holidays, and part of that meant replacing as many of the previously added one-by-one apps with RPM modules (where available).

One of these is cdrecord.exe, which I installed the RPM package for and intended to replace my originaly installed 'CDRecord/2 v2.0-Final' that came along with the 'Audio-Data/CD-Creator' application.

Well, as luck would have it having deployed the RPM package I attempted to test by scanning the bus for my DVD device, and that's where I ran into a snag:

Code: [Select]

argc:4
0: G:\APPS\MULTIMEDIA\ADC_056\bin\scanbus.exe
1: -2147482817
2: G:\usr\bin\cdrecord.exe
3: G:\APPS\MULTIMEDIA\ADC_056
Command is: G:\usr\bin\cdrecord.exe -scanbus
G:/usr/bin/sh.exe: 1: G:usrbincdrecord.exe: not found

Alright, so it looks like the SH shell is being invoked by the Audio-Data/CD-Creator application, why? I have no idea...can anyone tell?

It looks to me like sh.exe is stripping the "\", which results in a garbled cdrecord.exe name, which is why the "not found" message shows up.

I'm off to continue looking at this...

EDIT
====
Found the following contents of the scanbus.log file:

Code: [Select]

argc:4
0: G:\APPS\MULTIMEDIA\ADC_056\bin\scanbus.exe
1: -2147482739
2: G:\usr\bin\cdrecord.exe
3: G:\APPS\MULTIMEDIA\ADC_056

Command is: G:\usr\bin\cdrecord.exe -scanbus

Drop down listbox cleared.


Scanbus done.

...which literally imply that this is working fine here, and yet the actual VIO window must be failing as no device ID is actually populated in the setup window.

[Dave Yeo]

cdrecord.exe -scanbus works fine here,

Code: [Select]

cdrecord: Warning: using inofficial libscg transport code version (rdpe-scsi-os2.c-1.26 '@(#)scsi-os2.c 1.26 06/11/26 Copyright 1998 J. Schilling, C. Wohlgemuth').
Cdrecord-ProDVD-ProBD 3.01 (i386-pc-os2-gnu) Copyright (C) 1995-2015 Joerg Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
      and thus may have bugs that are not present in the original version.
      Please send bug reports and support requests to <rdpe@gmx.com>.
      The original author should not be bothered with problems of this version.


Warning: This version of cdrecord has not been configured via the standard
autoconfiguration method of the Schily makefile system. There is a high risk
that the code is not configured correctly and for this reason will not behave
as expected.

Warning: This version of libscg has not been configured via the standard
autoconfiguration method of the Schily makefile system. There is a high risk
that the code is not configured correctly and for this reason will not behave
as expected.
Using libscg version 'schily-0.9'.
scsibus0:
0,0,0   0) *
0,1,0   1) 'TSSTcorp' 'CDDVDW SH-S243D ' 'SB00' Removable CD-ROM
0,2,0   2) *
0,3,0   3) *
0,4,0   4) *
0,5,0   5) *
0,6,0   6) *
0,7,0   7) *
scsibus1:
...

[Dariusz Piatkowski]

Sorry Dave, I probably didn't explain this fully and/or in the best possible way.

The issue I'm running into occurs only when I select the 'Scan' button from within the 'CD-Creator Settings' object's pages, otherwise from CLI the actual execution is fine, I get my correct device ID back.

Now...here is what I did find out, I have the following statements in CONFIG.SYS:

REM [ Default shell values ]
SET SHELL=G:/usr/bin/sh.exe
rem SET EMXSHELL=G:/usr/bin/sh.exe
SET CONFIG_SHELL=G:/usr/bin/sh.exe
SET MAKESHELL=G:/usr/bin/sh.exe
SET EXECSHELL=G:/usr/bin/sh.exe

The BOLDED one was the problem-child...I am guessing I most likely set this up, don't remember why, but I do find a specific reference to it in the EMX INF files. For some reason I had set it to sh.exe as opposed to cmd.exe and well, that caused the 'Audio-Data/CD-Creator' class to fail the scan.

Either way, I have it REM'ed out now, noted why, if I fiind that it causes a problem elsewhere I'll need to revisit at that time.