Error Compiling resources under Windows XP

[James Ormiston]

I’m currently going through the process of re-compiling my Projects using CVI 7.1.1 and Windows XP.
When I compile a certain Project (some projects compile fine) I get the following LabWindows/CVI Message:

“Error compiling resources. Make sure your tmp directory is writeable and not full.”

I don’t get this problem when compiling the same project with CVI 7.1.1 and Windows 2000.

Any thoughts on this matter would be greatly appreciated.

Cheers
JO

[DaveC]

Your problem could be that you don't have write permissions to the cvibuild.[projectname] directory in your project directory. This would explain why you are able to compile in 2000 and not in XP as any type of extended write permissions are typically administered on a machine-by-machine basis except for the IT guys whose admin rights usually follow with the roaming profile.

To test this theory out, go to your project directory and open your cvibuild.[projectname] file within the directory. See if you can create a new file (doesn't matter what type) in the directory.

If you can't then you will have to move your project to a new directory and build from there. Usually the 'MyDocuments' folder isn't locked down.

[James Ormiston]

Dave,
Thanks for your reply.

I have tried as you suggested and I have no problem creating a file in the cvibuild.[projectname] directory. I have full administrator rights to the PC. I’ve been able to compile other projects without any problems.

Could it be anything to do with the strange behaviour of the read-only attribute of a file/directory in XP? I have had a look at the properties of the directory specified by the TMP Environment Variable (since the message details “Make sure your tmp directory is writeable and not full.”). The read-only attribute is marked with a “green square”. I have tried to turn off this option without any success. Each time I go back into the properties of the directory the “green square” is set in the read-only attribute.

Cheers
JO

[DaveC]

James,

My guess would be that it wouldn't have anything to do with the read-only attribute because as long as you can create files in the cvibuild.[projectname] directory than CVI should be able to as well.

Perhaps the .DLL or .exe file that you are creating is set to be built in a non-existing or non-writeable directory? You can check this by going to Build->Target Settings, and checking out the build path for the target file in both debug and release form (I use CVI 7.0 so your menu settings in 7.1 may be a little different, I'm not sure)

[James Ormiston]

I have seen another few posts that detail the same Message. These post state that it could be a corrupt Icon or a space within the path when embedding a UIR. I’m creating a DLL so there is no Icon and I’m not embedding a UIR.

It appears that this error Message (“Error compiling resources. Make sure your tmp directory is writeable and not full.”) has more than one meaning and it could be pointing me in wrong direction.

Does this message have any other meanings?

[LuisG]

James,

Do you have a lot of nested structures in the data types exported by your DLL? The reason I ask is because we found a bug in CVI 7.1 that could cause this error to be displayed when processing structures that were very deeply nested. If you think this applies to you, then that is probably the reason. Let me know.

Luis
NI

[Sailing Solo]

>> “Error compiling resources. Make sure your tmp directory is writeable and not full.”

I just had the same pop-up error, in a Windows NT environment.

In my situation, I had to change the cvibuild./resoures.res file
to make it NOT read-only. This fixed it for me.

Bill

[James Ormiston]

Luis,

The project that I’m compiling does contain a few deeply nested structures.

Can I remind you that I was able to compile the project previously using CVI 7.1.1 on a Windows 2000 system. I’m now trying to compile the same project using CVI 7.1.1 on a Windows XP Professional System.

Is there a fix available to this problem? If there is, where can I get the update? If there is not, do you have any idea when it will be available?

Many Thanks
James.

[LuisG]

Hello James,

Actually, I made a mistake. I didn't realize it at the time, but the bug that I was referring to was fixed between 7.1 and 7.1.1. So, if you ran into the problem when using 7.1.1 then it must be something else.

So, we're back to square one. We'll need to be able to reproduce it here in order to find out what is going on. You mentioned that it only happens for you withcertain projects. Did you really mean one specific project, or more than one? Would you be able and willing to attach a project here that has this problem?

Luis

[James Ormiston]

Luis,

We have managed to fix this problem.

The version of CVI we had installed was 7.1.1 (313) from our last release on the developer suite. This is not updated with the patch. I thought the patch up issued CVI to 7.1.1? When I installed the patch it made my CVI version 7.1.1 (314).

This is very unclear! Why wasn’t the patch named differently to make things stand out more? e.g. 7.1.1 f1 like other up-issues you have made.