Samba printing to Faxworks PMfax from remote -- error

[Herr Willms]

Since I moved from IBM's LAN-softwere to SAMBA, my PMfax (Faxworks by
Kellergroup, long defunct company) does not process files from other
stations in my LAN, which are running Windows.

The FxPrint Printer Driver opens a window saying (this is on a
system with German language interface):

----------- cut --------------
Job-ID <unbekannt> für FxPrint
Error auto-starting fax program
'D:\COMMS\FAXWORKS\PMFAX.EXE' (x01A2)

Die Verarbeitung wird beendet
---------------- off -------------

Translations:
unbekannt = unknown
für = for
"Die Verarbeitung wird beendet" = "Processing is terminated" (or
somesuch).

Another window with title "VX-REXX Console for Samba Print Command
for OS/2" opens with

--------- cut --------------

Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0"
"43427"'
58
Verzeichnis: "C:\SPOOL\FxPrint"
Spoolfile: "smbprn.00000007.Hw94nl"
Smbprinter: "FxPrint"
;FxSave;FXPRINT.Fax
<-->FxSave
FxPrint;FxPrint;FXPRINT.Fax
FxPrint<-->FxPrint
----------------- off ------------

and a smaller window with title "Samba Print Command for OS/2" and
the single text line 'Print "Testseite" (0,43427 bytes) to "FxPrint"'

The sections in the smb.conf regarding printing are

------- cut ---------------------

[FxPrint]
comment = FxPrint
path = C:/SPOOL/FxPrint
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxPrint

[FxSave]
comment = FxSave
path = C:/SPOOL/FxSave
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxSave

--------------- off -------------

I had changed the SPOOL files from the SAMBA Spool directory to the
one used when printing locally, but that did not change anything.

There is a "printcap" file next to the smb.conf, but I don't know
what should be in there.

Printing to the fax driver from OS/2 and WinOS2 applications works
without problems.

Could I possibly redirect the print to the LPT2 and LPT3 ports which
are used by WinO2 applications? A "COPY sometextfile.txt LPT2:" from
the commandline works fine.

What's up? Please help!


Cheers,
L.W.
Frankfurt, Germany


-----------------------------------------------------

[Herr Willms]

just adding comp.os.os2.misc and comp.os.os2.setup.misc in the vague
hope that somebody could please look into my problems and give me a
hint


Am Fri, 16 Apr 2010 09:46:18 UTC, schrieb "Herr Willms"

