ignis said:In combination with the fact that the specs of a particular type of DELL may seem similar, the internals of the machine may be quite different.
I quit selling Dell systems exactly be cause of this. We build our advanced graphic work ststions
Well I haven't gotten it sorted out yet, but I did make some interesting progress that I thought I'd share.
Essentially, Corel Photo Paint crashes in the following scenarios: Fresh 32-bit and 64-bit installs of XP SP2 all patched up. Even if it's the first program I install after doing this.
It WORKS when I install it under XP 64-bit virtualized (using Sun's Virtualbox) under a 32-bit XP host OS. This is SP2 fully patched.
I'm back to thinking this is a hardware configuration problem. I'm leaning at this point to the fact that virtual environments handle the hardware abstraction somewhat differently. This difference prevents the crash that happens using native 32-bit and 64-bit XP installs.
I might just try and turn this Dell back in for something with just 32-bit hardware. My user isn't comfortable running the virtual environment so I'll probably just abandon this, but thought I'd share that interesting tidbit.
Jim
A memory issue.
I wrote a post on it here today.
See it that rings any bells.
Very interesting. It seems you had the memory issue even though you passed stress tests? I've stress tested this overnight on multiple occassions using memtest and the Dell memory diagnostic tool. Nothing was every found, but I guess that doesn't rule it out then. I'll look in to what you said about XP loading itself in memory in the same place every time. Does it also load programs in the same space in memory? That seems inefficient and would lead to a lot of page thrashing without using the full amount of RAM available. I just found it strange that it crashes on load in the exact same spot with an "access denied" accessing the heap in two different OSs. I was under the impression that due to the 64-bit nature of XP x64 that the memory structure was different as well. Are you saying maybe it's not? But it is in the virtual environment?
I'm going to start swapping RAM around or slow it down and see what happens.
Make sure that you're fully patched with V12.