Re: Resources Eating?

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?

[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?

[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]

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?

[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

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

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

passthrough printing

[Guillermo Gomez]

Hi all

I recently installed dosemu and implemented passthrough printing in
Windows machines using AnzioLit which costs something like 30US$ per
licence. Is there any free software to solve that in Windows machine?

My other question is, how can i do the same with a Linux box instead of
Windows (i'm looking for help to kick out Windows from 40 machines in
our company, thanks in advance).

Guillermo
(Caracas)

Re: passthrough printing

[Sergey Suleymanov]

>>>>> Guillermo Gomez writes:

 Guillermo> My other question is, how can i do the same with a Linux
 Guillermo> box instead of Windows (i'm looking for help to kick out
 Guillermo> Windows from 40 machines in our company, thanks in
 Guillermo> advance).

        Why passthrough? LPD is much more convenient. It works for
        Windows-NT/2000 as well. Not to mention linux.

-- 
  Sergey Suleymanov

Re: passthrough printing

[Guillermo Gomez]

Sergey

LPD would work perfectly and would be easy to configure if the IP
address of the remote printer were not changing (dial up links).

Besides that, some remote station are behind NAT (IP masquerade) routers
so ther are not easily reached.

Any suggestions ?

Guillermo

On Thu, 2002-11-21 at 02:21, Sergey Suleymanov wrote:
> >>>>> Guillermo Gomez writes:
> 
>  Guillermo> My other question is, how can i do the same with a Linux
>  Guillermo> box instead of Windows (i'm looking for help to kick out
>  Guillermo> Windows from 40 machines in our company, thanks in
>  Guillermo> advance).
> 
>         Why passthrough? LPD is much more convenient. It works for
>         Windows-NT/2000 as well. Not to mention linux.
> 
> -- 
>   Sergey Suleymanov
> 
> -
> 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