Post by Herr Willms
Since I moved from IBM's LAN-softwere to SAMBA, my PMfax (Faxworks by
Kellergroup, long defunct company) does not process files from other
stations in my LAN, which are running Windows.
The FxPrint Printer Driver opens a window saying (this is on a
----------- cut --------------
Job-ID <unbekannt> für FxPrint
Error auto-starting fax program
'D:\COMMS\FAXWORKS\PMFAX.EXE' (x01A2)
Die Verarbeitung wird beendet
---------------- off -------------
unbekannt = unknown
für = for
"Die Verarbeitung wird beendet" = "Processing is terminated" (or
somesuch).
Another window with title "VX-REXX Console for Samba Print Command
for OS/2" opens with
--------- cut --------------
Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0"
"43427"'
58
Verzeichnis: "C:\SPOOL\FxPrint"
Spoolfile: "smbprn.00000007.Hw94nl"
Smbprinter: "FxPrint"
;FxSave;FXPRINT.Fax
<-->FxSave
FxPrint;FxPrint;FXPRINT.Fax
FxPrint<-->FxPrint
----------------- off ------------
and a smaller window with title "Samba Print Command for OS/2" and
the single text line 'Print "Testseite" (0,43427 bytes) to "FxPrint"'
The sections in the smb.conf regarding printing are
------- cut ---------------------
[FxPrint]
comment = FxPrint
path = C:/SPOOL/FxPrint
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxPrint
[FxSave]
comment = FxSave
path = C:/SPOOL/FxSave
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxSave
--------------- off -------------
I had changed the SPOOL files from the SAMBA Spool directory to the
one used when printing locally, but that did not change anything.
There is a "printcap" file next to the smb.conf, but I don't know
what should be in there.
Printing to the fax driver from OS/2 and WinOS2 applications works
without problems.
Could I possibly redirect the print to the LPT2 and LPT3 ports which
are used by WinO2 applications? A "COPY sometextfile.txt LPT2:" from
the commandline works fine.
What's up? Please help!
Cheers,
L.W.
Frankfurt, Germany
-----------------------------------------------------

[Dave Saville]

On Fri, 16 Apr 2010 23:42:49 UTC, "Herr Willms"

Post by Herr Willms
just adding comp.os.os2.misc and comp.os.os2.setup.misc in the vague
hope that somebody could please look into my problems and give me a
hint

If you are prepared to wait a few minutes for the fax to go and
assuming there is info in the Fax for PMFax to figure out where it is
going, you could just drop it into the Fax directory. PMF seems to
check every five minutes or so and sends them. I suspect it is some of
the code active from the network version which cost extra.

HTH

--
Regards
Dave Saville

[Herr Willms]

Am Sat, 17 Apr 2010 07:12:47 UTC, schrieb "Dave Saville"
<***@invalid.invalid> auf de.comp.os.os2.misc :

thanks for looking into it!

Post by Dave Saville
If you are prepared to wait a few minutes for the fax to go and
assuming there is info in the Fax for PMFax to figure out where it is
going, you could just drop it into the Fax directory.

The Faxworks software has first to interpret the printer data stream
to make a fax file out of it. Faxworks emulates an IBM Proprinter X24,
and all programs print to such a printer with the printer port leading
to the fax software. So without Faxworks actually processing this
datastream, there is no fax file.



Cheers,
L.W.

-- -----------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[Dave Saville]

On Sat, 17 Apr 2010 17:30:25 UTC, "Herr Willms"

Post by Herr Willms
Am Sat, 17 Apr 2010 07:12:47 UTC, schrieb "Dave Saville"
thanks for looking into it!

Post by Dave Saville
If you are prepared to wait a few minutes for the fax to go and
assuming there is info in the Fax for PMFax to figure out where it is
going, you could just drop it into the Fax directory.

The Faxworks software has first to interpret the printer data stream
to make a fax file out of it. Faxworks emulates an IBM Proprinter X24,
and all programs print to such a printer with the printer port leading
to the fax software. So without Faxworks actually processing this
datastream, there is no fax file.

So keep a local fax directory and FTP 'em over?

[Herr Willms]

Am Mon, 19 Apr 2010 08:15:21 UTC, schrieb "Dave Saville"

Post by Dave Saville

Post by Herr Willms
The Faxworks software has first to interpret the printer data stream
to make a fax file out of it. Faxworks emulates an IBM Proprinter X24,
and all programs print to such a printer with the printer port leading
to the fax software. So without Faxworks actually processing this
datastream, there is no fax file.

So keep a local fax directory and FTP 'em over?

My current workaround is to create a PDF on the Windows systems, and
to print this PDF to the Fax print driver on the OS/2 system. But that
is very tedious and time consuming. I also have to take care that the
PDF does include all fonts which are in the Windows document, and that
it can be opened by Acrobat Reader 3, which is the latest one
available for OS/2.


Cheers,
L.W.

-------------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[James J. Weinkam]

Post by Herr Willms
My current workaround is to create a PDF on the Windows systems, and
to print this PDF to the Fax print driver on the OS/2 system. But that
is very tedious and time consuming. I also have to take care that the
PDF does include all fonts which are in the Windows document, and that
it can be opened by Acrobat Reader 3, which is the latest one
available for OS/2.

Have you tried Ghostscript/GSView? It is much more up to date than Acrobat3.

[Herr Willms]

Am Mon, 19 Apr 2010 17:53:09 UTC, schrieb "James J. Weinkam"

Post by James J. Weinkam
Have you tried Ghostscript/GSView?

tried several times, but never understood how to get it going.

Post by James J. Weinkam
It is much more up to date than Acrobat3.

At least the Adobe Acrobat works.


Cheers,
L.W.

-----------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[Dave Yeo]

Post by Herr Willms
and that
it can be opened by Acrobat Reader 3, which is the latest one
available for OS/2.

The latest was a preview of Acrobat Reader 5, unluckily the Innotek link
is dead. I have Acrobat Reader 4 installed here as well.
Perhaps someone knows where to find them now.
Dave

[PaulRS]

Post by Dave Yeo

Post by Herr Willms
and that
it can be opened by Acrobat Reader 3, which is the latest one
available for OS/2.

The latest was a preview of Acrobat Reader 5, unluckily the Innotek link
is dead. I have Acrobat Reader 4 installed here as well.
Perhaps someone knows where to find them now.
Dave

If you bought OpenOffice 114 from Mensys and got the CD ("Media Kit")
Acrobat 5.1 is included under the "WEBPACK" directory
--

[Herr Willms]

Am Thu, 22 Apr 2010 23:32:55 UTC, schrieb "PaulRS"

Post by PaulRS
If you bought OpenOffice 114 from Mensys and got the CD ("Media Kit")
Acrobat 5.1 is included under the "WEBPACK" directory

Is that a) a OS/2 native application, or does it rely on some
Windows emulation?

is it b) included on the "Media kit" for 3.1.1 of Open Office, too?


Cheers,
L.W.

-----------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[PaulRS]

On Fri, 23 Apr 2010 10:58:41 UTC, "Herr Willms"

Post by Herr Willms
Am Thu, 22 Apr 2010 23:32:55 UTC, schrieb "PaulRS"

Post by PaulRS
If you bought OpenOffice 114 from Mensys and got the CD ("Media Kit")
Acrobat 5.1 is included under the "WEBPACK" directory

Is that a) a OS/2 native application, or does it rely on some
Windows emulation?
is it b) included on the "Media kit" for 3.1.1 of Open Office, too?

OpenOffice (www.openoffice.org) has been "ported" to OS2 much like the
mozilla browser stuff in that it is "unofficial." The "official"
versions are for Linux, Windows, Mac, Solaris. The ones sold by
Mensys are OS/2 native.

I have three versions 1.14; 1.15; and recently 3.11 - I got them all
on the CD (as opposed to download only). ONLY the 1.14 CD has the
WEBPACK directory that includes Acrobat 4 and 5.1 for OS/2. (I
checked all three CDs)

Paul

[Herr Willms]

Am Fri, 23 Apr 2010 16:22:52 UTC, schrieb "PaulRS"

Post by PaulRS
ONLY the 1.14 CD has the
WEBPACK directory that includes Acrobat 4 and 5.1 for OS/2.

My question was if these Acrobat readers are genuine, native OS/2
versions or if they require some Windows emulation. Adobe has, as far
as I know, never produced an OS/2 version beyond Acrobat 3.0.


Cheers,
L.W.

-------------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[PaulRS]

