Good Evening,

Is it possible to change {&BrandingUL} & {&BrandingLR} within MakeMSI code?

If so, what needs to be added, and which file does it need to be added to?

Also, my Desktop Shortcuts aren't created correctly, here is a pastebin of them:
http://pastebin.com/d6fd58716

Both are for the .exe, however have the icon of the .msc.

I'd also like to create a shortcut in the Start Menu folder for a different
.exe.

Please tell me if the above are possible, and if so, how to implement them.

Thanks in advance,

Chip D. Panarchy

Thanks for your reply Dennis.

Yes, what I'd prefer to do is change it within the scripts.
How do I change the BrandingTexts within MakeMSI?

Also, I'm trying to create two Desktop shortcuts, how do I do so?

Here is my code: http://pastebin.com/d6fd58716

It currently creates two shortcuts on the Desktop, one with the correct name and
location (Troubleshooting MMC) but incorrect icon, and one with incorrect name,
location & icon.

Please tell me how I can change the BrandingTexts and fix up the Desktop
shortcuts.

Thanks in advance,

Panarchy

--- In makemsi@yahoogroups.com, Dennis Bareis <dbareis@...> wrote:
>
> Hi,
>
> forumanarchy wrote:
>
>  > The reason I need editors is to redefine both {&BrandingUL} &
> {&BrandingLR}.
>  > Unless there's a way to redefine them in the scripts?
>
> Still not enough info, you say what you want to do but not why.  Are you
> generating multiple versions of the msi each with different values or
> are you touching up the msi (once).
>
> If the former why do you need to play with the fonts?  If the latter why
> not do this within MAKEMSI?  If you can't do it as part of the build
> (and why not?) then you could have a second MAKEMSI script to "touch up"
> the msi, see:
>
>   *
>
http://makemsi-manual.dennisbareis.com/using_orca_and_msidiff_to_automate_msi_up\
dates.htm
>   *
>
http://makemsi-manual.dennisbareis.com/making_changes_to_existing_databases.htm
>
>
>  >
>  > Also QWERTY.MSI helps me find the name of what I'm looking to change,
> which is helpful even if I use a program
>  > like SuperOrca to change those settings.
>
> Orca and other editors have search facilities...  Also not sure why you
> need to search, not many entries in the "TextStyle" table.
>
> Bye,
> Dennis
>

Hi,

forumanarchy wrote:

  > The reason I need editors is to redefine both {&BrandingUL} &
{&BrandingLR}.
  > Unless there's a way to redefine them in the scripts?

Still not enough info, you say what you want to do but not why.  Are you
generating multiple versions of the msi each with different values or
are you touching up the msi (once).

If the former why do you need to play with the fonts?  If the latter why
not do this within MAKEMSI?  If you can't do it as part of the build
(and why not?) then you could have a second MAKEMSI script to "touch up"
the msi, see:

   *
http://makemsi-manual.dennisbareis.com/using_orca_and_msidiff_to_automate_msi_up\
dates.htm
   *
http://makemsi-manual.dennisbareis.com/making_changes_to_existing_databases.htm


  >
  > Also QWERTY.MSI helps me find the name of what I'm looking to change,
which is helpful even if I use a program
  > like SuperOrca to change those settings.

Orca and other editors have search facilities...  Also not sure why you
need to search, not many entries in the "TextStyle" table.

Bye,
Dennis

Thanks Dennis, SuperOrca did the trick.

The reason I need editors is to redefine both {&BrandingUL} & {&BrandingLR}.

Unless there's a way to redefine them in the scripts?

Also QWERTY.MSI helps me find the name of what I'm looking to change, which is
helpful even if I use a program like SuperOrca to change those settings.

Please tell me if it is possible to change those settings within the scripts.

Thanks in advance,

Panarchy

