About gridman

gridman · ‎Nov 08, 2018

I have read all the other posts on connecting to Oracle in InstallShield. Also, I have created the Oracle Instant Client and ODBC prerequisite according to the Help topic, "Downloading the Oracle Basic Instant Client and the Oracle ODBC Instant Client and Creating an .msi Package and InstallShield Prerequisite for Both ". After the prerequisite is installed and the Oracle connection dialog displays, the servers are not enumerated. When I try to connect, it says it can't find the driver and "...may need to set the location of ORACLE_HOME." I have tried that, but have not been able to point it to the right place. Has anyone had success with connecting to Oracle in InstallShield lately?

gridman · ‎Oct 20, 2015

Yes, I have verified that. I installed SQL Server 2014 Express with Tools SP1 (x64) and found that the registry matched the conditions for SQL Server 2014 Express RTM (x64). And also, the entry is in the 64-bit part of the registry.

gridman · ‎Oct 19, 2015

Actually, the two packages I added that are SQL Server really are x64 and x86 files like they say they are. I think my problem is with the conditions. Even though I copied them from similar prerequisites (SQL Server 2014 Express), they are not getting triggered. When I generate a debuglog, it shows that no packages are selected for installation. So, something is wrong with the conditions. The installation does not even get to the point where it stages the files. I think if I had the wrong version, it would at least stage the files, then run it and give an error. But, I can't get anything to run. Thanks for the reply. Rod

gridman · ‎Oct 17, 2015

I have the Premier version and I'm using a Suite to install prerequistes for SQL Server 2014 Express with Tools SP1. And I am downloading the files from my client's website because that's the way he wants it. For .NET 3.5 SP1 and .NET 4.0, I imported the prerequistes. Those are working fine. But there are no prerequisites for the Tools version of SQL Server 2014 Express. So, I added the files as an Exe package. My problem is with the detection condition. I created the sames conditions for the Detection and Eligibility as I found with the SQL Server 2014 Express RTM prerequisite. However, when I run the installation on Win 7 x64, the package is never triggered for install. I don't have a condition on the corresponding Feature, so that is not what is causing the problem. The screenshot is attached. Does anyone have any ideas? These Suite conditions can be tricky.

gridman · ‎Jan 28, 2013

Thanks, that's what I figured. I will just use a checkbox with only the checkbox part and then place a regular label right beside it. Rod

gridman · ‎Jan 27, 2013

I know how to set the state of a checkbox programmatically in InstallScript. Does anyone know how I can set the label text of a checkbox programmatically? Thanks. Rod

gridman · ‎Mar 02, 2012

I am trying to create an Exit Condition for SQL Server 2008 Express in a Suite project. I have IS 2012 Premier. Here is the info: Registry Key: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS\MSSQLServer\CurrentVersion Value Name: CurrentVersion 64-Bit Key: False Comparision: LessThan Compare To: 10.0 Basically, if SQL Server 2008 Express is not installed, I don't want the installation to continue. I've tried lots of combinations (LessThanEqual, Greater, GreaterThan) but can't get this to work. I've also tried the RegistryExists condition, but I didn't have success with that either. Has anyone done this condition before?

gridman · ‎Feb 24, 2012

Thanks for the reply, Holger_G. Yes, I have created a catalog file. That didn't make any difference. I have done some reading on device driver signing, and it appears more complex that I initially thought. I will check out the link you posted.

gridman · ‎Feb 21, 2012

I have some more information. The device driver I am installing is minispy, which is a Microsoft sample that is included with the Windows Driver Kit. My client is using this as part of his installation. I went to the minispy site and there is a section on how to sign this driver. I was able to successfully sign it with my code signing certificate. Now when I install the signed driver through my installation, I still get the message saying the driver isn't signed. I know that message is not correct, because signtool.exe verified that it was signed. Very strange. There must be some option I am not setting. I'll do more investigation.

gridman · ‎Feb 20, 2012

I have a Basic MSI project with around 10 files. Among these files is a device driver. I have the .exe, .sys, and .inf files for the driver. In my project, I have setup the installation of the device driver in the Advance Settings for the component containing the driver files. I have also selected to sign the driver files in the release (with my code signing certificate). Yet, when I run the installation, it says the driver is unsigned and asks if I still want to install it. Is there a way to suppress this message? I wanted InstallShield to sign it, so I don't understand why it is saying this.

gridman · ‎Dec 16, 2011

I am creating a Launch Condition to make sure an installation is running on Win 7 SP1 64-bit. I got the Win 7 64-Bit part working. But, I can't figure out how to determine SP1. If you look at the Operating System Property Values topic in the Help, it says the ServicePackLevel is not applicable. I also tried using SYSINFO.WINNT.nServicePack, but that doesn't seem to be working either. Just wondered if anyone else had done this before.

gridman · ‎Oct 12, 2011

Thanks. I'm glad it will be fixed.

gridman · ‎Oct 11, 2011

I am using IS 2012 Premier and a Basic MSI project. I have noticed that when I create some registry entry keys for a component, and at the end of the tree of keys add a DWORD value, the first time I add it, it turns into a string. Meaning that, if I run the installation and look in the registry, it will show a REG_SZ value and not a REG_DWORD value. If I then go back to the component, delete the DWORD value (which is really a string), then add a DWORD value again and give it a value, on the next install it will really be a DWORD value in the registry. I can reproduce this consistently. It's a bit of an oddity. Anyone else experience this?

gridman · ‎Sep 16, 2011

OK. The part I was missing was because the custom actions were in the UI sequence only. So, what you say makes sense. I am putting the custom actions in both sequences and also changing from using SETUP.EXEs to MSIs in the packages. Thanks.

gridman · ‎Sep 15, 2011

John, I was using the following command line with Setup.exe in the Suite package installation: /s /v/qn I was not aware that using the quiet option would cause those custom actions to not run. Can you explain that to me so I know in the future?

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:11 PM

Connect to Oracle in InstallScript MSI

Re: Having Trouble with Suite Detection Condition

Re: Having Trouble with Suite Detection Condition

Having Trouble with Suite Detection Condition

Re: Set Checkbox label text programmatically?

Set Checkbox label text programmatically?

Problem creating Exit Condition for Suite Project

Re: First Time Device Driver Install Question

Re: First Time Device Driver Install Question

First Time Device Driver Install Question

Need to determine Windows 7 SP1 64-Bit

Re: DWORD Registry Entry turns to String

DWORD Registry Entry turns to String

Re: Suite Project on a 64-Bit Xeon Processor

Re: Suite Project on a 64-Bit Xeon Processor

Connect to Oracle in InstallScript MSI

Re: Having Trouble with Suite Detection Condition

Re: Having Trouble with Suite Detection Condition

Having Trouble with Suite Detection Condition

Re: Set Checkbox label text programmatically?

Set Checkbox label text programmatically?

Problem creating Exit Condition for Suite Project

Re: First Time Device Driver Install Question

Re: First Time Device Driver Install Question

First Time Device Driver Install Question