VC 1.52 Windows Debugger 
Author Message
 VC 1.52 Windows Debugger

Help! I am trying to use the VC 1.52 supplied with VC 4.0 to develop some
MS-DOS (16 bit) applications for use in Login Script files.  I'm trying to
run VC 1.52 under WIN95.  But I can't get the Windows De{*filter*} to load.  I
get the following error message whenever the de{*filter*} is loaded:

DEBUG ERROR: Could not load debuggee, Window is Out of Memory(1)

I''ve got 24 MB of RAM in the computer, plus lots of room for swap file
(>200 MB), so I don't understand what "memory" it's talking about.

Any help appreciated.  

Scott



Thu, 12 Aug 1999 03:00:00 GMT  
 VC 1.52 Windows Debugger

Quote:
>Help! I am trying to use the VC 1.52 supplied with VC 4.0 to develop some
>MS-DOS (16 bit) applications for use in Login Script files.  I'm trying to
>run VC 1.52 under WIN95.  But I can't get the Windows De{*filter*} to load.  I
>get the following error message whenever the de{*filter*} is loaded:

>DEBUG ERROR: Could not load debuggee, Window is Out of Memory(1)

>I''ve got 24 MB of RAM in the computer, plus lots of room for swap file
>(>200 MB), so I don't understand what "memory" it's talking about.

Scott,

I've used the VC1.52 IDE de{*filter*} & CVW under Win95, they should work
fine!

The memory in question is probably the base 640K region. If you run
mem /c /p from a DOS shell how much of that base memory is available?
I've got 604K available. Check that you've not got any huge (or
problematic) TSRs or real-mode drivers loading in your config.sys &
autoexec.bat files.

Dave
----
Address is altered to discourage junk mail.
Remove ".---" for the real address.



Fri, 13 Aug 1999 03:00:00 GMT  
 VC 1.52 Windows Debugger

Are you trying to debug the DOS program with the IDE de{*filter*}?  This
won't work, you need to use Codeview for DOS (comes with VC++ 1.52)
--
Why are builders afraid to have a 13th floor
    but book publishers aren't afraid to have a Chapter 11?



Fri, 13 Aug 1999 03:00:00 GMT  
 VC 1.52 Windows Debugger

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.

Thanks for the input.  

Scott  

Quote:
> Scott,

> I've used the VC1.52 IDE de{*filter*} & CVW under Win95, they should work
> fine!

> The memory in question is probably the base 640K region....

> Dave



Sat, 14 Aug 1999 03:00:00 GMT  
 VC 1.52 Windows Debugger

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.



Sun, 15 Aug 1999 03:00:00 GMT  
 
 [ 5 post ] 

 Relevant Pages 

1. VC 1.52 debugger question

2. Is there a way to debug VC 1.52 EXE with VC 5.0

3. Executing .bat file from VC 1.52 AND VC 4.2

4. VC 4.2 back to VC 1.52

5. MSVC 1.52 debugger problem

6. VC 1.52 Jet ODBC updates

7. VC 1.52 and RFX_Date

8. Finding VC 1.52

9. VC 1.52 16-bit Jet Access

10. Help with GetProcAddress in VC 1.52

11. vc 1.52

12. Trim function for VC 1.52

 

 
Powered by phpBB® Forum Software