--- In makemsi@yahoogroups.com, "Dennis" <dbareis@...> wrote:
>
> Hi,
>
> I'm not sure what I can do about any bugs in Querty.msi (its not my tool)...
>
> I downloaded it and changed a property and the msi saved OK.
>
> List of editors as per the doco:
>
>     http://makemsi-manual.dennisbareis.com/msi_editors.htm
>
>
> Better question is what you are doing and why, why use a GUI editor at all?
You say "how to get this to work", I need to know what "this" is first.
>
> Bye,
> Dennis
>
>
> --- In makemsi@yahoogroups.com, "forumanarchy" <forumanarchy@> wrote:
> >
> > Hello
> >
> > Not sure where to post this, but I've been having some trouble getting
QWERTY.MSI to work with MakeMSI.
> >
> > QWERTY.MSI allows for easy editing of already-made MSI files, via a GUI
Interface.
> >
> > Here's the error I receive;
> >
> > Embedding stream "_MAKEMSI_Cabs.MM01.cab".   2259 C:\Program
Files\MakeMsi\Samples\TryMe\Create MSI
Installers\out\TryMe.MM\QWERTY\Debug\Disk1_1\Manta.msi  .  Try to change cabinet
stream name and check whether the table "_MAKEMSI_Cabs" contains stream
"MM01.cab"  :  error code 1627 Media
> >
> > Embedding stream "_MAKEMSI_Cabs.MM02.cab".   2259 C:\Program
Files\MakeMsi\Samples\TryMe\Create MSI
Installers\out\TryMe.MM\QWERTY\Debug\Disk1_1\Manta.msi  .  Try to change cabinet
stream name and check whether the table "_MAKEMSI_Cabs" contains stream
"MM02.cab"  :  error code 1627 Media
> >
> > Is there anything you'd recommend I do in order to make this work?
> >
> > If this is a known bug, one that can't be fixed, then could you please
recommend another program I can use to edit the MSI?
> > (Specifically GUI changes, eg; Finish text)
> >
> > Please recommend something
> >
> > Thanks in advance,
> >
> > Panarchy
> >
>

Hi,

I'm not sure what I can do about any bugs in Querty.msi (its not my tool)...

I downloaded it and changed a property and the msi saved OK.

List of editors as per the doco:

     http://makemsi-manual.dennisbareis.com/msi_editors.htm


Better question is what you are doing and why, why use a GUI editor at all? You
say "how to get this to work", I need to know what "this" is first.

Bye,
Dennis


--- In makemsi@yahoogroups.com, "forumanarchy" <forumanarchy@...> wrote:
>
> Hello
>
> Not sure where to post this, but I've been having some trouble getting
QWERTY.MSI to work with MakeMSI.
>
> QWERTY.MSI allows for easy editing of already-made MSI files, via a GUI
Interface.
>
> Here's the error I receive;
>
> Embedding stream "_MAKEMSI_Cabs.MM01.cab".   2259 C:\Program
Files\MakeMsi\Samples\TryMe\Create MSI
Installers\out\TryMe.MM\QWERTY\Debug\Disk1_1\Manta.msi  .  Try to change cabinet
stream name and check whether the table "_MAKEMSI_Cabs" contains stream
"MM01.cab"  :  error code 1627 Media
>
> Embedding stream "_MAKEMSI_Cabs.MM02.cab".   2259 C:\Program
Files\MakeMsi\Samples\TryMe\Create MSI
Installers\out\TryMe.MM\QWERTY\Debug\Disk1_1\Manta.msi  .  Try to change cabinet
stream name and check whether the table "_MAKEMSI_Cabs" contains stream
"MM02.cab"  :  error code 1627 Media
>
> Is there anything you'd recommend I do in order to make this work?
>
> If this is a known bug, one that can't be fixed, then could you please
recommend another program I can use to edit the MSI?
> (Specifically GUI changes, eg; Finish text)
>
> Please recommend something
>
> Thanks in advance,
>
> Panarchy
>

Hello

Not sure where to post this, but I've been having some trouble getting
QWERTY.MSI to work with MakeMSI.

QWERTY.MSI allows for easy editing of already-made MSI files, via a GUI
Interface.

Here's the error I receive;

Embedding stream "_MAKEMSI_Cabs.MM01.cab".   2259 C:\Program
Files\MakeMsi\Samples\TryMe\Create MSI
Installers\out\TryMe.MM\QWERTY\Debug\Disk1_1\Manta.msi  .  Try to change cabinet
stream name and check whether the table "_MAKEMSI_Cabs" contains stream
"MM01.cab"  :  error code 1627 Media

