Resources Eating?

Resources Eating?

[Guillermo Gomez]

Hi all

I'm using dosemu to provide remote sessions (telnet) to certain dos
applicattion running in my Linux box.

Each Linux client has a binary dosemu installation in the server (what i
need is separate autoexec.bat for each client) plus a Windows98 DOS
(minnimu).

FreeDOS does not work witht this application written in QBasic (invalid
opcode messages). The application is also based in Novell betrieve
register mannager (sort of data base manager).

The point is that the "program" is eating all the CPU. When one session
is working everything looks fine and when more clients get's connected
the CPU is splitted more or less with equals shares:

Examples:

1 clients --> 90% CPU

2 clients --> +/- 45% each 

The problem is that the server machine start to behave badly (stop
sending data through the telnet server) for no apparent reason in
certain situations.

I already tried the hog thing, it's in 1 (default) so i guess i can't
lower it anymore :(

The last thing i tried was to nice the telnet server to 0 just to see if
that helps.

Running the program is no the big thing, the problem arises when we
print using the passhrough printng features of our telnet client (Anzio
Lite).

I sniffed the traffic and yes, the server jus stop sending data.
Somo simillar sympton happens when starting "btrieve". The screen
freezes but at this point if we press Esc, then the application keeps
going as nothing were happen.

Any help would be appreciate it.

Thanks in advance

Guillermo

Re: Resources Eating?

[Stas Sergeev]

Hello.

Guillermo Gomez wrote:
> The point is that the "program" is eating all the
> CPU.
What dosemu version is that?

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/

Re: Resources Eating?

[Guillermo Gomez]

I'm using binary distribution:

dosmeu-1.0.2.1-bin.tgz

guillermo

On Sun, 2003-12-07 at 12:02, Stas Sergeev wrote:
> Hello.
> 
> Guillermo Gomez wrote:
> > The point is that the "program" is eating all the
> > CPU.
> What dosemu version is that?
> 
> __________________________________
> Do you Yahoo!?
> New Yahoo! Photos - easier uploading and sharing.
> http://photos.yahoo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Resources Eating?

[Dukai Gábor]

Guillermo Gomez wrote:

>>>The point is that the "program" is eating all the
>>>CPU.
>>>      
>>>
I have found the same problem with a Clipper app. I could not solve it. 
It works for me with 5 clients but really slow.
There was a discussion about it on this list.


Dukai

Re: Resources Eating?

[Guillermo Gomez]

Well in my case is not a problem of speed or logic.

More than 10 sessions works, the big issue is printing (passthrough), it
works with "small" documents (up to 4 pages).

So i really can't tell if it's just because the resourses eating or a
networking problem.

Today i tested again (passthrough) and the nice 0 level of the telnet
server did not make any difference.

I included today the flag NO_DELAY for further testing.

The interactivity with the application is ok. What i see is the
developer of the application (or the compiler BC) using a stupid loop
consuming all the CPU cycles just for refreshing the display. However
the logic of the program is not being affected, is the network
transmission, it just stops, could that be a consequence of the lack of
CPU cycles?

Guillermo

On Sun, 2003-12-07 at 13:26, Dukai Gábor wrote:
> Guillermo Gomez wrote:
> 
> >>>The point is that the "program" is eating all the
> >>>CPU.
> >>>      
> >>>
> I have found the same problem with a Clipper app. I could not solve it. 
> It works for me with 5 clients but really slow.
> There was a discussion about it on this list.
> 
> 
> Dukai
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> 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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Resources Eating?

[Stas Sergeev]

Hello.

Guillermo Gomez wrote:
> dosmeu-1.0.2.1-bin.tgz
You are using dosemu version that is 2 years old and
is unsupported for ages. Unless you upgrade, you are
on your own with your problems.
To make you more motivated, I can note that the newer
dosemus are trying much harder to release as many CPU
power as possible to the OS.

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/

Re: Resources Eating?

[Justin Zygmont]

what version of dosemu is this?  Also, the hog thing can go lower, the 
higher number you give it.  Make sure you are using the the latest dosemu, 
1.99.


On 7 Dec 2003, Guillermo Gomez wrote:

> Hi all
> 
> I'm using dosemu to provide remote sessions (telnet) to certain dos
> applicattion running in my Linux box.
> 
> Each Linux client has a binary dosemu installation in the server (what i
> need is separate autoexec.bat for each client) plus a Windows98 DOS
> (minnimu).
> 
> FreeDOS does not work witht this application written in QBasic (invalid
> opcode messages). The application is also based in Novell betrieve
> register mannager (sort of data base manager).
> 
> The point is that the "program" is eating all the CPU. When one session
> is working everything looks fine and when more clients get's connected
> the CPU is splitted more or less with equals shares:
> 
> Examples:
> 
> 1 clients --> 90% CPU
> 
> 2 clients --> +/- 45% each 
> 
> The problem is that the server machine start to behave badly (stop
> sending data through the telnet server) for no apparent reason in
> certain situations.
> 
> I already tried the hog thing, it's in 1 (default) so i guess i can't
> lower it anymore :(
> 
> The last thing i tried was to nice the telnet server to 0 just to see if
> that helps.
> 
> Running the program is no the big thing, the problem arises when we
> print using the passhrough printng features of our telnet client (Anzio
> Lite).
> 
> I sniffed the traffic and yes, the server jus stop sending data.
> Somo simillar sympton happens when starting "btrieve". The screen
> freezes but at this point if we press Esc, then the application keeps
> going as nothing were happen.
> 
> Any help would be appreciate it.
> 
> Thanks in advance
> 
> Guillermo
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: Resources Eating?

[Guillermo Gomez]

Got the message, please point me out where's the bin package like the
one i use to work with (i'll chek the website anyway).

I downloaded the latest source code and compiled it. Great but my
problem now moves to the fact that any single client needs a separate
autoexec.bat as well as separate "login" profile.

What i'm doing is:

1.- Client telnet the linux box
2.- Client logs in with bash shell
3.- .bash_profile takes care of auto-launching the dosemu
4.- autoexec.bat takes cares of auto-launching the app
5.- As the app quits, the shell autoquits just after
	(no open shell for the user)

How u do suggest i could accomplish the same effect with a "system" wide
installation like the one resulted from compiling from source code?

Just as i reminder, i did tried the latest source code of DOSEMU and
FreeDOS (bin.ziped file) and the app program simply does not work (i
must use MS DOS).

If i can have a bin package like the old one i could just do the same
but with the newer version and then i might have a chance.

Thanks

Guillermo

On Sun, 2003-12-07 at 15:20, Stas Sergeev wrote:
> Hello.
> 
> Guillermo Gomez wrote:
> > dosmeu-1.0.2.1-bin.tgz
> You are using dosemu version that is 2 years old and
> is unsupported for ages. Unless you upgrade, you are
> on your own with your problems.
> To make you more motivated, I can note that the newer
> dosemus are trying much harder to release as many CPU
> power as possible to the OS.
> 
> __________________________________
> Do you Yahoo!?
> New Yahoo! Photos - easier uploading and sharing.
> http://photos.yahoo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Resources Eating?

[Justin Zygmont]

> What i'm doing is:
> 
> 1.- Client telnet the linux box
> 2.- Client logs in with bash shell
> 3.- .bash_profile takes care of auto-launching the dosemu
> 4.- autoexec.bat takes cares of auto-launching the app
> 5.- As the app quits, the shell autoquits just after
> 	(no open shell for the user)

what if they hit CRTL-C ? :)  you should be able to set their shell to 
dosemu.bin, and see if that works ok.  Can you make a seperate login for 
each different instance of dosemu, each with their own copy of dosemu, 
that way there is no need for a seperate autoexec.bat.  You must have a 
copy of real MSDOS don't you?

> How u do suggest i could accomplish the same effect with a "system" wide
> installation like the one resulted from compiling from source code?
> 
> Just as i reminder, i did tried the latest source code of DOSEMU and
> FreeDOS (bin.ziped file) and the app program simply does not work (i
> must use MS DOS).
> 
> If i can have a bin package like the old one i could just do the same
> but with the newer version and then i might have a chance.
> 
> Thanks
> 
> Guillermo
> 
> On Sun, 2003-12-07 at 15:20, Stas Sergeev wrote:
> > Hello.
> > 
> > Guillermo Gomez wrote:
> > > dosmeu-1.0.2.1-bin.tgz
> > You are using dosemu version that is 2 years old and
> > is unsupported for ages. Unless you upgrade, you are
> > on your own with your problems.
> > To make you more motivated, I can note that the newer
> > dosemus are trying much harder to release as many CPU
> > power as possible to the OS.
> > 
> > __________________________________
> > Do you Yahoo!?
> > New Yahoo! Photos - easier uploading and sharing.
> > http://photos.yahoo.com/
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> > the body of a message to majordomo@vger.kernel.org
> > 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 majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: Resources Eating?

[Guillermo Gomez]

Well i'll check out what happens if they hit Ctrl-C, as far as i
remember is just does nothing (don't gives back the shell).

The need for separate autoexec.bat is "customisation", all clients needs
a different paths and this is how the app works in order to account
users: must have separate autoexec.bat :(

Anyway the dosemu as shell login is a geat idea, i'll try it but there
is a little requirement for that:

Multiple login not allowed !!!

This is an app requirement from the app (again).

I'm taking care of this in .bash_profile (or .bashrc).

How could we avoid multiple login using dosemu as login shell?

I guess there must something in a lower level regarding the "login"
process.

Guillermo



On Sun, 2003-12-07 at 18:51, Justin Zygmont wrote:
> > What i'm doing is:
> > 
> > 1.- Client telnet the linux box
> > 2.- Client logs in with bash shell
> > 3.- .bash_profile takes care of auto-launching the dosemu
> > 4.- autoexec.bat takes cares of auto-launching the app
> > 5.- As the app quits, the shell autoquits just after
> > 	(no open shell for the user)
> 
> what if they hit CRTL-C ? :)  you should be able to set their shell to 
> dosemu.bin, and see if that works ok.  Can you make a seperate login for 
> each different instance of dosemu, each with their own copy of dosemu, 
> that way there is no need for a seperate autoexec.bat.  You must have a 
> copy of real MSDOS don't you?
> 
> >

Re: Resources Eating?

[Stas Sergeev]

Hello.

Guillermo Gomez wrote:
> Got the message, please point me out where's the bin
> package like the one i use to work with (i'll chek
> the website anyway).
> I downloaded the latest source code and compiled it.
There is a script there dist/mkbindist. I don't
know why it is still not executed automatically by
"make", which will make it more usefull, but you can
use it manually.

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/

Re: Resources Eating?

[Guillermo Gomez]

Hi 

Sorry for the stupid question, the bins were there just for me to
download them...

I already made the same procedure as i did with the previous version i
used.

1.- mkdir mydos
2.- copy both zipped files into mydos (dosemu/freedos)
3.- unzipped them
4.- i substitute freedos content with MS DOS (from W98) bin files
5.- Got the readlink compiled to make the dosemu script work
6.- Got the message running with the new version as exactly before
	Each user with a copy of dosemu and dos.
	Each one with an autoexec.bat and so on
GOOD NEWS
	The application behaves better with this version
	Now with the application "doing nothing", the CPU is sleeping :)
	When the app actually does something, the CPU usage jumps
	Summary: the CPU is used when the app requires it

GREAT but..... there's always a but....

Remember my problem was the passthrough printig, well i can't make it
work now :/

With the previous version, the modified section at global.conf as:

if (strlen($_printer))
      foreach $xxx ($LIST_DELIM, $_printer)
        ## $xxx = "' %s '";
        ## printer { options "' %s '" command "cat - | ansiprint "  
        printer { options '%s' command 'vtprint -fq' }
      done
endif

made the trick to return the print to the stdout filtered through the
vtprint program.

Now i made the same changes to my global.conf but i does not follow my
directions, it alwasy tries to do lp and reports the local lpd daemon
not responding (there's no printer configured).

Any suggestion to make this work?

Hoe the timeout parameter in the print command could be related to my
issue with large documents?

Thanks

Guillermo




	
On Mon, 2003-12-08 at 16:25, Stas Sergeev wrote:
> Hello.
> 
> Guillermo Gomez wrote:
> > Got the message, please point me out where's the bin
> > package like the one i use to work with (i'll chek
> > the website anyway).
> > I downloaded the latest source code and compiled it.
> There is a script there dist/mkbindist. I don't
> know why it is still not executed automatically by
> "make", which will make it more usefull, but you can
> use it manually.
> 
> __________________________________
> Do you Yahoo!?
> New Yahoo! Photos - easier uploading and sharing.
> http://photos.yahoo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Resources Eating?

[Bart Oldeman]

On 8 Dec 2003, Guillermo Gomez wrote:

> Well i found the problem is that the global.conf is "builtin" is taken
> precdence and my modified global.conf is not doing anything.
>
> I'm trying to use the -F option with no luck..How can i dump the
> "built-in" global.conf to tweak it using option -F.

Presently only by editing etc/global.conf in the source code and
recompiling. dosemu.bin in the bindist can be replaced by the one you
obtain that way.

> My installation is working ok without the -F option.

it's on my list to fix for 1.2.0. -F should work. The problem is here:

In file included from
dosemu/dosemu-cvs/dosemu-1.1.99.1/etc/global.conf:212
Error in : (line 212) parse error
Error in : (line 556) parse error
Error in : (line 556) expected 'emulated' or 'native'
3 error(s) detected while parsing the configuration-file

by the way, because your problem came up in different variations before
the CVS version (and 1.2.0-final when released) allow you to do what you
want in dosemu.conf or ~/.dosemurc:

# list of (/etc/printcap) printer names to appear as LPT1, LPT2, LPT3
# (not all are needed, empty for none). Default: "lp"

# $_printer = "lp"

# Print command to use. Default: "lpr", for "lpr -P printername".
# Sometimes (with CUPS) "lpr -l" is necessary.

# $_printer_command = "lpr"

Bart

[snip]

Re: Resources Eating?

[Guillermo Gomez]

Well i found the problem is that the global.conf is "builtin" is taken
precdence and my modified global.conf is not doing anything.

I'm trying to use the -F option with no luck..How can i dump the
"built-in" global.conf to tweak it using option -F.

My installation is working ok without the -F option.

Guillermo

On Mon, 2003-12-08 at 19:48, Guillermo Gomez wrote:
> Hi 
> 
> Sorry for the stupid question, the bins were there just for me to
> download them...
> 
> I already made the same procedure as i did with the previous version i
> used.
> 
> 1.- mkdir mydos
> 2.- copy both zipped files into mydos (dosemu/freedos)
> 3.- unzipped them
> 4.- i substitute freedos content with MS DOS (from W98) bin files
> 5.- Got the readlink compiled to make the dosemu script work
> 6.- Got the message running with the new version as exactly before
> 	Each user with a copy of dosemu and dos.
> 	Each one with an autoexec.bat and so on
> GOOD NEWS
> 	The application behaves better with this version
> 	Now with the application "doing nothing", the CPU is sleeping :)
> 	When the app actually does something, the CPU usage jumps
> 	Summary: the CPU is used when the app requires it
> 
> GREAT but..... there's always a but....
> 
> Remember my problem was the passthrough printig, well i can't make it
> work now :/
> 
> With the previous version, the modified section at global.conf as:
> 
> if (strlen($_printer))
>       foreach $xxx ($LIST_DELIM, $_printer)
>         ## $xxx = "' %s '";
>         ## printer { options "' %s '" command "cat - | ansiprint "  
>         printer { options '%s' command 'vtprint -fq' }
>       done
> endif
> 
> made the trick to return the print to the stdout filtered through the
> vtprint program.
> 
> Now i made the same changes to my global.conf but i does not follow my
> directions, it alwasy tries to do lp and reports the local lpd daemon
> not responding (there's no printer configured).
> 
> Any suggestion to make this work?
> 
> Hoe the timeout parameter in the print command could be related to my
> issue with large documents?
> 
> Thanks
> 
> Guillermo
> 
> 
> 
> 
> 	
> On Mon, 2003-12-08 at 16:25, Stas Sergeev wrote:
> > Hello.
> > 
> > Guillermo Gomez wrote:
> > > Got the message, please point me out where's the bin
> > > package like the one i use to work with (i'll chek
> > > the website anyway).
> > > I downloaded the latest source code and compiled it.
> > There is a script there dist/mkbindist. I don't
> > know why it is still not executed automatically by
> > "make", which will make it more usefull, but you can
> > use it manually.
> > 
> > __________________________________
> > Do you Yahoo!?
> > New Yahoo! Photos - easier uploading and sharing.
> > http://photos.yahoo.com/
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> > the body of a message to majordomo@vger.kernel.org
> > 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 majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Resources Eating?

[Guillermo Gomez]

Thanks Bart

I was killing myself trying to make it work...i saw many times the
'emulated' or 'native' message :-D

I'll try further with source code and hope to figure this out asap.

Guillermo

On Mon, 2003-12-08 at 20:20, Bart Oldeman wrote:
> On 8 Dec 2003, Guillermo Gomez wrote:
> 
> > Well i found the problem is that the global.conf is "builtin" is taken
> > precdence and my modified global.conf is not doing anything.
> >
> > I'm trying to use the -F option with no luck..How can i dump the
> > "built-in" global.conf to tweak it using option -F.
> 
> Presently only by editing etc/global.conf in the source code and
> recompiling. dosemu.bin in the bindist can be replaced by the one you
> obtain that way.
> 
> > My installation is working ok without the -F option.
> 
> it's on my list to fix for 1.2.0. -F should work. The problem is here:
> 
> In file included from
> dosemu/dosemu-cvs/dosemu-1.1.99.1/etc/global.conf:212
> Error in : (line 212) parse error
> Error in : (line 556) parse error
> Error in : (line 556) expected 'emulated' or 'native'
> 3 error(s) detected while parsing the configuration-file
> 
> by the way, because your problem came up in different variations before
> the CVS version (and 1.2.0-final when released) allow you to do what you
> want in dosemu.conf or ~/.dosemurc:
> 
> # list of (/etc/printcap) printer names to appear as LPT1, LPT2, LPT3
> # (not all are needed, empty for none). Default: "lp"
> 
> # $_printer = "lp"
> 
> # Print command to use. Default: "lpr", for "lpr -P printername".
> # Sometimes (with CUPS) "lpr -l" is necessary.
> 
> # $_printer_command = "lpr"
> 
> Bart
> 
> [snip]
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Resources Eating?

[Brett I. Holcomb]

Just to make sure I understand this:

1.  /etc/global.conf
A. Don't mess with /etc/global.conf because you can break things.
B.  I found my install left the /etc/global.conf.example and did not create a 
/etc/global.conf.  Would that have hurt me or is what's in the example file 
built into the dosemu.bin.

2.  /etc/dosemu.conf and /etc/dosemu.users is what we work with to change 
global settings - correct?

3.  ~/.dosemurc is used for users who want to set up their own special 
settings  - correct?

Thank you.

On Monday 08 December 2003 19:20, Bart Oldeman wrote:
> On 8 Dec 2003, Guillermo Gomez wrote:
> > Well i found the problem is that the global.conf is "builtin" is taken
> > precdence and my modified global.conf is not doing anything.
> >
> > I'm trying to use the -F option with no luck..How can i dump the
> > "built-in" global.conf to tweak it using option -F.
>
> Presently only by editing etc/global.conf in the source code and
> recompiling. dosemu.bin in the bindist can be replaced by the one you
> obtain that way.
>

Re: Resources Eating?

[Guillermo Gomez]

Hi

I compiled from source including global.conf modified as...

...

if (strlen($_printer))
    foreach $xxx ($LIST_DELIM, $_printer)
##   $xxx = "'-P", $xxx, "'";
##   printer { options $$xxx  command "lpr"  timeout $_printer_timeout }
     printer { options '%s' command 'vtprint -fq' }
   done
endif

...

But vtprint is reporting the following message

vtprint: Couldn't open %s for reading.-

What i'm doing wrong now?

Guillermo


On Mon, 2003-12-08 at 20:20, Bart Oldeman wrote:
> On 8 Dec 2003, Guillermo Gomez wrote:
> 
> > Well i found the problem is that the global.conf is "builtin" is taken
> > precdence and my modified global.conf is not doing anything.
> >
> > I'm trying to use the -F option with no luck..How can i dump the
> > "built-in" global.conf to tweak it using option -F.
> 
> Presently only by editing etc/global.conf in the source code and
> recompiling. dosemu.bin in the bindist can be replaced by the one you
> obtain that way.
> 
> > My installation is working ok without the -F option.
> 
> it's on my list to fix for 1.2.0. -F should work. The problem is here:
> 
> In file included from
> dosemu/dosemu-cvs/dosemu-1.1.99.1/etc/global.conf:212
> Error in : (line 212) parse error
> Error in : (line 556) parse error
> Error in : (line 556) expected 'emulated' or 'native'
> 3 error(s) detected while parsing the configuration-file
> 
> by the way, because your problem came up in different variations before
> the CVS version (and 1.2.0-final when released) allow you to do what you
> want in dosemu.conf or ~/.dosemurc:
> 
> # list of (/etc/printcap) printer names to appear as LPT1, LPT2, LPT3
> # (not all are needed, empty for none). Default: "lp"
> 
> # $_printer = "lp"
> 
> # Print command to use. Default: "lpr", for "lpr -P printername".
> # Sometimes (with CUPS) "lpr -l" is necessary.
> 
> # $_printer_command = "lpr"
> 
> Bart
> 
> [snip]
> 

Re: Resources Eating?

[Bart Oldeman]

On 8 Dec 2003, Guillermo Gomez wrote:

> I compiled from source including global.conf modified as...
>
> ...
>
> if (strlen($_printer))
>     foreach $xxx ($LIST_DELIM, $_printer)
> ##   $xxx = "'-P", $xxx, "'";
> ##   printer { options $$xxx  command "lpr"  timeout $_printer_timeout }
>      printer { options '%s' command 'vtprint -fq' }
>    done
> endif
>
> ...
>
> But vtprint is reporting the following message
>
> vtprint: Couldn't open %s for reading.-
>
> What i'm doing wrong now?

remove the %s. The command should read from a pipe now, instead of
printing a temporary file, and that's why the %s is obsolete.

Bart

Re: Resources Eating?

[Bart Oldeman]

On Mon, 8 Dec 2003, Brett I. Holcomb wrote:

> Just to make sure I understand this:
>
> 1.  /etc/global.conf
> A. Don't mess with /etc/global.conf because you can break things.

yes. its main job is to parse dosemu.conf. However every once in a while
we encounter situations that are impossible to configure with dosemu.conf.

> B.  I found my install left the /etc/global.conf.example and did not create a
> /etc/global.conf.  Would that have hurt me or

no

> is what's in the example file built into the dosemu.bin.

yes

>
> 2.  /etc/dosemu.conf and /etc/dosemu.users is what we work with to change
> global settings - correct?

yes. These files can also live in /etc/dosemu.

dosemu.users is optional. Only if certain users are allowed to use direct
hardware i/o ($_ports and so on) through a suid-root dosemu.bin or dosemu
-s with sudo, you'll need to edit it. As far as such access is
concerned, only console graphics works with a privileged dosemu by
default.

dosemu.conf lives in the same directory as dosemu.users.

> 3.  ~/.dosemurc is used for users who want to set up their own special
> settings  - correct?

yes. Just like /etc/profile vs. /etc/.profile. Some settings in .dosemurc
are ignored for security reasons.

Bart

Passthrough Printing

[Guillermo Gomez]

Ok, finally i made it through (thanks guys)

The pastrough printing is working for anyone considering it as an option
for the remote access to a DOS application with the actual source of
dosemu (dosemu-1.1.99.1])

Summary of my procedure:

1.- Download stable dosemu source code
2.- Download bin/zip freedos
3.- Rename freedos zip according INSTALL suggestions and moved
    into dosemu source tree
4.- Configure
5.- make
6.- make install

Well, in order to make the passthrough printing work i had to tweak
global.conf and because in this procedure global.conf get's compiled in
binary of dosemu, i follow:

7.- Get rid of bin/zip freedos file in the source tree of dosemu
    to avoid reinstalling freedos
8.- "Tweak global.conf in dosemu source tree (etc/global.conf)"
9.- make && make install
10.- Test 
11.- Goto 8 untill success :)

My successful lines in global.conf are:
(first locate the block then edit)
....
if (strlen($_printer))
  foreach $xxx ($LIST_DELIM, $_printer)
    ## $xxx = "'-P", $xxx, "'";
    ## printer { options $$xxx  command "lpr"  timeout $_printer_timeout
}
    printer { options '' command ' vtprint -fq ' timeout 1 }
  done
