TSR in upper memory

[Andy]

I have a small TSR that loads into upper memory.

mem/d can't see it.

Is there anything available that can. I know there are a lot of
command line utils I haven't yet
learned about.

Thanks.

 

[Rock]

I have a small TSR that loads into upper memory.

mem/d can't see it.

Is there anything available that can. I know there are a lot of
command line utils I haven't yet
learned about.

What OS are you talking about? You've posted to a newsgroup for the XP OS.
List of MS newsgroups: http://aumha.org/nntp.htm

 

[AW Barton]

I have a small TSR that loads into upper memory.

mem/d can't see it.

Is there anything available that can. I know there are a lot of
command line utils I haven't yet
learned about.

Thanks.

There's no such thing as 'upper memory' in WinXP. Is there?

 

[Andy]

have a small TSR that loads into upper memory.




There's no such thing as 'upper memory' in WinXP. Is there?

It may be emulated but it's there. Though I mainly write 32 bit code,
I occasionally modify some 16 bit code.

Some things done at the command line are faster than a GUI app.

 

[Detlev Dreyer]

I have a small TSR that loads into upper memory.

mem/d can't see it.

Is there anything available that can.

Try mem /c

 

[Andy]

Try mem /c

Didn't work. We git 'er figured out.

 

[Detlev Dreyer]

Didn't work. We git 'er figured out.

If that TSR doesn't show up, it either didn't load or it's using some-
thing called "Stealth programming" at that time. In the mid 90's, I was
using the latter technology in order to replace the native DOS keyboard
driver under Win9x since it was consuming a lot of (conventional) memory.
In both cases, that TSR won't show up at all. How exactly are you trying
to load that TSR?

 

[Andy]

If that TSR doesn't show up, it either didn't load or it's using some-
thing called "Stealth programming" at that time. In the mid 90's, I was
using the latter technology in order to replace the native DOS keyboard
driver under Win9x since it was consuming a lot of (conventional) memory.
In both cases, that TSR won't show up at all. How exactly are you trying
to load that TSR?

I have looked at the source and I don't see any obvious stealth other
than loading to upper memory.
It loaded correctly because it generates a log file.

I just found an old utility that logs all disk activity. I have found
that a lot of older code that is emulated by the cmd environment
doesn't quite work right. Usually some minor code modification will
allow their continued good use.

I have a very fast file searcher that I am fixing to work on multiple
drives. The DOS interrupt code that detects the drives available
doesn't work like it did thru Win 98.

Andy

Andy