As a further update:
I have now tried the virtual XP computer with 776MB (just used the slider to select near to 3/4 of 1GB instead of typing in 768MB) and Sweet Home starts straight away with the -Xmx1024m SweetHome3D.l4j.ini file in the Sweet Home root directory.
After that test I then further reduced the XP virtual machines memory down to 512MB and even with the -Xmx1024m file Sweet Home starts and even renders a full scene using Advanced photo render, it did take around 7 minutes to render a 400x267 resolution view, probably because the XP machine is paging out to the hard drive, using it as virtual memory. At least we now know it still works okay with the 1GB file even on computers with only 512MB of memory.
Could the previously encountered problems have been a combination of the users computer not having enough memory plus they had disabled (or set to low) their pagefile?
Here is the 512MB XP computer with -Xmx1024m file Advanced photo render results
Now this next test is just asking for trouble. A Windows 7 (x86 version of the OS) virtual computer running just 512MB of system memory, barely enough to run the OS let alone applications and Sweet Home with a -Xmx1024m SweetHome3D.l4j.ini file still starts and runs okay albeit slowly because the virtual hard drive is being used as virtual (virtual (if you will)) memory.
This is the 512MB Windows 7 computer with -Xmx1024m file render (sorry forgot to time it)
db4tech
