Re: DOSemu serial port problem

2003-11-03 Thread Edenyard
On Sun, 2 Nov 2003 10:54:32 -0800 (PST), Robert Komar wrote: The fuser command might help you find out if another process is using /dev/ttyS0. I tried fuser and it reported that the only PID using /dev/ttyS0 was the one that was shown by ps as running dosemu.bin. I have written a very

Re: DOSemu serial port problem

2003-11-02 Thread Dr. Claudia Neumann
Hi Edenyard, Am Freitag, 31. Oktober 2003 17:22 schrieben Sie: Many thanks for your help, Claudia! You suggested: try: $_com1 = /dev/ttyS0 no entries in $_ports and $irqpassing. make sure you have right access to /var/lock or make a directory /home/user/dosemu/lock and say in

Re: DOSemu serial port problem

2003-11-02 Thread Ged Haywood
Hi there, On Sun, 2 Nov 2003, Dr. Claudia Neumann wrote: Do I need something to actually block the rest of the system from taking an interest in /dev/ttyS0, perhaps? What might be trying to use just the RTS line? I am lost here. I don't know what a RTS line is. Request To Send. See

DOSemu serial port problem

2003-10-31 Thread Edenyard
I'd very much appreciate help with this serial port problem: I've installed DOSemu V1.1.99 from source an an Athlon and have got it running quite well on Slackware 9.1 (2.4.22 kernel). It recognises the DOS partition on the HDD, boots from the IBM DOS there and will run programmes like

Re: DOSemu serial port problem

2003-10-31 Thread Edenyard
Many thanks for your help, Claudia! You suggested: try: $_com1 = /dev/ttyS0 no entries in $_ports and $irqpassing. make sure you have right access to /var/lock or make a directory /home/user/dosemu/lock and say in .dosemurc $_ttylocks = /home/user/dosemu/lock I tried that and I