Three major questions.

Three major questions.

[Boris Reisig]

I am running dosemu 1.1.5.6 and would like to see if it is possible.

1) To get rid splash screen "Now type ENTER to start DOSEMU" and
automatically start dosemu without hitting a key.

2) Running a dos program directly from the linux prompt and exiting back
into linux after it is done.

3) To be able to turn a comport into a telnet port. This would be perfect
for BBS software if I could turn the com ports into telnet ports. For
example. If I connect to my box on port (for example) 5000, Dosemu would
redirect that as com1, port 5001 would be com2, etc. Any chance of this?

Re: Three major questions.

[Ralph Alvy]

Boris Reisig wrote:

> I am running dosemu 1.1.5.6 and would like to see if it is possible.
> 
> 1) To get rid splash screen "Now type ENTER to start DOSEMU" and
> automatically start dosemu without hitting a key.

From the X desktop, run xdosemu instead of dosemu.

> 
> 2) Running a dos program directly from the linux prompt and exiting back
> into linux after it is done.

From the desktop, run 'xdosemu myapp' where myapp is in your DOS path.

RE: Three major questions.

[administrator]

>I am running dosemu 1.1.5.6 and would like to see if it is possible.

>1) To get rid splash screen "Now type ENTER to start DOSEMU" and
>automatically start dosemu without hitting a key.

I will second this request.....
  -quiet   should take you straight to the prompt

>2) Running a dos program directly from the linux prompt and exiting back
>into linux after it is done.

You can do this with a simple bash script if we can take care of
problem number 1 above and 4 below.

>3) To be able to turn a comport into a telnet port. This would be perfect
>for BBS software if I could turn the com ports into telnet ports. For
>example. If I connect to my box on port (for example) 5000, Dosemu would
>redirect that as com1, port 5001 would be com2, etc. Any chance of this?

This would be more useful if the virtual com ports could have
a switch to turn on the virtual fossil driver/interface as well.

There are ways around this though....
I have a telnetable PCBoard running fine under 1.1.5.6
but it took a lot of " work around ".

4)
Which brings me to my own issue with dosemu the -U switch
dosemu -U pipein:pipeout    does not work.
Dosemu will take "whatever" command you send to pipein and
pushes   'Command "whatever" not found'  out  pipeout.

If anyone has ever gotten pipein to work correctly, please provide the
version number of the functional dosemu and any undocumented
steps required to make it work.

Re: Three major questions.

[Ryan Underwood]

Hi,

On Sat, Sep 06, 2003 at 05:03:05PM +0000, administrator wrote:
> 
> >3) To be able to turn a comport into a telnet port. This would be perfect
> >for BBS software if I could turn the com ports into telnet ports. For
> >example. If I connect to my box on port (for example) 5000, Dosemu would
> >redirect that as com1, port 5001 would be com2, etc. Any chance of this?
> 
> This would be more useful if the virtual com ports could have
> a switch to turn on the virtual fossil driver/interface as well.

Why not just run fossil.com in your autoexec.bat?

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

RE: Three major questions.

[Bart Oldeman]

On Sat, 6 Sep 2003, administrator wrote:

> >I am running dosemu 1.1.5.6 and would like to see if it is possible.
>
> >1) To get rid splash screen "Now type ENTER to start DOSEMU" and
> >automatically start dosemu without hitting a key.
>
> I will second this request.....
>   -quiet   should take you straight to the prompt

I wonder why it's not working for you two. dosemu and xdosemu create files
~/.dosemu/stamp-[x]dosemu the first time which prevent the splash message
being shown for all subsequent DOSEMU runs. At least, they do for me.
Have a look at `which dosemu`. There should be lines such as
if [ -z "$QUIET" -a ! -f $HOME/.dosemu/stamp-xdosemu ]; then

> >2) Running a dos program directly from the linux prompt and exiting back
> >into linux after it is done.
>
> You can do this with a simple bash script if we can take care of
> problem number 1 above and 4 below.

dosemu [-E] dos-command; see "man dosemu.bin" or the example in "man
dosemu". Alternatively use -input

> 4)
> Which brings me to my own issue with dosemu the -U switch
> dosemu -U pipein:pipeout    does not work.
> Dosemu will take "whatever" command you send to pipein and
> pushes   'Command "whatever" not found'  out  pipeout.
>
> If anyone has ever gotten pipein to work correctly, please provide the
> version number of the functional dosemu and any undocumented
> steps required to make it work.

-U is a programmer's tool; not so much a user's tool
" This option should therefor only used by frontends (such as kdos),
which first create the proper named  pipes  and  then launch DOSEMU."
"A tiny control terminal, which can serve as example, is the supplied
dosctrl programm."