Embedding stream "_MAKEMSI_Cabs.MM02.cab".   2259 C:\Program
Files\MakeMsi\Samples\TryMe\Create MSI
Installers\out\TryMe.MM\QWERTY\Debug\Disk1_1\Manta.msi  .  Try to change cabinet
stream name and check whether the table "_MAKEMSI_Cabs" contains stream
"MM02.cab"  :  error code 1627 Media

Is there anything you'd recommend I do in order to make this work?

If this is a known bug, one that can't be fixed, then could you please recommend
another program I can use to edit the MSI?
(Specifically GUI changes, eg; Finish text)

Please recommend something

Thanks in advance,

Panarchy

Hi,

I don't know too much about Linux but unfortunately I'd be very surprised if it
could be done.  Msi manipulations need to be done via Microsoft's Windows
Installer and MAKEMSI also needs to generate and execute VBSCRIPT.

Bye,
Dennis

--- In makemsi@yahoogroups.com, "atomix.productions" <stephane.clavel@...>
wrote:
>
> Hello,
>
> I searched the group, but didn't find anything related to this.
>
> Can makemsi be used on a unix OS to build msi files?
> Since makemsi is running on top of ppwizard, and ppwizard is unix compatible,
it seems it might be possible.
> But I wanted to know if anyone had already attempted this?
>
> The obvious reason for this, is to be able to create msi installers on-the-fly
from a website.
> The download page on the website (php code) would create a .mm file on the fly
according to the user profile etc, and compile the msi to send to the user.
>
> Would that be possible?
>

Hello,

I searched the group, but didn't find anything related to this.

Can makemsi be used on a unix OS to build msi files?
Since makemsi is running on top of ppwizard, and ppwizard is unix compatible, it
seems it might be possible.
But I wanted to know if anyone had already attempted this?

The obvious reason for this, is to be able to create msi installers on-the-fly
from a website.
The download page on the website (php code) would create a .mm file on the fly
according to the user profile etc, and compile the msi to send to the user.

Would that be possible?

Hi,

--- In makemsi@yahoogroups.com, "gdgzls2002" <gdgzls2002@...> wrote:
> How can I keep the data file in new .msi?
> (There is also a requirement that data file must be erased when uninstalling.)

This is the relevant part of the doco:

    http://makemsi-manual.dennisbareis.com/resource_life_cycle.htm

But needing to remove on uninstall complicates things, an MSI does know (via a
property) when its uninstalling via the installation of the new version so that
could be used on conditions.



> I tried 'ExeCa' to backup the data file, but cannot find
> the right sequence.

See "InstallExecuteSequence" in this page:

     http://makemsi-manual.dennisbareis.com/scheduleca.htm

In the msi being uninstalled the files are removed by "RemoveFiles", this
happens in the msi being installed at "RemoveExistingProducts" (which has been
moved from the default location shown on that page).

Verbose logs can be used to check sequencing...

> I also tried disable auto uninstall previous product,
> but it is not a good idea.

As you won't be able to tell whether or not you need to deleted the data....

Bye,
Dennis

Hi all,

The previous .msi has installed 2 files, one is exe file and the other is a data
file.

Data file got changed since installed.

Now new version of exe is going to be released.

Found that both old files got deleted during upgrade.

How can I keep the data file in new .msi? (There is also a requirment that data
file must be erased when uninstalling.)

I tried 'ExeCa' to backup the data file, but cannot find the right sequence.

I also tried disable auto uninstall previous product, but it is not a good idea.

Any help is welcome, thanks in advanced.

Hi,

Dennis wrote:
  > --- In makemsi@yahoogroups.com, "gozzgug" <gozzgug@...> wrote:
  > > Verify .NET 3.5 is installed.
  > You could use "RegistryRead" to look in registry:
  > http://makemsi-manual.dennisbareis.com/registryread.htm

I have now created an example page for how it can be done:

     http://makemsi-manual.dennisbareis.com/net_framework_installed.htm

Let me know if you have any issues with it.

Bye,
Dennis

Hi,


--- In makemsi@yahoogroups.com, "gozzgug" <gozzgug@...> wrote:
>
> I've never used MakeMSI before but it looks great.
> We are currenly deploying some dlls via batch file and it's very
> unreliable. Can anyone write a sample install for me so I can get
> an understanding on how it works? I've looked at the documentation
> but it's a little confusing.


