public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: John Coppens <john@jcoppens.com>
To: Richard <R.Gregory@liverpool.ac.uk>
Cc: dosEmu-list <linux-msdos@vger.kernel.org>
Subject: Re: Remote control of Dosemu
Date: Fri, 18 Jul 2008 21:18:51 -0300	[thread overview]
Message-ID: <20080718211851.ec7cc935.john@jcoppens.com> (raw)
In-Reply-To: <48811818.1050401@liverpool.ac.uk>

On Fri, 18 Jul 2008 23:24:24 +0100
Richard <R.Gregory@liverpool.ac.uk> wrote:

> I had this problem when running Norton Ghost, it asked a question at 
> startup that needed the sequence <Tab><Tab><Enter> before proceeding 
> with the command line options. The available DosEmu options didn't
> work, so I wrote a kernel module that simulated key presses. This was
> for a 2.4 kernel and a hack, I'm no kernel hacker.

That looks quite similar to the problem I'm having.
 
> In my case Ghost was running in a console on the front display. To get 
> an idea of Ghosts progress, I found the memory at 0xA0000 showed a 
> cross-section of the 4 colour screen. It looked like it was interlaced, 
> though I couldn't figure out how. For my purposes it was enough to save 
> the screen. It is possible the text version is also available in a 
> constant memory location.

I haven't really followed screen mapping with 32 bit mapping, so I have
no idea where the screen would be. But as this program must run at
hour-intervals, and shouldn't even interfere with the normal ops, I guess
there is no other way to run it except with DOSemu on stdin/out.

I'm starting to think that it will be easier to capture the entire
serial stream, and reverse engr it, protocol and all. I did some
preliminary captures but it seems quite complicated. 

It's really complicated because the machine is 35 km from here, so I
can't really test easily.

Thanks
John

  reply	other threads:[~2008-07-19  0:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18  4:19 Remote control of Dosemu John Coppens
     [not found] ` <48801E06.9080700@pobox.com>
     [not found]   ` <20080718135339.75dfae5c.john@jcoppens.com>
2008-07-18 17:21     ` Alain M.
2008-07-18 21:35       ` John Coppens
2008-07-18 22:24         ` Richard
2008-07-19  0:18           ` John Coppens [this message]
2008-07-19  0:24         ` Alain M.
2008-07-19  3:54           ` Frank Cox
2008-07-21 14:51             ` Alain M.
2008-07-19 17:14 ` Bart Oldeman
2008-07-21 18:38 ` Mike McCarty
2008-07-21 22:07   ` John Coppens
     [not found]   ` <20080721161839.43f36b4c.john@jcoppens.com>
2008-07-22  2:23     ` Mike McCarty

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=20080718211851.ec7cc935.john@jcoppens.com \
    --to=john@jcoppens.com \
    --cc=R.Gregory@liverpool.ac.uk \
    --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