s2.misc,comp.os.os2.networking.misc
s2.setup.misc:372 de.comp.os.os2.misc:1115 comp.os.os2.networking.misc:184
3ca1b5e8
From: "PaulRS"
On Fri, 23 Apr 2010 15:37:12 UTC, Herwig Bauernfeind
wrote:
> Herr Willms schrieb:
> > 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"
> > auf de.comp.os.os2.setup :
> >
> >> 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 fr FxPrint
> >> Error auto-starting fax program
> >> 'D:\COMMS\FAXWORKS\PMFAX.EXE' (x01A2)
> >>
> >> Die Verarbeitung wird beendet
> >> ---------------- off -------------
> >>
> >> Translations:
> >> unbekannt = unknown
> >> fr = 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
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
--
--- Internet Rex 2.31
* Origin: The gateway at Omicron Theta (1:261/20.999)
|