On Fri, 23 Apr 2010 18:28:52 UTC, "Herr Willms"

Post by Herr Willms
Am Fri, 23 Apr 2010 16:22:52 UTC, schrieb "PaulRS"

Post by PaulRS
ONLY the 1.14 CD has the
WEBPACK directory that includes Acrobat 4 and 5.1 for OS/2.

My question was if these Acrobat readers are genuine, native OS/2
versions or if they require some Windows emulation. Adobe has, as far
as I know, never produced an OS/2 version beyond Acrobat 3.0.

My understanding is that they are NOT genuine OS/2 - 3.0 is the last.
I believe that these are windows versions running on the INNOTEK
runtime stuff - much like OpenOffice

Paul

--

[Barbara]

Post by Dave Yeo

Post by Herr Willms
and that
it can be opened by Acrobat Reader 3, which is the latest one
available for OS/2.

The latest was a preview of Acrobat Reader 5, unluckily the Innotek link
is dead. I have Acrobat Reader 4 installed here as well.
Perhaps someone knows where to find them now.
Dave

Looks like 4 and 5 versions can be downloaded from:

http://www.os2site.com/sw/util/pdf/
(os2kitacrobatreader51preview1.exe)

This needs the InnoTek runtime which can also be found at:

http://www.os2site.com/sw/dev/InnoTek/
(innotekruntime_112b20.exe)

I've been using the 5.1 preview since 2006, no problems. It still
reads almost any PDF I retrieve, sometimes with warnings. Runtime has
to be installed first, which ends up in a directory called "Innowin"
on your boot drive. (Don't remember if I made that directory, or if
the install created it.) Then install the acrobat reader 5.1 preview.

[PaulRS]

On Fri, 16 Apr 2010 23:42:49 UTC, "Herr Willms"

Post by Herr Willms
just adding comp.os.os2.misc and comp.os.os2.setup.misc in the vague
hope that somebody could please look into my problems and give me a
hint
Am Fri, 16 Apr 2010 09:46:18 UTC, schrieb "Herr Willms"

