Quote:
>Oops, I forgot that 16 bit apps still can be helped by using the upper
>memory, even in WIN95. So I set up DOS=HIGH,UMB and avail memory jumped
>from 578K to 612K. Got my hopes up. Unfortumately, still get the error
>message when I try to launch this de{*filter*}. The only extra TSR I've got is
>the CD ROM driver. Any other ideas appreciated. At least I got the avail
>memory up a bit.
Scott,
How about Jim's suggestion? Are you debugging a Windows or DOS
application?
I've had a look on MSDN, and the only reference I can see to that
error is Knowledge Base article Q116492 "PRB: De{*filter*} Cannot Debug
DISPLAY.EXE". It's not very big, so here it is.
Dave
PSS ID Number: Q116492
Article last modified on 03-24-1995
1.00 1.50
WINDOWS
----------------------------------------------------------------------
The information in this article applies to:
- The Visual Workbench Integrated De{*filter*} included with:
Microsoft Visual C++ for Windows, versions 1.0 and 1.5
----------------------------------------------------------------------
SYMPTOMS
========
Attempts to run an application called DISPLAY.EXE in the Visual
Workbench de{*filter*} or CodeView causes the de{*filter*} to generate
the following error message:
DEBUG ERROR: Could not load debuggee, Windows is
Out of memory (1)
CAUSE
=====
There are several "Windows reserved" filenames that cause this
behavior,
such as the following:
CGA40WOA.EXE COMM.EXE COMMDLG.EXE GDI.EXE
DISPLAY.EXE DOSAPP.EXE FIXFONTS.EXE FONTS.EXE
KERNEL.EXE KEYBOARD.EXE MMSYSTEM.EXE MOUSE.EXE
PROGMAN.EXE SHELL.EXE USER.EXE TIMER.EXE
It is also possible to have conflicts with files already loaded into
memory by Windows. Microsoft Knowledge Base article Q86181: "Programs
with Reserved Windows Filenames May Not Run" discusses this problem
further.
RESOLUTION
==========
To work around this problem, rename the target executable with a name
that
does not match any of the names in the list above or any program that
has
already been loaded into memory. To find out whether an application in
memory has the same name as your application, run the Heap Walker
utility.
Heap Walker has the ability to sort applications by module name,
making it
easy to see whether another application shares the same name as yours.
If
so, you cannot use the de{*filter*} to debug your application.
Additional reference words: 1.00 1.50
KBCategory: kbtool kbprb
KBSubcategory: WBDebug
=============================================================================
Copyright Microsoft Corporation 1995.
----
Address is altered to discourage junk mail.
Remove ".---" for the real address.