How are you guys dealing with applications that are using network shares that does not exist for the install-account, but will exist for the user thats going to run the application.

When I try to install an application that has an Icon in the startmenu that points to for example I:\, I get an InstallShield error: "1327 Invalid Drive: I:\"

How are you doing with applications like this?

I have tried delete the Icon in the project, and maked a VBS to create the icon the way i posted here, but it dosn't always work as I want.

I am running InstallShield 10.50 Professional.


0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


hello jonasm,

i use wps 5.51 and i dont have that problem. We have a lot of client server apps. When i make a msi package you have to be sure that when compile the msi the drive letter is attached. Wps does not complain at all when you distribute it to the client, even when you dont have that specifically drive letter. The icon would not have the *.ico but when you connect to the drive the icon should get his normal icon.

greetings sejacru
Answered 07/26/2005 by: sejacru
Second Degree Blue Belt

Please log in to comment
some people (not me) drop a shortcut as a file. Then, of course, having it as an entry point won't work [:-]
Answered 07/26/2005 by: revizor
Third Degree Blue Belt

Please log in to comment
You should use two custom actions.

One at the start of he install to subst the I: drive to %temp%. (Subst is a command line which will redirect a drive letter to another connection)

A second to unsubst it...oh yeah and maybe a rollback custom action.

Works well.
Answered 07/26/2005 by: DavidLock
Senior Yellow Belt

Please log in to comment