Well kdos (KDE DOSEMU) never really became something I guess, but
dosctrl

dosctrl is in src/tools/periph

so this works

$ cd src/tools/periph
$ mkfifo fdin fdout
$ xdosemu -Ufdin:fdout &
$ ./dosctrl fdin fdout
help
ack [{on|off}]      get/set user hook handshake acknowledge
hello               just for testing, any kinf of argument
kill                kill the dosemu session from inside
version             prints the dosemu version
keystroke <strokes> insert keystrokes into the DOS session
log [debugflags]    get/set debugflags which control log output
hog [value]         get/set the HogThreshold
boot [{on|off}]     get/set the mode of the vbootfloppy
xmode [<args>]      set X parameters, without args gives help
lredir n: dir [ro]  redirect directory 'dir' to DOS drive 'n:'
help                this screen
ecpu [{on|off}]     get/set cpuemu
config              print the current configuration
version
dosemu-1.1.5.7
^C
$

Bart

RE: Three major questions.

[Cheryl Homiak]

Hmmm!!!!
I also get that screen reminding me how i can have home as d: and telling
me to hit enter for dosemu or control-c to cancel.



-- 
Cheryl

RE: Three major questions.

[administrator]

> >3) To be able to turn a comport into a telnet port. This would be perfect
> >for BBS software if I could turn the com ports into telnet ports. For
> >example. If I connect to my box on port (for example) 5000, Dosemu would
> >redirect that as com1, port 5001 would be com2, etc. Any chance of this?
>
> This would be more useful if the virtual com ports could have
> a switch to turn on the virtual fossil driver/interface as well.

Why not just run fossil.com in your autoexec.bat?

That is a valid way to do it.
But it is dependent on the "virtual serial interface" being able to
successfully "fake out" the fossil driver. I am guessing it is easier
to present a fossil interface directly to the app.

I envision it would work something like this....
dosemu  --make_virtual_port  com=5  fossil=off  uart=16550  pipe=myfifo

this way if you wanted to use an external fossil driver, you could but
hopefully the implementation would be so good, it would not be necessary.

Re: Three major questions.

[Stas Sergeev]

[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]

Hello.

Boris Reisig wrote:
> 1) To get rid splash screen "Now type ENTER to start DOSEMU" and 
> automatically start dosemu without hitting a key.
"dosemu -quiet" or don't use the dosemu
startup script at all.

> 3) To be able to turn a comport into a telnet port. This would be 
> perfect for BBS software if I could turn the com ports into telnet
> ports.
You probably mean a TCP port here.

> For example. If I connect to my box on port (for example) 5000,
> Dosemu would redirect that as com1, port 5001 would be com2, etc.
> Any chance of this?
This might be very easy as dosemu (since
very recently) can use a pseudo-terminals as
a serial ports.
I've just tried one possibility that came to
my mind first
(example of redirecting COM2 to TCP port 5000
as I see it, follows):

1. Wrote a small program "datacopy" (attached).
[Duh, something like that might be somewhere
among the generic Unix utilities, so I am sure
I've reinvented the wheel by writing it. Can
anyone point me the analog of such a prog?]

2. Configured dosemu to use a pseudo-terminal
as a serial port:
$_com2="/dev/ttyp1"

3. Started the TCP port listener that way:
faucet 5000 --in --out datacopy /dev/ptyp1
(note the difference between "ttyp1" in
step 2 and "ptyp1" here)

4. Opened a connection to that port with a
telnet:
telnet localhost 5000

5. Started dosemu.

6. Started the terminal program on COM2 and got
the communication between the DOS terminal prog
and the telnet session to ensure that the port is
redirected successfully.

"faucet" is from a "netpipes" package, but you
can also set up the [x]inetd for that work (but
using faucet is simpler).

I have never used that for anything real so I don't
know how good it suits the real life needs.
If that works for someone here, or if something is
still missing, or if there is a better solution,
please let me know. I think the current documentation
doesn't have a clear solution for that, so it must
be worked out and documented.