Post by Herr Willms
Since I moved from IBM's LAN-softwere to SAMBA, my PMfax (Faxworks by
Kellergroup, long defunct company) does not process files from other
stations in my LAN, which are running Windows.
The FxPrint Printer Driver opens a window saying (this is on a
----------- cut --------------
Job-ID <unbekannt> f�r FxPrint
Error auto-starting fax program
'D:\COMMS\FAXWORKS\PMFAX.EXE' (x01A2)
Die Verarbeitung wird beendet
---------------- off -------------
unbekannt = unknown
f�r = for
"Die Verarbeitung wird beendet" = "Processing is terminated" (or
somesuch).
Another window with title "VX-REXX Console for Samba Print Command
for OS/2" opens with
--------- cut --------------
Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0"
"43427"'
58
Verzeichnis: "C:\SPOOL\FxPrint"
Spoolfile: "smbprn.00000007.Hw94nl"
Smbprinter: "FxPrint"
;FxSave;FXPRINT.Fax
<-->FxSave
FxPrint;FxPrint;FXPRINT.Fax
FxPrint<-->FxPrint
----------------- off ------------
and a smaller window with title "Samba Print Command for OS/2" and
the single text line 'Print "Testseite" (0,43427 bytes) to "FxPrint"'
The sections in the smb.conf regarding printing are
------- cut ---------------------
[FxPrint]
comment = FxPrint
path = C:/SPOOL/FxPrint
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxPrint
[FxSave]
comment = FxSave
path = C:/SPOOL/FxSave
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxSave
--------------- off -------------
I had changed the SPOOL files from the SAMBA Spool directory to the
one used when printing locally, but that did not change anything.
There is a "printcap" file next to the smb.conf, but I don't know
what should be in there.
Printing to the fax driver from OS/2 and WinOS2 applications works
without problems.
Could I possibly redirect the print to the LPT2 and LPT3 ports which
are used by WinO2 applications? A "COPY sometextfile.txt LPT2:" from
the commandline works fine.
What's up? Please help!
Cheers,
L.W.
Frankfurt, Germany
-----------------------------------------------------

I am certainly not an "expert" in this area and I am replying just to
give some ideas to try.
My first thought goes with the initial error. It looks like FxPrint
is getting a file - possibly a file name that it does not know what to
do. I would experiement with a small fax and print it to a file on
one of the lan machines. Then move the file to the OS/2 box and try
to "copy file.ext FxPrint" and see if what you are putting out on the
lan box will print directly from the OS/2 box. If it does, then SAMBA
is adding something that FxPrint does not like. If it does not print
then the file created on the lan machine is the problem - either the
file itself or the file name. - Just some guesses and things to try
. .

--

[Herr Willms]

Am Tue, 20 Apr 2010 21:45:51 UTC, schrieb "PaulRS"

Post by PaulRS
I would experiement with a small fax and print it to a file on
one of the lan machines. Then move the file to the OS/2 box and try
to "copy file.ext FxPrint" and see if what you are putting out on the
lan box will print directly from the OS/2 box.

I followed the idea, printed a simple file on Windows with the
IBM-Proprinter X24 driver to a file. But COPY that file to FXPRINT
only creates a file named FXPRINT on the OS/2 machine.

The PRINT command als requires a valid unit name of LPTx.

The Faxprint driver on OS/2 does not protest against the file -- I
have printed such files to the OS/2 fax printer many times. It
complains about an invalid resp. unkown Job-ID for the print job
handed over by SAMBA.

Post by PaulRS
Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0" "43427"'
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"

I don't any explanation of what those s, p, J, c, and z are supposed
to mean.


I think that I have to look thru the SAMBA log files to find some
more information.

Cheers
L.W.

-----------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[PaulRS]

On Wed, 21 Apr 2010 14:59:10 UTC, "Herr Willms"

Post by Herr Willms

Post by PaulRS
Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0" "43427"'
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"

I don't any explanation of what those s, p, J, c, and z are supposed

First, I do know that the s, p, J, c, and z are the Printparms that
are being passed by smbprint.exe - the five things in quotes.

OK -- My next guess is that FxPrint does not understand one or more of
these parameters. I would study the help files (or in linux the "man"
page for smbprint.exe. If the letters s,p,J,c,z are specific ( Not
like "Batch" files where the parms are just 1,2,3, etc) then maybe
leaving some off may make the difference. In other words: Example -
the "0" parm may be the ID and you might be able to drop the "%c" from
the smbprint.exe command. Again just a guess - studying what smbprint
is sending over the lan may be the key.

Paul


--

[PaulRS]

Post by PaulRS
On Wed, 21 Apr 2010 14:59:10 UTC, "Herr Willms"

Post by Herr Willms

Post by PaulRS
Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0" "43427"'
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"

I don't any explanation of what those s, p, J, c, and z are supposed

First, I do know that the s, p, J, c, and z are the Printparms that
are being passed by smbprint.exe - the five things in quotes.
OK -- My next guess is that FxPrint does not understand one or more of
these parameters. I would study the help files (or in linux the "man"
page for smbprint.exe. If the letters s,p,J,c,z are specific ( Not
like "Batch" files where the parms are just 1,2,3, etc) then maybe
leaving some off may make the difference. In other words: Example -
the "0" parm may be the ID and you might be able to drop the "%c" from
the smbprint.exe command. Again just a guess - studying what smbprint
is sending over the lan may be the key.
Paul

In doing a quick internet search, I see that smbprint.exe is strickly
a part of the OS/2 SAMBA. So the parameters info would be strickly
limited to the OS/2 help or info. They probably work (or are ignored)
with regular printers, but FxPrint does not like one or more. If you
can figure out what each of those five parameters are, then you may
experiment by dropping one or more off and see what happens. I know
this is a real trial and error solution --- Unless someone else can
give more info here.
Paul

--

[Herr Willms]

Am Wed, 21 Apr 2010 15:51:55 UTC, schrieb "PaulRS"

Post by PaulRS
Again just a guess - studying what smbprint
is sending over the lan may be the key.

SMBPRINT is sending nothing over the LAN. SMBPRINT is a purely local
OS/2 affair. Some SAMBA daemon receives the file to be printed, and
executes the program smbprint.exe with five parameters. Some of these
parameters are false.


Cheers,
L.W.

-------------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[PaulRS]

On Wed, 21 Apr 2010 18:35:25 UTC, "Herr Willms"

Post by Herr Willms
Am Wed, 21 Apr 2010 15:51:55 UTC, schrieb "PaulRS"

Post by PaulRS
Again just a guess - studying what smbprint
is sending over the lan may be the key.

SMBPRINT is sending nothing over the LAN. SMBPRINT is a purely local
OS/2 affair. Some SAMBA daemon receives the file to be printed, and
executes the program smbprint.exe with five parameters. Some of these
parameters are false.

OK, Then smbprint locally may be sending stuff to FxPrint Driver via
the parameters that it does not like. Either way, my guess is still
to "play-around" with the smbprint.exe and the various parameters
("%x") that are attached to the command.

--

[Herr Willms]

Am Wed, 21 Apr 2010 22:11:19 UTC, schrieb "PaulRS"

Post by PaulRS
smbprint locally may be sending stuff to FxPrint Driver via
the parameters that it does not like.

As said -- the actual printer driver Fxprint complains about an
unknown Job-ID.

Post by PaulRS
Either way, my guess is still to "play-around" with the smbprint.exe
and the various parameters ("%x") that are attached to the command.

That's a good suggestion! I'll try that out later today.


Cheers,
L.W.


-----------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[Herr Willms]

Am Wed, 21 Apr 2010 14:59:10 UTC, schrieb "Herr Willms"

Post by PaulRS
Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0" "43427"'
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"

Executing SMBPRINT.EXE without any paramters get it to spell this
out:

smbprint.exe "spoolfile" "printerqueue" "jobname" "pages" "jobsize"

Let's see what happens when I call smbprint.exe manually.

I have produced by "print to file" a printfile. When I copy it to
the LPT port which is used by Fxprint, then everything goes fine --
the printfile appears as fax waiting to be sent over the wire.

When I use smbprint.exe in this form

smbprint.exe "testprint.prm" "fxprint" "testpage" "3" "128494"

then Faxwork is happy with the command, makes an entry in the list
of faxes, but does not show the file to be sent. Well, one problem
seems to have been solved, namely that of the "Unknown Job-ID" which
the Faxworks printer driver complains about. But the actual content of
the file to be printed does not appear. The same happens with a file
which is actually transferred via the net and which then gets a name
like "smbprn.00000004.50wJVF". It is OK when I simply COPY this file
to the LPT port assigned to the Faxprint driver.


Cheers,
L.W.

-------------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[Ilya Zakharevich]

Post by Herr Willms
When I use smbprint.exe in this form

smbprint.exe "testprint.prm" "fxprint" "testpage" "3" "128494"

then Faxwork is happy with the command, makes an entry in the list
of faxes, but does not show the file to be sent.

Just a wild guess: printer driver is a service; it might be that it
runs in a different process (?) and does not know the current
directory. I would try the full path...

Hope this helps,
Ilya

[Herr Willms]

Am Thu, 22 Apr 2010 20:05:57 UTC, schrieb Ilya Zakharevich

Post by Ilya Zakharevich

Post by Herr Willms
When I use smbprint.exe in this form

smbprint.exe "testprint.prm" "fxprint" "testpage" "3" "128494"

then Faxwork is happy with the command, makes an entry in the list
of faxes, but does not show the file to be sent.

I would try the full path...

Good hint, but it doesnt change the result.


Cheers,
L.W.

------------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[PaulRS]

On Thu, 22 Apr 2010 17:24:42 UTC, "Herr Willms"
<***@domain.invalid> wrote:

First, it looks like you are on the right track . . .

Post by Herr Willms
Am Wed, 21 Apr 2010 14:59:10 UTC, schrieb "Herr Willms"

Post by PaulRS
Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0" "43427"'

Where are the above "Printparms . . ." coming from? If parameter 4 is
"pages" as stated below in excuting smbprint.exe w/o parameters then
"0" pages may be the problem. I would guess that FxPrint would not do
anything for "0" pages. (continued down)

Post by Herr Willms

Post by PaulRS
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"

Executing SMBPRINT.EXE without any paramters get it to spell this
smbprint.exe "spoolfile" "printerqueue" "jobname" "pages" "jobsize"
Let's see what happens when I call smbprint.exe manually.
I have produced by "print to file" a printfile. When I copy it to
the LPT port which is used by Fxprint, then everything goes fine --
the printfile appears as fax waiting to be sent over the wire.
When I use smbprint.exe in this form

smbprint.exe "testprint.prm" "fxprint" "testpage" "3" "128494"

Here, "testprint.prm" does not appear to be a "spoolfile" - smbprint
is probably looking in the "spool" directory for a spool file. If
there is a valid spool file sent over the net in this directory you
might try substituting its name and a proper number of pages in your
manual test.
If this works, the problem seems to be from your original #1 post
with the "0" pages and where it is coming from as the rest of the
parameters look OK.

Again, I think you are on the right track - just depends how much
time you have to "PLAY!" (I always liked the SuSE Linux prompt "Have
a lot of fun" as I was pulling may hair out trying to do something and
figure out why things were not working ;-) Is this FUN yet?

Post by Herr Willms
then Faxwork is happy with the command, makes an entry in the list
of faxes, but does not show the file to be sent. Well, one problem
seems to have been solved, namely that of the "Unknown Job-ID" which
the Faxworks printer driver complains about. But the actual content of
the file to be printed does not appear. The same happens with a file
which is actually transferred via the net and which then gets a name
like "smbprn.00000004.50wJVF". It is OK when I simply COPY this file
to the LPT port assigned to the Faxprint driver.
Cheers,
L.W.
-------------------------------------------------------
Gewinnen und verlieren in einer Diskussion k�nnen sich
vern�nftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Pl�tzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

--

[Ruediger Ihle]

Post by Herr Willms
It is OK when I simply COPY this file
to the LPT port assigned to the Faxprint driver.

I don't know what smbprint actually does, but the error message

D:\COMMS\FAXWORKS\PMFAX.EXE' (x01A2)

suggests, that a non-PM programm (smbprint ?) is trying to start
a PM-program via the wrong API.

Question: If the copy-to-lpt approach works, can't you configure
SAMBA to do just this ?

[Herr Willms]

Am Fri, 23 Apr 2010 06:39:07 UTC, schrieb "Ruediger Ihle"

Post by Ruediger Ihle
Question: If the copy-to-lpt approach works, can't you configure
SAMBA to do just this ?

I tried that, but it didn't help. After that the system choked and I
had to reboot. So there is some probability that it makes things
worse.

The error message which the printer driver shows, says that it did
not receive a valid Job-ID. So my guess is that Samba does not call
SMBPRINT.EXE with the proper parameters, which should all be in
quotes.

As I said, when I execute smbprint.exe from the command line, the
printer driver does not complain, although it does not get the data to
be printed.

One problem hides the next.


Cheers,
L.W.

-----------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[Ilya Zakharevich]

Post by Ruediger Ihle
I don't know what smbprint actually does, but the error message
D:\COMMS\FAXWORKS\PMFAX.EXE' (x01A2)
suggests, that a non-PM programm (smbprint ?) is trying to start
a PM-program via the wrong API.

Then the solution to THIS part of the problem is to prepend

start /pm

to (smbprint ?)'s command line...

Yours,
Ilya

[PaulRS]

On Fri, 16 Apr 2010 23:42:49 UTC, "Herr Willms"

Post by Herr Willms
just adding comp.os.os2.misc and comp.os.os2.setup.misc in the vague
hope that somebody could please look into my problems and give me a
hint
Am Fri, 16 Apr 2010 09:46:18 UTC, schrieb "Herr Willms"

Post by Herr Willms
Since I moved from IBM's LAN-softwere to SAMBA, my PMfax (Faxworks by
Kellergroup, long defunct company) does not process files from other
stations in my LAN, which are running Windows.
The FxPrint Printer Driver opens a window saying (this is on a
----------- cut --------------
Job-ID <unbekannt> f�r FxPrint
Error auto-starting fax program
'D:\COMMS\FAXWORKS\PMFAX.EXE' (x01A2)
Die Verarbeitung wird beendet
---------------- off -------------
unbekannt = unknown
f�r = for
"Die Verarbeitung wird beendet" = "Processing is terminated" (or
somesuch).
Another window with title "VX-REXX Console for Samba Print Command
for OS/2" opens with
--------- cut --------------
Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0"
"43427"'
58
Verzeichnis: "C:\SPOOL\FxPrint"
Spoolfile: "smbprn.00000007.Hw94nl"
Smbprinter: "FxPrint"
;FxSave;FXPRINT.Fax
<-->FxSave
FxPrint;FxPrint;FXPRINT.Fax
FxPrint<-->FxPrint
----------------- off ------------
and a smaller window with title "Samba Print Command for OS/2" and
the single text line 'Print "Testseite" (0,43427 bytes) to "FxPrint"'
The sections in the smb.conf regarding printing are
------- cut ---------------------
[FxPrint]
comment = FxPrint
path = C:/SPOOL/FxPrint
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxPrint
[FxSave]
comment = FxSave
path = C:/SPOOL/FxSave
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxSave
--------------- off -------------
I had changed the SPOOL files from the SAMBA Spool directory to the
one used when printing locally, but that did not change anything.
There is a "printcap" file next to the smb.conf, but I don't know
what should be in there.
Printing to the fax driver from OS/2 and WinOS2 applications works
without problems.
Could I possibly redirect the print to the LPT2 and LPT3 ports which
are used by WinO2 applications? A "COPY sometextfile.txt LPT2:" from
the commandline works fine.
What's up? Please help!
Cheers,
L.W.
Frankfurt, Germany
-----------------------------------------------------

I also have this Fax Program. I took a look at the fax directory of
either sent or received files and they all have the filename:
FX000011.FAX
FX000012.FAX
Etc.

However, this is the "end of the line" file and not the raw info being
sent by the sending program over the SAMBA connection to FxPrint. Not
sure how one could do what I suggested in the earlier reply to get RAW
output into a file and copy the RAW program output to FxPrint on the
OS/2 box.

Possibly you could print a simple TEXT file to "file" (something from
WinOS2-Notepad - print it to a file, try sending it by SAMBA to
FxPrint. Then copy the file over to the OS2 box and "copy file.ext
FxPrint" - see what you get. Again, I just suggest, I am not an
expert here.

[Herwig Bauernfeind]

Post by Herr Willms
just adding comp.os.os2.misc and comp.os.os2.setup.misc in the vague
hope that somebody could please look into my problems and give me a
hint
Am Fri, 16 Apr 2010 09:46:18 UTC, schrieb "Herr Willms"

Post by Herr Willms
Since I moved from IBM's LAN-softwere to SAMBA, my PMfax (Faxworks by
Kellergroup, long defunct company) does not process files from other
stations in my LAN, which are running Windows.
The FxPrint Printer Driver opens a window saying (this is on a
----------- cut --------------
Job-ID <unbekannt> für FxPrint
Error auto-starting fax program
'D:\COMMS\FAXWORKS\PMFAX.EXE' (x01A2)
Die Verarbeitung wird beendet
---------------- off -------------
unbekannt = unknown
für = for
"Die Verarbeitung wird beendet" = "Processing is terminated" (or
somesuch).
Another window with title "VX-REXX Console for Samba Print Command
for OS/2" opens with
--------- cut --------------
Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0"
"43427"'
58
Verzeichnis: "C:\SPOOL\FxPrint"
Spoolfile: "smbprn.00000007.Hw94nl"
Smbprinter: "FxPrint"
;FxSave;FXPRINT.Fax
<-->FxSave
FxPrint;FxPrint;FXPRINT.Fax
FxPrint<-->FxPrint
----------------- off ------------
and a smaller window with title "Samba Print Command for OS/2" and
the single text line 'Print "Testseite" (0,43427 bytes) to "FxPrint"'
The sections in the smb.conf regarding printing are
------- cut ---------------------
[FxPrint]
comment = FxPrint
path = C:/SPOOL/FxPrint
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxPrint
[FxSave]
comment = FxSave
path = C:/SPOOL/FxSave
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxSave
--------------- off -------------
I had changed the SPOOL files from the SAMBA Spool directory to the
one used when printing locally, but that did not change anything.
There is a "printcap" file next to the smb.conf, but I don't know
what should be in there.
Printing to the fax driver from OS/2 and WinOS2 applications works
without problems.
Could I possibly redirect the print to the LPT2 and LPT3 ports which
are used by WinO2 applications? A "COPY sometextfile.txt LPT2:" from
the commandline works fine.
What's up? Please help!

Sorry, to jump in that late here, I answered at the samba gmane list.
I can shed some light onto a few things that are in question here:

1.) smbprint.exe is VX-REXX based PM program written by me excusively
for our Samba for eCS. It is more or less a one trick pony:

The Samba Server calls it as a print command whenever the server
receives something to print.

print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"

smbprint checks which printer it should print to and prints the file to
this printer in the OS/2 printing subsystem. Not more, not less. It
requires exactly 5 parameters in the following order:

%s = "spoolfile including path"

%p = "printerqueue"

%J = "jobname"

%c = "pages"

%z = "jobsize"

The variables are filled with appropriate values from the Samba daemon
when smbprint is executed.

The variables are documented in the smb.conf documentation for the print
command, look here

http://samba.org/samba/docs/man/manpages-3/smb.conf.5.html

2.) smbprint.exe is not the only possibility to achieve printing
capabilities with Samba. The variables provided by Samba provide a
toolset to deal with.

It is perfectly acceptable to build a print command like in smb.conf

print command = cmd.exe /c copy "%s" LPT2

which should work in the described case.

It is also possibly to use lpr.exe to do it.

The only advantage of smbprint.exe is that it also understands the
jobname and number of pages and also passes these to the OS/2 printer
subsystem, while when using other solutions, you will only see a default
title etc. when opening the printer object.

3.) sscc.exe, the "Samba Configuration Center", is able to create an
appropriate printcap file. Menu "File" - "Create printcap". Printcap is
located in %ETC%.

Note: If sscc.exe detects that your printcap file was created using CUPS
it wont touch it during installation.

4.) I intend to opensource smbprint.exe at the Samba repository at
netlabs (like the other GUI tools), it was simply forgotten until now,
as the plan always was (and is) to get our Samba working with CUPS.
smbprint.exe was meant to fill the gap until CUPS support for Samba is here.

