From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Coppens Subject: Re: Remote control of Dosemu Date: Fri, 18 Jul 2008 21:18:51 -0300 Message-ID: <20080718211851.ec7cc935.john@jcoppens.com> References: <20080718011954.dc5e47b5.john@jcoppens.com> <48801E06.9080700@pobox.com> <20080718135339.75dfae5c.john@jcoppens.com> <4880D133.60204@pobox.com> <20080718183545.f97c49ce.john@jcoppens.com> <48811818.1050401@liverpool.ac.uk> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <48811818.1050401@liverpool.ac.uk> Sender: linux-msdos-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Richard Cc: dosEmu-list On Fri, 18 Jul 2008 23:24:24 +0100 Richard wrote: > I had this problem when running Norton Ghost, it asked a question at > startup that needed the sequence 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