[-- Attachment #2: datacopy.c --]
[-- Type: text/plain, Size: 729 bytes --]

#include <stdio.h>
#include <fcntl.h>
#include <unistd.h>
#include <sys/time.h>
#include <sys/types.h>

int main(int argc, char *argv[])
{
   char buf[1600];
   int f,l;
   fd_set fds;
 
   if(argc < 2) {
      printf("Usage: datacopy file_name\n");
      return 1;
   }

   f = open(argv[1], O_RDWR);

   while(1){
	FD_ZERO(&fds);
        FD_SET(STDIN_FILENO, &fds);
        FD_SET(f, &fds);

	select(f + 1, &fds, NULL, NULL, NULL);

	if( FD_ISSET(f, &fds) ) {
	   l = read(f,buf,sizeof(buf));
	   if (l <= 0)
	      break;
           write(STDOUT_FILENO,buf,l);
	}
	if( FD_ISSET(STDIN_FILENO, &fds) ) {
	   l = read(STDIN_FILENO,buf,sizeof(buf));
	   if (l <= 0)
	      break;
           write(f,buf,l);
	}
   }
   return 0;
}

Re: Three major questions.

[Matthew Clarke]

dimanche, le 7 septembre, 2003, Stas Sergeev nous a dit ceci:

> Hello.

[ snip ]

> 1. Wrote a small program "datacopy" (attached).
> [Duh, something like that might be somewhere
> among the generic Unix utilities, so I am sure
> I've reinvented the wheel by writing it. Can
> anyone point me the analog of such a prog?]

The package/program "socat" might fit the bill.

	http://www.dest-unreach.org/socat/

[ chop ]

Matt.
-- 
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
				-- Richard P. Feynman

Re: Three major questions.

[Stas Sergeev]

Hello.

Matthew Clarke wrote:
>>1. Wrote a small program "datacopy" (attached).
>>[Duh, something like that might be somewhere
>>among the generic Unix utilities, so I am sure
>>I've reinvented the wheel by writing it. Can
>>anyone point me the analog of such a prog?]
> The package/program "socat" might fit the bill.
> 	http://www.dest-unreach.org/socat/
Thanks, ultimately great program!
Actually it absoletes everything I've said yesterday.
With socat, it is enough to do only:
socat tcp-l:5000 PTY,link=/tmp/vmodem
and set $_com2="/tmp/vmodem" and that's it.
Easier than I could ever imagine :)

Re: Three major questions.

[Ryan Underwood]

Hi,

On Sat, Sep 06, 2003 at 07:40:47PM +0000, administrator wrote:
> > >3) To be able to turn a comport into a telnet port. This would be perfect
> > >for BBS software if I could turn the com ports into telnet ports. For
> > >example. If I connect to my box on port (for example) 5000, Dosemu would
> > >redirect that as com1, port 5001 would be com2, etc. Any chance of this?
> >
> > This would be more useful if the virtual com ports could have
> > a switch to turn on the virtual fossil driver/interface as well.
> 
> Why not just run fossil.com in your autoexec.bat?
> 
> That is a valid way to do it.
> But it is dependent on the "virtual serial interface" being able to
> successfully "fake out" the fossil driver. I am guessing it is easier
> to present a fossil interface directly to the app.

Well, I was meaning the DOSEMU built in fossil interface.  You could use
another fossil driver (like X00 or BNU) that lays on top of the serial
port, but the DOSEMU driver should be more compatible under more
circumstances since it is dependent on the DOSEMU internal
fossil implementation.  In my experience, this has been the case, though
there are some poorly programmed fossil applications that depend on
specific non-features of X00/BNU and the like.

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: Three major questions.

[Justin Zygmont]

On Sat, 6 Sep 2003, Boris Reisig wrote:

> I am running dosemu 1.1.5.6 and would like to see if it is possible.
> 
> 1) To get rid splash screen "Now type ENTER to start DOSEMU" and
> automatically start dosemu without hitting a key.
> 
> 2) Running a dos program directly from the linux prompt and exiting back
> into linux after it is done.

I remember seeing other dos emulators would work like this, I guess it 
would mean having to run some part of the emulator in background all the 
time, different design I guess.

 
> 3) To be able to turn a comport into a telnet port. This would be perfect
> for BBS software if I could turn the com ports into telnet ports. For
> example. If I connect to my box on port (for example) 5000, Dosemu would
> redirect that as com1, port 5001 would be com2, etc. Any chance of this?

this sounds cumbersome at best


> 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: Three major questions.

[Ryan Underwood]

Hi,

On Tue, Sep 09, 2003 at 01:56:35PM -0400, Justin Zygmont wrote:
> On Sat, 6 Sep 2003, Boris Reisig wrote:
> 
> > I am running dosemu 1.1.5.6 and would like to see if it is possible.
> > 
> > 1) To get rid splash screen "Now type ENTER to start DOSEMU" and
> > automatically start dosemu without hitting a key.
> > 
> > 2) Running a dos program directly from the linux prompt and exiting back
> > into linux after it is done.
> 
> I remember seeing other dos emulators would work like this, I guess it 
> would mean having to run some part of the emulator in background all the 
> time, different design I guess.

