Checking the host OS

Tom Glod tom at makeshyft.com
Fri Aug 30 23:41:46 EDT 2019


I have personal experience with trying to create a graphic that is 32,000 x
32,000 and exporting it.

on win32 i will run out of ram and lock up........ if not hard crash before
it even gets to it......and if i can test the standalone bitness I can
decline to attempt an impossible feat.

on win64 i could try it and if the system has enough ram, then it should
succeed.  I also have to increase the cache size to huge amounts to try to
create huge images.

I think the highest i succeeded in a 32 bit standalone was like 14k x
14k....it was 3 years ago where i did those tests....and don't remember the
details only that i was hitting the 32 bit memory wall.

thats one example of when asking the engine if its 32bit or 64 bit would
help.

On Fri, Aug 30, 2019 at 11:10 PM Mark Wieder via use-livecode <
use-livecode at lists.runrev.com> wrote:

> On 8/30/19 12:22 PM, Devin Asay via use-livecode wrote:
>
> > Now that we can build both 32 and 64 bit applications for Windows, it’s
> important to be able to tell whether the host OS is 32 or 64 bit.
>
> Why? If the 64-bit application won't run on the 32-bit system you won't
> get as far as your scripted test. Am I missing something?
>
> --
>   Mark Wieder
>   ahsoftware at gmail.com
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



More information about the use-livecode mailing list