DOS memory inspector?

[Twospruces]

Anyone have a suggestion for a good simple memory inspector? I want to confirm what Int13h and int19h contents are.
thanks in advance.

(I did see that PCDOC40 includes this function but it is not running very stably)

[Stone]

What about debug?

[krebizfan]

I wouldn't wish DEBUG on my worst enemy.

A friendlier utility might be https://www.pcorner.com/list/UTILITY/DVECT.ZIP/INFO/ or https://www.pcorner.com/list/UTILITY/VECTOR.ZIP/INFO/ I remember there being a lot a similar utilities but I am having trouble finding them.

[BloodyCactus]

debug will do all you need tho..

[Chuck(G)]

Or write your own. Should be extremely simple.

[Agent Orange]

Or write your own. Should be extremely simple.

I'm thinking if he couldwrite his own he wouldn't have posted in the first place.

[Stone]

I'm thinking if he couldwrite his own he wouldn't have posted in the first place.

Good to see somebody's thinking.

As Gen. George S. Patton Jr. said, 'If everybody is thinking alike, then somebody isn't thinking.'

[Twospruces]

I didn't know about debug. Thanks, I 'll try that first, as I want to be able to look at a range of memory. Basically I am debugging XUB on a machine that may use memory differently than XUB assumes. cheers

[Chuck(G)]

I'm thinking if he couldwrite his own he wouldn't have posted in the first place.

If the OP is debugging XUB, (s)he certainly understands assembly, no?

One thing that simple DOS DEBUG won't do is get you to reliably displaying memory inside of a DOS critical section. That's why I suggested writing your own. I also suspect that there are debuggers that run as TSRs and don't use DOS to display things. At least I have a couple.

[Agent Orange]

If the OP is debugging XUB, (s)he certainly understands assembly, no?

Could be Chuck, but not everyone has your talents.