I'll reply to my own message I suppose. I had two problems. The second
was that I was specifying a range of ports to passthrough that encompassed
other devices, dosemu therefore ignored the entire statement aparently
(thats a bit nonintuitive -- shouldn't there be a run time warning/error
about that instead of silently ignoring?). I figured out my first problem
by reading parser.y. I wanted 'trace ports {range 0x1ff 0xfff}', I think.
But maybe thats wrong. I don't know. It still intermitently traces and
not traces. Does tracing not work on ports also specified as ones to go
to the hardware? Any way to do that? It really defeats my purpose if I
can't trace the accesses that make it to the hardware.
af
On Sat, 27 Nov 1999, Adam Fritzler wrote:
>
> I have both .98.8 and .99.13 booting just fine, however, I'd like to be
> able to trace i/o port activity. I have a dos app that configures a
> network card of mine; I'd like to be able to run the config utility under
> dosemu and figure out how its configuring the card. It currently does not
> work under dosemu (doesn't find the card). I've turned on every option
> that seems to relate to tracing i/o activity (-D+a) and letting it pass
> through to the actual hardware ($_ports = "range 0x1ff 0xfff"), but its
> still not going. I'm not sure exactly how the app detects the precense of
> a card, but I'pm guessing it just probes a series of i/o addresses.
> Putting all those addresses in $_ports I would think would let all the
> reasable ports pass through.
>
> Can dosemu list all i/o accesses, or do I have to go add printf's to it
> myself? Any ideas on why the ports aren't getting through? (I figure if I
> can figure out how to trace, I could more easily figure out the second
> problem.)
>
> Thanks. CC to me, not sub'd.
> af
>
> ---
> Adam Fritzler
> { [EMAIL PROTECTED], [EMAIL PROTECTED]}
> http://www.auk.cx/~mid/
> "You may call me Lor." -- Lor
>
>
---
Adam Fritzler
{ [EMAIL PROTECTED], [EMAIL PROTECTED]}
http://www.auk.cx/~mid/
"You may call me Lor." -- Lor
