PDA

View Full Version : ICE error reference



NewsArchive
01-25-2001, 01:00 AM
INSTALLDIR is not present in the directory table shown in the power
editor, so I cannot delete it there. If I delete it in orca it will
just re-appear when I rebuild my project from ISWI, so I am not getting
to the root of the problem this way.

Any more ideas,

Simon.

Florian Neu wrote:

> Delete INSTALLDIR from directory Tabel...
>
> ###
>
> Simon Woodman schrieb:
>
>
>> Has anyone experienced an ICE Error 56 before? How would I go about
>> solving it using ISWI 1.52? The error that I get from ORCA is:
>>
>> ICE56
>> ERROR
>> Directory 'INSTALLDIR' is an invalid root directory. It or one of its
>> children contains files. Only TARGETDIR or its children can have files.
>>
>> In the directory table I have a directory called INSTALLDIR which has
>> the default direcrtory SOURCEDIR. I have four components that have a
>> lot more components generated by dynamic linking. These four components
>> show that INSTALLDIR is the parent in the directory table but all of the
>> generated ones show that TARGETDIR is the parent. If I change INSTALLDIR
>> to TARGETDIR using orca then the error goes away.
>>
>> How do I get ISWI to use TARGETDIR instead of INSTALLDIR for the actual
>> components as it is not listed in the drop down list?
>>
>> Any help would be much appreciated.
>>
>> Simon
>>
>> ----------------------
>> Simon Woodman
>> IBM Hursley Park
>> S.J.Woodman@uk.ibm.com

NewsArchive
03-02-2001, 01:00 AM
Thanks for the answer, but
unfortunately I didn't find any message about this problem. And the found
solution
isn't formally good because we have to certify just the same setup package
with we'll send to customers.


"Rune G" <rg#world-online.no> wrote in message news:3a9f5bb3@12.41.20.38...
> The way I did this was that I created a setup with only one language
> that I runned the validation test on from ORCA.exe..
>
> There is a way to merge the .mst file into the .msi file for validation
> checking,
> but I don't know how.
>
> I think I remember that there was a post earlier (in end of january or in
> february) that
> stated how to do this...
>
> Check earlier postings...
>
> Hope this helps..
> --Rune G
>
> "Arthur Zeytunyan" <badger@reksoft.ru> wrote in message
> news:3a9f4f73$1@12.41.20.38...
> > Hi!
> > Could you please help me with the following:
> > I have a multiple language installation. So all the localized dialogs,
> etc.
> > are in MST-files not in MSI-file. If just to validate MSI-file we will
> have
> > some errors like "Invalid DefaultDir string", "Invalid Filename",
"Unknown
> > action", etc. I know if to build an MSI applying one of the Transforms
all
> > these errors will disappear. But if to ask Veritest is this acceptable,
> they
> > say: " The MSI file itself must be error free (fully capable of error
free
> > installation) prior to having the MST file applied to it".
> >
> > So what can I do to have error free MSI-file and still with a
possibility
> to
> > apply different MST-files according to selected language?
> >
> > Thanks a lot in advance for the help
> >
> > SY, Arthur
> >
> >
>
>

NewsArchive
03-02-2001, 01:00 AM
"Arthur Zeytunyan" <badger@reksoft.ru> wrote in message
news:3a9f75c7@12.41.20.38...
> Thanks for the answer, but
> unfortunately I didn't find any message about this problem.
Some discussion about multi-language setups and transforms was in
news://installshield.iswi.international
I don't remember seeing a good and easy solution for your problem.

> And the found solution isn't formally good because we have to certify
> just the same setup package with we'll send to customers.

> > I have a multiple language installation. So all the localized dialogs,
> > etc. are in MST-files not in MSI-file.
> > I know if to build an MSI applying one of the Transforms all these
> > errors will disappear. But if to ask Veritest is this acceptable,
> > they say: " The MSI file itself must be error free
> > (fully capable of error freeinstallation) prior to having the MST file
applied to it".
I do understand that requirement as you can't stop one of your users from
double
clicking on your MSI file without first applying the transform.