Hope this helps.

Regards,
Herwig

[PaulRS]

On Fri, 23 Apr 2010 15:37:12 UTC, Herwig Bauernfeind

Post by Herwig Bauernfeind

Post by Herr Willms
just adding comp.os.os2.misc and comp.os.os2.setup.misc in the vague
hope that somebody could please look into my problems and give me a
hint
Am Fri, 16 Apr 2010 09:46:18 UTC, schrieb "Herr Willms"

Post by Herr Willms
Since I moved from IBM's LAN-softwere to SAMBA, my PMfax (Faxworks by
Kellergroup, long defunct company) does not process files from other
stations in my LAN, which are running Windows.
The FxPrint Printer Driver opens a window saying (this is on a
----------- cut --------------
Job-ID <unbekannt> f�r FxPrint
Error auto-starting fax program
'D:\COMMS\FAXWORKS\PMFAX.EXE' (x01A2)
Die Verarbeitung wird beendet
---------------- off -------------
unbekannt = unknown
f�r = for
"Die Verarbeitung wird beendet" = "Processing is terminated" (or
somesuch).
Another window with title "VX-REXX Console for Samba Print Command
for OS/2" opens with
--------- cut --------------
Printparms='"smbprn.00000007.Hw94nl" "FxPrint" "Testseite" "0"
"43427"'
58
Verzeichnis: "C:\SPOOL\FxPrint"
Spoolfile: "smbprn.00000007.Hw94nl"
Smbprinter: "FxPrint"
;FxSave;FXPRINT.Fax
<-->FxSave
FxPrint;FxPrint;FXPRINT.Fax
FxPrint<-->FxPrint
----------------- off ------------
and a smaller window with title "Samba Print Command for OS/2" and
the single text line 'Print "Testseite" (0,43427 bytes) to "FxPrint"'
The sections in the smb.conf regarding printing are
------- cut ---------------------
[FxPrint]
comment = FxPrint
path = C:/SPOOL/FxPrint
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxPrint
[FxSave]
comment = FxSave
path = C:/SPOOL/FxSave
read only = No
create mask = 0700
guest ok = Yes
printable = Yes
printing = os2
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
lpq command = lpq.exe -s %i -p %p
lprm command = lprm.exe -s %i -p %p %j
printer name = FxSave
--------------- off -------------
I had changed the SPOOL files from the SAMBA Spool directory to the
one used when printing locally, but that did not change anything.
There is a "printcap" file next to the smb.conf, but I don't know
what should be in there.
Printing to the fax driver from OS/2 and WinOS2 applications works
without problems.
Could I possibly redirect the print to the LPT2 and LPT3 ports which
are used by WinO2 applications? A "COPY sometextfile.txt LPT2:" from
the commandline works fine.
What's up? Please help!

Sorry, to jump in that late here, I answered at the samba gmane list.
1.) smbprint.exe is VX-REXX based PM program written by me excusively
The Samba Server calls it as a print command whenever the server
receives something to print.
print command = C:\APPS\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"
smbprint checks which printer it should print to and prints the file to
this printer in the OS/2 printing subsystem. Not more, not less. It
%s = "spoolfile including path"
%p = "printerqueue"
%J = "jobname"
%c = "pages"
%z = "jobsize"
The variables are filled with appropriate values from the Samba daemon
when smbprint is executed.
The variables are documented in the smb.conf documentation for the print
command, look here
http://samba.org/samba/docs/man/manpages-3/smb.conf.5.html
2.) smbprint.exe is not the only possibility to achieve printing
capabilities with Samba. The variables provided by Samba provide a
toolset to deal with.
It is perfectly acceptable to build a print command like in smb.conf
print command = cmd.exe /c copy "%s" LPT2
which should work in the described case.
It is also possibly to use lpr.exe to do it.
The only advantage of smbprint.exe is that it also understands the
jobname and number of pages and also passes these to the OS/2 printer
subsystem, while when using other solutions, you will only see a default
title etc. when opening the printer object.
3.) sscc.exe, the "Samba Configuration Center", is able to create an
appropriate printcap file. Menu "File" - "Create printcap". Printcap is
located in %ETC%.
Note: If sscc.exe detects that your printcap file was created using CUPS
it wont touch it during installation.
4.) I intend to opensource smbprint.exe at the Samba repository at
netlabs (like the other GUI tools), it was simply forgotten until now,
as the plan always was (and is) to get our Samba working with CUPS.
smbprint.exe was meant to fill the gap until CUPS support for Samba is here.
Hope this helps.
Regards,
Herwig

