All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard <R.Gregory@liverpool.ac.uk>
To: John Coppens <john@jcoppens.com>
Cc: "Alain M." <alainm@pobox.com>, dosEmu-list <linux-msdos@vger.kernel.org>
Subject: Re: Remote control of Dosemu
Date: Fri, 18 Jul 2008 23:24:24 +0100	[thread overview]
Message-ID: <48811818.1050401@liverpool.ac.uk> (raw)
In-Reply-To: <20080718183545.f97c49ce.john@jcoppens.com>

Hi John,

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.

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.

The details of the kernel module and screen grab are here, in section 5:
http://www.csc.liv.ac.uk/~greg/ghost4linux/index.html


Richard

John Coppens wrote:
> On Fri, 18 Jul 2008 14:21:55 -0300
> "Alain M." <alainm@pobox.com> wrote:
> 
>> BUT, you did not say if your application is command line, TUI or
>> graphic...
> 
> Hella Alain.
> 
> The program is TUI - direct video access, so, I don't know if any dumb
> mode would be possible. From a few disassembly intents, I suspect it was
> written in Turbo Pascal o C.
> 
> I have no need to do ssh. The program must be run every hour, a number
> of commands typed in, and a value, shown on the screen, must be captured.
> 
> I've also tried to write a TSR at some point, and with some success, and
> maybe I should continue on that path, as I can then probably look
> directly at the memory where the result appears.
> 
> But, if possible, I'd rather find a more elegant way...
> 
> Thanks,
> John
> --
> 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


  reply	other threads:[~2008-07-18 22:24 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 [this message]
2008-07-19  0:18           ` John Coppens
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=48811818.1050401@liverpool.ac.uk \
    --to=r.gregory@liverpool.ac.uk \
    --cc=alainm@pobox.com \
    --cc=john@jcoppens.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.