4 gb = 3.25 gb?

[DaForce]

Good stuff. He seem like a very rude arrogant person, imagine telling a customer they need to update their computer knowledge... thats shockingly rude.

Mmm that switch looks like the ticket, but im sure i have seen people here using xp64 and rendering with over 2gb of ram used... weird.

[Gijs]

Yeah, I can go over 2GB as well, but seems it can't go over 3GB. I haven't found yet where to put the /LARGEADRESSAWARE switch, but I think it is worth giving it a try.

Still I am stuck with another problem, which is that 3dsmax doesn't close (the process) after shutting 3dsmax down the first time.

[Gijs]

O.K., just found that /LAA is something that is application releated, and since max already goes over 2GB, it looks like it is already LAA.

Does anyone managed to use over 3GB of memory this way? If the answer is yes, then I guess the mem problem is not yet fully resolved.

[mike.edel]

AFAIK you cant get max to use more than 3Gb, since its a 32 bit application. Windows 64 could assign more than 3gb to one process (as opposed to win xp) but the application itself can only handle it if its 64bit, too.
So i think you'll have to wait for max64 (which is being worked on from what some people suggested)

mike

ps: glad it works now - really strange customer policy they got over there
especially since you might have come back for additional render machines in the future

edit: just looked at the microsoft article you linked to - what they are talking about under Memory allocation settings seems to be the maxium amount of ram windows can assign to one 32bit process
so 32bit windows could assign 2gb (or 3gb with the /3gb switch) while win64 could assign 2gb or 4gb with /largeaddressaware
i'd just use the largeaddressaware switch for good measure

given tha fact that most programs need continuous chunks of memory to operate you could run into stability problems before even reaching these barriers
after all windows itself needs a bit of memory (what an understatement!) for itself, too

edit2: just reread some stuff about largeadressaware: its a switch you compile into your application in order to support more ram
so max already has it (otherwise it wouldnt go above 2gigs on xp/xp64)
first thought it was a boot.ini switch

[mike.edel]

found some stuff that might be interesting to the 64bit users here:
http://msmvps.com/blogs/xperts64/default.aspx
seems he has done some writing on winxp64 for microsoft
he also has some helpful tips on his site

http://www.microsoft.com/communities...&lang=en&cr=US
microsoft newsgroup on windowsxp64

[Gijs]

edit2: just reread some stuff about largeadressaware: its a switch you compile into your application in order to support more ram
so max already has it (otherwise it wouldnt go above 2gigs on xp/xp64)
first thought it was a boot.ini switch

Yep, that's what I initially thought too. Still I am intereseted to know if it has to do with my memory or not that max crashes above 3gb (total ram usage I forgot to mention that earlier)