s2.misc,comp.os.os2.networking.misc
de.comp.os.os2.misc:1096 comp.os.os2.networking.misc:165
3ca1b5e8
From: "PaulRS"
On Fri, 16 Apr 2010 23:42:49 UTC, "Herr Willms"
wrote:
> 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!
> >
> >
> > 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
. .
--
--- Internet Rex 2.31
* Origin: The gateway at Omicron Theta (1:261/20.999)
|
