port access problems in 1.1.99.1

port access problems in 1.1.99.1

[Richard White]

Hi:
I'm having what have so far turned out to be insoluble problems with dosemu 
(1.1.99.1) under Redhat 9

1) Current status/environment:
RedHat 9 (kernel 2.4.20), with Dosemu 1.1.99.1 and matching freedos binaries 
installed per instructions, which worked as specified.  To be able to check 
on possible permissions issues, it was installed separately both in my user 
home and in root's. 

~/dosemu/conf/dosemurc has been changed as follows:-
$_com1 = "/dev/ttyS0"
$_printer = "lpr"

After the above, all DOS apps I have tried seem to run nicely EXCEPT in regard 
to port access, as follows:-

1) On trying to print from DOS, (either via e.g. "copy autoexec.bat LPT1:"or 
via DBase III, which otherwise runs correctly, and which prints to LPT1:), we 
get the same error message:
"lpr: unable to print file client-not-found"
This same message appears whether or not I am running as root.

2) On starting an app that needs Com1, we get a message  "error initializing 
serial port"  I do not know where this is generated.  as above, the message is 
the same whether running as root or as a normal user, so permissions may not 
be the problem.  

 I have checked permissions as follows:-
A) /var/lock = 777 (note that in RH9, the only content of /var/lock seems to 
be a 'subsys' directory, which - is this a configuration issue that needs to 
be addressed?  ( i have tried changing the value of ttylocks to match (i.e. 
to /var/lock/subsys), but with no effect)

B) /dev/ttyS0 = 666 
Thus as far as I can see, i have made all the changes that are normally 
suggested, unless I am missing something.

Has anyone seen behaviour like this, and/or an anyone advise how to diagnose 
this please?

thanks!

Richard White

Re: port access problems in 1.1.99.1

[Anderson Pereira Ataides]

Richard,

About the serial port, please check if your port is working (just to be sure 
problem is not with hardware). I say that because running as root it should 
work and it is working with me.

About printer, it is not a dosemu problem. It's cups configuration. You have 
to edit two cups files to solve this problem: mime.types and mime.convs 
(probably these files are under /etc/cups directory). Uncomment the folowing 
line in mime.types:
	application/octet-stream
and in mime.convs:
	application/octet-stream       application/vnd.cups-raw        0       -

Then you have to restart cups. Now you are able to print to lpt.

[]s
Anderson Pereira Ataides




Em Qui 30 Out 2003 14:07, Richard White escreveu:
> Hi:
> I'm having what have so far turned out to be insoluble problems with dosemu
> (1.1.99.1) under Redhat 9
>
> 1) Current status/environment:
> RedHat 9 (kernel 2.4.20), with Dosemu 1.1.99.1 and matching freedos
> binaries installed per instructions, which worked as specified.  To be able
> to check on possible permissions issues, it was installed separately both
> in my user home and in root's.
>
> ~/dosemu/conf/dosemurc has been changed as follows:-
> $_com1 = "/dev/ttyS0"
> $_printer = "lpr"
>
> After the above, all DOS apps I have tried seem to run nicely EXCEPT in
> regard to port access, as follows:-
>
> 1) On trying to print from DOS, (either via e.g. "copy autoexec.bat
> LPT1:"or via DBase III, which otherwise runs correctly, and which prints to
> LPT1:), we get the same error message:
> "lpr: unable to print file client-not-found"
> This same message appears whether or not I am running as root.
>
> 2) On starting an app that needs Com1, we get a message  "error
> initializing serial port"  I do not know where this is generated.  as
> above, the message is the same whether running as root or as a normal user,
> so permissions may not be the problem.
>
>  I have checked permissions as follows:-
> A) /var/lock = 777 (note that in RH9, the only content of /var/lock seems
> to be a 'subsys' directory, which - is this a configuration issue that
> needs to be addressed?  ( i have tried changing the value of ttylocks to
> match (i.e. to /var/lock/subsys), but with no effect)
>
> B) /dev/ttyS0 = 666
> Thus as far as I can see, i have made all the changes that are normally
> suggested, unless I am missing something.
>
> Has anyone seen behaviour like this, and/or an anyone advise how to
> diagnose this please?
>
> thanks!
>
> Richard White
>
> -
> 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: port access problems in 1.1.99.1

[Justin Zygmont]

I am able to use my com port for my modem, but i've had a few other 
obsecure problems that I have to look into.  I think you should be able to 
at least access your com port.


On Thu, 30 Oct 2003, Richard White wrote:

> Hi:
> I'm having what have so far turned out to be insoluble problems with dosemu 
> (1.1.99.1) under Redhat 9
> 
> 1) Current status/environment:
> RedHat 9 (kernel 2.4.20), with Dosemu 1.1.99.1 and matching freedos binaries 
> installed per instructions, which worked as specified.  To be able to check 
> on possible permissions issues, it was installed separately both in my user 
> home and in root's. 
> 
> ~/dosemu/conf/dosemurc has been changed as follows:-
> $_com1 = "/dev/ttyS0"
> $_printer = "lpr"
> 
> After the above, all DOS apps I have tried seem to run nicely EXCEPT in regard 
> to port access, as follows:-
> 
> 1) On trying to print from DOS, (either via e.g. "copy autoexec.bat LPT1:"or 
> via DBase III, which otherwise runs correctly, and which prints to LPT1:), we 
> get the same error message:
> "lpr: unable to print file client-not-found"
> This same message appears whether or not I am running as root.
> 
> 2) On starting an app that needs Com1, we get a message  "error initializing 
> serial port"  I do not know where this is generated.  as above, the message is 
> the same whether running as root or as a normal user, so permissions may not 
> be the problem.  
> 
>  I have checked permissions as follows:-
> A) /var/lock = 777 (note that in RH9, the only content of /var/lock seems to 
> be a 'subsys' directory, which - is this a configuration issue that needs to 
> be addressed?  ( i have tried changing the value of ttylocks to match (i.e. 
> to /var/lock/subsys), but with no effect)
> 
> B) /dev/ttyS0 = 666 
> Thus as far as I can see, i have made all the changes that are normally 
> suggested, unless I am missing something.
> 
> Has anyone seen behaviour like this, and/or an anyone advise how to diagnose 
> this please?
> 
> thanks!
> 
> Richard White
> 
> -
> 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: port access problems in 1.1.99.1

[Dr. Claudia Neumann]

Hi Richard!

Am Freitag, 31. Oktober 2003 02:33 schrieben Sie:
> I have implemented Claudia's suggestion.  There is now a raw printer queue
> installed ('DOSraw') using redhat graphical tools, but it seems to show up
> and be usable by CUPS.  One thing puzzles me about this wueue though.
> Although its type is 'raw print stream' if I print to it from , e.g. Open
> Office, I get readable output (I would have expected a postscript stream
> perhaps).  Don't know if that is important.

No it is not important. CUPS checks, if it is really raw and if it finds it is 
.ps, it gives it to the ps-filter. 

If it doesn't work in DOSemu, perhaps you have to copy the file
"printcap.cups" to "printcap". I don't know if DOSemu needs the file printcap.

Look as well at:
http://www.mail-archive.com/linux-msdos@vger.kernel.org/msg02714.html

cu

Claudia

Re: solved printing problems in 1.1.99.1

[Dr. Claudia Neumann]

Hi Richard,

Am Sonntag, 2. November 2003 07:39 schrieben Sie:
> Dear Claudia:
>
> It looks as if the printing is solved, thanks primarily to you!  I took
> another look at your posting in the mail archive and started from scratch
> again, trying to follow your instructions exactly.  While I have a
> solution,, it was not exactly based on your recommendations, and you may be
> interested and/or know why.  Here is what I did:-
>
> 1) Create a 'raw print stream' printer as you say.  The name of this
> printer seems to be critical.  I have not been able to get any name other
> than "lp" to work.
> Note: The only reason my similar effort of 2 days ago did not work now
> seems to be that i was using (you may remember) the name 'DOSraw'.  Even
> though this name was matched by editing 'dosemurc' of course, it still
> fails.  the only name I have so far been able to get to work is the default
> 'lp'.  Do you have any idea why?  May this mean that there is some built-in
> default name that must be changed via global.conf?

some time ago I experienced the problem, that the "raw" printer in CUPS should 
be the first printer in the line in /etc/printcap and the default printer in 
CUPS. I don't know if this is still necessary.

In my installation with CUPS I name the printer "raw" and tell it to DOSemu 
with
$_printer ="raw"

If this doesn't function as wanted you can use global.conf in /etc/dosemu (as 
root):
copy the file global.conf.example to global.conf and change the lines:

  ipxsupport $_ipxsupport
  novell_hack $_novell_hack
  if (strlen($_printer))
    foreach $xxx ($LIST_DELIM, $_printer)
      $xxx = "'-P", $xxx, "'";
      printer { options $$xxx  command "lpr"  timeout $_printer_timeout }
    done
  endif


to

  ipxsupport $_ipxsupport
  novell_hack $_novell_hack
  if (strlen($_printer))
    foreach $xxx ($LIST_DELIM, $_printer)
      $xxx = "'-P", $xxx, "'";
      printer { options $$xxx  command "lp -d raw"  timeout $_printer_timeout 
}
    done
  endif

and leave out $_printer ="" in $HOME/.dosemurc altogether

> 2) Where I differ with your instructions is that with CUPS under RedHat, at
> least, you should not attempt to copy any printcap files manually (indeed
> /etc/printcap carries warnings against doing so).  As I understand it, the
> master printer config file is /etc/cups/printers.conf.  The CUPS daemon
> creates /etc/printcap from this master, probably at boot time, or whenever
> it is restarted.

Okay, with my Debian installation there was no /etc/printcap only 
/etc/printcap.cups and DOSemu wouldn't print without it.

> 3) Finally, you may remember the 2 suggestions from Anderson that I cc'd to
> you.  They did not solve the problem originally, and after successfully
> following your instructions, I have removed both of those changes,
> apparently without ill-effect, though I am still testing.
>
> Does all the above make sense to you? If so, I thought I would send a
> summary posting to the list as it might help someone else.

As I said before we need a better documentation. I am working on it.

cu

Claudia

Re: port access problems in 1.1.99.1

[Stas Sergeev]

Hello.

Richard White wrote:
> 2) On starting an app that needs Com1, we get a message  "error initializing 
> serial port"  I do not know where this is generated.
Have a look into a -D9+s log, this may
shed some light on the problem. If you
think this is a bug in dosemu, you can
open a bug report and attach the log to
it or post it here if it is small.