REG.EXE and linker failure

[dajum]

We have a users machine who felt that the reg.exe program from MS was a hole in their security, so they changed the permissions on the executable to require administrator privelges. Once they did they when our scripts try to run the compiler/linker, the linker fails with a message that it can't find uuid.lib. It returns a message error status of "Error - 183 status = 1104".

Can you tell me what this error means?

Do you know why permissions on REG.EXE affect the compiler/linker?

Dave

[Wendy_Doerner__Intel]

Dave,

The reg.exe utility from Microsoft "Adds, changes, and displays registry subkey information and values in registry entries." The Intel Compiler does need to modify the registry to install on the system. Did the customer try to install the compiler after the change to REG.EXE? I am checking to see if the compiler would need access to it during compilation, but it may be Microsoft* Visual Studio that is using it.

The error means the compiler can not find the uuid.lib file needed by the compiler. It is usually caused by a failure during installation which results in the file not being installed or referenced by the compiler correctly. This file usually resides in Microsoft* Visual Studio or SDK directories.

Wendy

Attaching or including files in a post

[Wendy_Doerner__Intel]

More specifically, you could make sure the Windows SDK is in the linker library search path.

Wendy

[dajum]

Wendy,

The installation of the compiler/linker and VS were all performed before any changes were made to the REG.EXE permissions. The compiler/linker ran fine after the installation. It was used extensively to compile and test all of our code. Note that we do not use Visual Studio as a GUI, we do all of our compiling and linking from within other programs. This all worked fine. Then the permissions changes are made on REG.EXE, so there all of the files for the compiler and linkers are still installed. I don't know all the details of how our software executes the compiler, but I believe it is similar to opening a command prompt window. All of the environment variables need to be set so the various paths are set for the compiler to find. I believe we execute IFORTVARS.BAT within the program. But I don't know why any of that would have to change the registry, but it probably queries the registry at some point, and I suspect that might occur via REG.EXE. It could even be within the compiler or linker, as it appears to us like the compilation has succeeded, but the link fails.

Thanks,

Dave

[Steven_L_Intel1]

The compiler does not use reg.exe at all and doesn't query the registry. I suggest that you find out how your software accesses the compiler.

Here's a simple test - open Start > Intel Software Developmemt Tools > Intel Visual Fortran 11.1.xxx > Build Environment for IA-32 applications. Create a simple "Hello World" program and build it using an ifiort command. Does it build?