Page 1 of 1

Problems with open .post.res file

Posted: Thu May 24, 2018 8:43 am
by Anto
Hi,
I try to open a post.res file with GID but after a short period of upload,
GID suddenly closes.
The dimension file is 2.54 Gb. Is this the problem? Namely, is the RAM or
video card of my PC the problem?

Tank you very much

Re: Problems with open .post.res file

Posted: Thu May 24, 2018 10:24 am
by escolano
Maybe it is a problem of not enough RAM. If the file is 2.54 Gb it really spend much more RAM, because it is compressed in disk.

Verify that you have set in Utilities->Preferences...
Post files->Use result cache
(and set 'Use a maximum (MB) appropriated to your physical RAM: by default it's set to 1 GB)
this allow to handle very big result files, because won't be loaded the full results of the file to RAM. It will load/unload some results on demand (only when are needed to be showed).

But maybe the problem is not the lack of RAM, maybe the file is corrupted.
If you are unable to view its results, provide us privately a copy if possible (using dropbox, or other similar media)

Re: Problems with open .post.res file

Posted: Thu May 24, 2018 11:42 am
by Anto
Tank you for your reply,
I searched for "Utilities->Preferences...
Post files->Use result cache" but I don't find it.
I attach the jpeg of the Utilities window

Re: Problems with open .post.res file

Posted: Thu May 24, 2018 12:17 pm
by abelcs
According to the GiD logo in the snapshot, I guess you are using a really old version (maybe version 7?). This option is in more modern versions.

Re: Problems with open .post.res file

Posted: Thu May 24, 2018 2:01 pm
by Anto
Yes, I have 7.6.6 GID version :D .
Tank you very much for the reply!

Re: Problems with open .post.res file

Posted: Thu May 24, 2018 2:22 pm
by escolano
You can download some version 13 http://www.gidhome.com/download/official-versions
and use it with a free, one month local, password to visualize the results of this big file.
https://www.gidhome.com/purchase/passwords

Note: use a GiD x64 version, not a x32 version
(a x32 process can only address about 2^32=4 GB of RAM, in practice in Windows x32 a process that spend more than 2GB will crash)