I will assume you have gone through this:

     http://makemsi-manual.dennisbareis.com/quickstart.htm


> Completely silent install.

All Windows Installers (.msi) support silent install unless you break it:

     http://makemsi-manual.dennisbareis.com/msiexec_exe_silent_install.htm



> Verify .NET 3.5 is installed.

You could use "RegistryRead" to look in registry:

      http://makemsi-manual.dennisbareis.com/registryread.htm

> Create 2 new folders.

If you are putting files in here then not required otherwise see "Directory"
command.

> Unregister files if they exist in folder1 or folder2 from previous installs.

Probably a custom action if you detect a batch file based install:

     http://makemsi-manual.dennisbareis.com/custom_actions.htm

> Copy new files to folder1.
> Copy new files to folder2.
> Register the new files in folder1 and folder2.

"Files" command (see "SelfReg" parm

> I would like the install to show up in add/remove programs.

Automatic


Bye,
Dennis

I've never used MakeMSI before but it looks great. We are currenly deploying
some dlls via batch file and it's very unreliable. Can anyone write a sample
install for me so I can get an understanding on how it works? I've looked at the
documentation but it's a little confusing.

What I need the install to do is:

Completely silent install.
Verify .NET 3.5 is installed.
Create 2 new folders.
Unregister files if they exist in folder1 or folder2 from previous installs.
Copy new files to folder1.
Copy new files to folder2.
Register the new files in folder1 and folder2.
I would like the install to show up in add/remove programs.

Thanks very much for anyone that can help!

Hi,

Please try the code I uploaded to the files area instead.

Thanks,
Dennis

alortiz007 wrote:
>
>
>
> Yes, sorry I forgot to mention that about the comma, and some spaces
> that I guess were added by the yahoo webpage, since the fixes where
> obvoius I did them...
>
> uploaded to the files area:
>

Thanks again...

Yes, sorry I forgot to mention that about the comma, and some spaces that I
guess were added by the yahoo webpage, since the fixes where obvoius I did
them...

uploaded to the files area:

http://f1.grp.yahoofs.com/v1/cHT9SlxQ2bT42LrC_gNYJa2grlBhPBh1TYE9XKS1I2Xbxzoi0S2\
ZNJg5AJmGYBNK9_GJEB_-8BY3XMLap-5mkHSSY2nx1SYL/20161RtmData.DBG.rar

http://f1.grp.yahoofs.com/v1/cHT9SrUxMjL42LrCv5WDNB3bGkHhFOMwe4b52DJaFY8q5EeMVvi\
YYYzjqek5__BV3HlsO82xAcr3s-3GbGOqSLR_86Uxxtwr/Log.rar

Once again thanks for all your help.

> --- In makemsi@yahoogroups.com, "Lynn" <lhaynes@> wrote:
> >
> > Dennis,
> >
> > We would like to download a prior version (9.045) of MakeMsi, as that's the
version we used in testing, and we're preparing to go live. Do you have prior
versions available for download on your website?
> >
> > Thanks,
> > Lynn Haynes
> >
>

If necessary, I have a copy of a MakeMSI install whose setup dialog box says
"9.0.45".  I tried uploading to the Files section, but the file is too big.

Hi,
yes please, I noticed I'd added an extra comma but I'm guessing you picked that
up as it would generate a different issue.  probably best to upload to teh
makemsi files area, either way zip it please.

Thanks
Dennis

--- In makemsi@yahoogroups.com, "alortiz007" <alortiz007@...> wrote:
>
> Dennis,
>
> Thanks for looking into this.
> I ran the latest release from today and made the changes you indicated.
> It failed with the message below
> I kept the debug file and the generated log directory, please let me know if
you want them.
>
> Thanks again.
>
>
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!![ Fatal  Error ]!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> Location  : line 41 of
"E:\RtmFactory\workDirs\20161\MsiScripts\RtmData\20161RtmData.MM"
> File Line : #output
> More Info?: out\20161RtmData.DBG.TXT (console file)
> Detected @: Line 16,701 of PPWIZ4MM.4MM (v08.307)
> PPWIZARD  : Length 441,471 bytes.  TimeStamped 20081102161944
> Running In: WIN32 ("WIN2K"), REXX-Regina_3.3(Julian)(MT) 5.00 20 Sept 2004
> Reason
> ~~~~~~
> Probable Syntax Error detected while checking generated file
> Got unexpected RC of "1" (expected RC of 21924)
> Error checking
"E:\RtmFactory\workDirs\20161\MsiScripts\RtmData\out\20161RtmData.MM\Log\Pass1+2\
.vbs"
>
>
> SYNTAX CHECK'S OUTPUT
> ~~~~~~~~~~~~~~~~~~~~~
>
E:\RtmFactory\workDirs\20161\MsiScripts\RtmData\out\20161RtmData.MM\Log\Pass1+2.\
vbs(2522, 11) Microsoft VBScript compilation error: Syntax error
>
> SYNTAX ERROR ON LINE #2522 (column 11)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 2515: MmID = "@VBS0304"
> 2516: DeleteTableRows("Dialog_ = 'UserRegistrationDlg'")
> 2519: MmID = "@VBS0305"
> 2520: TableNow ""
>
> 2522> margin --- {ErrorHere:column 11}=>
>

Dennis,

Thanks for looking into this.
I ran the latest release from today and made the changes you indicated.
It failed with the message below
I kept the debug file and the generated log directory, please let me know if you
want them.

Thanks again.


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![ Fatal  Error ]!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Location  : line 41 of
"E:\RtmFactory\workDirs\20161\MsiScripts\RtmData\20161RtmData.MM"
File Line : #output
More Info?: out\20161RtmData.DBG.TXT (console file)
Detected @: Line 16,701 of PPWIZ4MM.4MM (v08.307)
PPWIZARD  : Length 441,471 bytes.  TimeStamped 20081102161944
Running In: WIN32 ("WIN2K"), REXX-Regina_3.3(Julian)(MT) 5.00 20 Sept 2004
Reason
~~~~~~
Probable Syntax Error detected while checking generated file
Got unexpected RC of "1" (expected RC of 21924)
Error checking
"E:\RtmFactory\workDirs\20161\MsiScripts\RtmData\out\20161RtmData.MM\Log\Pass1+2\
.vbs"


SYNTAX CHECK'S OUTPUT
~~~~~~~~~~~~~~~~~~~~~
E:\RtmFactory\workDirs\20161\MsiScripts\RtmData\out\20161RtmData.MM\Log\Pass1+2.\
vbs(2522, 11) Microsoft VBScript compilation error: Syntax error

SYNTAX ERROR ON LINE #2522 (column 11)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2515: MmID = "@VBS0304"
2516: DeleteTableRows("Dialog_ = 'UserRegistrationDlg'")
2519: MmID = "@VBS0305"
2520: TableNow ""

2522> margin --- {ErrorHere:column 11}=>

Hi,

Normally not (I do recommend users keep old version when upgrading just in case)
but its possible I may have one in a backup at home, I'll check later.

Depending on how complex your msi is (with CAs etc), you may just want to bight
the bullet and compare the msi's using msidiff and compare file/registry from an
install of the old and new as a sanity check.


Bye,
Dennis

--- In makemsi@yahoogroups.com, "Lynn" <lhaynes@...> wrote:
>
> Dennis,
>
> We would like to download a prior version (9.045) of MakeMsi, as that's the
version we used in testing, and we're preparing to go live. Do you have prior
versions available for download on your website?
>
> Thanks,
> Lynn Haynes
>

Dennis,

We would like to download a prior version (9.045) of MakeMsi, as that's the
version we used in testing, and we're preparing to go live. Do you have prior
versions available for download on your website?

Thanks,
Lynn Haynes

Hi,

Now that I've read your email again you are obviously going over the 2GB
limit and this must be a MAKECAB.EXE bug so I am going to add a default
limit of:

    #define? COMPILE_CABDDF_MaxDiskSize
<$COMPRESS_MAX_VALID_CAB_SIZE>

The default value calulated as follows, please add to the start of your
script and try and let me know the results:


#ifndef COMPRESS_MAX_VALID_CAB_SIZE                            ;;0 would
work if not for MAKECAB.EXE bug(s)
     ;--- User hasn't overriden value so define to 2GB less a safety
margin ---
     #define   @@2GB           2000000000                       ;;2GB as
per "http://en.wikipedia.org/wiki/Gigabyte"
     #define   @@SafetyMargin  1 * 1024 * 1024                  ;;Allow 1MB
     #evaluate ^COMPRESS_MAX_VALID_CAB_SIZE^, ^<$@@2GB> -
(<$@@SafetyMargin>)^
#endif


Thanks
Dennis


Dennis wrote:
  >
  >
  > Hi,
  >
  > --- In makemsi@yahoogroups.com, "alortiz007" <alortiz007@...> wrote:
  > > I have had success as long as I can set everything to be in the
same disk, I opted for external cabs, as to reduce the inital load time
of the msi ( these setups can have several GBs in them.)
  > > I ran into a situtation with one of these projects, where there are
many files ( aprox 7100 files, 7.9 GB) where for some reason when set to
no disk size limit
  >

Hi,

Just uploaded a new version of MAKEMSI with cabinet caching.

You'd want to try it out, let me know how it goes.

Bye,
Dennis

Hi,



--- In makemsi@yahoogroups.com, "alortiz007" <alortiz007@...> wrote:
> I have had success as long as I can set everything to be in the same disk, I
opted for external cabs, as to reduce the inital load time of the msi ( these
setups can have several GBs in them.)
> I ran into a situtation with one of these projects, where there are many files
( aprox 7100 files, 7.9 GB) where for some reason when set to no disk size limit

I will make this page:

http://makemsi-manual.dennisbareis.com/compile_options.htm

Point to this page:

http://makemsi-manual.dennisbareis.com/cabinet_file_size_limitations.htm

My guess is that one of those limits is being exceeded.



> also, due to the fact that these files to be installed are already compressed
( PDF files),

PDFs (in general) can be compressed or uncompressed text.


>there is no gain in getting them into cab files, on the contrary, it
>has a considerable impact on the makemsi execution time

I will try to release a new version of MAKEMSI tonight which matches this doco;

    http://makemsi-manual.dennisbareis.com/compile.htm

I have documented how you can group files and supply different compression
options as well as caching the compiles (and that would encourage smaller
cabinets).



> leavingthe files  uncompressed but only referenced in
> the internal msi table

Sorry no doco on that the SDK doco is what you'd need and its non-trivial.  The
MAKEMSI file(s) commands don't support them.

Bye,
Dennis

Hi,

Thanks for reporting it, will fix for next release.

--- In makemsi@yahoogroups.com, "Mockenhaupt, Christoph" <c.mockenhaupt@...>
wrote:
>
> Hi Dennis,
>
> I just stumbled over a little bug in uisample.mmh. When disabling the
> automatic detection if typical button is required, syntax check of the
> generated vbscript fails:

Hi,

I have worked it out and will fix it soon (hopefully tonight) and release a new
version, I think this bugs been there for ages, I was glad it was't my recent
changes :-)

