Hi Bart, thanks for your repply.
Yes, i want to print in the local printer (remote machine). I've been
doing it with vtprint but the results are not acceptable to the
management (i don't believe is a DOSEMU issue, but it would be nice to
have some way to do it in a reliable way with open tools, i wish :)
The smbclient looks ok, i'll do some tests with it if i have enough
time.
I had setup a remote smb printer in the server located in a windows
machine in our network (local network).I'm using FC1 and Samba 3 (comes
with the distribution).
If i do:
lpr file.txt
The smb printer works ok... so i just tried lpr in my .dosemurc.
I tried the following in my ~/.dosemurc with success:
printer { options "-l -P maga" command "lpr" timeout 20 }
maga is the named smb printer added with Fedora Core 1 standard tools.
Where can i find more details about the options of printer config
directive ? (%variables, etc..)
1.- Next i will try to do it over the internet with a radio-modem (real
internet environment).
2.- After that the problem will be "to locate" the printer.
As far as i know it's possible to use Samba features (printing) with IP
addresses instead of names (i'll see).
Then i would need to reconfigure the smb printing queue to the right
address.
I guess i can write a shell script to do that before the client starts
to print.
3.- Fortunately the printers are all the same so we don't need to setup
many different printing queues, we just need to setup n queues of the
same type.
The passthrough printing "should work perfectly" and is very simple to
implement so it's a shame we have to let it go :(
My bet is that if we separate the data flow, printing and displaying, we
might have less problems (not sure) and if one get's corrupted, the
other one is not interfered (separate ways).
FYI the DOS application is writen in QBasic and it's compiled (exe
files). They are linked with btrieve exes(database) for access to
multiple files at the same time.
The application never ran with FreeDOS, i always had to switch to MS
DOS. I always get Far Heap Corruption or low level stuff like that....
Recompiling over FreeDOS with same tools would make a difference ?
Hope this stuff help to anyone else with remote printing problems with
dos applications.
Regards
Guillermo
On Thu, 2004-05-06 at 18:46, Bart Oldeman wrote:
> On Thu, 6 May 2004, Guillermo Gomez wrote:
>
> > My situation is:
> >
> > 1.- DOSEMU is running in Linux Server(FC1) with centralized
> > DOS app.
> > 2.- DOS clients (Windows98) are remote machines (internet)
> >
> > I've been using passthrough printing for around 6 months with non stable
> > results and now we must find a solution quickly.
> >
> > With the latest dosemu version we can customize print command per user.
> >
> > I already ported the whole thing to a devel machine and it's working
> > locally.
> >
> > I thought about two/three options:
> > 1.- smb shared printers
> > printing command used in .dosemurc?
> > 2.- ldp print server on remote machines
> > (know some one for free?)
> > 3.- ipp (??? don't have a clue)
>
> You mean the remote machine should print to the printer connected to the
> client? DOSEMU can't solve that itself. Quite complicated.
>
> You might be able to figure out the hostname who logged in ("who am i"
> may help) and route it via a "smbclient" Linux script which does something
> like
> smbclient //smbserver/printer -c 'print -'
> This should print to the printer share at smbserver from stdin.
> (see "man smbclient")
> I have no idea if that really works but I don't see any reason why not.
>
> Bart
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