This is easy to do, use the -E option to dosemu.bin and then execute
unix -e under dosemu (done automatically with the FreeDOS autoexec.bat)

i.e. dosemu -Efoo would run the command 'foo' when 'unix -e' is issued
inside the dos session.

> > 3) To be able to turn a comport into a telnet port. This would be perfect
> > for BBS software if I could turn the com ports into telnet ports. For
> > example. If I connect to my box on port (for example) 5000, Dosemu would
> > redirect that as com1, port 5001 would be com2, etc. Any chance of this?
> 
> this sounds cumbersome at best

I did this; simply make a script that runs your desired program in
dosemu, and bind that script to a port in /etc/inetd.conf.  When the
user telnets to the port, the port I/O becomes dosemu standard I/O.
Easy to run a LORD or TW2002 server this way (in local mode though).

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: Three major questions.

[Stas Sergeev]

Hello.

Ryan Underwood wrote:
> I did this; simply make a script that runs your desired program in 
> dosemu, and bind that script to a port in /etc/inetd.conf.  When
> the user telnets to the port, the port I/O becomes dosemu standard
> I/O.
What dosemu version is this?
There was an isatty() check added recently
(but not *very* recently), see parser.y.in:1284.
It supposed to fail if you are trying to use
a virtual com port on a redirected stdio, so
I don't think this way still works. Or is it?

Re: Three major questions.

[Ryan Underwood]

Hi,

On Wed, Sep 10, 2003 at 10:04:03PM +0400, Stas Sergeev wrote:
> Hello.
> 
> Ryan Underwood wrote:
> >I did this; simply make a script that runs your desired program in 
> >dosemu, and bind that script to a port in /etc/inetd.conf.  When
> >the user telnets to the port, the port I/O becomes dosemu standard
> >I/O.
> What dosemu version is this?
> There was an isatty() check added recently
> (but not *very* recently), see parser.y.in:1284.
> It supposed to fail if you are trying to use
> a virtual com port on a redirected stdio, so
> I don't think this way still works. Or is it?

This was with 1.0.2 stable IIRC.

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: Three major questions.

[Stas Sergeev]

Hello.

Ryan Underwood wrote:
>> What dosemu version is this? There was an isatty() check added
>> recently (but not *very* recently), see parser.y.in:1284. It
>> supposed to fail if you are trying to use a virtual com port on a
>> redirected stdio, so I don't think this way still works. Or is
>> it?
> This was with 1.0.2 stable IIRC.
OK, even in this case I can't imagine
how this could work. Dosemu assumes that
this is a tty in all the places around.
For example it does
strcpy(sptr->dev, ttyname(0))
which leads to a SIGSEGV for apparent
reasons in case stdio is redirected.
That was the point of adding an isatty()
check at first place.
Then it uses ioctl() for obtaining a serial
port status. ioctl'ing socket will simply
fail so the status will always be bogus.
So actually I don't think this could ever
work. There was a bug reports filled on SF
that this doesn't work and segfaults, and
then it was prohibited with an isatty() check
and the better alternative of using a
pseudo-tty's was added instead.

So it would be really usefull if you provide
more info on how exactly have you done that
and avoided all the underwater stones, and
also how to do that with the recent dosemus.

Re: Three major questions.

[Ryan Underwood]

Hi,

On Thu, Sep 11, 2003 at 05:58:22PM +0400, Stas Sergeev wrote:
> Hello.
> 
> Ryan Underwood wrote:
> >>What dosemu version is this? There was an isatty() check added
> >>recently (but not *very* recently), see parser.y.in:1284. It
> >>supposed to fail if you are trying to use a virtual com port on a
> >>redirected stdio, so I don't think this way still works. Or is
> >>it?
> >This was with 1.0.2 stable IIRC.
> OK, even in this case I can't imagine
> how this could work. Dosemu assumes that
> this is a tty in all the places around.
> For example it does
> strcpy(sptr->dev, ttyname(0))
> which leads to a SIGSEGV for apparent
> reasons in case stdio is redirected.
> That was the point of adding an isatty()
> check at first place.
> Then it uses ioctl() for obtaining a serial
> port status. ioctl'ing socket will simply
> fail so the status will always be bogus.
> So actually I don't think this could ever
> work. There was a bug reports filled on SF
> that this doesn't work and segfaults, and
> then it was prohibited with an isatty() check
> and the better alternative of using a
> pseudo-tty's was added instead.
> 
> So it would be really usefull if you provide
> more info on how exactly have you done that
> and avoided all the underwater stones, and
> also how to do that with the recent dosemus.

Sure, I'll try to put a little documentation together when I have some
spare time.

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253