For now you can use "INTEGER" in place of "DWORD".

Bye,
Dennis

--- In makemsi@yahoogroups.com, "Mockenhaupt, Christoph" <c.mockenhaupt@...>
wrote:

> I updated MakeMsi from 8.148 to 9.296.
> Unfortunaltely, I now get validation error ICE70 for some registry entries:
>
> ICE70        ERROR     The value '#&H1389' is an invalid numeric value for
> registry entry RegKey005.  If you meant to use a string, then the string
> value entry must be preceded by ## not #.
>
> I call the Registry macro with VALUE="&H1389" and TYPE="DWORD".

Hi Dennis,

First, I would like to say thanks for your great product.

I think I might have found a bug and have some questions...

I intend to use makemsi to build msi setups by batch, these are intended for
large sets of data.
I have had success as long as I can set everything to be in the same disk, I
opted for external cabs, as to reduce the inital load time of the msi ( these
setups can have several GBs in them.)
I ran into a situtation with one of these projects, where there are many files (
aprox 7100 files, 7.9 GB) where for some reason when set to no disk size limit,
it fails ( I don't have that error message at hand), but when I set it, instead
of creating the disks to fit a DVD-R, it creates the cab file for each disk to
be of exactly 387 MB (405,872,640 bytes) What I added into my make file is:

#define+ COMPILE_TYPE             <$COMPILE_CAB_EXTERNAL_WITH_MSI>
#define+ COMPILE_CABDDF_MaxDiskSize <$COMPRESS_CAPACITY_DVD+R(SL)>
#define+ COMPILE_RESERVED_BYTES_ON_MEDIA1      314572800

#define+ COMPILE_CABDDF_Compress             OFF
#define+ COMPILE_COMPRESS_4_PRODUCTION  OFF

also, due to the fact that these files to be installed are already compressed (
PDF files), there is no gain in getting them into cab files, on the contrary, it
has a considerable impact on the makemsi execution time, I saw in another post
you mention something about not leaving the files uncompressed but only
referenced in the internal msi table, however I fail to find documentaion to
that end, can you provide some guidance and /or samples on how to do that?

Thanks,
Alberto

Hi Dennis,

I updated MakeMsi from 8.148 to 9.296.
Unfortunaltely, I now get validation error ICE70 for some registry entries:

ICE70        ERROR     The value '#&H1389' is an invalid numeric value for registry entry RegKey005.  If you meant to use a string, then the string value entry must be preceded by ## not #.

I call the Registry macro with VALUE="&H1389" and TYPE="DWORD". Is this no longer supported? At least in the docu there is still an example like this so I suppose this should be working. Using the decimal value (VALUE="5001") works fine, but I would prefer to use the hex value.

--
Cheers
Christoph

Hi Dennis,

I just stumbled over a little bug in uisample.mmh. When disabling the automatic detection if typical button is required, syntax check of the generated vbscript fails:

SYNTAX ERROR ON LINE #46053 (column 59)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
46045: RowUpdate()
46047: MmID = "@VBS8840"
46048: TableNow ""
46049: pb_FileHash("Y")

46053> dim DisableTypicalButton : DisableTypicalButton = trueif   {ErrorHere:column 59}=> DisableTypicalButton then

The code in uisample.mmh:
---------------------------------------------------------------------------------------
#( ''
   #define DisableTypicalSetupButtonIfRequired

   ;--- Decide if we need the typical button --------------------------------
   dim DisableTypicalButton : DisableTypicalButton = true
   #if ['<$UISAMPLE_DISABLE_TYPICAL_SETUP>' = 'S']
       ;--- May want to disable it... ---------------------------------------
       <$Table "Feature">
           #(
               <$Row
                   @WHERE=^<$UISAMPLE_DISABLE_TYPICAL_SETUP_IF_LEVEL>^
                   @Code="Y"
               >
           #)
               ;--- At least one feature that is deselected by default ----------
               DisableTypicalButton = false
           <$/Row>
       <$/Table>
   #endif

   ;--- Disable the button? -------------------------------------------------
   if  DisableTypicalButton then<?NewLine>
...
---------------------------------------------------------------------------------------

Adding "<?NewLine>" between "#endif" and ";--- Disable the button?" solves the problem. I havn't look at the problem any further, but I suppose the <$Table> and or <$Row> macro inserts a "<?NewLine>" somewhere and everything is fine if UISAMPLE_DISABLE_TYPICAL_SETUP is "S".

Sorry, no sample code. But setting
#define UISAMPLE_DISABLE_TYPICAL_SETUP A
in TryMe.mm will reproduce the problem.

--
Cheers
Christoph

Hi,

Yahoo just lost my original reply so sorry but this is the short version...

--- In makemsi@yahoogroups.com, "Tim P" <t1m_p@...> wrote:

> So the "quick-and-dirty" approach seems to be for me to use the WrapInstall
command to drop everything I want into a temp folder and then, as the final
action, use ExeCa to invoke the original installer.

Wrap Install does the "ExeCa" already




>no user input, no questions,

    http://makemsi-manual.dennisbareis.com/msiexec_exe_silent_install.htm



> no uninstaller

    http://makemsi-manual.dennisbareis.com/no_installation_registration.htm



> makedir c:\tempinst

Not required

> output embedded files with folder structure kept to c:\tempinst

"Files" command(s) - "TREE" option

> run c:\tempinst\install.exe

"Execa"  Or use "Wrap Install" for both commands

Bye,
Dennis