Thanks for "jumping in" - Your explainations and the light your shed
certainly beat my "muddling around in the dark!" I trust this helps
the original poster.
Paul
--

[Herr Willms]

Am Fri, 23 Apr 2010 15:37:12 UTC, schrieb Herwig Bauernfeind

Post by Herwig Bauernfeind
smbprint checks which printer it should print to and prints the file to
this printer in the OS/2 printing subsystem. Not more, not less. It
%s = "spoolfile including path"
%p = "printerqueue"
%J = "jobname"
%c = "pages"
%z = "jobsize"
The variables are filled with appropriate values from the Samba daemon
when smbprint is executed.

My diagnosis is that this does not happen correctly, otherwise the
actual OS/2 would not complain about an "unknown Job-ID". I guess that
some of the quote characters are forgotten, or vanish by some of those
magic substitution rules of REXX or C.

On the other hand, when I execute smbprint.exe from the command
line, the printer driver does not complain about an "unknown Job-ID",
but does apparently not really get the print file. SMBPRINT.EXE also
deletes the print file when it works on it; maybe it is lost before
the printer driver can get hold of it...

Maybe I should mention that this is pure OS/2 4.5 (or 4.52, the one
found on the eCS 1.0 installtion discs).

Post by Herwig Bauernfeind
The variables are documented in the smb.conf documentation for the print
command, look here
http://samba.org/samba/docs/man/manpages-3/smb.conf.5.html

