FileInstall problem

[Basti756]

Hi,

I made a script which installs an application and its dependencies. There are a few .reg files and a .msi file which I wanted to include in the script. Inlcuding the files with FileInstall() works, but they are kinda messed up when the compiled script is executed. It somehow looks like those files have been compiled to binary.

Here's what one of the .reg files looks before compiling the script:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\VAG\\update\Columns\0000]
"Item"="ProgDesc"
"Name"="Name"
"Section"="Name"
"ColID"=dword:00000000
"Sort"=dword:00000001
"Width"=dword:000000f7

This is what the file looks when being extracted by FileInstall() (just a part of it):

ÐÏà¡±á                >  þÿ                       z      þÿÿÿ       €   ÿ   €  ÿ  €  ÿ  €  ÿ  €  ÿ  €  ÿ  €  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿýÿÿÿ            ›      ,   
                                                                   !   "   #   $   %   &   '   (   )   *   +   .   -   D   /   0   1   2   3   4   5   6   7   8   9   :   ;   <   =   >   ?   @   A   B   C   F   þÿÿÿþÿÿÿG   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   X   Y   Z   [   \   ]   ^   _   `   a   b   c   d   e   f   g   h   i   j   k   l   m   n   o   p   q      s   t   u   v   w   x   y   E   ¢   |   }   ~         R o o t   E n t r y                                               ÿÿÿÿÿÿÿÿ   „    À   F         àoËÐQÌ{   @   @HŒDðDrDhD7H                                                      ÿÿÿÿÿÿÿÿÿÿÿÿ                                  O          @HC5BæErE<H                                                        ÿÿÿÿ                                 N          @HBäExE(H                                                        
   ÿÿÿÿ                                 M          @HBäExE(;2D³D1BñE6H                                                  ÿÿÿÿ                                 L          @HC/B                                                           ÿÿÿÿÿÿÿÿÿÿÿÿ                                 F   V     @HDñE                                                                 ÿÿÿÿ                                   D   L      @HRDöEäC¯;;B&F7BB4FhD&B                                        ÿÿÿÿ   ÿÿÿÿ                                    =   Œ    @HB'C$H                                                      
ÿÿÿÿÿÿÿÿÿÿÿÿ                                    3          @H–Eì;ìCh<¤E+H                                                 ÿÿÿÿÿÿÿÿÿÿÿÿ                                 7   |     @HYEòDhE7G                                                      ÿÿÿÿ   ÿÿÿÿ                                  4   ˜     @Hÿ?äCìAäE¬D1H                                                     ÿÿÿÿ                                 ƒ   Ð)      @H?dA/B6H                                                       ÿÿÿÿÿÿÿÿ                                  1   T      @HÊA0C±;;B&F7BB4FhD&B                                            ÿÿÿÿÿÿÿÿ                                  0   0      @HÊAùEÎF¨AøE(?(E8B±A(H                                              ÿÿÿÿ                                   .   T      @HŠA7CrDBûE                                                      ÿÿÿÿÿÿÿÿÿÿÿÿ                                  '   ¤    @HNEµD5H                                                    
      ÿÿÿÿ                                     x      @H?;òC8D±E                                                      ÿÿÿÿÿÿÿÿÿÿÿÿ                                              @H??wElDj>²D/H                                                   ÿÿÿÿÿÿÿÿÿÿÿÿ                                    r         @H??wElDj;äE$H                                                        ÿÿÿÿ                                      PÔ    \WIPROPDriveQR:\WIPROPDriveRS:\WIPROPDriveST:\WIPROPDriveTU:\WIPROPDriveUV:\WIPROPDriveVW:\WIPROPDriveWX:\WIPROPDriveXY:\WIPROPDriveYZ:\WIPROPDriveZWICOMP00000001WIFEAT00000001New FeatureSourceDirTARGETDIR{E2C7F2EC-CFAA-437B-BC86-9B2F410D048C}WIRemoveTextFileRemoveTextFilePositionTextAltPositionTextRemovalTextWinINSTALL: Primary key, non-localized token.WinINSTALL: File name used for installation, may be localized.  This may contain a "short name|long name" pair.WinINSTALL: Foreign key into the Directory table denoting the directory where the text file is.WinINSTALL: Primary text removal position enumeration.WinINSTALL: Alternate text removal position enumeration.WinINSTALL: Text to be removed.WinINSTALL: Text removal action enumeration.WinINSTALL: Foreign key into the Component table referencing component that controls the removal of the text.WITextFileTextFileInsertionTextWinINSTALL: Primary text installation position enumeration.WinINSTALL: Alternate text installation position enumeration.WinINSTALL: Text rner of the bounding rectangle of the control.Vertical coordinate of the upper left corner of the bounding rectangle of the control.The name of an action. The billboard is displayed during the progress messages received from this action.Name of the billboard.An external key to the Feature Table. The billboard is shown only if this feature is being installed.OrderingA positive integer. If there is more than one billboard corresponding to an action they will be shown in the order defined by this column.The unformatted binary data.Unique key identifying the binary data.The index into the File table. This must be an executable file.PathPathsA list of ;  delimited paths that represent the paths to be searched for the import DLLS. The list is usually a list of properties each enclosed within square brackets [] .CheckBoxA named property to be tied to the item.The value string associated with the item.Optional AppID containing DCOM information for associated application (string GUID).optional argument for LocalServers.Class registration attributes.The CLSID of an OLE factory.Required foreign key into the Component Table, specifying the component for which to return a path when called through LocateComponent.The numeric server context for this server. CLSCTX_xxxxFilename1;2;3Optional default inproc handler.  Only optionally provided if Context=CLSCTX_LOCAL_SERVER.  Typically "ole32.dll" or "mapi32.dll"Localized description for the Class.Required foreign key into the Feature Table, specifying the feature to validate or install

The OS I'm using for compiling is Windows 7 SP1 x64

[Basti756]

The boardsoftware somehow messes with my code snippet. Here's a part of the mentioned result:

ÐÏࡱá > þÿ z þÿÿÿ € ÿ € ÿ € ÿ € ÿ € ÿ € ÿ € ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿýÿÿÿ › ,

! " # $ % & ' ( ) * + . - D / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C F þÿÿÿþÿÿÿG H I J K L M N O P Q R S T U V W X Y Z [ ] ^ _ ` a b c d e f g h i j k l m n o p q s t u v w x y E ¢ | } ~ R o o t E n t r y ÿÿÿÿÿÿÿÿ „ À F àoËÐQÌ{ @ @HŒDðDrDhD7H ÿÿÿÿÿÿÿÿÿÿÿÿ O @HC5BæErE<H ÿÿÿÿ N @HBäExE(H

ÿÿÿÿ M @HBäExE(;2D³D1BñE6H ÿÿÿÿ L @HC/B ÿÿÿÿÿÿÿÿÿÿÿÿ F V @HDñE ÿÿÿÿ D L @HRDöEäC¯;;B&F7BB4FhD&B ÿÿÿÿ ÿÿÿÿ = Œ @HB'C$H

ÿÿÿÿÿÿÿÿÿÿÿÿ 3 @H–Eì;ìCh<¤E+H ÿÿÿÿÿÿÿÿÿÿÿÿ 7 | @HYEòDhE7G ÿÿÿÿ ÿÿÿÿ 4 ˜ @Hÿ?äCìAäE¬D1H ÿÿÿÿ ƒ Ð) @H?dA/B6H ÿÿÿÿÿÿÿÿ 1 T @HÊA0C±;;B&F7BB4FhD&B ÿÿÿÿÿÿÿÿ 0 0 @HÊAùEÎF¨AøE(?(E8B±A(H ÿÿÿÿ . T @HŠA7CrDBûE ÿÿÿÿÿÿÿÿÿÿÿÿ ' ¤ @HNEµD5H

ÿÿÿÿ x @H?;òC8D±E ÿÿÿÿÿÿÿÿÿÿÿÿ @H??wElDj>²D/H ÿÿÿÿÿÿÿÿÿÿÿÿ r @H??wElDj;äE$H ÿÿÿÿ PÔ WIPROPDriveQR:WIPROPDriveRS:WIPROPDriveST:WIPROPDriveTU:WIPROPDriveUV:WIPROPDriveVW:WIPROPDriveWX:WIPROPDriveXY:WIPROPDriveYZ:WIPROPDriveZWICOMP00000001WIFEAT00000001New FeatureSourceDirTARGETDIR{E2C7F2EC-CFAA-437B-BC86-9B2F410D048C}WIRemoveTextFileRemoveTextFilePositionTextAltPositionTextRemovalTextWinINSTALL: Primary key, non-localized token.WinINSTALL: File name used for installation, may be localized. This may contain a "short name|long name" pair.WinINSTALL: Foreign key into the Directory table denoting the directory where the text file is.WinINSTALL: Primary text removal position enumeration.WinINSTALL: Alternate text removal position enumeration.WinINSTALL: Text to be removed.WinINSTALL: Text removal action enumeration.WinINSTALL: Foreign key into the Component table referencing component that controls the removal of the text.WITextFileTextFileInsertionTextWinINSTALL: Primary text installation position enumeration.WinINSTALL: Alternate text installation position enumeration.WinINSTALL: Text rner of the bounding rectangle of the control.Vertical coordinate of the upper left corner of the bounding rectangle of the control.The name of an action. The billboard is displayed during the progress messages received from this action.Name of the billboard.An external key to the Feature Table. The billboard is shown only if this feature is being installed.OrderingA positive integer. If there is more than one billboard corresponding to an action they will be shown in the order defined by this column.The unformatted binary data.Unique key identifying the binary data.The index into the File table. This must be an executable file.PathPathsA list of ; delimited paths that represent the paths to be searched for the import DLLS. The list is usually a list of properties each enclosed within square brackets [] .CheckBoxA named property to be tied to the item.The value string associated with the item.Optional AppID containing DCOM information for associated application (string GUID).optional argument for LocalServers.Class registration attributes.The CLSID of an OLE factory.Required foreign key into the Component Table, specifying the component for which to return a path when called through LocateComponent.The numeric server context for this server. CLSCTX_xxxxFilename1;2;3Optional default inproc handler. Only optionally provided if Context=CLSCTX_LOCAL_SERVER. Typically "ole32.dll" or "mapi32.dll"Localized description for the Class.Required foreign key into the Feature Table, specifying the feature to validate or install

[JLogan3o13]

Ok, not sure if it is the forum or what you're posting, but your posts are a mess. Can you please post only the code for your script so we can take a look?

[abberration]

Instead of extracting registry files, why not integrate them into your script with RegWrite. Example:

RegWrite("HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeVAGupdateColumns0000","Item","REG_SZ",'ProgDesc')
RegWrite("HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeVAGupdateColumns0000","Name","REG_SZ",'Name')
RegWrite("HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeVAGupdateColumns0000","Section","REG_SZ",'Name')
RegWrite("HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeVAGupdateColumns0000","ColID","REG_DWORD",'00000000')
RegWrite("HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeVAGupdateColumns0000","Sort","REG_DWORD",'00000001')
RegWrite("HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeVAGupdateColumns0000","Width","REG_DWORD",'000000f7')

[careca]

Now imagine it was a really big file, with lots of keys, what would you do?

[BrewManNH]

I'd do the same thing, make them RegWrites and use error checking to assure that they've been imported ok. Using a .reg file you don't have that kind of granular control over the process.

[abberration]

Now imagine it was a really big file, with lots of keys, what would you do?

A while back, I found a script on this forum called Reg2Au3. Use it to convert the reg files to au3 files. Easy peasy.

[Basti756]

First of all sorry for the messed up posts.

I know about the registry functions but integrating the files within the script would have saved me a lot of work. That was before I knew about Reg2Au3 .

There is also an answer file for a unattended Oracle Client installation which I wanted to be integrated (which gets messed up too BTW) but I think I'll rather use AutoIt's native functions.

Back to topic: Did you experience this behavior of FileInstall()?

Here's what I did:

• using FileInstall() to integrate some files <- OK
• files being extracted when running the script <- OK
• file content after they've been extracted <- NOK

The strange thing is I integrated 3 REG files, the Oracle answer file and a small MSI file. After they'd been extracted, they were all the same size (around 855kb) and looking at them with a text editor would show what I wrote in my second post.

I'm using Windows Server 2008 R2 SP1 (which is a 64Bit OS) for compiling. Could that be the reason?

EDIT:

This is embarrassing now... the issues I had with FileInstall() turned out to be one of those copy-paste-errors. Here's what I did:

FileInstall("C:some.msi",@TempDir & "some.msi")

I needed a couple of files included so I copied and pasted this line a few times and changed the target path... not the source:

FileInstall("C:some.msi",@TempDir & "some.msi")
FileInstall("C:some.msi",@TempDir & "first.reg")
FileInstall("C:some.msi",@TempDir & "second.reg")

No wonder that the extracted files were totally messed.

Thanks anyways, Bastian

Edited November 3, 2012 by Basti756

[JLogan3o13]

Glad you resolved your issue Basti756. Those copy and paste errors will get you every time. I remember when I first started C#, the instructor told us never to copy and paste, because it would cause us more headaches than anything else.