endif
....

Please note i'm using vtprint (there's also ansiprint) print filtering
for "printing escape sequence compliant terminals or emulators".

With this procedure the print effect from DOS application with default
settings (assuming your boot dir and dos is working) it's to send the
ASCII file with the correct escape sequence in order to print in a
locally attached printer to the terminal or emulator (in my case we are
using Anzio Lite in Windows machines as the clients).

Be carefull on what your print ! It's for ASCII text not for graphics ;)

Bart has wrote and email saying this feature will be easy to do with the
final release of 2.0 dosemu and that it can be used with the actual cvs
version but if u don't want get into this just because you want to waite
for the release, this procedure is a workaround for this particular
situation.

However, i have a problem, a network problem (think so):

1.- I made tests using telnet localhost, 30 printings in a row worked ok
with each print job as 19 pages long.Cool :)

2.- If i do the same but remotely, it looks like it starts to "random",
1 of 3, 2 of 4, with no pattern, some came out correctly and some not,
"without TCP errors", no TCP sequence problems, no TCP retransmission,
it just stops sending the data like TCP never got it.

I concluded it's a network problem but i don't know how to start to
debug it , i should start being sure the print job is being queued in
the TCP socket, how could i do that? where the info could being lost?

I sniffed the telnet traffic and there was no TCP errors, no
retransmission, nothing pointing me where the problem is.