I'll have a look.

Post by Herwig Bauernfeind
2.) smbprint.exe is not the only possibility to achieve printing
capabilities with Samba. The variables provided by Samba provide a
toolset to deal with.

My alternative would be to leave SAMBA completely out of the
equation, and try a pure TCP/IP LPR/LPD solution, but then,
unfortunately, I don't see (yet) how to configure this.

Post by Herwig Bauernfeind
It is perfectly acceptable to build a print command like in smb.conf
print command = cmd.exe /c copy "%s" LPT2

I tried, and got a system choking which had to be reloaded via a
hard reset.

Post by Herwig Bauernfeind
3.) sscc.exe, the "Samba Configuration Center", is able to create an
appropriate printcap file. Menu "File" - "Create printcap". Printcap is
located in %ETC%.

It can be found in various ETCs... but nevertheless I find this at
the end of the file log.smbd:

------- cut ----------------------
[2010/04/23 10:40:10, 1] lib/util_unistr.c:init_valid_table(260)
could not load C:\APPS\SAMBA/lib/valid.dat
[2010/04/23 10:40:10, 1] lib/util_unistr.c:init_valid_table(262)
creating default valid table

[2010/04/23 10:40:10, 3] printing/pcap.c:pcap_cache_reload(117)
reloading printcap cache
[2010/04/23 10:40:10, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2010/04/23 10:40:10, 3] printing/pcap.c:pcap_cache_reload(223)
reload status: error

