TSR into upper memory

  • Thread starter Thread starter HandyMan
  • Start date Start date
H

HandyMan

Wasn't quite sure where to post this.

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.
 
HandyMan said:
Wasn't quite sure where to post this.

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.

It would be wise to provide better details.

What OS?
What is the TSR?
How is it loaded?
Is Windows running?

Have you tried using Google? (What?)
 
It would be wise to provide better details.

What OS?
What is the TSR?
How is it loaded?
Is Windows running?

Have you tried using Google? (What?)


If you aren't familar with the terms above, I must be in the wrong
group.

Andy
 
....[invisible TSR]
If you aren't familar with the terms above, I must be in the wrong
group.

Andy

Wrong, Andy.

Todd is most certainly familiar with MEM and TSRs.

Each OS has its own quirks. Knowing which particular version you are using
(and from your header you're using XP) allows us to eliminate some of the
posibilities. It also allows us the opportunity to say which group is more
appropriate, if that is the case.

Knowing which TSR allows us to load it and check out your problem. Most of
the regulars in this group and related groups are old-style hackers - in the
original sense, prepared to spend a vast amount of time on investigating and
solving mysteries.

Wrong group? Very likely. Probably alt.msdos.batch.nt would be better - but
had you been using W9x or DOS, then alt.msdos.batch would be a better
choice. Many alt... regulars keep an eye on this group too. Same people -
but different frame-of-mind. Same as you don't keep sheets and shirts and
socks all in a drawer labelled "cloth things." Or maybe you do...

Had you simply responded "XYZ" and I'm using XP, then we could help further.
As it is, you're none the wiser, the problem still exists and people have
the impression that you're more interested in playing 20 questions than in
solving your problem. If you're not prepared to answer simple questions,
then don't be surprised when others conclude that it's not worth their time
responding.
 
Todd is most certainly familiar with MEM and TSRs.

Each OS has its own quirks. Knowing which particular version you are using
(and from your header you're using XP) allows us to eliminate some of the
posibilities. It also allows us the opportunity to say which group is more
appropriate, if that is the case.

Knowing which TSR allows us to load it and check out your problem. Most of
the regulars in this group and related groups are old-style hackers - in the
original sense, prepared to spend a vast amount of time on investigating and
solving mysteries.


Using XP Sp2

There is no problem. mem/c only shows TSRs loaded into lower memory.

My TSR loads itself into high memory. I am studying some source code
to modify it for another use.

I want to find out the size of the TSR being put there.

Andy
 
Using XP Sp2

There is no problem. mem/c only shows TSRs loaded into lower memory.

My TSR loads itself into high memory. I am studying some source code
to modify it for another use.

I want to find out the size of the TSR being put there.

Boot from a dos floppy disk and load it there.
 
Show us what mem /c and mem /d is reporting.

A better util shows this when TSR is loaded and confirmed running OK.

Psp Cnt Size Name Command Line Hooked Vectors
---- --- ------ ---------- -------------------
--------------------------------
1 16,880 DOS
0421 2 3,744 COMMAND /U 23 24 2E
1 112 ---free---
0551 2 634,512 ---free---
655,344 ---total--

High Memory
1 20,960 DOS
1 928 ---free---
D34D 1 464 MSCDEXNT
D36B 1 2,672 REDIR 2A 5C 73
D413 2 34,848 DOSX 2F
1 78,560 ---free---
138,544 ---total--
 
A better util shows this when TSR is loaded and confirmed running OK.

Psp Cnt Size Name Command Line Hooked Vectors
---- --- ------ ---------- -------------------
--------------------------------
1 16,880 DOS
0421 2 3,744 COMMAND /U 23 24 2E
1 112 ---free---
0551 2 634,512 ---free---
655,344 ---total--

High Memory
1 20,960 DOS
1 928 ---free---
D34D 1 464 MSCDEXNT
D36B 1 2,672 REDIR 2A 5C 73
D413 2 34,848 DOSX 2F
1 78,560 ---free---
138,544 ---total--

Sorry, me no understand. Give us all the details or nobody is going to
help you, unless you are very fortunate.
 
Sorry, me no understand. Give us all the details or nobody is going to
help you, unless you are very fortunate.

You have the details. I can't supply you when you aren't clear what
you want.

Andy
 
HandyMan said:
You have the details. I can't supply you when you aren't clear what
you want.

Ok, let's start the 20 questions over then.

Which class is this homework problem for?
Why are you asking others to do your homework?
Do you actually believe instructors do not read newsgroups?
 
Todd Vargo said:
Ok, let's start the 20 questions over then.

Which class is this homework problem for?
Why are you asking others to do your homework?
Do you actually believe instructors do not read newsgroups?

And why is the output from mem/c on your xp/sp2 system formatted quite
differently from what it shows on my xp/sp2 system? Which version of mem are
you using - mine looks like this:

Directory of C:\WINDOWS\system32
2006-02-28 06:00 AM 39,274 mem.exe

/Al
 
[ ]
[ ]
You have the details. I can't supply you when you aren't clear
what you want.

You were asked to provide MEM /C and MEM /D output running in DOS
with the TSR loaded. So "NO details" have been provided as was
requested.

Are you studying dentistry? :)
 
Ok, let's start the 20 questions over then.

Which class is this homework problem for?
Why are you asking others to do your homework?
Do you actually believe instructors do not read newsgroups?


You have a VERY long history of "angry" responses. I will no longer
answer any more posts from you.
 
[ ]

[ ]
You have the details. I can't supply you when you aren't clear
what you want.

You were asked to provide MEM /C and MEM /D output running in DOS
with the TSR loaded. So "NO details" have been provided as was
requested.

Are you studying dentistry? :)

See reponse to Mr. Todd.
 
HandyMan said:
Show us what mem /c and mem /d is reporting.
A better util shows this when TSR is loaded and confirmed
running OK.

[ ]
Sorry, me no understand. Give us all the details or nobody is
going to help you, unless you are very fortunate.
You have the details. I can't supply you when you aren't clear
what you want.

You were asked to provide MEM /C and MEM /D output running in DOS
with the TSR loaded. So "NO details" have been provided as was
requested.

Are you studying dentistry? :)

See reponse to Mr. Todd.

The (minor, imho) "angriness" that Todd showed was not out of keeping with
your lack of responsiveness. If you had given sufficient information to
describe the actual problem, Todd, Mark, myself, or a number of others who
spend time here because we want to help people would likely have provided
the answer you were looking for.

/Al
 
Back
Top