Someone believes it could come from dosemu?

Any suggestions?

Regards

Guillermo



On Mon, 2003-12-08 at 22:23, Guillermo Gomez wrote:
> Hi
> 
> I compiled from source including global.conf modified as...
> 
> ...
> 
> if (strlen($_printer))
>     foreach $xxx ($LIST_DELIM, $_printer)
> ##   $xxx = "'-P", $xxx, "'";
> ##   printer { options $$xxx  command "lpr"  timeout $_printer_timeout }
>      printer { options '%s' command 'vtprint -fq' }
>    done
> endif
> 
> ...
> 
> But vtprint is reporting the following message
> 
> vtprint: Couldn't open %s for reading.-
> 
> What i'm doing wrong now?
> 
> Guillermo
> 
> 
> On Mon, 2003-12-08 at 20:20, Bart Oldeman wrote:
> > On 8 Dec 2003, Guillermo Gomez wrote:
> > 
> > > Well i found the problem is that the global.conf is "builtin" is taken
> > > precdence and my modified global.conf is not doing anything.
> > >
> > > I'm trying to use the -F option with no luck..How can i dump the
> > > "built-in" global.conf to tweak it using option -F.
> > 
> > Presently only by editing etc/global.conf in the source code and
> > recompiling. dosemu.bin in the bindist can be replaced by the one you
> > obtain that way.
> > 
> > > My installation is working ok without the -F option.
> > 
> > it's on my list to fix for 1.2.0. -F should work. The problem is here:
> > 
> > In file included from
> > dosemu/dosemu-cvs/dosemu-1.1.99.1/etc/global.conf:212
> > Error in : (line 212) parse error
> > Error in : (line 556) parse error
> > Error in : (line 556) expected 'emulated' or 'native'
> > 3 error(s) detected while parsing the configuration-file
> > 
> > by the way, because your problem came up in different variations before
> > the CVS version (and 1.2.0-final when released) allow you to do what you
> > want in dosemu.conf or ~/.dosemurc:
> > 
> > # list of (/etc/printcap) printer names to appear as LPT1, LPT2, LPT3
> > # (not all are needed, empty for none). Default: "lp"
> > 
> > # $_printer = "lp"
> > 
> > # Print command to use. Default: "lpr", for "lpr -P printername".
> > # Sometimes (with CUPS) "lpr -l" is necessary.
> > 
> > # $_printer_command = "lpr"
> > 
> > Bart
> > 
> > [snip]
> > 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html