> > > So what can I do to have error free MSI-file and still with a
possibility
> > > to apply different MST-files according to selected language?
If i remember correctly the discussion in iswi.international mentioned a way
to create a "standard" language MSI and using two transforms to change it to
another language. I got the impression that this would require more
knowledge of transforms than i have and is not really supported by ISWI.

The only easy solution that i can think of is using the release wizard to
create a release per language.
This will use more disk space as you have a full MSI for each language and
not just the transform but at least every one of the MSI files will work
correctly if started by just double-clicking it.

If you find a good solution to your problem please let us know.

Regards,
---
Klaus Neumayer Phone:+43/316/25 20 21 371
Materna Fax: +43/316/25 20 21 358
Development Center Mobile Solutions
http://www.graz.materna.com

NewsArchive
07-31-2001, 12:00 AM
There is a program for editing the .ism file it's called Orca and I think
you can get it from the Microsoft site (I typed "Orca install" into yahoo
and it found me a download)

Thanks
Gaz

"Gareth Homewood" <beer@drink.com> wrote in message
news:3b66b251$1@news.installshield.com...
> Your error ICE36 is because you have a short cut (to a program exe) on the
> program start up menu that is using a icon file if you are using a program
> exe then the exe should contain the icon and the field in the install
short
> cut properties should be empty. I know this because I had the same
problem.
>
> If that does not fix it goto (on your Windows installer)
> Organize Your Setup | General Information
>
> And remove the Display icon
> the might fix it and if that don't I ain't got a clue
>
> Thanks
> Gaz
>
>
> "Eyvind" <DONT_SPAM_eeb@dk.damgaard.com> wrote in message
> news:3b66ab82$1@news.installshield.com...
> > Hi all
> >
> > I am using IPWI 2.03
> >
> > I have some trouble with the following ICE errors/warnings :
> >
> > ICE03 Error Invalid format string; Table: Control, Column: Text, Key(s):
> > Translation.Memo_NL http://dartools/iceman/ice03.html Control Text
> > Translation Memo_NL
> >
> > I have tracked the bug to an .RTF file, which is a license agreement for
> > Holland. OK... so the error was in the RTF document, i opened the RTF in
> > word, and saved it as a new file, and the filesize was a few bytes
> bigger...
> > But the problem is still there. I have alot of other licensedocuments,
but
> > they are all ok. If i remove the RTF doc, the ICE error is gone. What
> could
> > be wrong here ?
> >
> >
> > ICE36 Warning Icon Bloat. Icon MyProgram.exe is not used in the Class,
> > Shortcut, or ProgID table. This adversely affects performance.
> > http://dartools/iceman/ice36.html Icon Name MyProgram.exe
> >
> > This is because of an extra icon, in the icon table.. but how do you
> delete
> > that extra icon from IPWI ?
> >
> >
> > I have alot of these... :
> >
> > ICE45 Warning Row 'DLG_Upgrade.Bitmap1' in table 'Control' has bits set
in
> > the 'Attributes' column that are reserved. They should be 0 to ensure
> > compatability with future installer versions.
> > http://dartools/iceman/ice45.html Control Attributes DLG_Upgrade Bitmap1
> >
> > Where can i edit these bits ? Or how can i fix the warning ?
> >
> >
> > Also... if i setup an installation project, and include all the
languages
> > from the WEST installation, i get TONS of errors and warnings when
> > validating... is there a workaround for this ?
> >
> > Thanks in advance
> >
> > --
> > Regards
> > Eyvind
> >
> > PS. Is there a tool around for editing the .ISM files ?
> >
> >
> >
> >
> >
> >
> >
> >
>
>

NewsArchive
07-31-2001, 12:00 AM
You can only open MSI and MSM files with ORCA.

i dont know how to edit the control bits in IPWI... :(

Stockwell_LEDS
12-31-2001, 10:33 AM
I found a location where the ice errors are explained.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/ices_1xrn.asp


I guess its probably too much to ask InstallShield to provide some sort of user friendliness in terms of having meaningful error codes

I can't find the table my error 'not a valid key is referring to'

the first table is easy 'directory'

but according to the reference material there should be a second table somewhere.

any help would be appreciated.