Question 1: Has anyone made similar observations?
Does anyone know other large memory configurations
that do work?

Question 2: How about WINE faking the amount of memory
reported to Photoshop in a way that one working size
is used? For example, using 1280 MByte on a 2 GByte
machine?

On Wed, 06 May 2009 10:17:01 +0200, Andreas Schallenberg
no_reply at (no spam) yahoo.com> wrote:

Question 1: Has anyone made similar observations?
Does anyone know other large memory configurations
that do work?

Try (on a recent wine) the software. If the problem that you suspect
exists, try changing the settings for emulated windows version (default
is win XP).

IIRC the win9* versions did not use more then 512MB, so that could work
(or can be made to work in a compatible way).

Unfortunately it doesn't. Just tested with 1GB RAM,

Question 2: How about WINE faking the amount of memory
reported to Photoshop in a way that one working size
is used? For example, using 1280 MByte on a 2 GByte
machine?

How about testing first if there is a problem?

A comment from GlobalMemoryStatus function:

| /* work around for broken photoshop 4 installer */
| if ( lpBuffer->dwAvailPhys + lpBuffer->dwAvailPageFile >=
| 2U*1024*1024*1024)
| lpBuffer->dwAvailPageFile = 2U*1024*1024*1024 -
| lpBuffer->dwAvailPhys - 1;

There are more of such work around's in the wine sources to be found.
...

Question 2: How about WINE faking the amount of memory
reported to Photoshop in a way that one working size
is used? For example, using 1280 MByte on a 2 GByte
machine?

How about testing first if there is a problem?

Guess why I wrote this post

There are more of such work around's in the wine sources to be found.
...

Interesting. So this is for Photoshop 4 installer...
I'll have a look at the source if I find something
for Photoshop 3 and the main application. Thank you
for that information.

...
So instead of relying on your memories about the results of a (possibly)
old version of wine I asked for a recent test from yourself.

Ok, sorry, then I got you wrong.

...
If you want help file a bug report on http://bugs.winehq.org and attach
there the result of a relay trace. You need to type something like this:

WINEDEBUG=+relay wine yourprogram.exe &>wine.log

The resulting wine.log text file needs to be compressed. Best to use
lzma which gives fare out the best compression ratio.

If you prefer, send the log directly to me (wijn at online dot nl)
...

Hello Rein!

Rein Klazes wrote:
...
So instead of relying on your memories about the results of a (possibly)
old version of wine I asked for a recent test from yourself.

Ok, sorry, then I got you wrong.

...
If you want help file a bug report on http://bugs.winehq.org and attach
there the result of a relay trace. You need to type something like this:

WINEDEBUG=+relay wine yourprogram.exe &>wine.log

The resulting wine.log text file needs to be compressed. Best to use
lzma which gives fare out the best compression ratio.

If you prefer, send the log directly to me (wijn at online dot nl)
...

I just created this report:
http://bugs.winehq.org/show_bug.cgi?id=18379

I did not add your hint about the Photoshop 4 Installer
workaround. Maybe this needs to be added, too.

Regards,
Andreas

Heck I got the the opposite results.

I installed Publisher under Wine and cannot get Wine to assign more than
32 megs to the application and it immediately runs out of memory.

Thus far no one has been able to explain how to assign memory to
applications in Wine

Raak wrote:

FWIW: I've tried this on with at least three different Linux
distributions and even tried Crossover Office (which is essentially just
Wine with a few tweaks.)

But there is no way anyone has ever come up with a way for me to get
Wine to assign more memory to the application

On Sat, 09 May 2009 11:59:10 -0500, philo <philo at (no spam) privacy.net> wrote:

Raak wrote:

FWIW: I've tried this on with at least three different Linux
distributions and even tried Crossover Office (which is essentially just
Wine with a few tweaks.)

But there is no way anyone has ever come up with a way for me to get
Wine to assign more memory to the application

How do follow memory usage?

As an example, I use agent to write this message. With 'top' I get to
see this:

| PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
| 5193 rein 20 0 2604m 63m 9928 S 1 2.1 16:11.74 agent.exe

Wine has reserved 2.6 Gig's of memory for this process. That is virtual
memory, it is reserved but not all used. What is in use (taking RAM, or
swap) is 63meg (RES means resident). If needed that will grow without I
have to do anything.

Your problem is not "wine assigning too little memory".

Rein.

Ok I checked and you are right...

the first bit of helpful info I've gotten...

So basically, the memory is there for Wine to use...
but for whatever reason it's *not* being used by the application.

When I run Publisher natively (in Windows) however the behavior is such
that Publisher is using several gigs of RAM...but when running in
Linux/Wine...it only uses 32megs .


Now I know in Photoshop, for example there is a setting for how much RAM
you want it to use...but in Publisher there is no such setting.


So bottom line is...when using Publisher in Wine...how do I get it
to use the memory that is apparently there?

It is certainly not using it

On Sat, 09 May 2009 16:14:17 -0500, philo <philo at (no spam) privacy.net> wrote:

Ok I checked and you are right...

the first bit of helpful info I've gotten...

So basically, the memory is there for Wine to use...
but for whatever reason it's *not* being used by the application.

When I run Publisher natively (in Windows) however the behavior is such
that Publisher is using several gigs of RAM...but when running in
Linux/Wine...it only uses 32megs .


Now I know in Photoshop, for example there is a setting for how much RAM
you want it to use...but in Publisher there is no such setting.


So bottom line is...when using Publisher in Wine...how do I get it
to use the memory that is apparently there?

It is certainly not using it

You are ignoring the possibility that Publisher's error message is not
accurate.

It would be help full if you could file a bug report at
http://bugs.winehq.org and supply a link to a publisher file with the
problem. The bugzilla upload limit of 1meg is probably not enough to
attach it directly.

Rein.

Rein Klazes wrote:
...
You are ignoring the possibility that Publisher's error message is not
accurate.
...

Oh no...

the error message is quite accurate.

The file is huge (1 gig) It's a very large publication.
Even running Publisher natively, my machine has runs rather slowly.

As I think I've stated, when running natively, Publisher is using
several gigs of RAM when I open the file.
...
I think Rein is trying to tell you that despite the

philo schrieb:
Rein Klazes wrote:
...
You are ignoring the possibility that Publisher's error message is not
accurate.
...
Oh no...

the error message is quite accurate.

The file is huge (1 gig) It's a very large publication.
Even running Publisher natively, my machine has runs rather slowly.

As I think I've stated, when running natively, Publisher is using
several gigs of RAM when I open the file.
...
I think Rein is trying to tell you that despite the
fact that the file is large and the message says that
Publisher runs out of memory the problem may be different.
What if Publisher running under WINE is unable to open
the file due to other library calls failing?

There are many ways to handle error situations in software
and is is not unusual that reasons for some errors are not
correctly encoded in status words. If a programmer finds
it extremely unlikely that a routine fails in practice,
the failure is not represented by an individual error state.
So, the routine reports that it is unable to open the file
and returns a different error code (or message) that is
different than (but hopefully somehow close to) the real
reason.

WINE surely behaves different that a native Windows OS
in many ways. It is not unlikely that you caught such
a situation. I wouldn't bet on Rein being wrong in this case.

Regards,
Andreas