PDA

View Full Version : Miscellaneous Posts



NewsArchive
08-24-2001, 12:00 AM
?
Are you drunking?

NewsArchive
08-24-2001, 12:00 AM
Merging and extracting COM data take the longest.

I wish ISD7 supported compile on demand. Builds really take a looooong
time.

At 3000 files, I suspect that my app is only average size for a multi-tiered
web app. But I get the impression that ISD7 was only tested with small
installations.


"Kent Foyer" <no@address.com> wrote in message
news:3b868858$1@news.installshield.com...
> Where is the build slow? If you look in the output window what table is
it
> building that is slow? Are you building compressed?
>
> Also, we have two build options. In the "Advanced Settings" of the
Release
> wizard there is an "Optimize size" check box. This is from help:
>
> "Select this option to improve the compression of your data files.
Selecting
> this option will generally decrease the size of your compressed files, but
> the build process may take more time to complete."
>
> So if you select this box (which is default) the build will take longer
> because it is better compression. If size is of no concern, but you want
a
> faster build deselect this check box.
>
> Hope this helps.
>
> Kent
>
> "Walter" <walterfiedler@ online.com> wrote in message
> news:3b865486@news.installshield.com...
> > Hello,
> > I have just migrate my project from IS6 to Dev7 (win98 SE).
> >
> > The build time is apprex. 10 times longes as IS6 takes.
> >
> > Is it possible to increase this speed?
> >
> > Thanks
> > Walter
> >
> >
> >
>
>

NewsArchive
08-24-2001, 12:00 AM
Hi Evan,

To try and speed things up for you, you may want to try self-registration
instead of COM extraction. Not everyone needs COM extraction--most people
can probably just use self-registration.

Also, build-time COM extraction is only needed when the COM data changes a
lot. If the COM data doesn't change you can use the one-time COM extraction
in the component wizard.

You said merging was also slow. How many merge are included?

Also, we are going to optimize the COM extraction process.

Kent


"Evan A. Barr" <Not@Public.com> wrote in message
news:3b86a1d5@news.installshield.com...
> Merging and extracting COM data take the longest.
>
> I wish ISD7 supported compile on demand. Builds really take a looooong
> time.
>
> At 3000 files, I suspect that my app is only average size for a
multi-tiered
> web app. But I get the impression that ISD7 was only tested with small
> installations.
>
>
> "Kent Foyer" <no@address.com> wrote in message
> news:3b868858$1@news.installshield.com...
> > Where is the build slow? If you look in the output window what table is
> it
> > building that is slow? Are you building compressed?
> >
> > Also, we have two build options. In the "Advanced Settings" of the
> Release
> > wizard there is an "Optimize size" check box. This is from help:
> >
> > "Select this option to improve the compression of your data files.
> Selecting
> > this option will generally decrease the size of your compressed files,
but
> > the build process may take more time to complete."
> >
> > So if you select this box (which is default) the build will take longer
> > because it is better compression. If size is of no concern, but you
want
> a
> > faster build deselect this check box.
> >
> > Hope this helps.
> >
> > Kent
> >
> > "Walter" <walterfiedler@ online.com> wrote in message
> > news:3b865486@news.installshield.com...
> > > Hello,
> > > I have just migrate my project from IS6 to Dev7 (win98 SE).
> > >
> > > The build time is apprex. 10 times longes as IS6 takes.
> > >
> > > Is it possible to increase this speed?
> > >
> > > Thanks
> > > Walter
> > >
> > >
> > >
> >
> >
>
>

NewsArchive
08-24-2001, 12:00 AM
The problem with using COM extraction from the component wizard is that you
can't run it on an existing component. It creates a new component and then
you have to make all the other changes to it to match the original
component. I've got too many COM objects to do this.

As for self-registration, that is against best practices.

I am using 20 merge modules. Basically, I try to use merge modules for all
third party and Windows components if one is available. At minimum, this
means I'm using the same Component Code for their components.


"Kent Foyer" <no@address.com> wrote in message
news:3b86b967$1@news.installshield.com...
> Hi Evan,
>
> To try and speed things up for you, you may want to try self-registration
> instead of COM extraction. Not everyone needs COM extraction--most people
> can probably just use self-registration.
>
> Also, build-time COM extraction is only needed when the COM data changes a
> lot. If the COM data doesn't change you can use the one-time COM
extraction
> in the component wizard.
>
> You said merging was also slow. How many merge are included?
>
> Also, we are going to optimize the COM extraction process.
>
> Kent
>
>
> "Evan A. Barr" <Not@Public.com> wrote in message
> news:3b86a1d5@news.installshield.com...
> > Merging and extracting COM data take the longest.
> >
> > I wish ISD7 supported compile on demand. Builds really take a looooong
> > time.
> >
> > At 3000 files, I suspect that my app is only average size for a
> multi-tiered
> > web app. But I get the impression that ISD7 was only tested with small
> > installations.
> >
> >
> > "Kent Foyer" <no@address.com> wrote in message
> > news:3b868858$1@news.installshield.com...
> > > Where is the build slow? If you look in the output window what table
is
> > it
> > > building that is slow? Are you building compressed?
> > >
> > > Also, we have two build options. In the "Advanced Settings" of the
> > Release
> > > wizard there is an "Optimize size" check box. This is from help:
> > >
> > > "Select this option to improve the compression of your data files.
> > Selecting
> > > this option will generally decrease the size of your compressed files,
> but
> > > the build process may take more time to complete."
> > >
> > > So if you select this box (which is default) the build will take
longer
> > > because it is better compression. If size is of no concern, but you
> want
> > a
> > > faster build deselect this check box.
> > >
> > > Hope this helps.
> > >
> > > Kent
> > >
> > > "Walter" <walterfiedler@ online.com> wrote in message
> > > news:3b865486@news.installshield.com...
> > > > Hello,
> > > > I have just migrate my project from IS6 to Dev7 (win98 SE).
> > > >
> > > > The build time is apprex. 10 times longes as IS6 takes.
> > > >
> > > > Is it possible to increase this speed?
> > > >
> > > > Thanks
> > > > Walter
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
08-25-2001, 12:00 AM
I just timed my build and it took 13 minutes. Including the areas I have
already mentioned, the time hogs were Resolving strings and especially Build
Files.

I now do as much debugging as possible in Orca.

NewsArchive
08-30-2001, 12:00 AM
Hi Martin,

"Martin Markevics" <martinm@installshield.com> wrote in message
news:3b8d3de0$1@news.installshield.com...
> The Icon Index that you are setting (e.g. 5) is the icon index that is
used
> (from the given binary) to build an icon in the Icon table. The Icon_
> column of the Class table refers to this built entry in the Icon table.
>>> ... rest deleted for clarity...

I can live with your explanation of why the IconIndex in the Class table is
initially 1 (although I do not agree 100% with it). This is really not the
main problem though.

Let me give an example to show what I mean.

Say I want to change the Icon table myself. The Direct Editor lets me do
this -- Great.
I add my own entry, IconA, which points to file IconA.exe, which in turn
contains 10 icons. For simplicity lets say the icon index values range from
1 to 10.

Now, I have 10 vanilla COM components associated with a single feature in my
product. I want these 10 components to all share the same Icon table
entry -- namely IconA. To illustrate the problem clearly lets say that
component 1 uses icon index 10, component 2 uses 9, and so on ending with
component 10 using icon index 1.

To accomplish this I turn to the Direct Editor again -- wonderful. I browse
the Class table looking for the 10 COM Classes associated with my 10 COM
components. I modify two things for each component -- 1) Icon_ field becomes
IconA, and 2) IconIndex changes as per what I described above (i.e.
component 1 has value 10, component 10 has value 1).

After building using ISD v7.0.0.224, nine out of the ten components wil
have the correct icon index values in the Class table when we open up the
MSI file in ORCA.

Which one fails? This depends on which component is processed during the
build first.

What is wrong? The component that fails has Icon index 1 instead of what I
specified in the Direct Editor's Class table.

For simplicity lets say it is component 1 that gets built first. After the
build I would expect component 1 to have IconIndex value of 10 in the class
table. Instead what I see is that it has IconIndex 1. All the other
components have the correct icon index value.

Also note that I have not touched the user interface of the component view
to make these changes -- all changes were made using the direct editor.

I see this as two separate problems -- one that I can live with easily (as
per my very first statement), and one that I can live with but much more
painfully!

How painful you ask? My workaround was to generate a fake component that has
an icon in the class table that is always built first. I achieve this by
naming the component "__IconBug" and giving it GUID {0000000....000} - then
I export to ISV format and reimport to ISM. Voila, __IconBug is built first.

Now, if I were to insert this component into the example above, I end up
with all ten components having the correct icon but an extra component I do
not need.

Luckily I can remove the component with a post build script.

Sincerely,
Adrian Accinelli

NewsArchive
08-31-2001, 12:00 AM
Thank you Klaus! That did the trick.

Question: Did you really accidently set the version number to 1.0.1q? That
doesn't sound like an acident to me. As for me, I meant to set the version
number to 1.0 (Build 201)! I suppose one could call it an accident that we
didn't read the fine print!

Thanks again!
Don


"Klaus Neumayer" <klaus.neumayer@graz.materna.com> wrote in message
news:3b8f891e$1@news.installshield.com...
> "dsanborn" <dsanborn@home.com> wrote in message
> news:3b8eb99d$1@news.installshield.com...
> > When we attempt to install our application
> > (ported from IS 6.30 to ID Dev> 7),
> > we get the following error message:
> >
> > 'Error 1406: Could not write VersionMinor to
> >
>
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{GUID
> > }. Verify that you have sufficient access to that key, or contact your
> > support personnel.'
> >
> > Note: GUID refers to an actual GUID... I'm just to lazy to type it!
> >
> > We have attempted installation as a user with Admin privilidges and as
> > Administrator. We've also tried this on multiple machines. We get the
> > message on both Win NT 4.0 and Win 2000.
> What is your "Product Version" set to?
>
> I remember getting this error message when i accidently set the product
> version to something like "1.0.1q"
> The Installer wants to write the minor part of the version number to a
> REG_DWORD.
> If if is unable to convert the minor part of your version number to a
DWORD
> this seems to trigger the error message you got.
>
> Hope that helps,
> Klaus
>
>

NewsArchive
08-31-2001, 12:00 AM
Validation should have detected this problem. Did you run a
validation? Is this a basic MSI project or a standard project?

--
Stefan Krueger - Independent Setup Consultant

InstallSite - code samples, tips, tools, bug lists, and more
http://www.installsite.org http://www.installsite.de (GERMAN)
Support and consulting http://www.installsite.org/krueger

Stefan Krueger and the InstallSite web site are not affiliated
with InstallShield Software Corporation.

"dsanborn" <dsanborn@home.com> schrieb im Newsbeitrag
news:3b8fbdb5$1@news.installshield.com...
> Thank you Klaus! That did the trick.
>
> Question: Did you really accidently set the version number to
1.0.1q? That
> doesn't sound like an acident to me. As for me, I meant to set the
version
> number to 1.0 (Build 201)! I suppose one could call it an accident
that we
> didn't read the fine print!
>
> Thanks again!
> Don
>
>
> "Klaus Neumayer" <klaus.neumayer@graz.materna.com> wrote in message
> news:3b8f891e$1@news.installshield.com...
> > "dsanborn" <dsanborn@home.com> wrote in message
> > news:3b8eb99d$1@news.installshield.com...
> > > When we attempt to install our application
> > > (ported from IS 6.30 to ID Dev> 7),
> > > we get the following error message:
> > >
> > > 'Error 1406: Could not write VersionMinor to
> > >
> >
>
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
\{GUID
> > > }. Verify that you have sufficient access to that key, or
contact your
> > > support personnel.'
> > >
> > > Note: GUID refers to an actual GUID... I'm just to lazy to type
it!
> > >
> > > We have attempted installation as a user with Admin privilidges
and as
> > > Administrator. We've also tried this on multiple machines. We
get the
> > > message on both Win NT 4.0 and Win 2000.
> > What is your "Product Version" set to?
> >
> > I remember getting this error message when i accidently set the
product
> > version to something like "1.0.1q"
> > The Installer wants to write the minor part of the version number
to a
> > REG_DWORD.
> > If if is unable to convert the minor part of your version number
to a
> DWORD
> > this seems to trigger the error message you got.
> >
> > Hope that helps,
> > Klaus
> >
> >
>
>

NewsArchive
09-04-2001, 12:00 AM
Thanks for your response, I did in fact have both a component and directory
by the name of database (all lower case). I've now changed both of these to
a different name, but I still get the same problem. Any other suggestions
out there?