[2010/04/23 10:40:10, 3] printing/pcap.c:pcap_cache_reload(117)
reloading printcap cache
[2010/04/23 10:40:10, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2010/04/23 10:40:10, 3] printing/pcap.c:pcap_cache_reload(223)
reload status: error
----------------------- off --------------------------
[extra line breaks added to enhance readability]

Post by Herwig Bauernfeind
Hope this helps.

Not really...


Cheers,
L.W.

-------------------------------------------------------

[Dave Saville]

On Fri, 23 Apr 2010 18:28:58 UTC, "Herr Willms"
<***@domain.invalid> wrote:

<snip>

Post by Herr Willms
My diagnosis is that this does not happen correctly, otherwise the
actual OS/2 would not complain about an "unknown Job-ID". I guess that
some of the quote characters are forgotten, or vanish by some of those
magic substitution rules of REXX or C.

Well with the examples you gave there ought to be nothing the various
shells involved might misinterpret. ie no blanks in names that would
make two parameters if the quotes were lost or special characters that
might confuse the shell.

Unless for some odd reason one of the steps *expects quotes around its
parms and by then they are gone. What happens if you do a CLI one
without quotes?

[Herr Willms]

Am Fri, 23 Apr 2010 19:08:34 UTC, schrieb "Dave Saville"

Post by Dave Saville
Unless for some odd reason one of the steps *expects quotes around its
parms

smbprint.exe requires the paramters enclosed in quotes.

Post by Dave Saville
and by then they are gone. What happens if you do a CLI one
without quotes?

The printer driver or smbprint.exe complains about some parameter
missing.


Cheers,
L.W.

-------------------------------------------------------
Gewinnen und verlieren in einer Diskussion können sich
vernünftigerweise nur beziehen auf Gewinn an Erkenntnis und Verlust
von Vorurteilen. Wer meint, es ginge um Gewinnen von Plätzen in der
Hackordnung und Niedermachen eines "Gegners", sollte sich begraben
lassen.

[Dave Saville]

On Fri, 23 Apr 2010 19:35:29 UTC, "Herr Willms"

Post by Herr Willms
Am Fri, 23 Apr 2010 19:08:34 UTC, schrieb "Dave Saville"

Post by Dave Saville
Unless for some odd reason one of the steps *expects quotes around its
parms

smbprint.exe requires the paramters enclosed in quotes.

Post by Dave Saville
and by then they are gone. What happens if you do a CLI one
without quotes?

The printer driver or smbprint.exe complains about some parameter
missing.

Can you doulbe the quotes up somewhere?