Exit due to Error: 37 - Image file is not an image

Maybe I already found part of the answer:

The environment I created using the Environments 64 was once created as a 64 bits environment, but now seems to think it is a 32 bits environment...

So I guess error 37 wants to tell my I am trying to start a 64 bit image with a 32 bit VM (or maybe vice versa, but seemingly not the case here).

This doesn't happen if I just create an environment and save the image after connecting it to the Library. But it does happen once I loaded my project code (which uses an external DLL, currently in its 32 bit variant) and save that one.

So it seems I am really asking a question about Environments: why does it turn a 64 bits environment into a 32 bit environment? And is there any chance to change this?

Joachim

Am Freitag, 23. November 2018 08:47:40 UTC+1 schrieb Joachim Tuchel:

Hi there ;-)

Before I start telling complicated stories of VA 9.1 64 bits being installed in parallel to 32 bits on the same Windows machine and strange behaviour after image saves, I start with an easy question:

What is error 37 exactly?

When we've cleared that one, I'll probably bore you guys with some longer stories about phenomena.

Spoiler alarm: A question you should be prepared fror is this one:

Why would this error show up after I used environments to copy a new image into the environment...

I guess one of the questions that wait in the background is how I can find out if an image is a 64 or a 32 bit image without starting a VM...

Joachim

Is this probably related:

<a href="https://www.instantiations.com/docs/FAQ/wwhelp/wwhimpl/js/html/wwhelp.htm#href=va17003.html" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.instantiations.com%2Fdocs%2FFAQ%2Fwwhelp%2Fwwhimpl%2Fjs%2Fhtml%2Fwwhelp.htm%23href%3Dva17003.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFA_05i5ctt13MKhUtSOevtsUVRQA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.instantiations.com%2Fdocs%2FFAQ%2Fwwhelp%2Fwwhimpl%2Fjs%2Fhtml%2Fwwhelp.htm%23href%3Dva17003.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFA_05i5ctt13MKhUtSOevtsUVRQA&#39;;return true;">https://www.instantiations.com/docs/FAQ/wwhelp/wwhimpl/js/html/wwhelp.htm#href=va17003.html

I wonder if it's really the case that loading PlatformFunctions which contain 32 bit data types  (uint32 pointers) really convert a 64 bit image to a 32 bit image and this would really turn the environment into a 32 bit one... ?????

If so, what would be the suggested path to preparing my code to 64 bits? Sure, I can use a 32 bit image and change the definitions of the PlatformFunctions there, but I can't test them. Sounds like a strange way to do that...

Hmm.

Am Freitag, 23. November 2018 09:14:34 UTC+1 schrieb Joachim Tuchel:

Maybe I already found part of the answer:

The environment I created using the Environments 64 was once created as a 64 bits environment, but now seems to think it is a 32 bits environment...

So I guess error 37 wants to tell my I am trying to start a 64 bit image with a 32 bit VM (or maybe vice versa, but seemingly not the case here).

This doesn't happen if I just create an environment and save the image after connecting it to the Library. But it does happen once I loaded my project code (which uses an external DLL, currently in its 32 bit variant) and save that one.

So it seems I am really asking a question about Environments: why does it turn a 64 bits environment into a 32 bit environment? And is there any chance to change this?

Joachim

Am Freitag, 23. November 2018 08:47:40 UTC+1 schrieb Joachim Tuchel:

Hi there ;-)

Before I start telling complicated stories of VA 9.1 64 bits being installed in parallel to 32 bits on the same Windows machine and strange behaviour after image saves, I start with an easy question:

What is error 37 exactly?

When we've cleared that one, I'll probably bore you guys with some longer stories about phenomena.

Spoiler alarm: A question you should be prepared fror is this one:

Why would this error show up after I used environments to copy a new image into the environment...

I guess one of the questions that wait in the background is how I can find out if an image is a 64 or a 32 bit image without starting a VM...

Joachim