(I'm using Installshield Developer 7)
Thanks,
Jason.


"David Thornley" <NoReplyPlease@installshield.com> wrote in message
news:3b951e74$1@news.installshield.com...
> One of my co-workers was tackling an issue with the same symptoms and it
> turns out that if you have a directory or a property called DATABASE that
> you will get this behavior. DATABASE is a reserved word. There may be
> other properties that cause this error as well such as TRANSFORMS.
>
>
> Regards
> David Thornley
>
> "Jason" <jason@joeprogrammer.net> wrote in message
> news:3b950970$1@news.installshield.com...
> > Hi,
> >
> > During an installation the following error occurs:
> >
> > Internal Error 2318. D:\WINNT\Installer\
> >
> > I click the OK button, then receive this error:
> >
> > Error: -1603 Fatal error during installation.
> >
> > The installation then fails. For the life of me I can't figure out what
> the
> > problem is. Any thoughts would be GREATLY appreciated.
> >
> > Thanks,
> > Jason Vander Zalm.
> >
> >
>
>

NewsArchive
09-04-2001, 12:00 AM
lease use the direct editor to view the directory table. Make sure that the
directory identifier did not remain as DIRECTORY even though you changed the
path in the component view. You may have changed the path, but you need to
use the direct editor to verify that the identifier does not still conflict.

When you change the directory identifier in the directory table, please make
sure you also go to the component table and change the Directory_ Column for
the component you want to install to the database folder to match the
unique name you created in the directory table.

Regards
David Thornley
"Jason" <jason@joeprogrammer.net> wrote in message
news:3b9527e4$1@news.installshield.com...
>
> Thanks for your response, I did in fact have both a component and
directory
> by the name of database (all lower case). I've now changed both of these
to
> a different name, but I still get the same problem. Any other suggestions
> out there?
>
> (I'm using Installshield Developer 7)
> Thanks,
> Jason.
>
>
> "David Thornley" <NoReplyPlease@installshield.com> wrote in message
> news:3b951e74$1@news.installshield.com...
> > One of my co-workers was tackling an issue with the same symptoms and it
> > turns out that if you have a directory or a property called DATABASE
that
> > you will get this behavior. DATABASE is a reserved word. There may be
> > other properties that cause this error as well such as TRANSFORMS.
> >
> >
> > Regards
> > David Thornley
> >
> > "Jason" <jason@joeprogrammer.net> wrote in message
> > news:3b950970$1@news.installshield.com...
> > > Hi,
> > >
> > > During an installation the following error occurs:
> > >
> > > Internal Error 2318. D:\WINNT\Installer\
> > >
> > > I click the OK button, then receive this error:
> > >
> > > Error: -1603 Fatal error during installation.
> > >
> > > The installation then fails. For the life of me I can't figure out
what
> > the
> > > problem is. Any thoughts would be GREATLY appreciated.
> > >
> > > Thanks,
> > > Jason Vander Zalm.
> > >
> > >
> >
> >
>
>

NewsArchive
09-04-2001, 12:00 AM
THANKS DAVID.

That was exactly the problem. I would have never figured that one out
without your help. I would think that Installshield should at a minimum
provide a warning if a reserved word is used as a directory name. Absolutely
no reference to the error number, or the solution anywhere in the
documentation or the knowledge base (or msdn).

Thanks again,
Jason.


"David Thornley" <NoReplyPlease@installshield.com> wrote in message
news:3b952b9e$1@news.installshield.com...
> lease use the direct editor to view the directory table. Make sure that
the
> directory identifier did not remain as DIRECTORY even though you changed
the
> path in the component view. You may have changed the path, but you need
to
> use the direct editor to verify that the identifier does not still
conflict.
>
> When you change the directory identifier in the directory table, please
make
> sure you also go to the component table and change the Directory_ Column
for
> the component you want to install to the database folder to match the
> unique name you created in the directory table.
>
> Regards
> David Thornley
> "Jason" <jason@joeprogrammer.net> wrote in message
> news:3b9527e4$1@news.installshield.com...
> >
> > Thanks for your response, I did in fact have both a component and
> directory
> > by the name of database (all lower case). I've now changed both of these
> to
> > a different name, but I still get the same problem. Any other
suggestions
> > out there?
> >
> > (I'm using Installshield Developer 7)
> > Thanks,
> > Jason.
> >
> >
> > "David Thornley" <NoReplyPlease@installshield.com> wrote in message
> > news:3b951e74$1@news.installshield.com...
> > > One of my co-workers was tackling an issue with the same symptoms and
it
> > > turns out that if you have a directory or a property called DATABASE
> that
> > > you will get this behavior. DATABASE is a reserved word. There may
be
> > > other properties that cause this error as well such as TRANSFORMS.
> > >
> > >
> > > Regards
> > > David Thornley
> > >
> > > "Jason" <jason@joeprogrammer.net> wrote in message
> > > news:3b950970$1@news.installshield.com...
> > > > Hi,
> > > >
> > > > During an installation the following error occurs:
> > > >
> > > > Internal Error 2318. D:\WINNT\Installer\
> > > >
> > > > I click the OK button, then receive this error:
> > > >
> > > > Error: -1603 Fatal error during installation.
> > > >
> > > > The installation then fails. For the life of me I can't figure out
> what
> > > the
> > > > problem is. Any thoughts would be GREATLY appreciated.
> > > >
> > > > Thanks,
> > > > Jason Vander Zalm.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
09-05-2001, 12:00 AM
> no reference to the error number, or the solution anywhere in the
> documentation or the knowledge base (or msdn).

.... except on InstallSite. here's the relevant article from the Bugs
Bulletin:

Runtime Error 2318 if Subdirectory "Database" is Used
Description:
Error message "Internal Error 2318. C:\WINDOWS\TEMP" is displayed at
runtime. The path in the error message is the TEMP directory. This
happens if one of your components has a destination directory of
[INSTALLDIR]\Database. The error message is displayed before the
InstallWelcome dialog in Basic MSI projects, or during installation
progress in Standard projects.
Cause:
ISD creates an entry in the Directory table, called "DATABASE". The
presence of this entry is enough to trigger the error. It appears that
this is a reserved word, but not taken into account.
Workarounds:
Renaming the entry using the Direct Editor to something else fixes the
problem - you don't need to change the directory itself, just the
table key.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00.
Created: 2001-08-30 InstallShield tracking number: 1-6JAXQ

--
Stefan Krueger - Independent Setup Consultant

InstallSite - code samples, tips, tools, bug lists, and more
http://www.installsite.org http://www.installsite.de (GERMAN)
Support and consulting http://www.installsite.org/krueger

Stefan Krueger and the InstallSite web site are not affiliated
with InstallShield Software Corporation.

NewsArchive
09-10-2001, 12:00 AM
Hi Stefan,

The additional entries are not processed during an installation -- otherwise
I would have found this bug much sooner ;)

Casual installations that are not targeted towards certification do not have
to worry about this bug. Once you try validating however, you will get two
ICE03 errors (one for Component_, the other for File_) for every
DuplicateFile table entry that is not intended for the release.

In case other people are having problems here is a variant of the script I
am using (using temporarily I hope):
'======================================================
option explicit
Const msiOpenDatabaseModeTransact = 1
Const msiViewModifyDelete = 6

Dim Installer : Set Installer =
Wscript.CreateObject("WindowsInstaller.Installer") : CheckError
Dim argNum, argCount:argCount = Wscript.Arguments.Count
Dim databasePath : databasePath = Wscript.Arguments(0)
Dim database : set database = Installer.OpenDatabase(databasePath,
msiOpenDatabaseModeTransact ) : CheckError
Dim query : query = "SELECT FileKey, Component_ FROM DuplicateFile"
Dim dupFileView, dupFileRec, compView, compRec

Set dupFileView = database.OpenView(query) : CheckError
dupFileView.Execute : CheckError

Do
Set dupFileRec = dupFileView.Fetch
If dupFileRec Is Nothing Then Exit Do
query = "Select Component From Component WHERE Component = '" &
dupFileRec.StringData(2) & "'"
set compView = database.OpenView( query ) : CheckError
compView.Execute : CheckError
set compRec = compView.Fetch
if compRec Is Nothing Then
Wscript.Echo "Invalid: " & dupFileRec.StringData(1) & ", " &
dupFileRec.StringData(2) & "."
dupFileView.Modify msiViewModifyDelete, dupFileRec : CheckError
End if
set compRec = nothing
set compView = nothing
Loop
set dupFileRec = nothing
set dupFileView = nothing

database.Commit
Wscript.Quit 0

'
' Helper Functions
'

Sub CheckError
Dim message, errRec
If Err = 0 Then Exit Sub
message = Err.Source & " " & Hex(Err) & ": " & Err.Description
If Not installer Is Nothing Then
Set errRec = installer.LastErrorRecord
If Not errRec Is Nothing Then message = message & vbLf & errRec.FormatText
End If
Fail message
End Sub

Sub Fail(message)
Wscript.Echo message
Wscript.Quit 2
End Sub

'======================================================

Sincerely,
Adrian Accinelli

"Stefan Krueger" <nwsgrp@installsite.org> wrote in message
news:3b9d3904$1@news.installshield.com...
> Are the file being duplicated? Since their DuplicateFile entry
> references a non existing component I would expect that they are not
> duplicated.
>
> --
> Stefan Krueger - Independent Setup Consultant
>
> InstallSite - code samples, tips, tools, bug lists, and more
> http://www.installsite.org http://www.installsite.de (GERMAN)
> Support and consulting http://www.installsite.org/krueger
>
> Stefan Krueger and the InstallSite web site are not affiliated
> with InstallShield Software Corporation.

NewsArchive
09-12-2001, 12:00 AM
Hi Mike,

Sorry if I wasn't clear enough about the listview problem so let me clarify
this even more.

1. When adding files to a component in the view "Specify Application
Data/Files" I right-click on the [INSTALLDIR] and select the menu item "Add
Component". I make sure the newly added component is selected and if needed
I alter the properties for the selected component. Then I drag'n'drop files
from the listview "Source computer's files" to the listview "Destination
computer's files". But sometimes the listview "Destination computer's files"
stay empty. If I drag'n'drop the same file again I receive an error saying
that the file is already there. If I click on another component the files in
that component will be displayed but if I switch back to the component that
didn't show the files it will still be empty. If I click on the "Advanced
Views/Components" I can there see the component in question along with the
files associated with that component. However, if I now switch back to the
view "Specify Application Data/Files" and select that component the files
will finally show. This *bug* (or whatever it is) happens alot. You may have
to add a couple of components (say 10-15) before this will happen though.

2. The treeview "Source computer's folders" and the listview "Source
computer's files" are both displayed instantly. It is the listview
"Destination computer's files" that is extremely slow. Even on my 1GHz DDR
machine the items are displayed approximately 2 items per second. That is
terrible. The next time I switch to that view the data is cached and will
thus be displayed instantly. But if I add a new component all the files are
re-populated at the same slow speed as before (~2 items/s). When switching
to the "Specify Application Data/Files" view the treeview "Destination
computer's folders" have the item "[INSTALLDIR]" pre-selected thus
displaying just about all the files in my project. But still, reading a
file's version resource and creating a system imagelist containing the icon
do not take that long.

Regards,

Magnus Persson
Software Developer
www.timelox.com

"Mike Marino" <michaelm@installshield.com> wrote in message
news:3b9e32fa$1@news.installshield.com...
> Magnus Persson:
>
> Which node in the Files View Tree (Lower Left) are you selecting that
> displays an empty file list? When you add a file, the file will be
> displayed when the component it was added to is selected, or the Parent
> Folder of that component is selected. If this is not the case, please let
> me know. Any steps you could provide to reproduce this would also be
> helpful.
>
> If the Files View seems slow when you click on the it's node in the "View
> List" this is most often caused by a broken shortcut in a user's desktop
> folder. When we populate the "Source" Tree and List we populate them with
> all items on the desktop by default. If this location contains a shortcut
> that points to nothing (or an invalid location) it will take a really long
> time for the view to populate.
>
> Thank you,
> Mike Marino
>
> "Magnus Persson" <magnus.persson@timelox.com> wrote in message
> news:3b9dba81@news.installshield.com...
> > Often when I add files to components in the 'Specify Aplication
> Data/Files'
> > view the files are actually added to the component but the listview of
the
> > 'Destination computer's files' is empty. Even if I click on other
> components
> > and then back again it is still empty. Clicking on 'Advanced
> > Views/Components' will show that there are files tied to that component
> and
> > if I then change back to the 'Specify Aplication Data/Files' view the
> > component is now populated with files. This bug is kinda annoying
because
> > whenever I click on 'Specify Aplication Data/Files' view, developer
> freezes
> > while updating the information in the 'Destination computer's files'
> > listview. This 'freeze' time is very long if you have 20 files all with
> > icons and version resources.
> >
> > /Magnus
> >
> >
>
>

NewsArchive
09-13-2001, 12:00 AM
Magnus Persson:

I have been unable to reproduce the non-appearing file, or the slow
refreshing issues. Are you dragging in files from a network location? We
do not actually query the icon of a source file in the destination file
list, however we do try to get the file information (Version, Modified date,
etc.). Slow network connections can slow this procedure down. If it is a
networking issue, we could look at adding a "fast" mode that would not query
the OS for any information.

If you feel this may be related to a setting in a particular project, please
send me the project and I will try to reproduce the issue in-house.

Thank you for your time and feedback,
Mike Marino

"Magnus Persson" <magnus.persson@timelox.com> wrote in message
news:3b9f0152$1@news.installshield.com...
> Hi Mike,
>
> Sorry if I wasn't clear enough about the listview problem so let me
clarify
> this even more.
>
> 1. When adding files to a component in the view "Specify Application
> Data/Files" I right-click on the [INSTALLDIR] and select the menu item
"Add
> Component". I make sure the newly added component is selected and if
needed
> I alter the properties for the selected component. Then I drag'n'drop
files
> from the listview "Source computer's files" to the listview "Destination
> computer's files". But sometimes the listview "Destination computer's
files"
> stay empty. If I drag'n'drop the same file again I receive an error saying
> that the file is already there. If I click on another component the files
in
> that component will be displayed but if I switch back to the component
that
> didn't show the files it will still be empty. If I click on the "Advanced
> Views/Components" I can there see the component in question along with the
> files associated with that component. However, if I now switch back to the
> view "Specify Application Data/Files" and select that component the files
> will finally show. This *bug* (or whatever it is) happens alot. You may
have
> to add a couple of components (say 10-15) before this will happen though.
>
> 2. The treeview "Source computer's folders" and the listview "Source
> computer's files" are both displayed instantly. It is the listview
> "Destination computer's files" that is extremely slow. Even on my 1GHz DDR
> machine the items are displayed approximately 2 items per second. That is
> terrible. The next time I switch to that view the data is cached and will
> thus be displayed instantly. But if I add a new component all the files
are
> re-populated at the same slow speed as before (~2 items/s). When switching
> to the "Specify Application Data/Files" view the treeview "Destination
> computer's folders" have the item "[INSTALLDIR]" pre-selected thus
> displaying just about all the files in my project. But still, reading a
> file's version resource and creating a system imagelist containing the
icon
> do not take that long.
>
> Regards,
>
> Magnus Persson
> Software Developer
> www.timelox.com
>
> "Mike Marino" <michaelm@installshield.com> wrote in message
> news:3b9e32fa$1@news.installshield.com...
> > Magnus Persson:
> >
> > Which node in the Files View Tree (Lower Left) are you selecting that
> > displays an empty file list? When you add a file, the file will be
> > displayed when the component it was added to is selected, or the Parent
> > Folder of that component is selected. If this is not the case, please
let
> > me know. Any steps you could provide to reproduce this would also be
> > helpful.
> >
> > If the Files View seems slow when you click on the it's node in the
"View
> > List" this is most often caused by a broken shortcut in a user's desktop
> > folder. When we populate the "Source" Tree and List we populate them
with
> > all items on the desktop by default. If this location contains a
shortcut
> > that points to nothing (or an invalid location) it will take a really
long
> > time for the view to populate.
> >
> > Thank you,
> > Mike Marino
> >
> > "Magnus Persson" <magnus.persson@timelox.com> wrote in message
> > news:3b9dba81@news.installshield.com...
> > > Often when I add files to components in the 'Specify Aplication
> > Data/Files'
> > > view the files are actually added to the component but the listview of
> the
> > > 'Destination computer's files' is empty. Even if I click on other
> > components
> > > and then back again it is still empty. Clicking on 'Advanced
> > > Views/Components' will show that there are files tied to that
component
> > and
> > > if I then change back to the 'Specify Aplication Data/Files' view the
> > > component is now populated with files. This bug is kinda annoying
> because
> > > whenever I click on 'Specify Aplication Data/Files' view, developer
> > freezes
> > > while updating the information in the 'Destination computer's files'
> > > listview. This 'freeze' time is very long if you have 20 files all
with
> > > icons and version resources.
> > >
> > > /Magnus
> > >
> > >
> >
> >
>
>

NewsArchive
09-17-2001, 12:00 AM
Yes, I am dragging files in from a network location (10mbit/s LAN) that is
not very loaded (600-1000kbytes/s). A fast mode sounds interesting though.

/Magnus

"Mike Marino" <michaelm@installshield.com> wrote in message
news:3ba0de4b$1@news.installshield.com...
> Magnus Persson:
>
> I have been unable to reproduce the non-appearing file, or the slow
> refreshing issues. Are you dragging in files from a network location?
We
> do not actually query the icon of a source file in the destination file
> list, however we do try to get the file information (Version, Modified
date,
> etc.). Slow network connections can slow this procedure down. If it is a
> networking issue, we could look at adding a "fast" mode that would not
query
> the OS for any information.
>
> If you feel this may be related to a setting in a particular project,
please
> send me the project and I will try to reproduce the issue in-house.
>
> Thank you for your time and feedback,
> Mike Marino
>
> "Magnus Persson" <magnus.persson@timelox.com> wrote in message
> news:3b9f0152$1@news.installshield.com...
> > Hi Mike,
> >
> > Sorry if I wasn't clear enough about the listview problem so let me
> clarify
> > this even more.
> >
> > 1. When adding files to a component in the view "Specify Application
> > Data/Files" I right-click on the [INSTALLDIR] and select the menu item
> "Add
> > Component". I make sure the newly added component is selected and if
> needed
> > I alter the properties for the selected component. Then I drag'n'drop
> files
> > from the listview "Source computer's files" to the listview "Destination
> > computer's files". But sometimes the listview "Destination computer's
> files"
> > stay empty. If I drag'n'drop the same file again I receive an error
saying
> > that the file is already there. If I click on another component the
files
> in
> > that component will be displayed but if I switch back to the component
> that
> > didn't show the files it will still be empty. If I click on the
"Advanced
> > Views/Components" I can there see the component in question along with
the
> > files associated with that component. However, if I now switch back to
the
> > view "Specify Application Data/Files" and select that component the
files
> > will finally show. This *bug* (or whatever it is) happens alot. You may
> have
> > to add a couple of components (say 10-15) before this will happen
though.
> >
> > 2. The treeview "Source computer's folders" and the listview "Source
> > computer's files" are both displayed instantly. It is the listview
> > "Destination computer's files" that is extremely slow. Even on my 1GHz
DDR
> > machine the items are displayed approximately 2 items per second. That
is
> > terrible. The next time I switch to that view the data is cached and
will
> > thus be displayed instantly. But if I add a new component all the files
> are
> > re-populated at the same slow speed as before (~2 items/s). When
switching
> > to the "Specify Application Data/Files" view the treeview "Destination
> > computer's folders" have the item "[INSTALLDIR]" pre-selected thus
> > displaying just about all the files in my project. But still, reading a
> > file's version resource and creating a system imagelist containing the
> icon
> > do not take that long.
> >
> > Regards,
> >
> > Magnus Persson
> > Software Developer
> > www.timelox.com
> >
> > "Mike Marino" <michaelm@installshield.com> wrote in message
> > news:3b9e32fa$1@news.installshield.com...
> > > Magnus Persson:
> > >
> > > Which node in the Files View Tree (Lower Left) are you selecting that
> > > displays an empty file list? When you add a file, the file will be
> > > displayed when the component it was added to is selected, or the
Parent
> > > Folder of that component is selected. If this is not the case, please
> let
> > > me know. Any steps you could provide to reproduce this would also be
> > > helpful.
> > >
> > > If the Files View seems slow when you click on the it's node in the
> "View
> > > List" this is most often caused by a broken shortcut in a user's
desktop
> > > folder. When we populate the "Source" Tree and List we populate them
> with
> > > all items on the desktop by default. If this location contains a
> shortcut
> > > that points to nothing (or an invalid location) it will take a really
> long
> > > time for the view to populate.
> > >
> > > Thank you,
> > > Mike Marino
> > >
> > > "Magnus Persson" <magnus.persson@timelox.com> wrote in message
> > > news:3b9dba81@news.installshield.com...
> > > > Often when I add files to components in the 'Specify Aplication
> > > Data/Files'
> > > > view the files are actually added to the component but the listview
of
> > the
> > > > 'Destination computer's files' is empty. Even if I click on other
> > > components
> > > > and then back again it is still empty. Clicking on 'Advanced
> > > > Views/Components' will show that there are files tied to that
> component
> > > and
> > > > if I then change back to the 'Specify Aplication Data/Files' view
the
> > > > component is now populated with files. This bug is kinda annoying
> > because
> > > > whenever I click on 'Specify Aplication Data/Files' view, developer
> > > freezes
> > > > while updating the information in the 'Destination computer's files'
> > > > listview. This 'freeze' time is very long if you have 20 files all
> with
> > > > icons and version resources.
> > > >
> > > > /Magnus
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
09-17-2001, 12:00 AM
Magnus Persson:

I have reproduced slow Version Number population in the Files View. It is
definitely related to files being reference over a network. I filed a Work
Order to look into this issue further. The internal reference number is
1-6MROH.

Thank you for your feedback,
Mike Marino

"Magnus Persson" <magnus.persson@timelox.com> wrote in message
news:3ba5b5ce$1@news.installshield.com...
> Yes, I am dragging files in from a network location (10mbit/s LAN) that is
> not very loaded (600-1000kbytes/s). A fast mode sounds interesting though.
>
> /Magnus
>
> "Mike Marino" <michaelm@installshield.com> wrote in message
> news:3ba0de4b$1@news.installshield.com...
> > Magnus Persson:
> >
> > I have been unable to reproduce the non-appearing file, or the slow
> > refreshing issues. Are you dragging in files from a network location?
> We
> > do not actually query the icon of a source file in the destination file
> > list, however we do try to get the file information (Version, Modified
> date,
> > etc.). Slow network connections can slow this procedure down. If it is
a
> > networking issue, we could look at adding a "fast" mode that would not
> query
> > the OS for any information.
> >
> > If you feel this may be related to a setting in a particular project,
> please
> > send me the project and I will try to reproduce the issue in-house.
> >
> > Thank you for your time and feedback,
> > Mike Marino
> >
> > "Magnus Persson" <magnus.persson@timelox.com> wrote in message
> > news:3b9f0152$1@news.installshield.com...
> > > Hi Mike,
> > >
> > > Sorry if I wasn't clear enough about the listview problem so let me
> > clarify
> > > this even more.
> > >
> > > 1. When adding files to a component in the view "Specify Application
> > > Data/Files" I right-click on the [INSTALLDIR] and select the menu item
> > "Add
> > > Component". I make sure the newly added component is selected and if
> > needed
> > > I alter the properties for the selected component. Then I drag'n'drop
> > files
> > > from the listview "Source computer's files" to the listview
"Destination
> > > computer's files". But sometimes the listview "Destination computer's
> > files"
> > > stay empty. If I drag'n'drop the same file again I receive an error
> saying
> > > that the file is already there. If I click on another component the
> files
> > in
> > > that component will be displayed but if I switch back to the component
> > that
> > > didn't show the files it will still be empty. If I click on the
> "Advanced
> > > Views/Components" I can there see the component in question along with
> the
> > > files associated with that component. However, if I now switch back to
> the
> > > view "Specify Application Data/Files" and select that component the
> files
> > > will finally show. This *bug* (or whatever it is) happens alot. You
may
> > have
> > > to add a couple of components (say 10-15) before this will happen
> though.
> > >
> > > 2. The treeview "Source computer's folders" and the listview "Source
> > > computer's files" are both displayed instantly. It is the listview
> > > "Destination computer's files" that is extremely slow. Even on my 1GHz
> DDR
> > > machine the items are displayed approximately 2 items per second. That
> is
> > > terrible. The next time I switch to that view the data is cached and
> will
> > > thus be displayed instantly. But if I add a new component all the
files
> > are
> > > re-populated at the same slow speed as before (~2 items/s). When
> switching
> > > to the "Specify Application Data/Files" view the treeview "Destination
> > > computer's folders" have the item "[INSTALLDIR]" pre-selected thus
> > > displaying just about all the files in my project. But still, reading
a
> > > file's version resource and creating a system imagelist containing the
> > icon
> > > do not take that long.
> > >
> > > Regards,
> > >
> > > Magnus Persson
> > > Software Developer
> > > www.timelox.com
> > >
> > > "Mike Marino" <michaelm@installshield.com> wrote in message
> > > news:3b9e32fa$1@news.installshield.com...
> > > > Magnus Persson:
> > > >
> > > > Which node in the Files View Tree (Lower Left) are you selecting
that
> > > > displays an empty file list? When you add a file, the file will be
> > > > displayed when the component it was added to is selected, or the
> Parent
> > > > Folder of that component is selected. If this is not the case,
please
> > let
> > > > me know. Any steps you could provide to reproduce this would also
be
> > > > helpful.
> > > >
> > > > If the Files View seems slow when you click on the it's node in the
> > "View
> > > > List" this is most often caused by a broken shortcut in a user's
> desktop
> > > > folder. When we populate the "Source" Tree and List we populate
them
> > with
> > > > all items on the desktop by default. If this location contains a
> > shortcut
> > > > that points to nothing (or an invalid location) it will take a
really
> > long
> > > > time for the view to populate.
> > > >
> > > > Thank you,
> > > > Mike Marino
> > > >
> > > > "Magnus Persson" <magnus.persson@timelox.com> wrote in message
> > > > news:3b9dba81@news.installshield.com...
> > > > > Often when I add files to components in the 'Specify Aplication
> > > > Data/Files'
> > > > > view the files are actually added to the component but the
listview
> of
> > > the
> > > > > 'Destination computer's files' is empty. Even if I click on other
> > > > components
> > > > > and then back again it is still empty. Clicking on 'Advanced
> > > > > Views/Components' will show that there are files tied to that
> > component
> > > > and
> > > > > if I then change back to the 'Specify Aplication Data/Files' view
> the
> > > > > component is now populated with files. This bug is kinda annoying
> > > because
> > > > > whenever I click on 'Specify Aplication Data/Files' view,
developer
> > > > freezes
> > > > > while updating the information in the 'Destination computer's
files'
> > > > > listview. This 'freeze' time is very long if you have 20 files all
> > with
> > > > > icons and version resources.
> > > > >
> > > > > /Magnus
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
09-17-2001, 12:00 AM
Adam:

First of all, DoInstall only works if you want to launch standard project.

Secondly, the first argument you passed to DoInstall is wrong. Please check
the document on "DoInstall".

Fei

"Adam Watkins" <AWatkins@ccci.org> wrote in message
news:3ba3b3dc$1@news.installshield.com...
> Nerver mind. I found a flag for the setup that probably puts a window up
> that IS can see and tell if it has finished.
>
> -Adam Watkins
>
> "Adam Watkins" <AWatkins@ccci.org> wrote in message
> news:3ba3acae@news.installshield.com...
> > If I run this setup using DoInstall, it doesn't run at all. The
Setup.log
> > file reports error -5. If I use LaunchAppAndWait, it works fine, it
just
> > doesn't wait till the install is finished. Here is my code:
> >
> > strPath = "\"" + TempFolder^"ASA\\setup.exe\"";
> > strCommandLine = " TARGET_DIR=\"" + strPathASA + "\" SHARED_DIR=\"" +
> > strPathASAShared + "\" -s -f1\"" + SUPPORTDIR^"ASASetup.iss\"";
> > DoInstall(strPath, strCommandLine, WAIT);
> >
> > file://Cleanup files
> > DeleteDir(TempFolder^"ASA", ALLCONTENTS);
> >
> > All I change is DoInstall and this works:
> >
> > strPath = "\"" + TempFolder^"ASA\\setup.exe\"";
> > strCommandLine = " TARGET_DIR=\"" + strPathASA + "\" SHARED_DIR=\"" +
> > strPathASAShared + "\" -s -f1\"" + SUPPORTDIR^"ASASetup.iss\"";
> > LaunchAppAndWait(strPath, strCommandLine, WAIT);
> >
> > file://Cleanup files
> > DeleteDir(TempFolder^"ASA", ALLCONTENTS);
> >
> > Just doesn't pause...
> >
> > Thanks,
> > Adam Watkins
> >
> >
>
>

NewsArchive
09-19-2001, 12:00 AM
Hi Chandima,

Thanks a lot for your answer.

In fact, we do use quotation marks even if the path does not contain any
space, but it doesn't work.

I've not tried to build the project using the Automation Layer yet, since
I've got a new problem.
It seems that some methods and properties have been improved to perform some
kind of controls when they're called/set.

For example, I've noticed that one cannot set ISWIComponent.Destination to
an empty string (sounds sensible).

But, I've also discovered that Windows Installer directory properties must
be enclosed in *ANGLE* brackets (instead of *SQUARE* brackets.in IPWIE
2.03).
Are there any other "lightning changes" like this one we should be aware of
?

Best regards,
Jean-Luc Agathos

"Chandima Rajakaruna" <no reply@installshield.com> wrote in message
news:3ba66469$1@news.installshield.com...
> Try
>
> ISCmdBld.exe -p "\\Machine\Sharing\Subfolder\Project.ism"
>
> (with quotation marks)
>
> If this does not work either, you could try building your project thorugh
> the Automation Layer. Suppose your project has a Product Configuration
named
> "ProdConfig" and a release named "Release", enter the following code in VB
> script and execute. It'll build your release to C:\Automation\Release.
>
[... Sample Code ...]
>
> "Jean-Luc Agathos" <jagathos@businessobjects.com> wrote in message
> news:3ba2c045@news.installshield.com...
> > Hi,
> >
> > I've just discovered a regression in ID7: when I try to build a setup
from
> > command line, ISCmdBuild fails if the project path follows universal
> naming
> > convention.
> >
> > I.e: the following command fails (abnormal termination)
> >
> > ISCmdBld.exe -p \\Machine\Sharing\Subfolder\Project.ism"
> >
> > whereas
> >
> > ISCmdBld.exe -p "C:\Sharing\Subfolder\Project.ism"
> >
> > is okay.
> >
> > Both methods used to work with IPWIE 2.03.
> > This weird behaviour might prevent us from migrating since our automated
> > process would be broken.
> >
> > Has anyone faced the same issue ?
> > Please, ... share ;-)
> >
> > Best regards,
> > Jean-Luc Agathos
> >
> >
>
>

NewsArchive
09-19-2001, 12:00 AM
For the record, I tried playing with Major upgrades and encountered the same
problem. Same error messages.

I find it puzzling that such an obviously important feature is either
horribly broken, or just non-intuitive and implemented contrary to
documentation. (I guess there's a third option - we are both idiots!) But
we cannot ship a product that cannot be upgraded, so hopefully the solution
will come quickly and easily.

> I have almost the same problem. I have everything else in my new installer
> project working except major upgrades. If you find any answers, please
post
> something here. I promise to do the same.
>
> In my case, I'm trying to implement a "major upgrade" package. I am
changing
> the product code and package code while keeping the upgrade code
unchanged.
> When I run my installation package, it eventually says "Error 1628: failed
> to complete installation". Eventually, I get a message that says "Error
> 1714. The older version of <product name> cannot be removed. Contact your
> technical support group." Then the installation terminates.
>

NewsArchive
09-19-2001, 12:00 AM
"Greg S." <gregs@there.com> wrote in
news:3ba91f03$1@news.installshield.com:

> documentation. (I guess there's a third option - we are both idiots!)

I sincerely doubt that you are an idiot and I'm pretty sure that I'm not.
(Would an idiot know that he is an idiot?) But I freely admit that I'm no
InstallShield expert.

NewsArchive
09-20-2001, 12:00 AM
Not that I can think of. But I know the documentation is up to date. So if
you have a doubt check the documentation. If that still doesn't help you,
just email me at chandimar@installShield.com.

"Jean-Luc Agathos" <jagathos@businessobjects.com> wrote in message
news:3ba7c768$1@news.installshield.com...
> Hi Chandima,
>
> Thanks a lot for your answer.
>
> In fact, we do use quotation marks even if the path does not contain any
> space, but it doesn't work.
>
> I've not tried to build the project using the Automation Layer yet, since
> I've got a new problem.
> It seems that some methods and properties have been improved to perform
some
> kind of controls when they're called/set.
>
> For example, I've noticed that one cannot set ISWIComponent.Destination to
> an empty string (sounds sensible).
>
> But, I've also discovered that Windows Installer directory properties must
> be enclosed in *ANGLE* brackets (instead of *SQUARE* brackets.in IPWIE
> 2.03).
> Are there any other "lightning changes" like this one we should be aware
of
> ?
>
> Best regards,
> Jean-Luc Agathos
>
> "Chandima Rajakaruna" <no reply@installshield.com> wrote in message
> news:3ba66469$1@news.installshield.com...
> > Try
> >
> > ISCmdBld.exe -p "\\Machine\Sharing\Subfolder\Project.ism"
> >
> > (with quotation marks)
> >
> > If this does not work either, you could try building your project
thorugh
> > the Automation Layer. Suppose your project has a Product Configuration
> named
> > "ProdConfig" and a release named "Release", enter the following code in
VB
> > script and execute. It'll build your release to C:\Automation\Release.
> >
> [... Sample Code ...]
> >
> > "Jean-Luc Agathos" <jagathos@businessobjects.com> wrote in message
> > news:3ba2c045@news.installshield.com...
> > > Hi,
> > >
> > > I've just discovered a regression in ID7: when I try to build a setup
> from
> > > command line, ISCmdBuild fails if the project path follows universal
> > naming
> > > convention.
> > >
> > > I.e: the following command fails (abnormal termination)
> > >
> > > ISCmdBld.exe -p \\Machine\Sharing\Subfolder\Project.ism"
> > >
> > > whereas
> > >
> > > ISCmdBld.exe -p "C:\Sharing\Subfolder\Project.ism"
> > >
> > > is okay.
> > >
> > > Both methods used to work with IPWIE 2.03.
> > > This weird behaviour might prevent us from migrating since our
automated
> > > process would be broken.
> > >
> > > Has anyone faced the same issue ?
> > > Please, ... share ;-)
> > >
> > > Best regards,
> > > Jean-Luc Agathos
> > >
> > >
> >
> >
>
>

NewsArchive
09-21-2001, 12:00 AM
James, I would say it is not accidental or an oversight. It is a deliberate
effort. Mr. Bhatia has also promissed me a revision to the EULA and to look
into changes in the future. I'm still skeptical of what the future may hold,
but maybe that's my nature. :-)

Steve

"James Millson" <jmillson@ezmail.org.uk> wrote in message
news:3baa6269@news.installshield.com...
> Mr Bhatia himself has given me a temporary solution to my problem, and
said
> he will "look into" resolving the issue in future versions.
>
> I beleive it was probably an accidental oversight that they didn't plan
for
> people using non-standard UIs, but I see that as a move in the right
> direction.
>
> Yours,
>
> James Millson
> jmillson@ezmail.org.uk
>
> EzMail UK Limited
>
>
>

NewsArchive
09-21-2001, 12:00 AM
Don't listen to what they say, look at what they do.

Steve Carless wrote:

> James, I would say it is not accidental or an oversight. It is a deliberate
> effort. Mr. Bhatia has also promissed me a revision to the EULA and to look
> into changes in the future. I'm still skeptical of what the future may hold,
> but maybe that's my nature. :-)
>
> Steve
>
> "James Millson" <jmillson@ezmail.org.uk> wrote in message
> news:3baa6269@news.installshield.com...
>
>>Mr Bhatia himself has given me a temporary solution to my problem, and
>>
> said
>
>>he will "look into" resolving the issue in future versions.
>>
>>I beleive it was probably an accidental oversight that they didn't plan
>>
> for
>
>>people using non-standard UIs, but I see that as a move in the right
>>direction.
>>
>>Yours,
>>
>>James Millson
>>jmillson@ezmail.org.uk
>>
>>EzMail UK Limited
>>
>>
>>
>>
>
>

NewsArchive
09-22-2001, 12:00 AM
Looks like I got the bottled response then. And I went and personally
thanked him for a response :(.

Like Gier said, we'll have to wait for the action.

James

"Steve Carless" <psoft@mediaone.net> wrote in message
news:3bab5852$1@news.installshield.com...
> James, I would say it is not accidental or an oversight. It is a
deliberate
> effort. Mr. Bhatia has also promissed me a revision to the EULA and to
look
> into changes in the future. I'm still skeptical of what the future may
hold,
> but maybe that's my nature. :-)
>
> Steve
>
> "James Millson" <jmillson@ezmail.org.uk> wrote in message
> news:3baa6269@news.installshield.com...
> > Mr Bhatia himself has given me a temporary solution to my problem, and
> said
> > he will "look into" resolving the issue in future versions.
> >
> > I beleive it was probably an accidental oversight that they didn't plan
> for
> > people using non-standard UIs, but I see that as a move in the right
> > direction.
> >
> > Yours,
> >
> > James Millson
> > jmillson@ezmail.org.uk
> >
> > EzMail UK Limited
> >
> >
> >
>
>

NewsArchive
09-25-2001, 12:00 AM
I Chandima,

We have finally solved the problems we had reported.

1. We did managed to build the project using the automation layer.

2. Angle brackets are okay, but:
-ID7 doesn't like leading blanks in ISWIComponent.Destination;
-the documentation string in the type library (viewed using the Visual
Basic object viewer) is not up to date.

Thanks again for your help,
Jean-Luc Agathos

"Chandima Rajakaruna" <no reply@installshield.com> wrote in message
news:3ba9f5d6$1@news.installshield.com...
> Not that I can think of. But I know the documentation is up to date. So if
> you have a doubt check the documentation. If that still doesn't help you,
> just email me at chandimar@installShield.com.
>
> "Jean-Luc Agathos" <jagathos@businessobjects.com> wrote in message
> news:3ba7c768$1@news.installshield.com...
> > Hi Chandima,
> >
> > Thanks a lot for your answer.
> >
> > In fact, we do use quotation marks even if the path does not contain any
> > space, but it doesn't work.
> >
> > I've not tried to build the project using the Automation Layer yet,
since
> > I've got a new problem.
> > It seems that some methods and properties have been improved to perform
> some
> > kind of controls when they're called/set.
> >
> > For example, I've noticed that one cannot set ISWIComponent.Destination
to
> > an empty string (sounds sensible).
> >
> > But, I've also discovered that Windows Installer directory properties
must
> > be enclosed in *ANGLE* brackets (instead of *SQUARE* brackets.in IPWIE
> > 2.03).
> > Are there any other "lightning changes" like this one we should be aware
> of
> > ?
> >
> > Best regards,
> > Jean-Luc Agathos
> >
> > "Chandima Rajakaruna" <no reply@installshield.com> wrote in message
> > news:3ba66469$1@news.installshield.com...
> > > Try
> > >
> > > ISCmdBld.exe -p "\\Machine\Sharing\Subfolder\Project.ism"
> > >
> > > (with quotation marks)
> > >
> > > If this does not work either, you could try building your project
> thorugh
> > > the Automation Layer. Suppose your project has a Product Configuration
> > named
> > > "ProdConfig" and a release named "Release", enter the following code
in
> VB
> > > script and execute. It'll build your release to C:\Automation\Release.
> > >
> > [... Sample Code ...]
> > >
> > > "Jean-Luc Agathos" <jagathos@businessobjects.com> wrote in message
> > > news:3ba2c045@news.installshield.com...
> > > > Hi,
> > > >
> > > > I've just discovered a regression in ID7: when I try to build a
setup
> > from
> > > > command line, ISCmdBuild fails if the project path follows universal
> > > naming
> > > > convention.
> > > >
> > > > I.e: the following command fails (abnormal termination)
> > > >
> > > > ISCmdBld.exe -p \\Machine\Sharing\Subfolder\Project.ism"
> > > >
> > > > whereas
> > > >
> > > > ISCmdBld.exe -p "C:\Sharing\Subfolder\Project.ism"
> > > >
> > > > is okay.
> > > >
> > > > Both methods used to work with IPWIE 2.03.
> > > > This weird behaviour might prevent us from migrating since our
> automated
> > > > process would be broken.
> > > >
> > > > Has anyone faced the same issue ?
> > > > Please, ... share ;-)
> > > >
> > > > Best regards,
> > > > Jean-Luc Agathos
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
09-25-2001, 12:00 AM
Sorry, I've just noticed I made a mistake in my previous note.

You should read:

[...]
2. *SQUARE* brackets are okay, but
[...]

Best regards,
Jean-Luc Agathos

"Jean-Luc Agathos" <jagathos@businessobjects.com> wrote in message news:...
> I Chandima,
>
> We have finally solved the problems we had reported.
>
> 1. We did managed to build the project using the automation layer.
>
> 2. Angle brackets are okay, but:
> -ID7 doesn't like leading blanks in ISWIComponent.Destination;
> -the documentation string in the type library (viewed using the Visual
> Basic object viewer) is not up to date.
>
> Thanks again for your help,
> Jean-Luc Agathos

NewsArchive
09-27-2001, 12:00 AM
almost like "demo syndrome" isn't it :o) i.e. works fine until you say "come
and look at this, I've sussed it" to your boss.....

"Barry Wimlett" <barry@endless.co.uk> wrote in message
news:3bb1c499$1@news.installshield.com...
> Can never find the right bit in the manual - til I've admitted I can'tfind
> the right bit in the manual in public.
>
> doh!
>
> Barry
>
>
>
>
>

NewsArchive
09-28-2001, 12:00 AM
Thanks Mike...Basically, that is the same conclusion that I came at.
Unfortunately, the error did not present itself at me in an obvious form,
rather I had to back into it be successively removing halves of my
installation. Even the MSI validation did not seem to uncover the problem.
Anyway, 95% of the reason I posted this here is so that somebody running
into the same mysterious 2318 and/or 1603 error codes might hopefully be
able to find one possible root of their problem quicker than I did . (Any
chance of this seeing the light-of-day on the Website KB?)

Again, thanks for the prompt reply. Dev7 is certainly an intriguing
product...looks like it may meet my current needs, but I do look forward to
a maintenance release.

--John M. Garland

"Mike Marino" <michaelm@installshield.com> wrote in message
news:3bb4cfa9$1@news.installshield.com...
> John M. Garland:
>
> "Database" is an MSI reserved word. That is why you are getting those
> errors. You should be able to have a folder with the name "Database",
> however, you will need to change the Directory Identifier of that folder
to
> something else. The Directory Identifier of a folder can be changed by
> right clicking on the folder in the File's view and selecting
"Properties".
>
> By default when you create a folder called "Database" we give a Directory
> Identifier of "DATABASE" this is incorrect, and we are looking to address
> this in a future release.
>
> Hope this helps,
> Mike Marino
>
> "John M. Garland" <jgarland@pinnaclesys.com> wrote in message
> news:3bb4be5a@news.installshield.com...
> > Submitted to IS as bug through website on 9/28/01:
> >
> > Developer 7, standard setup mode: I have a folder named "Database" that
I
> > would like to install under [InstallDir] (and, corresponsdingly, an
> Access
> > DB that I'd like to place into that folder.) This presents a bit of a
> > problem, manifested as an "Internal Error 2318" and "-1603 Fatal Error"
> when
> > running the installer. Took quite some time to get at the exact root of
> the
> > problem (name of a subfolder was the LAST thing I thought it would be);
> > Simply changing the name from "Database" to "Databasx" resolves the
> problem.
> > The machines I am installing aon are Win2K, SP2 (running Windows
Installer
> > Service version 1.1)
> >
> >
> > John M. Garland
> > Software Engineer
> > Pinnacle Systems, Team Sports Division
> >
> >
> >
>
>
>
>

NewsArchive
09-28-2001, 12:00 AM
Thanks for the reply Kent. Can this list make its way into the
InstallShield online KB? It would be quite helpful if it had as part of its
keyword set the 2318 and -1603 error codes, and text indicating this is one
possible source of those errors. Thanks much

--John M. Garland

"Kent Foyer" <no@address.com> wrote in message
news:3bb4d559$1@news.installshield.com...
> The problem is actually with MSI itself. MSI has an undocumented property
> named DATABASE. It uses this at runtime. However, if you have this in
your
> Directory table then MSI has problems. We discovered this problem soon
> after release.
>
> Anyway, besides properties in the Property and Directory tables (look in
the
> Direct Editor) here are some other properties not to use::
>
> CLEANUPUNINSTALLROLLBACK
> CLIENTPROCESSID
> CLIENTUILEVEL
> CURRENTDIRECTORY
> DATABASE
> SUPPORTDIR
> ISSETUP_UISEQUENCE_PROCESSED
> ISSETUPDRIVEN
> ISSETUPFILESCOMPLETED
> ISStartupEvent
> OriginalDatabase
> PackageCode
> PackagecodeChanging
> SourcedirProduct
> VersionMsi
>
>
> "John M. Garland" <jgarland@pinnaclesys.com> wrote in message
> news:3bb4be5a@news.installshield.com...
> > Submitted to IS as bug through website on 9/28/01:
> >
> > Developer 7, standard setup mode: I have a folder named "Database" that
I
> > would like to install under [InstallDir] (and, corresponsdingly, an
> Access
> > DB that I'd like to place into that folder.) This presents a bit of a
> > problem, manifested as an "Internal Error 2318" and "-1603 Fatal Error"
> when
> > running the installer. Took quite some time to get at the exact root of
> the
> > problem (name of a subfolder was the LAST thing I thought it would be);
> > Simply changing the name from "Database" to "Databasx" resolves the
> problem.
> > The machines I am installing aon are Win2K, SP2 (running Windows
Installer
> > Service version 1.1)
> >
> >
> > John M. Garland
> > Software Engineer
> > Pinnacle Systems, Team Sports Division
> >
> >
> >
>
>

NewsArchive
09-29-2001, 12:00 AM
Right. Thanks. Now I can't get it to crash again. hmmm!

"Mike Marino" <michaelm@installshield.com> wrote in message
news:3bb4a864$1@news.installshield.com...
> Bruce Cartland:
>
> If you are getting this error when you right click on Sequence Root (User
> Interface, or Execute) and select Insert, this is a known issue and we are
> looking into the problem. While we are doing that, you can always select
> the first child node of the User Interface (or Execute) node, right click
> and then select Insert. Then select the first child node again, right
click
> and select Move Down.
>
> Hope this helps,
> Mike Marino
>
> "Bruce Cartland" <bruce.cartland@pobox.com> wrote in message
> news:3bb400f8@news.installshield.com...
> > MSVC++ Runtime Library
> >
> > Runtime Error!
> >
> > Program: d:\dapps\InstallShield\Developer\isdev.exe
> >
> > abnormal program termination
> >
> >
> >
>
>

NewsArchive
09-29-2001, 12:00 AM
John,

just in case you didn't know: there's a (unofficial) bug list at
http://www.installsite.org/bugs_isd.htm where this problem is listed
since Aug. 30 (and now being updated with the other reserved words
from Kent's message). I suggest you check list list before spending
too much time researching a bug.

--
Stefan Krueger - Independent Setup Consultant

InstallSite - code samples, tips, tools, bug lists, and more
http://www.installsite.org http://www.installsite.de (GERMAN)
Support and consulting http://www.installsite.org/krueger

Stefan Krueger and the InstallSite web site are not affiliated
with InstallShield Software Corporation.


"John M. Garland" <jgarland@pinnaclesys.com> schrieb im Newsbeitrag
news:3bb4d7ee$1@news.installshield.com...
> Thanks Mike...Basically, that is the same conclusion that I came at.
> Unfortunately, the error did not present itself at me in an obvious
form,
> rather I had to back into it be successively removing halves of my
> installation. Even the MSI validation did not seem to uncover the
problem.
> Anyway, 95% of the reason I posted this here is so that somebody
running
> into the same mysterious 2318 and/or 1603 error codes might
hopefully be
> able to find one possible root of their problem quicker than I did .
(Any
> chance of this seeing the light-of-day on the Website KB?)
>
> Again, thanks for the prompt reply. Dev7 is certainly an intriguing
> product...looks like it may meet my current needs, but I do look
forward to
> a maintenance release.
>
> --John M. Garland
>
> "Mike Marino" <michaelm@installshield.com> wrote in message
> news:3bb4cfa9$1@news.installshield.com...
> > John M. Garland:
> >
> > "Database" is an MSI reserved word. That is why you are getting
those
> > errors. You should be able to have a folder with the name
"Database",
> > however, you will need to change the Directory Identifier of that
folder
> to
> > something else. The Directory Identifier of a folder can be
changed by
> > right clicking on the folder in the File's view and selecting
> "Properties".
> >
> > By default when you create a folder called "Database" we give a
Directory
> > Identifier of "DATABASE" this is incorrect, and we are looking to
address
> > this in a future release.
> >
> > Hope this helps,
> > Mike Marino
> >
> > "John M. Garland" <jgarland@pinnaclesys.com> wrote in message
> > news:3bb4be5a@news.installshield.com...
> > > Submitted to IS as bug through website on 9/28/01:
> > >
> > > Developer 7, standard setup mode: I have a folder named
"Database" that
> I
> > > would like to install under [InstallDir] (and,
corresponsdingly, an
> > Access
> > > DB that I'd like to place into that folder.) This presents a
bit of a
> > > problem, manifested as an "Internal Error 2318" and "-1603 Fatal
Error"
> > when
> > > running the installer. Took quite some time to get at the exact
root of
> > the
> > > problem (name of a subfolder was the LAST thing I thought it
would be);
> > > Simply changing the name from "Database" to "Databasx" resolves
the
> > problem.
> > > The machines I am installing aon are Win2K, SP2 (running Windows
> Installer
> > > Service version 1.1)
> > >
> > >
> > > John M. Garland
> > > Software Engineer
> > > Pinnacle Systems, Team Sports Division
> > >
> > >
> > >
> >
> >
> >
> >
>
>

NewsArchive
09-29-2001, 12:00 AM
Thanks Stefan. I did search your DB (your site continues to be an
invaluable tool in my development kit) but did not find this prblem under
its previous incarnation. I may have overlooked it. Another possibility,
as I am shifting primarily from ISPE (rather than ISWI), I find that I am
still "cutting my teeth" on some of the new aspects and mindsets of the MSI
tools. Old keywords to search on, etc aren't as useful as they once were,
and I ma discovering new ones daily. As I mentioned in an earlier post, I
like what I am seeing so far in the Dev7 package...around most corners I am
finding pleasant surprises...unfortunately they are still surprises to me.

Anyway, thanks for the reference, the update on the site, and the site in
general. Keep up the great work.

--JMG


"Stefan Krueger" <nwsgrp@installsite.org> wrote in message
news:3bb5bfb2@news.installshield.com...
> John,
>
> just in case you didn't know: there's a (unofficial) bug list at
> http://www.installsite.org/bugs_isd.htm where this problem is listed
> since Aug. 30 (and now being updated with the other reserved words
> from Kent's message). I suggest you check list list before spending
> too much time researching a bug.
>
> --
> Stefan Krueger - Independent Setup Consultant
>
> InstallSite - code samples, tips, tools, bug lists, and more
> http://www.installsite.org http://www.installsite.de (GERMAN)
> Support and consulting http://www.installsite.org/krueger
>
> Stefan Krueger and the InstallSite web site are not affiliated
> with InstallShield Software Corporation.
>
>
> "John M. Garland" <jgarland@pinnaclesys.com> schrieb im Newsbeitrag
> news:3bb4d7ee$1@news.installshield.com...
> > Thanks Mike...Basically, that is the same conclusion that I came at.
> > Unfortunately, the error did not present itself at me in an obvious
> form,
> > rather I had to back into it be successively removing halves of my
> > installation. Even the MSI validation did not seem to uncover the
> problem.
> > Anyway, 95% of the reason I posted this here is so that somebody
> running
> > into the same mysterious 2318 and/or 1603 error codes might
> hopefully be
> > able to find one possible root of their problem quicker than I did .
> (Any
> > chance of this seeing the light-of-day on the Website KB?)
> >
> > Again, thanks for the prompt reply. Dev7 is certainly an intriguing
> > product...looks like it may meet my current needs, but I do look
> forward to
> > a maintenance release.
> >
> > --John M. Garland
> >
> > "Mike Marino" <michaelm@installshield.com> wrote in message
> > news:3bb4cfa9$1@news.installshield.com...
> > > John M. Garland:
> > >
> > > "Database" is an MSI reserved word. That is why you are getting
> those
> > > errors. You should be able to have a folder with the name
> "Database",
> > > however, you will need to change the Directory Identifier of that
> folder
> > to
> > > something else. The Directory Identifier of a folder can be
> changed by
> > > right clicking on the folder in the File's view and selecting
> > "Properties".
> > >
> > > By default when you create a folder called "Database" we give a
> Directory
> > > Identifier of "DATABASE" this is incorrect, and we are looking to
> address
> > > this in a future release.
> > >
> > > Hope this helps,
> > > Mike Marino
> > >
> > > "John M. Garland" <jgarland@pinnaclesys.com> wrote in message
> > > news:3bb4be5a@news.installshield.com...
> > > > Submitted to IS as bug through website on 9/28/01:
> > > >
> > > > Developer 7, standard setup mode: I have a folder named
> "Database" that
> > I
> > > > would like to install under [InstallDir] (and,
> corresponsdingly, an
> > > Access
> > > > DB that I'd like to place into that folder.) This presents a
> bit of a
> > > > problem, manifested as an "Internal Error 2318" and "-1603 Fatal
> Error"
> > > when
> > > > running the installer. Took quite some time to get at the exact
> root of
> > > the
> > > > problem (name of a subfolder was the LAST thing I thought it
> would be);
> > > > Simply changing the name from "Database" to "Databasx" resolves
> the
> > > problem.
> > > > The machines I am installing aon are Win2K, SP2 (running Windows
> > Installer
> > > > Service version 1.1)
> > > >
> > > >
> > > > John M. Garland
> > > > Software Engineer
> > > > Pinnacle Systems, Team Sports Division
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
>

NewsArchive
09-29-2001, 12:00 AM
In case of runtime or build errors, I suggest you first search for the
error number (without the minus sign). I try to have both the number
an the text in the article, but sometimes the wording may not always
match exactly.

--
Stefan Krueger - Independent Setup Consultant

InstallSite - code samples, tips, tools, bug lists, and more
http://www.installsite.org http://www.installsite.de (GERMAN)
Support and consulting http://www.installsite.org/krueger

Stefan Krueger and the InstallSite web site are not affiliated
with InstallShield Software Corporation.


"John M. Garland" <jgarland@pinnaclesys.com> schrieb im Newsbeitrag
news:3bb5e9c9$1@news.installshield.com...
> Thanks Stefan. I did search your DB (your site continues to be an
> invaluable tool in my development kit) but did not find this prblem
under
> its previous incarnation. I may have overlooked it. Another
possibility,
> as I am shifting primarily from ISPE (rather than ISWI), I find that
I am
> still "cutting my teeth" on some of the new aspects and mindsets of
the MSI
> tools. Old keywords to search on, etc aren't as useful as they once
were,
> and I ma discovering new ones daily. As I mentioned in an earlier
post, I
> like what I am seeing so far in the Dev7 package...around most
corners I am
> finding pleasant surprises...unfortunately they are still surprises
to me.
>
> Anyway, thanks for the reference, the update on the site, and the
site in
> general. Keep up the great work.
>
> --JMG
>
>
> "Stefan Krueger" <nwsgrp@installsite.org> wrote in message
> news:3bb5bfb2@news.installshield.com...
> > John,
> >
> > just in case you didn't know: there's a (unofficial) bug list at
> > http://www.installsite.org/bugs_isd.htm where this problem is
listed
> > since Aug. 30 (and now being updated with the other reserved words
> > from Kent's message). I suggest you check list list before
spending
> > too much time researching a bug.
> >
> > --
> > Stefan Krueger - Independent Setup Consultant
> >
> > InstallSite - code samples, tips, tools, bug lists, and more
> > http://www.installsite.org http://www.installsite.de (GERMAN)
> > Support and consulting http://www.installsite.org/krueger
> >
> > Stefan Krueger and the InstallSite web site are not affiliated
> > with InstallShield Software Corporation.
> >
> >
> > "John M. Garland" <jgarland@pinnaclesys.com> schrieb im
Newsbeitrag
> > news:3bb4d7ee$1@news.installshield.com...
> > > Thanks Mike...Basically, that is the same conclusion that I came
at.
> > > Unfortunately, the error did not present itself at me in an
obvious
> > form,
> > > rather I had to back into it be successively removing halves of
my
> > > installation. Even the MSI validation did not seem to uncover
the
> > problem.
> > > Anyway, 95% of the reason I posted this here is so that somebody
> > running
> > > into the same mysterious 2318 and/or 1603 error codes might
> > hopefully be
> > > able to find one possible root of their problem quicker than I
did .
> > (Any
> > > chance of this seeing the light-of-day on the Website KB?)
> > >
> > > Again, thanks for the prompt reply. Dev7 is certainly an
intriguing
> > > product...looks like it may meet my current needs, but I do look
> > forward to
> > > a maintenance release.
> > >
> > > --John M. Garland
> > >
> > > "Mike Marino" <michaelm@installshield.com> wrote in message
> > > news:3bb4cfa9$1@news.installshield.com...
> > > > John M. Garland:
> > > >
> > > > "Database" is an MSI reserved word. That is why you are
getting
> > those
> > > > errors. You should be able to have a folder with the name
> > "Database",
> > > > however, you will need to change the Directory Identifier of
that
> > folder
> > > to
> > > > something else. The Directory Identifier of a folder can be
> > changed by
> > > > right clicking on the folder in the File's view and selecting
> > > "Properties".
> > > >
> > > > By default when you create a folder called "Database" we give
a
> > Directory
> > > > Identifier of "DATABASE" this is incorrect, and we are looking
to
> > address
> > > > this in a future release.
> > > >
> > > > Hope this helps,
> > > > Mike Marino
> > > >
> > > > "John M. Garland" <jgarland@pinnaclesys.com> wrote in message
> > > > news:3bb4be5a@news.installshield.com...
> > > > > Submitted to IS as bug through website on 9/28/01:
> > > > >
> > > > > Developer 7, standard setup mode: I have a folder named
> > "Database" that
> > > I
> > > > > would like to install under [InstallDir] (and,
> > corresponsdingly, an
> > > > Access
> > > > > DB that I'd like to place into that folder.) This presents
a
> > bit of a
> > > > > problem, manifested as an "Internal Error 2318" and "-1603
Fatal
> > Error"
> > > > when
> > > > > running the installer. Took quite some time to get at the
exact
> > root of
> > > > the
> > > > > problem (name of a subfolder was the LAST thing I thought it
> > would be);
> > > > > Simply changing the name from "Database" to "Databasx"
resolves
> > the
> > > > problem.
> > > > > The machines I am installing aon are Win2K, SP2 (running
Windows
> > > Installer
> > > > > Service version 1.1)
> > > > >
> > > > >
> > > > > John M. Garland
> > > > > Software Engineer
> > > > > Pinnacle Systems, Team Sports Division
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
>
>

NewsArchive
09-29-2001, 12:00 AM
Looks like they took some action on 9/27.
Looks like the EULA has been changed on 9/27 to allow us to
"legally" remove the branding....well, in one place it says
we can not, but later on it sounds like it's O.K. if you
really want to...
(source InstallShield KnowledgeBase, Document ID: Q105444)

PS!
There is a tool posted at www.installsite.org to do this.


James Millson wrote:
>
> Looks like I got the bottled response then. And I went and personally
> thanked him for a response :(.
>
> Like Gier said, we'll have to wait for the action.
>
> James
>
> "Steve Carless" <psoft@mediaone.net> wrote in message
> news:3bab5852$1@news.installshield.com...
> > James, I would say it is not accidental or an oversight. It is a
> deliberate
> > effort. Mr. Bhatia has also promissed me a revision to the EULA and to
> look
> > into changes in the future. I'm still skeptical of what the future may
> hold,
> > but maybe that's my nature. :-)
> >
> > Steve
> >
> > "James Millson" <jmillson@ezmail.org.uk> wrote in message
> > news:3baa6269@news.installshield.com...
> > > Mr Bhatia himself has given me a temporary solution to my problem, and
> > said
> > > he will "look into" resolving the issue in future versions.
> > >
> > > I beleive it was probably an accidental oversight that they didn't plan
> > for
> > > people using non-standard UIs, but I see that as a move in the right
> > > direction.
> > >
> > > Yours,
> > >
> > > James Millson
> > > jmillson@ezmail.org.uk
> > >
> > > EzMail UK Limited
> > >
> > >
> > >
> >
> >
_______________________________________________________________
Geir A. Myrestrand

NewsArchive
09-30-2001, 12:00 AM
In the help 'Calculating the Custom Action Type' select 'Run InstallScript
Code' and 'Calculate'. Other options can be anything. It gives me a value of
65664 which the Custom Action Wizard or the Type field does not accept
(gives 1 to 8191 message).

Not much of a problem though as I can calculate the values myself from the
MSI help 'Summary List of All Custom Action Types'.

cheers.

"Stefan Krueger" <nwsgrp@installsite.org> wrote in message
news:3bb5c67a@news.installshield.com...
> Could you please give some details?
> Which options do you select that result in 8191 when they should give
> 65856? Where in help (MSI help or ISD7 help) do you see 65856?
>
> --
> Stefan Krueger - Independent Setup Consultant
>
> InstallSite - code samples, tips, tools, bug lists, and more
> http://www.installsite.org http://www.installsite.de (GERMAN)
> Support and consulting http://www.installsite.org/krueger
>
> Stefan Krueger and the InstallSite web site are not affiliated
> with InstallShield Software Corporation.
>
>
> "Bruce Cartland" <bruce.cartland@pobox.com> schrieb im Newsbeitrag
> news:3bafe06e@news.installshield.com...
> > InstallShield is expecting a value between 1 and 8191 but the help
> is
> > calculating values like 65856.
> >
> >
>

NewsArchive
10-01-2001, 12:00 AM
Running the CA wizard and selecting the appropriate setting should
create the correct type value. However entering the value directly in
the CA properties only accepts values up to 8191, which I believe is a
UI bug.
Background information: CA types above 65535 are not defined in MSI,
but are a special notiation created by InstallShield for InstalLScript
CAs (InstallScript is not native to Windows Installer).

--
Stefan Krueger - Independent Setup Consultant

InstallSite - code samples, tips, tools, bug lists, and more
http://www.installsite.org http://www.installsite.de (GERMAN)
Support and consulting http://www.installsite.org/krueger

Stefan Krueger and the InstallSite web site are not affiliated
with InstallShield Software Corporation.


"Bruce Cartland" <bruce.cartland@pobox.com> schrieb im Newsbeitrag
news:3bb6ab4f$1@news.installshield.com...
> In the help 'Calculating the Custom Action Type' select 'Run
InstallScript
> Code' and 'Calculate'. Other options can be anything. It gives me a
value of
> 65664 which the Custom Action Wizard or the Type field does not
accept
> (gives 1 to 8191 message).
>
> Not much of a problem though as I can calculate the values myself
from the
> MSI help 'Summary List of All Custom Action Types'.
>
> cheers.
>
> "Stefan Krueger" <nwsgrp@installsite.org> wrote in message
> news:3bb5c67a@news.installshield.com...
> > Could you please give some details?
> > Which options do you select that result in 8191 when they should
give
> > 65856? Where in help (MSI help or ISD7 help) do you see 65856?
> >
> > --
> > Stefan Krueger - Independent Setup Consultant
> >
> > InstallSite - code samples, tips, tools, bug lists, and more
> > http://www.installsite.org http://www.installsite.de (GERMAN)
> > Support and consulting http://www.installsite.org/krueger
> >
> > Stefan Krueger and the InstallSite web site are not affiliated
> > with InstallShield Software Corporation.
> >
> >
> > "Bruce Cartland" <bruce.cartland@pobox.com> schrieb im Newsbeitrag
> > news:3bafe06e@news.installshield.com...
> > > InstallShield is expecting a value between 1 and 8191 but the
help
> > is
> > > calculating values like 65856.
> > >
> > >
> >
>
>

NewsArchive
10-01-2001, 12:00 AM
Related information from msi help:
The Condition field enables or disables a component only during the
CostFinalize action. To enable or disable a component after
CostFinalize, you must use a custom action or the DoAction
ControlEvent to call MsiSetComponentState.

I guess this is a basic msi project?

--
Stefan Krueger - Independent Setup Consultant

InstallSite - code samples, tips, tools, bug lists, and more
http://www.installsite.org http://www.installsite.de (GERMAN)
Support and consulting http://www.installsite.org/krueger

Stefan Krueger and the InstallSite web site are not affiliated
with InstallShield Software Corporation.


"Geir A. Myrestrand" <geir@sendmail.com> schrieb im Newsbeitrag
news:3BB6C677.30533F29@sendmail.com...
> Log your installs, then run a diff between a successful install log
> and a log for a failed install. This may help you track down the
> difference(s) that causes your inconsistent installs.
>
> Bob wrote:
> >
> > This proplem only occurs on some computers. The installation works
fine on
> > some. I can not isolate the differences in the systems that work
and the
> > ones that don't. One faliure occured with a clean NT installation
with SP4
> > while I had it work on a different system with exactly the same
setup. The
> > failures and successes are consistant. If it fails it will always
fail, if
> > it works it will always work.
> >
> > I have added a dialog with a combo box, that sets a property. This
property
> > is getting set, I know this because I have text in later dialogs
that are
> > displayed based on the value set for this property and that works
fine. The
> > problem is that any components that are to be installed based on
the value
> > of this property are not processed.
> >
> > I have tried making this property localized and public. When I set
the
> > default value of the property (in the Property Table) to a value
that will
> > install a conditional component, the component gets installed on
every
> > system.
> >
> > Please help, This has cost me days already.
> > Bobby
>
> --
> _______________________________________________________________
> Geir A. Myrestrand

NewsArchive
10-01-2001, 12:00 AM
See my final response to "Branding in every dialog, to write the CEO" above.


"Geir A. Myrestrand" <geir@sendmail.com> wrote in message
news:3BB6BF7D.F09389DF@sendmail.com...
> Looks like they took some action on 9/27.
> Looks like the EULA has been changed on 9/27 to allow us to
> "legally" remove the branding....well, in one place it says
> we can not, but later on it sounds like it's O.K. if you
> really want to...
> (source InstallShield KnowledgeBase, Document ID: Q105444)
>
> PS!
> There is a tool posted at www.installsite.org to do this.
>
>
--SNIP--

NewsArchive
10-08-2001, 12:00 AM
Maybe I don't understand what you problem is.

"\REGISTRY\Machine\" means HKLM but if you problem is just string
manipulation I suggest you read about the string functions in Dev7 (just
type the keyword 'strings'). Extracting parts of strings or contatenating
strings is very easy in Dev7 (see StrFind and StrSub).

/Magnus

"Magnus Persson" <magnus.persson@timelox.com> wrote in message
news:3bc1a8bd$1@news.installshield.com...
> Reading the registry using the WinAPIs RegOpenKeyEx() and
RegQueryValueEx()
> works fine.
>
> I tested to call RegOpenKeyEx() with "Hardware\Devicemap\Video" as
> 'lpSubKey'. Then called RegQueryValueEx() with "\Device\Video0" as
> 'lpValueName' and in my case it returned the string
> "\REGISTRY\Machine\System\ControlSet001\Services\nv\Device0".
>
> Havn't tried using the built-in functions for reading registry keys in
Dev7
> but it should work the same. Maybe it's a bug. If so you could easily call
> the WinAPIs directly using InstallScript or make you own support dll (in
> c/c++ perhaps) that will do it for you.
>
> /Magnus
>
> "Harshad Sovani" <sharshad@angelfire.com> wrote in message
> news:3BC19E0E.82922AA@angelfire.com...
> > Hi all,
> >
> > There is an entry under HKLM\Hardware\devicemap\video called
> > \Device\Video1. It contains a path, which corresponds to another key.
> > This key has an String value "InstalledDisplayDrivers". I need to prefix
> > the contents of this value with a string, say abc123\0. Does anybody
> > have an idea how can i achieve it?
> >
> > Thanks,
> > Harshad.
> >
>
>

NewsArchive
10-09-2001, 12:00 AM

NewsArchive
10-09-2001, 12:00 AM
Since you can reproduce this with many files, I wonder if there is something
about your file system that may be contributing to this. Would it be
possible to get some details about your D Drive that may help me to
reproduce this. The odd thing is that in the files view we are displaying
this correctly...so I'm kind of stumped as to what might be going on here.

Please verify that the file sizes are being built into the MSI package
correctly by opening the MSI package in Direct Mode and looking at the file
table. If we are also building this data incorrectly you could have issues
with improper costing at runtime. It probably is not a big deal with 180K,
but that can add up real quick.


"Chris Graham" <cgraham@kanbay.com.au> wrote in message
news:3BC245F5.72E7EEA4@kanbay.com.au...
> Hello David,
> I can reproduce it with just about any file.
>
> I just realised that the thing that I was doing differently was I was
> turning off the 'Use System Attributes'. If any file was displayed as 'X
Kb',
> I was only getting X bytes displayed. I need to turn this off, as some of
the
> files that are included in the build are under source controll, and have
the
> read-only bit set, which I do not want set when installed. If there is
another
> way of resetting file attributes, then please let me know, but this is all
> that I could find in the doco.
>
> I've attached a screen shot to illustrate.
>
> -Chris
>
> David Thornley wrote:
>
> > I can not reproduce this. Can you reproduce this with more than one
file,
> > or just this particular file? If it is just this particular file can
you
> > possibly zip up and post the file.
> >
> > If you can reproduce this with multiple files, can you tell us about
your
> > OS, and file system. Is the file located on a network, if so what kind
of
> > network.
> >
> > Regards
> > David Thornley
> >
> > "Chris Graham" <cgraham@kanbay.com.au> wrote in message
> > news:3BC1253B.35C47C4A@kanbay.com.au...
> > > Select a file of a reasonable size. In my case, it is displayed as
'180
> > > Kb'.
> > > RMB, select properties.
> > > The file size is listed as 180 bytes. Doh! :-)
> > >
> > > -Chris
> > >
> > >
>


----------------------------------------------------------------------------
----

NewsArchive
10-10-2001, 12:00 AM
please tell what was the actual cause of the problem.
and how did you resolved it

kavin
"dsanborn" <dsanborn@home.com> wrote in message
news:3bb97aed$1@news.installshield.com...
> Eureka!
> I found the problem. This was an old project that I converted from an
older
> InstallShield. The script was passing a value to a registry setting via
one
> of the directory entries. I changed the approach and we're off to the
> races!
>
> Don
>
>
>
> "dsanborn" <dsanborn@home.com> wrote in message
> news:3bb9531f@news.installshield.com...
> > Kent,
> > I forgot to answer your question... This is a standard project.
> >
> > Also, I took another cold look at the Directory table. I removed the
> > entries 'CRISIS_2000' and 'DefaultDir1' and then I changed INSTALLDIR so
> > that it's parent is ISYourProductDir (to follow the standard install
> > location).
> >
> > Now I'm getting "Error 1606. Could not access network location True"
> instead
> > of 'False'.
> >
> > Is that progress or what!
> >
> > Don
> >
> >
> >
> > "Kent Foyer" <no@address.com> wrote in message
> > news:3bb8f76d$1@news.installshield.com...
> > > Is this a standard or basic project?
> > >
> > > I think there is some problem with the Directory table. Can you post
> your
> > > directory table?
> > >
> > > Kent
> > >
> > > "dsanborn" <dsanborn@home.com> wrote in message
> > > news:3bb8ed68$1@news.installshield.com...
> > > > Colin,
> > > > I've got the exact same problem (well almost). Mine gives me "Error
> > 1606.
> > > > Could not access network location False". I'm in the same boat.
For
> > the
> > > > life of me, I can't find the root of the problem.
> > > >
> > > > Help!
> > > > Don
> > > >
> > > >
> > > > "Colin Ronayne" <cronayne@hotmail.com> wrote in message
> > > > news:3bb8a307$1@news.installshield.com...
> > > > > "Error 1606. Could not access network location True" Does this
mean
> > > that
> > > > it
> > > > > is looking for a directory called True, or is it True that it can'
t
> > find
> > > > the
> > > > > network location. This error appears at the CostFinalise Action,
> and
> > I
> > > > cant
> > > > > seem to figure it out. Any help would be appreciated. Thanks,
> > > > > Colin.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
10-10-2001, 12:00 AM
My D: drive is a 14.6Gb local NTFS (under Win 2000) with 3.5Gb free.

I've currently packaged everything up into a single.exe. I'll split it out and
have a look. I'll get back to you when I've managed to do that (in the mean
time, thanks for the other tip of checking the ref counts).

-Chris

PS: This is my first time in using _any_ InstallShield product (after having
*FUN* with the Orca package) and I quite like the product. I've found your tech
support and follow up excellent. Most appreciated.

David Thornley wrote:

> Since you can reproduce this with many files, I wonder if there is something
> about your file system that may be contributing to this. Would it be
> possible to get some details about your D Drive that may help me to
> reproduce this. The odd thing is that in the files view we are displaying
> this correctly...so I'm kind of stumped as to what might be going on here.
>
> Please verify that the file sizes are being built into the MSI package
> correctly by opening the MSI package in Direct Mode and looking at the file
> table. If we are also building this data incorrectly you could have issues
> with improper costing at runtime. It probably is not a big deal with 180K,
> but that can add up real quick.
>
> "Chris Graham" <cgraham@kanbay.com.au> wrote in message
> news:3BC245F5.72E7EEA4@kanbay.com.au...
> > Hello David,
> > I can reproduce it with just about any file.
> >
> > I just realised that the thing that I was doing differently was I was
> > turning off the 'Use System Attributes'. If any file was displayed as 'X
> Kb',
> > I was only getting X bytes displayed. I need to turn this off, as some of
> the
> > files that are included in the build are under source controll, and have
> the
> > read-only bit set, which I do not want set when installed. If there is
> another
> > way of resetting file attributes, then please let me know, but this is all
> > that I could find in the doco.
> >
> > I've attached a screen shot to illustrate.
> >
> > -Chris
> >
> > David Thornley wrote:
> >
> > > I can not reproduce this. Can you reproduce this with more than one
> file,
> > > or just this particular file? If it is just this particular file can
> you
> > > possibly zip up and post the file.
> > >
> > > If you can reproduce this with multiple files, can you tell us about
> your
> > > OS, and file system. Is the file located on a network, if so what kind
> of
> > > network.
> > >
> > > Regards
> > > David Thornley
> > >
> > > "Chris Graham" <cgraham@kanbay.com.au> wrote in message
> > > news:3BC1253B.35C47C4A@kanbay.com.au...
> > > > Select a file of a reasonable size. In my case, it is displayed as
> '180
> > > > Kb'.
> > > > RMB, select properties.
> > > > The file size is listed as 180 bytes. Doh! :-)
> > > >
> > > > -Chris
> > > >
> > > >
> >
>
> ----------------------------------------------------------------------------
> ----

NewsArchive
10-10-2001, 12:00 AM

NewsArchive
10-11-2001, 12:00 AM
> Do other small installs run fine on this machine? Is there plenty of disk
> space available on the machine?

Other installs (created with ISPro 6.12) work fine and there are plenty of
disk space left.

/Magnus

NewsArchive
10-12-2001, 12:00 AM
I actually meant other installs created with IS7. Can you create a small
sample install and make sure that works (make sure you specify a value for
ARPPRODUCTICON in the sample install).

"Magnus Persson" <magnus.persson@timelox.com> wrote in message
news:3bc5467f@news.installshield.com...
> > Do other small installs run fine on this machine? Is there plenty of
disk
> > space available on the machine?
>
> Other installs (created with ISPro 6.12) work fine and there are plenty of
> disk space left.
>
> /Magnus
>
>

NewsArchive
10-13-2001, 12:00 AM
Well - an exe without it's associated DLLs is not going to work so that
seems 'atomic'. Also SCRs, VXDs, SYS should also be treated the same way
surely?. Obviously however DLLs may be shared amongst exes sooo....

....I did say I might change my mind and I have. I now have each file as a
component (except for txt, pdf, hlp?,etc) and include VXDs, SYS, etc in the
definition of component. It's actually easier to find the files now (50+).

Interestingly I have decided to even extend the idea of 'component' to
registry settings. This is because a reg setting can be shared amongst
components and the same component can have different keys depending on the
platform (don't blame my app for this). Makes the reg settings easier to
track.

I name all components according to a scheme, such
mn.ws.942.component1 = microsoft or novell . workstation or server . 9x or
nt4 or 2000.
m.s.4.component2
m.s.2.component2 (same file name different binary)
reg.m.s.42.key = reg setting common to whatever..
ini.mn.w.9.component3

...and so on.

By the way - know how to distinguish PDCs and BDCs?

cheers
bruce

"Stefan Krueger" <nwsgrp@installsite.org> wrote in message
news:3bb4a6a1@news.installshield.com...
> The reason is auto repair. Each component has one key file. When
> launching an application Windows checks all the key files, and
> re-installs them if they have been deleted. Therefore each essential
> file should be in a separate component. Another reason is that
> components are atomic: you can't install only a part of it. So if you
> have an exe, several DLLs and OCXs all in one component, you can't
> decide to just install (or uninstall) some of them. A third reason is
> updates...
> Where do you see the problem with this?
>
> --
> Stefan Krueger - Independent Setup Consultant
>
> InstallSite - code samples, tips, tools, bug lists, and more
> http://www.installsite.org http://www.installsite.de (GERMAN)
> Support and consulting http://www.installsite.org/krueger
>
> Stefan Krueger and the InstallSite web site are not affiliated
> with InstallShield Software Corporation.
>
>
> "Bruce Cartland" <bruce.cartland@pobox.com> schrieb im Newsbeitrag
> news:3bb3eab1$1@news.installshield.com...
> > I meant "I haven't need a script so far ..."
> >
> > One thing though. While I'm still a bit of a newbie and may change
> my
> > opinion when I understand MSI more (after the course:) - right now I
> think
> > Microsofts install component architecture SUCKS big time. Can't
> agree with
> > their idea of "Best Practice". It is really difficult to manage a
> project
> > when every DLL, EXE or HLP is a seperate component especially with
> different
> > versions of the same file for different targets. Also, what about
> > screensavers, device drivers, OCXs etc - they're all binaries, yet
> they
> > don't seem to be included in the definition of components.
> >
> > thanks for listening :)
> > bruce
> >
> > "Bruce Cartland" <bruce.cartland@pobox.com> wrote in message
> > news:3bb3e755@news.installshield.com...
> > > I have a pretty complex application/system level install with
> common and
> > > multiple versions of files and configs targetting 9x, NT4
> workstations and
> > > servers (PDCs and BDCs), and NT2000 workstations and servers (AD),
> and all
> > > the previous with and without the Novell/Netware Client. The
> package is
> > > installing application files, NT services, COM servers, GINA
> (login)
> > > replacements, screensavers, etc. Only the GINA 'feature' requires
> a
> > reboot.
> > > Haven't figured out how to incorporate the device drivers yet.
> > >
> > > We used to have several IS6 packages (8) at 4MB each which
> prompted the
> > user
> > > for the version to install. With ISDev7/MSI I now have ONE 5Mb
> package
> > that
> > > auto-detects the environment. I am doing this without ANY
> SCRIPTING using
> > > Basic MSI.
> > >
> > > BLOODY BRILLIANT.
> > >
> > > Ok so I have some issues. Couldn't upgrade old projects so started
> from
> > > scratch (which was a good thing in retrospect). ISDev7 is buggy. I
> backup
> > > projects religiously. I am VERY CAREFUL using Direct Edit as I've
> trashed
> > > two projects with it so far.
> > >
> > > My main problem is the bug that doesn't allow me to add Scripts
> (but I
> > have
> > > needed a script yet - it's just as easy for me to knock up an exe
> and run
> > > that via a Custom Action).
> > >
> > > All in all - a great experience.
> > >
> > > cheers
> > > bruce
> > >
> > >
> >
> >
>

NewsArchive
10-22-2001, 12:00 AM
OK, now I'm REALLY confused.

I upgraded the project to Installshield Developer 7 in the hopes that the
problem would go away.

And it did... I was so relieved - Win98 now works fine.

I then got QA to double-check the other OSes - now Win2000 has the EXACT
same problem as before.

I'm really at a loss here - it only happens during an upgrade, the actual
files are copied successfully, it's only the shortcuts that are screwed.
Running the installer and selecting Remove uninstalls everything and allows
it to be reinstalled successfully. Running the installer and selecting
Repair actually repairs the shortcuts so that they work.

In summary, using ISWI the upgrade doesn't work on Win9x, using ISD7 the
upgrade doesn't work on Win2K.

Any ideas are desperately welcome!
Andrew

"Andrew Parsons" <andrew.parsons@quicken.com.au> wrote in message
news:3bcfa372@news.installshield.com...
> I've got some more information.
>
> 1) The problem does not occur on NT/2000. It does occur on Win98 and
WinMe.
> 2) If the installer is used as a fresh install (ie, no previous version
> installed), it works fine
> 3) If the installer is used as an "upgrade", it successfully uninstalls
the
> previous version, and installs all but one file of the new one (just
happens
> to be JetComp.exe).
> 4) Double-clicking the shortcut produces this problem, but double-clicking
> the actual EXE in the installation directory works fine. Both shortcuts
have
> this problem (the one on the desktop and the one in the start menu).
> 5) Watching the messages on the installer, everything looks fine - the
last
> message is "Registering Product" which takes a while and then the finish
> button appears and it shuts the installer down fine.
> 6) If we run the installer again, it prompts for Modify/Repair/Remove -
> using the Remove option uninstalls everything, and then running the
> installer for the final time everything installs properly (just the same
as
> a fresh install). I have yet to get them to try the Modify/Repair options.
> 7) I've tried rebuilding the setup, both as a all in one setup.exe file,
and
> with all files separate and both produce this problem.
>
> What should I look for in the automatic repair function?
>
> Thanks
> Andrew
>
>
>
> "Pieter van Kampen" <vankampenp@hotmail.com> wrote in message
> news:3bceaf88@news.installshield.com...
> > Strange. I would look in the direction of the automatic repair function.
> If
> > you delete a file from the installed package, it will start install as
> soon
> > as you attempt to start the software. So check if everything is there
that
> > should be there. Does your second install delete something from your
first
> > install?
> >
> > Pieter
> >
> > "Andrew Parsons" <andrew.parsons@quicken.com.au> wrote in message
> > news:3bce7775$1@news.installshield.com...
> > > Hi all,
> > >
> > > I have an installer package that upgrades a previous version by first
> > > uninstalling the previous version before installing the new version.
> > >
> > > Last week, QA tested it and it all ran fine. This week, however, it
> > doesn't.
> > > I haven't changed anything in the setup.exe file (I have not rebuilt
it
> in
> > > InstallShield), the only change from my end was that I changed the
name
> > from
> > > "setup (gosh I hope this works).exe" to "setup.exe" (should be obvious
> why
> > I
> > > changed the name).
> > >
> > > Now, when the QA guys run the installer, it detects the old version
and
> > > uninstalls it. It then installs the files and the shortcuts on the
> desktop
> > > and hangs.
> > >
> > > When the QA guys shut it down, reboot, and doubleclick the shortcut to
> > start
> > > the app, it fires off the installer again. Every attempt produces the
> same
> > > problem.
> > >
> > > They claim they're not doing anything different from last week... And
to
> > > make it weird, our application is comprised of two separate products
> that
> > > need to be installed separately - one still installs fine, but the
other
> > is
> > > causing this problem.
> > >
> > > Can someone give me some ideas on why it would want to restart the
> > installer
> > > every time the application shortcut is doubleclicked?
> > >
> > > Thanks
> > > Andrew
> > >
> > >
> >
> >
>
>

NewsArchive
10-23-2001, 12:00 AM
Bruce,

All you have to do is open the project that you copied (or created with Save
As), then go to 1 - Organize Your Setup | General Information | Summay
Information Stream. You'll see a "Package Code" entry on the right hand
side. If you click on it, the lower content window will display a button
labeled "Generate GUID". You can click on this to create a new one for the
copied IS project.

Hope that helps!
Dave

"Christoher F. Conner" <CFConner@hotmail.com> wrote in message
news:3bc9bdbe@news.installshield.com...
> I have not researched if the attached GuidGen.exe (by microsoft - its part
> of the platform sdk) is distributable. The newsgroup admin may delete the
> attachment/message. If you wish to get this along with all the great
tools -
> download the platform sdk.
>
> When running it, select the 4th option (registry format) which is the
format
> for windows installer.
>
> =-Chris
>
> "Bruce Cartland" <bruce.cartland@pobox.com> wrote in message
> news:3bc7ceb3@news.installshield.com...
> > I thought I'd split my project up my copying it and modifying the
copies.
> > Bad idea. After some weird behaviour finally figured out that the GUIDs
> were
> > all the same.
> >
> > Is there any way to do this without having to start a new project or
going
> > to each component, etc and regenerating the GUIDs? 'Save As' doesn't
> > regenerate the GUIDs.
> >
> > thanks
> > bruce
> >
> >
> >
>
>
>

NewsArchive
10-23-2001, 12:00 AM
You are correct about this Dave, however some people have had some problems
with the Guid button not working correctly. I was just offering a separate
utility that would create them as well.

=-Chris

"Dave Matsumoto" <dmatsumoto@11yticolev.com> wrote in message
news:3bd592b0$1@news.installshield.com...
> Bruce,
>
> All you have to do is open the project that you copied (or created with
Save
> As), then go to 1 - Organize Your Setup | General Information | Summay
> Information Stream. You'll see a "Package Code" entry on the right hand
> side. If you click on it, the lower content window will display a button
> labeled "Generate GUID". You can click on this to create a new one for
the
> copied IS project.
>
> Hope that helps!
> Dave
>
> "Christoher F. Conner" <CFConner@hotmail.com> wrote in message
> news:3bc9bdbe@news.installshield.com...
> > I have not researched if the attached GuidGen.exe (by microsoft - its
part
> > of the platform sdk) is distributable. The newsgroup admin may delete
the
> > attachment/message. If you wish to get this along with all the great
> tools -
> > download the platform sdk.
> >
> > When running it, select the 4th option (registry format) which is the
> format
> > for windows installer.
> >
> > =-Chris
> >
> > "Bruce Cartland" <bruce.cartland@pobox.com> wrote in message
> > news:3bc7ceb3@news.installshield.com...
> > > I thought I'd split my project up my copying it and modifying the
> copies.
> > > Bad idea. After some weird behaviour finally figured out that the
GUIDs
> > were
> > > all the same.
> > >
> > > Is there any way to do this without having to start a new project or
> going
> > > to each component, etc and regenerating the GUIDs? 'Save As' doesn't
> > > regenerate the GUIDs.
> > >
> > > thanks
> > > bruce
> > >
> > >
> > >
> >
> >
> >
>
>

NewsArchive
10-24-2001, 12:00 AM
Ted,

maybe I am not being clear..

I am using the SdShowDlgEdit3 dialog, which has the following 3 edit fields:

svEdit1
svEdit2
svEdit3

I need to write the contents of those fields to an ini file created during
installation, using the "INI Files Changes".

How can I set the svEdit1 string to something that can be used later in the
installation process.

For example, the SdAskDestPath dialog changes the value of [INSTALLDIR], and I
can then use [INSTALLDIR] in the INI File "Data Value" section.

Since the ini file is created after the SdShowDlgEdit3 dialog, I cannot modify
the keywords I need to in the Installscript.

Any suggestions?

Ted wrote:

> CtrlGetText function.
>
> Ted.
>
> "Todd Beebe" <todd@internetworking.com> wrote in message
> news:3BD60493.20EF0C8E@internetworking.com...
> > I understand how to write to the inifile, but I don't know how to retrieve
> the
> > value of a dialog text edit field.
> >
> > For example, the SdCustomerInformationEx dialog has 3 text edit fields
> > (username, companyname, and serial number).
> >
> > Using the "INI File Changes" section, what Data Value could I use to add
> the
> > items listed above to an INI File?
> >
> >
> > Robert Love wrote:
> >
> > > You can use the ISD Script command of GetProfString, it is documented in
> the
> > > Language Reference Help File. It is found under the Functions|Built-in
> > > Functions|Initialization File Functions section of the Table of
> Contents.
> > >
> > > Robert Love
> > >
> > > "Todd Beebe" <todd@internetworking.com> wrote in message
> > > news:3BD5F1F2.692C7B11@internetworking.com...
> > > >
> > > > I am probably missing something simple, but how do I retrieve the
> value
> > > > of a text edit field? I can successfully modify the [INSTALLDIR]
> > > > property and write that, but the other edit fields do not use
> properties
> > > > for their initial value.
> > > >
> > > > Thanks in advance.
> > > >
> >

NewsArchive
10-24-2001, 12:00 AM
Ted,

maybe I am not being clear..

I am using the SdShowDlgEdit3 dialog, which has the following 3 edit fields:

svEdit1
svEdit2
svEdit3

I need to write the contents of those fields to an ini file created during
installation, using the "INI Files Changes".

How can I set the svEdit1 string to something that can be used later in the
installation process.

For example, the SdAskDestPath dialog changes the value of [INSTALLDIR], and I
can then use [INSTALLDIR] in the INI File "Data Value" section.

Since the ini file is created after the SdShowDlgEdit3 dialog, I cannot modify
the keywords I need to in the Installscript.

Any suggestions?

Ted wrote:

> CtrlGetText function.
>
> Ted.
>
> "Todd Beebe" <todd@internetworking.com> wrote in message
> news:3BD60493.20EF0C8E@internetworking.com...
> > I understand how to write to the inifile, but I don't know how to retrieve
> the
> > value of a dialog text edit field.
> >
> > For example, the SdCustomerInformationEx dialog has 3 text edit fields
> > (username, companyname, and serial number).
> >
> > Using the "INI File Changes" section, what Data Value could I use to add
> the
> > items listed above to an INI File?
> >
> >
> > Robert Love wrote:
> >
> > > You can use the ISD Script command of GetProfString, it is documented in
> the
> > > Language Reference Help File. It is found under the Functions|Built-in
> > > Functions|Initialization File Functions section of the Table of
> Contents.
> > >
> > > Robert Love
> > >
> > > "Todd Beebe" <todd@internetworking.com> wrote in message
> > > news:3BD5F1F2.692C7B11@internetworking.com...
> > > >
> > > > I am probably missing something simple, but how do I retrieve the
> value
> > > > of a text edit field? I can successfully modify the [INSTALLDIR]
> > > > property and write that, but the other edit fields do not use
> properties
> > > > for their initial value.
> > > >
> > > > Thanks in advance.
> > > >
> >

NewsArchive
10-24-2001, 12:00 AM
FeatureSetTarget (previously known as ComponentSetTarget). Very useful in
my opinion - create as many user defined variables as you want.

Ted.

"Todd Beebe" <todd@internetworking.com> wrote in message
news:3BD6E195.139DF03C@internetworking.com...
> Ted,
>
> maybe I am not being clear..
>
> I am using the SdShowDlgEdit3 dialog, which has the following 3 edit
fields:
>
> svEdit1
> svEdit2
> svEdit3
>
> I need to write the contents of those fields to an ini file created during
> installation, using the "INI Files Changes".
>
> How can I set the svEdit1 string to something that can be used later in
the
> installation process.
>
> For example, the SdAskDestPath dialog changes the value of [INSTALLDIR],
and I
> can then use [INSTALLDIR] in the INI File "Data Value" section.
>
> Since the ini file is created after the SdShowDlgEdit3 dialog, I cannot
modify
> the keywords I need to in the Installscript.
>
> Any suggestions?
>
> Ted wrote:
>
> > CtrlGetText function.
> >
> > Ted.
> >
> > "Todd Beebe" <todd@internetworking.com> wrote in message
> > news:3BD60493.20EF0C8E@internetworking.com...
> > > I understand how to write to the inifile, but I don't know how to
retrieve
> > the
> > > value of a dialog text edit field.
> > >
> > > For example, the SdCustomerInformationEx dialog has 3 text edit fields
> > > (username, companyname, and serial number).
> > >
> > > Using the "INI File Changes" section, what Data Value could I use to
add
> > the
> > > items listed above to an INI File?
> > >
> > >
> > > Robert Love wrote:
> > >
> > > > You can use the ISD Script command of GetProfString, it is
documented in
> > the
> > > > Language Reference Help File. It is found under the
Functions|Built-in
> > > > Functions|Initialization File Functions section of the Table of
> > Contents.
> > > >
> > > > Robert Love
> > > >
> > > > "Todd Beebe" <todd@internetworking.com> wrote in message
> > > > news:3BD5F1F2.692C7B11@internetworking.com...
> > > > >
> > > > > I am probably missing something simple, but how do I retrieve the
> > value
> > > > > of a text edit field? I can successfully modify the [INSTALLDIR]
> > > > > property and write that, but the other edit fields do not use
> > properties
> > > > > for their initial value.
> > > > >
> > > > > Thanks in advance.
> > > > >
> > >
>

NewsArchive
10-24-2001, 12:00 AM
I tried the Wise Windows Installer product and found it harder to use and
not without its own problems. I think a lot of the issues have to do with
the Microsoft Windows Installer itself.

You are right that ISDev7 is MUCH buggier than reasonable but there are work
arounds. I strongly recommend that you install ORCA from the MS Platform
SDK. You can use this to edit the msi directly and see what it is ISDev is
creating. Learn to use the Direct Editor in IS. The Platform SDK and MSDN
have a description of these tables as well as other necessary information.

As for nobody in this newsgroup responding to your questions, you need to be
more patient. No one is paying me or the others to respond. I am only
responding because others have helped me.


"Lewis Gordon Pringle, Jr." <lewis@sophists.com> wrote in message
news:3bd6b9b1@news.installshield.com...
> I'm really depressed. I've had several people work for me over the last
> few years doing installer development. They used InstallShield (windows
> installer version). They all failed. All they managed todo was produce
> broken, half-functional installers.
>
-- SNIP --

NewsArchive
10-24-2001, 12:00 AM
COMPETITOR FREE RESPONSE (due to previous "deleted by Installshield" post):

There are no alternatives to Installshield, but there are other older
versions of Installshield you may want to consider.

One of the problems is that Installshield 7 is very, very powerful - with
great power comes great responsibility (i.e. you are responsible for any
shortcomings and bugs). We've all seen this all before with IS 6.x series -
I only felt confident in shipping a 6.x install when we hit the 6.2 series
(a year after initial 6 release), i.e. it takes a long time for a .0 product
to become stable. Give it 6-8 months or so, then I think most the kinks
will be ironed out of the 7 product.

I always recommend Intstallshield 5.53 - prove me wrong that this is the
best piece of install software ever designed: simple, and it just works.
Two qualities that I really like. Several MAJOR packages still use this to
this day. (e.g. Microsoft SQL Server, Adobe Acrobat, etc).

Ted.

NewsArchive
10-25-2001, 12:00 AM
Did installshield censor my posted reply? I don't see it and from the
looks of your message it looks like you did and now you don't.

Robert Love


"Ted" <Ted@t--x.org> wrote in message
news:3bd772cf@news.installshield.com...
> COMPETITOR FREE RESPONSE (due to previous "deleted by Installshield"
post):
>
> There are no alternatives to Installshield, but there are other older
> versions of Installshield you may want to consider.
>
> One of the problems is that Installshield 7 is very, very powerful - with
> great power comes great responsibility (i.e. you are responsible for any
> shortcomings and bugs). We've all seen this all before with IS 6.x
series -
> I only felt confident in shipping a 6.x install when we hit the 6.2 series
> (a year after initial 6 release), i.e. it takes a long time for a .0
product
> to become stable. Give it 6-8 months or so, then I think most the kinks
> will be ironed out of the 7 product.
>
> I always recommend Intstallshield 5.53 - prove me wrong that this is the
> best piece of install software ever designed: simple, and it just works.
> Two qualities that I really like. Several MAJOR packages still use this
to
> this day. (e.g. Microsoft SQL Server, Adobe Acrobat, etc).
>
> Ted.
>
>
>

NewsArchive
10-25-2001, 12:00 AM
Yes, Installshield will tolerate pretty much anything in these newsgroups
including flames, EXCEPT any mention whatsoever of competing products, so
yes, your reply (which I considered quite good) is gone forever.

Ted.

"Robert Love" <rlove@qqest.com> wrote in message
news:3bd865ff$1@news.installshield.com...
> Did installshield censor my posted reply? I don't see it and from the
> looks of your message it looks like you did and now you don't.
>
> Robert Love
>
>
> "Ted" <Ted@t--x.org> wrote in message
> news:3bd772cf@news.installshield.com...
> > COMPETITOR FREE RESPONSE (due to previous "deleted by Installshield"
> post):
> >
> > There are no alternatives to Installshield, but there are other older
> > versions of Installshield you may want to consider.
> >
> > One of the problems is that Installshield 7 is very, very powerful -
with
> > great power comes great responsibility (i.e. you are responsible for any
> > shortcomings and bugs). We've all seen this all before with IS 6.x
> series -
> > I only felt confident in shipping a 6.x install when we hit the 6.2
series
> > (a year after initial 6 release), i.e. it takes a long time for a .0
> product
> > to become stable. Give it 6-8 months or so, then I think most the kinks
> > will be ironed out of the 7 product.
> >
> > I always recommend Intstallshield 5.53 - prove me wrong that this is the
> > best piece of install software ever designed: simple, and it just works.
> > Two qualities that I really like. Several MAJOR packages still use
this
> to
> > this day. (e.g. Microsoft SQL Server, Adobe Acrobat, etc).
> >
> > Ted.
> >
> >
> >
>
>

NewsArchive
10-25-2001, 12:00 AM
Please ignore - I figured it out.

"Sam Darwin" <sam@freepeers.com> wrote in message
news:3bd743f4$1@news.installshield.com...
> Hello all,
> I am pretty new to InstallShield, so I hope that someone out there can
help
> me.
>
> I am editing the text in one of the Dialogs (specifically SdWelcome) and
> have put in a paragraph which is a few lines long. During the actual
> installation process my paragraph does not display. It simply reports
"STR
> OVER LIMIT", which I guess means that my text was too long. However, the
> text was not so much that it couldn't easily appear on the screen.
>
> So the question is "How much text can you write into a dialog?", and
> secondly "How could I add another text box to the existing dialog?" in
order
> to add the text which apparently can't fit into the first text box.
>
> Thanks,
> Sam
>
> sam@freepeers.com
>
>

NewsArchive
10-26-2001, 12:00 AM
If you install something and then delete a file, the Installer will start
again to reinstall the file as soon as you start the installed executable.
That is why I suggested to have a look in that direction.

Upgrading may have changed the windows installer version that you bundle,
causing the different behavior. Try installing your ISD7 version by double
clicking the .msi package rather than the setup.exe created by ISD7 (which
includes the installation of the latest Microsoft installer.)

To really know what is going on, make a log file during the install. It
should give you enough information to find out what is going on. Look for
command line and log in the ISWI or ISD7 help.

Pieter


"Andrew Parsons" <andrew.parsons@quicken.com.au> wrote in message
news:3bd39f29@news.installshield.com...
> OK, now I'm REALLY confused.
>
> I upgraded the project to Installshield Developer 7 in the hopes that the
> problem would go away.
>
> And it did... I was so relieved - Win98 now works fine.
>
> I then got QA to double-check the other OSes - now Win2000 has the EXACT
> same problem as before.
>
> I'm really at a loss here - it only happens during an upgrade, the actual
> files are copied successfully, it's only the shortcuts that are screwed.
> Running the installer and selecting Remove uninstalls everything and
allows
> it to be reinstalled successfully. Running the installer and selecting
> Repair actually repairs the shortcuts so that they work.
>
> In summary, using ISWI the upgrade doesn't work on Win9x, using ISD7 the
> upgrade doesn't work on Win2K.
>
> Any ideas are desperately welcome!
> Andrew
>
> "Andrew Parsons" <andrew.parsons@quicken.com.au> wrote in message
> news:3bcfa372@news.installshield.com...
> > I've got some more information.
> >
> > 1) The problem does not occur on NT/2000. It does occur on Win98 and
> WinMe.
> > 2) If the installer is used as a fresh install (ie, no previous version
> > installed), it works fine
> > 3) If the installer is used as an "upgrade", it successfully uninstalls
> the
> > previous version, and installs all but one file of the new one (just
> happens
> > to be JetComp.exe).
> > 4) Double-clicking the shortcut produces this problem, but
double-clicking
> > the actual EXE in the installation directory works fine. Both shortcuts
> have
> > this problem (the one on the desktop and the one in the start menu).
> > 5) Watching the messages on the installer, everything looks fine - the
> last
> > message is "Registering Product" which takes a while and then the finish
> > button appears and it shuts the installer down fine.
> > 6) If we run the installer again, it prompts for Modify/Repair/Remove -
> > using the Remove option uninstalls everything, and then running the
> > installer for the final time everything installs properly (just the same
> as
> > a fresh install). I have yet to get them to try the Modify/Repair
options.
> > 7) I've tried rebuilding the setup, both as a all in one setup.exe file,
> and
> > with all files separate and both produce this problem.
> >
> > What should I look for in the automatic repair function?
> >
> > Thanks
> > Andrew
> >
> >
> >
> > "Pieter van Kampen" <vankampenp@hotmail.com> wrote in message
> > news:3bceaf88@news.installshield.com...
> > > Strange. I would look in the direction of the automatic repair
function.
> > If
> > > you delete a file from the installed package, it will start install as
> > soon
> > > as you attempt to start the software. So check if everything is there
> that
> > > should be there. Does your second install delete something from your
> first
> > > install?
> > >
> > > Pieter
> > >
> > > "Andrew Parsons" <andrew.parsons@quicken.com.au> wrote in message
> > > news:3bce7775$1@news.installshield.com...
> > > > Hi all,
> > > >
> > > > I have an installer package that upgrades a previous version by
first
> > > > uninstalling the previous version before installing the new version.
> > > >
> > > > Last week, QA tested it and it all ran fine. This week, however, it
> > > doesn't.
> > > > I haven't changed anything in the setup.exe file (I have not rebuilt
> it
> > in
> > > > InstallShield), the only change from my end was that I changed the
> name
> > > from
> > > > "setup (gosh I hope this works).exe" to "setup.exe" (should be
obvious
> > why
> > > I
> > > > changed the name).
> > > >
> > > > Now, when the QA guys run the installer, it detects the old version
> and
> > > > uninstalls it. It then installs the files and the shortcuts on the
> > desktop
> > > > and hangs.
> > > >
> > > > When the QA guys shut it down, reboot, and doubleclick the shortcut
to
> > > start
> > > > the app, it fires off the installer again. Every attempt produces
the
> > same
> > > > problem.
> > > >
> > > > They claim they're not doing anything different from last week...
And
> to
> > > > make it weird, our application is comprised of two separate products
> > that
> > > > need to be installed separately - one still installs fine, but the
> other
> > > is
> > > > causing this problem.
> > > >
> > > > Can someone give me some ideas on why it would want to restart the
> > > installer
> > > > every time the application shortcut is doubleclicked?
> > > >
> > > > Thanks
> > > > Andrew
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
10-26-2001, 12:00 AM
Is the svSerial you are using a global variable?

Kent

"Todd Beebe" <todd@internetworking.com> wrote in message
news:3BD72472.3AA1529F@internetworking.com...
> It does. But then when I try to access svSerial in the onFirstUIAfter
> function it is blank.
>
> Any suggestions on how to obtain a field that is set in the UIBefore
function
> and is needed in the UIAfter function?
>
> Kent Foyer wrote:
>
> > I think the svSerial parameter that is passed in is also an in/out
> > parameter. So when the user presses next this variable will contain the
> > serial number the user typed in.
> >
> > Kent
> >
> > "Todd Beebe" <todd@internetworking.com> wrote in message
> > news:3BD716E1.CA6B998D@internetworking.com...
> > > I am using the SDCustomerInformationEx dialog which has the szSerial
> > > edit field that the user defines the product serial number during the
> > > onFirstUIBefore function.
> > >
> > > I need to access the contents of the szSerial field for a dialog in
the
> > > onFirstUIAfter function.
> > >
> > > Any suggestions?
> > >
>

NewsArchive
10-26-2001, 12:00 AM
I know...but how do I get rid of this now. I am trying to locate...but it
seems I am not able to.

Thx!
Manish


"Phil Wilson" <phil.wilson@unisys.com> wrote in message
news:3bd9cf82$1@news.installshield.com...
> I don't think you need that "\" after [INSTALLDIR]. I seem to remember
that
> it already includes the backslash.
>
> "manish" <mdawar@telseon.com> wrote in message
> news:3bd9aa63$1@news.installshield.com...
> > Hi Everyone,
> >
> > I am trying to create a package using Installshield developer 7 and when
I
> > am running the Installation, I get this strange error
> >
> > "Error 1324: The path [INSTALLDIR]\CompanyName contains an invalid
> > character."
> >
> > After I say ok to this error I get another error
> >
> > "1628: Failed to complete Installation."
> >
> > Can anyone help in this Issue. I am stuck and need your help.
> >
> > Regards,
> >
> > Manish
> >
> > mdawar@telseon.com <mailto:mdawar@telseon.com>
> >
> >
> >
>
>

NewsArchive
10-26-2001, 12:00 AM
It could be in Organize Your Setup, General Information, INSTALLDIR.

Or in Advanced Views, Setup Design, each top level feature has a
Destination.

"manish" <mdawar@telseon.com> wrote in message
news:3bd9d192$1@news.installshield.com...
> I know...but how do I get rid of this now. I am trying to locate...but it
> seems I am not able to.
>
> Thx!
> Manish
>
>
> "Phil Wilson" <phil.wilson@unisys.com> wrote in message
> news:3bd9cf82$1@news.installshield.com...
> > I don't think you need that "\" after [INSTALLDIR]. I seem to remember
> that
> > it already includes the backslash.
> >
> > "manish" <mdawar@telseon.com> wrote in message
> > news:3bd9aa63$1@news.installshield.com...
> > > Hi Everyone,
> > >
> > > I am trying to create a package using Installshield developer 7 and
when
> I
> > > am running the Installation, I get this strange error
> > >
> > > "Error 1324: The path [INSTALLDIR]\CompanyName contains an invalid
> > > character."
> > >
> > > After I say ok to this error I get another error
> > >
> > > "1628: Failed to complete Installation."
> > >
> > > Can anyone help in this Issue. I am stuck and need your help.
> > >
> > > Regards,
> > >
> > > Manish
> > >
> > > mdawar@telseon.com <mailto:mdawar@telseon.com>
> > >
> > >
> > >
> >
> >
>
>

NewsArchive
10-29-2001, 01:00 AM
In all circumstances, the msi dialog reappears behind the top-most window.
I've tried SetWindowPos, BringWindowToTop, and SetFocus but none of them
have an affect. Is there anything else I can try?


"Evan A. Barr" <Not@Public.com> wrote in message
news:3bddaf9d@news.installshield.com...
> OK, figured that one out. The issue was that I was testing within the
> ISDev7 IDE.
> Thanks for your help.
>
>
> "Evan A. Barr" <Not@Public.com> wrote in message
> news:3bddad1c@news.installshield.com...
> > Ah! I was using CmdGetHwndDlg with the name of the current msi dialog
> > instead of FindWindow and that of course wasn't working.
> >
> > There is still a problem though, when I use ShowWindow(hMsiWnd,SW_SHOW),
> the
> > window appears behind other open windows. I tried using SetFocus and
> > BringWindowToTop but with no success.
> >
> >
> > "David Thornley" <davidt@installshield.com> wrote in message
> > news:3bdd8f8a$1@news.installshield.com...
> > > You actually need to hide the MSI dialogs. In 2.03 you could call
> > > Disable(MSIDIALOG) to do this, however we removed that from Developer
7
> > > thinking that if people wanted standard dialogs they would use a
> standard
> > > project. Since that does not look like the case I have added a WO
> asking
> > to
> > > add that function back in.
> > >
> > > Until then, you can hide the MSI dialogs yourself with the following
> > script
> > > code...donated to me by one of my co workers. The limitation of this
is
> > > that if there are two MSI installations running at the same time you
> will
> > > hide the dialogs of both installations...but as long as you unhide
when
> > your
> > > dialog is done,with SW_SHOW, I would think you should be OK.
> > >
> > > HWND hMsiWnd;
> > > hMsiWnd = FindWindow("MsiDialogCloseClass","");
> > > ShowWindow(hMsiWnd,SW_HIDE);
> > >
> > > ShowWindow will not color code in the script editor, but it will still
> > > compile. I have added WO
> > >
> > > Regards
> > > David Thornley
> >
> >
> >
>
>

NewsArchive
10-30-2001, 01:00 AM
Well you just saved me! I was having the same similar problem as Manish,
and I finally found a top level feature that had an incorrect setting in
it's Destination value.
Thanks,
Mike...

"Phil Wilson" <phil.wilson@unisys.com> wrote in message
news:3bd9d4a8$1@news.installshield.com...
> It could be in Organize Your Setup, General Information, INSTALLDIR.
>
> Or in Advanced Views, Setup Design, each top level feature has a
> Destination.
>
> "manish" <mdawar@telseon.com> wrote in message
> news:3bd9d192$1@news.installshield.com...
> > I know...but how do I get rid of this now. I am trying to locate...but
it
> > seems I am not able to.
> >
> > Thx!
> > Manish
> >
> >
> > "Phil Wilson" <phil.wilson@unisys.com> wrote in message
> > news:3bd9cf82$1@news.installshield.com...
> > > I don't think you need that "\" after [INSTALLDIR]. I seem to remember
> > that
> > > it already includes the backslash.
> > >
> > > "manish" <mdawar@telseon.com> wrote in message
> > > news:3bd9aa63$1@news.installshield.com...
> > > > Hi Everyone,
> > > >
> > > > I am trying to create a package using Installshield developer 7 and
> when
> > I
> > > > am running the Installation, I get this strange error
> > > >
> > > > "Error 1324: The path [INSTALLDIR]\CompanyName contains an invalid
> > > > character."
> > > >
> > > > After I say ok to this error I get another error
> > > >
> > > > "1628: Failed to complete Installation."
> > > >
> > > > Can anyone help in this Issue. I am stuck and need your help.
> > > >
> > > > Regards,
> > > >
> > > > Manish
> > > >
> > > > mdawar@telseon.com <mailto:mdawar@telseon.com>
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
10-31-2001, 01:00 AM
"Art Middlekauff" <artm@installshield.com> wrote in message
news:3bdf3956$1@news.installshield.com...
> When I have seen this error before, it could be corrected by opening IE
and
> going to
> View | Encoding and unchecking AutoSelect. Could you please try that and
> let me know if it solves the problem.

Art,
that resolves the symptom, but not the problem. I develop web sites in many
encodings other than English it makes it a pain to have to change my IE
settings each time that I switch from using ISDev7 to modifying/viewing web
pages. Why doesn't IS just embed the charset encoding into the HTML
documents and avoid the problem altogether?

-Pete

NewsArchive
10-31-2001, 01:00 AM
Bug # 1-6X931. This will receive high priority.

Regards,
Art

-----Original Message-----
From: Pete Delgado [mailto:Peter.Delgado@sdrc.com]
Posted At: Wednesday, October 31, 2001 12:47 PM
Posted To: general
Conversation: IDE JavaScript Errors
Re: IDE JavaScript Errors



"Art Middlekauff" <artm@installshield.com> wrote in message
news:3bdf3956$1@news.installshield.com...
> When I have seen this error before, it could be corrected by opening
IE
and
> going to
> View | Encoding and unchecking AutoSelect. Could you please try that
and
> let me know if it solves the problem.

Art,
that resolves the symptom, but not the problem. I develop web sites in
many
encodings other than English it makes it a pain to have to change my IE
settings each time that I switch from using ISDev7 to modifying/viewing
web
pages. Why doesn't IS just embed the charset encoding into the HTML
documents and avoid the problem altogether?

-Pete

NewsArchive
11-07-2001, 01:00 AM
Thanks for the pointer Dave. However the VersionNT and WindowsBuild
propeties will not distiguish Windows 2000 Server from Windows 2000 DCE.

I have however worked out how to do it.

I can use a VBScript (within a custom action) to check the registry key
listed below :
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions]
"ProductType"="ServerNT"
"ProductSuite"="Enterprise Terminal Server Datacenter"


By the way, DCE stands for Data Center Edition.

Willie

"David Thornley" <davidt@installshield.com> wrote in message
news:3be6c6af$1@news.installshield.com...
> I am not sure what DCE is, but maybe you could make use of the VersionNT
and
> WindowsBuild properties...you would need to find out what the build number
> is for WIN2K DCE and then test for that in an InstalLCondition, available
on
> the product properties page of the General Information View.
>
>
> Regards
> David Thornley
>
> "Willie Wright" <willie@aurema.com> wrote in message
> news:1004912726.210336@cousin.sw.oz.au...
> > I know how to restrict an installation to a specific version of windows
> > (e.g. Windows 2000 or Whistler)via the "Operating System Properties".
> > However I need to restrict my installation to Windows 2000 DCE and I
can't
> > determine how to do this.
> >
> > Anyone got any ideas.
> >
> > Thanks,
> > Willie
> >
> >
>
>

NewsArchive
11-09-2001, 01:00 AM
hi kent,
thanks but I already solve this problem, but now I have one which seem very
tricky, I have this error message displayed:

** Fatal Error: -6002: Error while attempting to run the custom build setp
for objects.

What should I do now
Thakn in advance!!!!


"Kent Foyer" <kent@installshield.com> wrote in message
news:3bec49f6$1@news.installshield.com...
> Most likely, one of the links in the ISSetupFile table is incorrect. Open
> this table in the Direct Editor and make sure the file name and path point
> to a file that actually exists on your machine.
>
> Kent
>
> "alain tamdem" <alain.tamdem@rauland.com> wrote in message
> news:3bec4411$1@news.installshield.com...
> > hi ,
> > I am trying to built my setup .exe and i still have this error
displayed:
> >
> >
> > ** Fatal Error: -5026: Error building table ISSetupFile
> >
> >
> >
> >
> >
> > what should I do ???
> > thanks in advance
> >
> >
> >
>
>

NewsArchive
11-12-2001, 01:00 AM
I have a similar problem so I thought I'd post here. Using standard setup, I
want to copy the CD image to a folder after installing. I can't get the
value of SourceDir or SRCDIR even after ResolveSource action has been
called. The contents both is always the temp folder (the MSI has been
extracted from setup.exe) How do I do this ?

"David Thornley" <davidt@installshield.com> wrote in message
news:3bf00f5c$1@news.installshield.com...
> Maybe I'm a little confused about exactly what you are trying to do..I had
> thought that your explicit scrDir and supportDir references were just
> typo's....but properties with those names do not exist...unless you
created
> them, so you would need to use SOURCEDIR and SUPPORTDIR.
>
> "Josephine Cai" <josephine@kurzweiledu.com> wrote in message
> news:3BF035C5.44E9B429@kurzweiledu.com...
> > No, I am not asking about user-defined properties.
> >
> > I tried passing srcDir and supportDir as property or constant. But I am
> not
> > getting the value of the system variable correctly in my function.
> According to
> > Help, srcDir is initialized to the value of [sourcedir], which is
actually
> the
> > application path. So I set that value to my application path. About
> supportDir,
> > it's resolved by scripting engine and I am not sure how to reference it,
> > [SUPPORTDIR]?
> >
> > Thanks and Regards,
> > Josephine
> >
> > David Thornley wrote:
> >
> > > If you click the help button on that panel, it will display a topic
that
> > > discusses your options in detail. In the case of passing a property
as
> an
> > > argument, you would select in Property as the source and then enter
the
> name
> > > of the property that you want to pass in as the value.
> > >
> > > Regards
> > > David Thornley
> > >
> > > "Josephine Cai" <josephine@kurzweiledu.com> wrote in message
> > > news:3BF00F21.7ACDB39B@kurzweiledu.com...
> > > > Hi,
> > > >
> > > > I need to pass the sytem variables srcDir and supportDir as
arguments
> in
> > > > my dll function. I am wondering how to reference them in the custom
> > > > action wizard. Whether to refer them as "in property" or
"constant"?
> > > > And what should their values be?
> > > >
> > > > Thanks and Regards,
> > > > Josephine
> > > >
> >
>
>

NewsArchive
11-12-2001, 01:00 AM
When the setup is extracted from setup.exe, the installation is being run
from the temp folder...that is why the SRCDIR variable points to that.
There does exist a work order asking for a System Variable along the lines
of SETUPEXE_DIR, though without that functionality there really is no way to
get back to the original source location with a single setup.exe image.
With an uncompressed image, the installation is run from the initial source
location.

Regards
David Thornley

"Bill Oeftering" <bill@mainstreetcomp.com> wrote in message
news:3bf03315$1@news.installshield.com...
> I have a similar problem so I thought I'd post here. Using standard setup,
I
> want to copy the CD image to a folder after installing. I can't get the
> value of SourceDir or SRCDIR even after ResolveSource action has been
> called. The contents both is always the temp folder (the MSI has been
> extracted from setup.exe) How do I do this ?
>
> "David Thornley" <davidt@installshield.com> wrote in message
> news:3bf00f5c$1@news.installshield.com...
> > Maybe I'm a little confused about exactly what you are trying to do..I
had
> > thought that your explicit scrDir and supportDir references were just
> > typo's....but properties with those names do not exist...unless you
> created
> > them, so you would need to use SOURCEDIR and SUPPORTDIR.
> >
> > "Josephine Cai" <josephine@kurzweiledu.com> wrote in message
> > news:3BF035C5.44E9B429@kurzweiledu.com...
> > > No, I am not asking about user-defined properties.
> > >
> > > I tried passing srcDir and supportDir as property or constant. But I
am
> > not
> > > getting the value of the system variable correctly in my function.
> > According to
> > > Help, srcDir is initialized to the value of [sourcedir], which is
> actually
> > the
> > > application path. So I set that value to my application path. About
> > supportDir,
> > > it's resolved by scripting engine and I am not sure how to reference
it,
> > > [SUPPORTDIR]?
> > >
> > > Thanks and Regards,
> > > Josephine
> > >
> > > David Thornley wrote:
> > >
> > > > If you click the help button on that panel, it will display a topic
> that
> > > > discusses your options in detail. In the case of passing a property
> as
> > an
> > > > argument, you would select in Property as the source and then enter
> the
> > name
> > > > of the property that you want to pass in as the value.
> > > >
> > > > Regards
> > > > David Thornley
> > > >
> > > > "Josephine Cai" <josephine@kurzweiledu.com> wrote in message
> > > > news:3BF00F21.7ACDB39B@kurzweiledu.com...
> > > > > Hi,
> > > > >
> > > > > I need to pass the sytem variables srcDir and supportDir as
> arguments
> > in
> > > > > my dll function. I am wondering how to reference them in the
custom
> > > > > action wizard. Whether to refer them as "in property" or
> "constant"?
> > > > > And what should their values be?
> > > > >
> > > > > Thanks and Regards,
> > > > > Josephine
> > > > >
> > >
> >
> >
>
>

NewsArchive
11-14-2001, 01:00 AM
Thanks again for your reply.

No I'm not using *any* merge modules. My installer is very simple: just
copies a couple of files, displays a few custom dialogs, some simple
functions in a script and uses functions in a custom a custom DLL to set up
some drivers.

So am I correct in thinking that it's the IS-Script engine that is requiring
the updated MSI Engine to be installed? Seems kind of silly to me.

How would I go about replacing the isscript.msi?

Also how can I return my W2K machine to it's "virgin" state so I can test
this again (i.e. how can I remove the updates to IS-Script and MSI Engine?)

"Nikolaus Schmitt" <n.schmitt@scaet.de> wrote in message
news:3bf320f8@news.installshield.com...
> Forgot to check Your former posts before writing my last reply ...
> You already set Schema to 110. Does the setup contain any "newer"
> (=Schema200) merge modules?
> If not, The ISScript.msi requires schema=200.
>
> Before blaming teh IS people:
> MSI 2 doesn't need to reboot the system after installation/upgrade.
> Assembling a setup carefully, there will be no reboot up to the very end
of
> all setups. I could imagine, that IS updated the ISScript.msi from 7.0 to
> 7.01 keeping the "no reboot" feature of MSI 2 in mind.
>
> You could try to exchange the isscript.msi after build by the 7.0 version
> ... it should be schema 1.10 or 1.20.
>
>

NewsArchive
11-16-2001, 01:00 AM
Opps...sorry I ment CTRL+ENTER.

....and I am running ISDev701 on Win2kPro SP2.

/Magnus

"Ray Ju" <ray@installshield.com> wrote in message
news:3bf425c6$1@news.installshield.com...
> Maghus,
>
> In 7.01, when I hit SHIFT+ENTER, the String Entry dialog just saves the
data
> and closed. There is no invalid character displayed. I tried it on NT4
SP6
> and Win2K and got the same result. What version of Developer you are
> unning? Help me to recreate the problem.
>
> Thanks.
> Ray,
>
>
> "Magnus Persson" <magnus.persson@timelox.com> wrote in message
> news:3bf396a4$1@news.installshield.com...
> > When you right-click in the string table and select 'Create & Set' in
the
> > popup menu, you can enter a string that contains <CR>/<LF> by pressing
> > SHIFT+ENTER. But then you click on OK the resulting string contains
> invalid
> > characters. However, you can manually change these characters to \n to
> make
> > the string work. Otherwise the string will be cut at the first occurance
> of
> > the invalid characters.
> >
> > /Magnus
> >
> >
>
>

NewsArchive
11-16-2001, 01:00 AM
Yes. You are right. When adding <CR>/<LF> to a String table entry, \n\r
should be used, not CTRL+ENTER.

Thanks.
Ray,


"Magnus Persson" <magnus.persson@timelox.com> wrote in message
news:3bf4be55$1@news.installshield.com...
> Opps...sorry I ment CTRL+ENTER.
>
> ...and I am running ISDev701 on Win2kPro SP2.
>
> /Magnus
>
> "Ray Ju" <ray@installshield.com> wrote in message
> news:3bf425c6$1@news.installshield.com...
> > Maghus,
> >
> > In 7.01, when I hit SHIFT+ENTER, the String Entry dialog just saves the
> data
> > and closed. There is no invalid character displayed. I tried it on NT4
> SP6
> > and Win2K and got the same result. What version of Developer you are
> > unning? Help me to recreate the problem.
> >
> > Thanks.
> > Ray,
> >
> >
> > "Magnus Persson" <magnus.persson@timelox.com> wrote in message
> > news:3bf396a4$1@news.installshield.com...
> > > When you right-click in the string table and select 'Create & Set' in
> the
> > > popup menu, you can enter a string that contains <CR>/<LF> by pressing
> > > SHIFT+ENTER. But then you click on OK the resulting string contains
> > invalid
> > > characters. However, you can manually change these characters to \n to
> > make
> > > the string work. Otherwise the string will be cut at the first
occurance
> > of
> > > the invalid characters.
> > >
> > > /Magnus
> > >
> > >
> >
> >
>
>

NewsArchive
11-20-2001, 01:00 AM
i did, and i still have the problem...
Any other ideas ?

"Gomathi Y Rajesh(InstallShield)" <installshield.pro7.betafeedback> wrote in
message news:3bf93bfe$1@news.installshield.com...
> Hi Ingolf,
>
> This was bug in 7.0 which is fixed in 7.01
> You can download 7.01 from Download center in www.installshield.com
> Select InstallShield Developer product with version 7.0x.
>
>
http://www.installshield.com/downloads/mp.asp?prod=wind&pver=wind701e&lan=en
> glish&xmlUse=y
>
> Hope this helps,
> Gomathi
>
>
> "Ingolf" <DONT_SPAMingolf@musling.dk> wrote in message
> news:3bf8c27e@news.installshield.com...
> > When i use the DELete key, in a dialog-behaviour event, it will delete
all
> > lines below the one i am editing.
> >
> > Is this a bug ?
> >
> >
>
>

NewsArchive
11-20-2001, 01:00 AM
Thank you Nicholas! (easy enough! :-))

Peter

"Nicholas Mooney" <nicholas_mooney@nospamhotmail.com> wrote in message
news:3bfa9d56$1@news.installshield.com...
> No, simply set the value to [System] and then add the folder name off of
> that:
>
> [System]drivers (the "\" should be implicit)
>
> Nick
>
> "Peter Osucha" <peter.osucha@eti-energytechnologies.com> wrote in message
> news:3bfa99fe@news.installshield.com...
> > Hello,
> >
> > I have to install some files into the system32\drivers directory for a
> Win2K
> > installation. When I look at the component in the IS IDE, the top entry
> of
> > the component's properties allows me to set the target folder. 'System'
> is
> > an option but 'system\drivers' is not an option. How can I install to
> this
> > folder? Do I have to create a new folder for this destination by
clicking
> > on the 'Destination' property line and adding a new folder?
> >
> > Sincerely,
> > Peter
> >
> >
>
>

NewsArchive
11-21-2001, 01:00 AM
WinXP / 2000 any sp

Insert a few valid lines in a button event.

Set the curser in the CONDITION field in any event. Press your DELete key..
this will delete all event-lines below the one you are editing ... nice!

This does not happen if you use the backspace key... dont you guys have a
DELete key ? ;)

"Ingolf" <DONT_SPAMingolf@musling.dk> wrote in message
news:3bfa0e8e@news.installshield.com...
> i did, and i still have the problem...
> Any other ideas ?
>
> "Gomathi Y Rajesh(InstallShield)" <installshield.pro7.betafeedback> wrote
in
> message news:3bf93bfe$1@news.installshield.com...
> > Hi Ingolf,
> >
> > This was bug in 7.0 which is fixed in 7.01
> > You can download 7.01 from Download center in www.installshield.com
> > Select InstallShield Developer product with version 7.0x.
> >
> >
>
http://www.installshield.com/downloads/mp.asp?prod=wind&pver=wind701e&lan=en
> > glish&xmlUse=y
> >
> > Hope this helps,
> > Gomathi
> >
> >
> > "Ingolf" <DONT_SPAMingolf@musling.dk> wrote in message
> > news:3bf8c27e@news.installshield.com...
> > > When i use the DELete key, in a dialog-behaviour event, it will delete
> all
> > > lines below the one i am editing.
> > >
> > > Is this a bug ?
> > >
> > >
> >
> >
>
>

NewsArchive
11-30-2001, 01:00 AM
Thanks! That was the tip I needed. Found the reference under Binary in
DirectEditor, removed it, and compiled without errors.

"Marwan Tabet" <No-Reply@installshield.com> wrote in message
news:3c066bff$1@news.installshield.com...
> Ken,
> Did you try doing a search on "Tester.exe" in the DirectEditor?
>
> "Ken Ross" <kross@horizon-boss.com> wrote in message
> news:3c065171@news.installshield.com...
> > I've simply deleted a file that was part of my installation (deleted
from
> > the physical folder AND from the Files list) and now when I try to do a
> > build I get:
> >
> > ** Error: -1024: File C:\Install\vb\Tester.exe not found. Cannot stream
> the
> > file into the Binary table
> >
> > I've looked everywhere I can think of in the installation "program" to
try
> > and find any lingering reference to the program but no luck. I've looked
> > through all the Advanced Views and I've also followed one person's
> > suggestion of trying the "Project->Reset InstallShield Custom Actions"
> > function.
> >
> > If anyone else has seen this or has any suggestions on where I might
find
> > this reference (I'm more than happy to load files into a hex editor if
> > necessary), please pass it along.
> >
> > Thanks much!
> >
> > Ken
> >
> >
> >
>
>

ashkan2005
09-17-2006, 05:52 AM
hi
i have a problam in build release1
ISDEV : fatal error -6002: Error while attempting to run the custom build setup for objects.
please help me. tank you