From: "administrator" <administrator@mail.hq42.net>
To: linux-msdos@vger.kernel.org
Subject: RE: Three major questions. Issue 4
Date: Sun, 7 Sep 2003 00:13:50 +0000 (UTC)
Date: Sat, 6 Sep 2003 20:15:07 -4:00 [thread overview]
Message-ID: <01C374B3.91421160@VORPAL> (raw)
> $ 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
> $
>
> All this does is trade on input terminal for another...
> and tie me to x as well.
no, it is just an example. You can start dosemu instead of xdosemu if you
like and start dosctrl in another terminal. All that dosctrl does it to
talk to fdout and get input from fdin in an infinite loop.
> I know how to create and permission a FIFO
> it "talks" to dosemu fine ( dosemu reads from it )
> dosemu produces ( bogus) output on the output pipe
> so we know it is connected to the output pipe....
> so why do I get the Command "whatever" not found
> no matter what I type?
if you type "help" it should present you with the above left.
And the light comes on at last...:)
I do have it setup correctly...
I just do not have a dos shell
I have the pre-initialization environment
Is this correct?
$ echo help > fdin
$ cat fdout
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
Maybe you were thinking that it directly takes DOS commands. It doesn't.
No "dir" and "copy", but "xmode" and "hog" are valid commands.
It controls certain aspects of a virtual machine.
> Does this "feature" actually work? ( in 1.1.5.6 )
> Has it ever worked in any version?
> ( with normal FIFO files driven by a frontend )
it works like I showed you. Not more not less.
When I type "help" I get the correct output...:)
but the keystroke command is giving me some trouble
is the syntax like the -input flag?
or do I put them in plain? ( no quote and no trailing \r )
send me a couple of quick examples of
keystroke input syntax ( do you have to quote the string?)
next reply other threads:[~2003-09-07 0:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-07 0:13 administrator [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-07 1:28 Three major questions. Issue 4 administrator
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01C374B3.91421160@VORPAL \
--to=administrator@mail.hq42.net \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox