Plug-In Error

[JXBURNS]

Still struggling to get permissions sorted on my Win2003 server so another question.

I could not get the CREATE FOLDER option to work correctly. It would create the folder but the two subsequent SET ACCESS commands did nothing even though I put all 3 before the APPLY INSTALL statement. I did this as I wanted the folder to have the rights attached before the files were copied so they inherited the same rights. In this case read only as the we have already worked out that the SET ACCESS for write (incorrectly) gives full control (hopefully fixed in a later version??)

So reading other messages here I thought let's use the CALL DLL function to create the folder:

Code: Select all

~InstallAware Clipboard Data~
~Call DLL Function~
~{FC602A2A-F0CF-4A45-AF12-624A44B2A590}~
~kernel32.dll,CreateDirectoryA,bool,FOLDEROK,"pointer to string",$TARGETDIR$,"double word",0,$~
~~mIDEFunc.dll\\mEXEFunc.dll~~

But when I run on the destination machine the system objects with the error that has been mentioned elsewhere on these forums:

Code: Select all

Unable to load plug-in library. Please rebuild your project and make sure all required plug-ins are installed. 

Action skipped

Now the question is - how do I make sure that all required plug-ins are installed? All I did to create the CALL DLL function was to select it from the list in MSICODE view and set the parameters. Am I supposed to do something else? I can't see adding a specific path should help as kernel32.dll is in the WINSYS folder.

Thanks - John

[MichaelNesmith]

Purple commands in your script only take effect when Apply Install is called. Therefore, your Create Folder command will not take effect until Apply Install is called. So, your approach in using Call DLL Function is correct.

About the error you're getting with Call DLL Function - shouldn't be happening. Rebuild your project, turn off debug mode and set the build mode to uncompressed, let me know what happens.

[JXBURNS]

Michael,

Does exactly the same thing in uncompressed mode (did not have debug set in either case).

Rgds John

[MichaelNesmith]

Sorry, the plug-in normally works, not sure what's going on wrong there

[Tinus]

John,

delete the command and reenter (do not cut'n paste). This worked for me.
Give it a try.

[JXBURNS]

OK Tinus had the right idea and now worked fine.

FYI looking at original (copy/pasted from an example in this forum):

Code: Select all

~InstallAware Clipboard Data~
~Call DLL Function~
~{FC602A2A-F0CF-4A45-AF12-624A44B2A590}~
~kernel32.dll,CreateDirectoryA,bool,FOLDEROK,"pointer to string",$TARGETDIR$,"double word",0,$~
~~mIDEFunc.dll\\mEXEFunc.dll~~

And then when I created manually.

Code: Select all

~InstallAware Clipboard Data~
~Call DLL Function~
~{11E2CE75-12D1-444D-A32B-86F9483C55FC}~
~kernel32.dll,CreateDirectoryA,bool,FOLDEROK,"pointer to string",$TARGETDIR$,"double word",0,$~
~mIDEFunc.dll\\mEXEFunc.dll~

As you can see the GUID (?) is different. Not sure what this relates to but obviously something that needs to be described in the help file or when posting messages here that this is unique to the installer being developed. Or perhaps the software could check the generated GUID?

Whilst these are niggling things, overall I am starting to get used to the software and managing to do most things in it without too much difficulty. Pretty pleased I have been able to shift an MSI file out to workstations using Group Policy!

Thanks - John

[u5urp3r]

Thanks Tinus. Had this issue for sometime with non-debug builds of my installer. Removing, saving and reinserting the plug-in line worked a charm.

Cheers again...

[Lin]

Thank you Tinus!!!