comp.lang.idl-pvwave archive: archive » Re: largest array, most memory accessible

Home » Public Forums » archive » Re: largest array, most memory accessible

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: largest array, most memory accessible [message #41206]

Mon, 18 October 2004 21:58

netnews.comcast.net is currently offline

netnews.comcast.net
Messages: 10
Registered: October 2004

Junior Member

Karl Schultz wrote:
> "Karl Schultz" wrote...
>
>> "Rick Towler" wrote ...
>>
>>> Karl,
>>>
>>> How will all this change with the introduction of WinXP-64? While I
>>> very much hope you guys are working on a 64-bit version of IDL for
>>> windows, I won't ask you to comment on that. But, how will opening up
>>> the address space affect the 32bit version of IDL running on windows?
>>
>> I don't know exactly how a 64-bit Windows would run 32-bit apps. But at
>
> the
>
>> moment, I do not think it would be that much different than the 3GB
>> situation today. There would probably still have to be some kernel space
>> mapped below 4G.
>
>
> Actually, I just found a blog saying that a 32-bit app compiled with the
> large address flag can access 4G in Win 64. I don't know how true that
> statement is, however.

FWIW, I just read the same thing. With a 64bit OS running a 32-bit exe
the full 4GB will be available to the 32-bit app as long as there is
sufficient memory in the system to allow for the OS+extras to be loaded
elsewhere.

-r

Report message to a moderator

[Message index]

		Re: largest array, most memory accessible By: netnews.comcast.net on Mon, 18 October 2004 21:58
		Re: largest array, most memory accessible By: Karl Schultz on Thu, 14 October 2004 16:59
		Re: largest array, most memory accessible By: R.G. Stockwell on Thu, 14 October 2004 15:28
		Re: largest array, most memory accessible By: Karl Schultz on Wed, 13 October 2004 17:22

Previous Topic:	initial keyboard focus, tabbing and keyboard accelerators
Next Topic:	Project files

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 00:57:53 PDT 2025

Total time taken to generate the page: 1.43730 seconds