Re: .Net 2.0 app behavior on 64-bit machine.

Tech-Archive recommends: Fix windows errors by optimizing your registry


"Chris Mullins" <cmullins@xxxxxxxxx> wrote in message
news:%234W6osUQGHA.4952@xxxxxxxxxxxxxxxxxxxxxxx
"Sriram" <Sriram@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
I have an 1.1 .net app ported to 64-bit 2.0 framework that uses a 3rd
party
CAD drawing DLL(natively 32-bit but runs in WOW mode on 64-bit per their
documentation).

So you have a mixed application at this point. What Build Targets are you
compiling your .Net code to be?

There does not seem to be any improvement wrt performance (that is, the
.net
app running on 1.1 on a 32-bit machine using their 32 bit DLL). Am I
missing
something here?

What kind of performance improvements were you expecting to see?

Or, is the 32-bit 3rd party CAD generating DLL a bottleneck, though they
claim that on 64-bit boxes, their DLL can address the 4GB virtual memory
limit??

I would say it's unlikley their 32 bit dll is addressing 4GB of virtual
memory.

If I remember right, a process is either 32 bit or 64 bit, but not both.
So if you have a 32 bit DLL, your whole process is going to be 32 bit.



32-bit processes running on 64-bit windows in WOW64 can use the whole 4GB of
addressable memory because there is no reservation of address space for
kernel mode code in WOW64. This will work so long as the executable is
marked as LARGEADDRESSAWARE.

David

Now whether this translates into


.

Relevant Pages

  • Re: How can I estimate how much memory a DLL will take when loaded?
    ... unless you have the source code and can determine an upper bound of memory that the DLLs code will allocate dynamically based on the way the DLL is used. ... If you are talking about virtual memory in the adress space of a process that loads the DLL, then as a lower bound, look at the "Virtual Size" of the DLL in Dependency Walker. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: How can I estimate how much memory a DLL will take when loaded?
    ... unless you have the source code and can determine an upper ... the way the DLL is used. ... If you are talking about virtual memory in the adress space of a process ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Checking How much memory Loaded DLL uses
    ... If the question is how much virtual memory the DLL uses then its basically its size. ... You can verify this with Memory Validator - use the Virtual view and move your mouse until the status indicates the DLL the mouse pointer is on top of. ... If the question is how much memory does this DLL allocate when it executes then you need a software tool like Memory Validator - look at the objects tab, select the DLL tab and then choose the DLL in the DLL combo box. ...
    (microsoft.public.vc.mfc)
  • Re: DLL load error on Dell AXIM x50v when WI-FI enabled
    ... The problem is that the system is out of virtual memory address ranges, ... Google the newsgroups for virtual memory, ce, LoadLibrary ... DLL early, before your heaphave become sizable. ... > When the WI-FI is turned off and then the application is loaded everything ...
    (microsoft.public.pocketpc.developer)
  • Re: [Lit.] Buffer overruns
    ... > floating point support or a memory expansion option. ... had virtual memory support grafted on. ... > where the modified instruction was fetched from. ... vis-a-vis the official coporate strategic operating system TSS/360. ...
    (sci.crypt)