Had a call from a client who copied his pc OI to a laptop running vista.

had a problem with the 2 dll registration messages for OIPI that appear when you first run to screen, with registration error.

Without having VISTA experience, I knew straight away it had something to do with access rights. We accently discivered that if you right click on oinsight.exe there is an option in there to say you trust this program and for it to run with admin priveleges. This fixed the problem, still retaining the users UACI assume

Barry,

I have seen this message on XP or 2003 when the logged on user does not have rights to modify the registry. When a report is first run on a new computer it attempts to autoregister vsprint7.ocx and vspdf.ocx. In Vista, as I understand it, applications are normally run with an enhanced security profile. Meaning that an application should not normally be modifying the registry. That should have been taken care of during an installation procedure. Now OI is sort of unique in that it does not require a Windows Install except for those darn ocxes. One possible workaround is to create a batch file that does the regsvr32 commands for the two ocxex. This has to be run with administrator privelages but OI should not have to be.

This is just my train of thought… I have not tried this out since I have not found the time to upgrade to Vista.

HTH,

John

It would be nice if RTI would have a new Client install made up for this specific purpose

Great idea!!!, I am sure there is other stuff that should go in it…oinsight.ini setup?

]] autoregister vsprint7.ocx and vspdf.ocx.

!insertmacro InstallLib REGDLL 1 REBOOT_PROTECTED C:\OI32\vsprint7.ocx $SYSDIR\vsprint7.ocx $SYSDIR[/color][/color][/size]         
               

Jim,

You are suggesting that someone would adopt NSIS, which would mean abandoning perfectly good technology from 1995 – like InstallShield. If we abandon old technology for new, simply because of better features and performance, what hope is there for …. Oh, I better stop right away.

Anon

I love NSIS, killer tool, fast, constantly updated, powerful, easy to use, and best of all free.

Just so no one gets me wrong – I was thinking of BOB, along with InstallShield. I agree with Jim about NSIS, we should all be using it.

We've changed to it too :)

The Sprezzatura Group

World leaders in all things RevSoft

Just to elaborate, our old installs for S/List were around 1.4M. The NSIS ones are about 350K.

We've also been able to create generic routines, so all we do is defined product name, registration details and some names to create a full installation package.

pre.code {

background-color: #E5E5E5;

border: 1px solid #000000;

width: 800px;

padding: 5px;

font-family: courier, verdana, arial, serif;

margin: 0px 10px auto;

}

; HM NIS Edit Wizard helper defines
!include "ZZEXPORT.INI"

!define PRODUCT_NAME "S/Form Source"
!define OUTPUT_FILE "SOURCE\SForm Source Setup.exe"
!define INSTALL_ROUTINE "INSTALL_SFORM"
!define INSTALL_ROUTINE_OBJ "$$INSTALL_SFORM"
!define LICENSE_PRODUCT "SFORM"
!define README_FILE "SForm ReadMe.txt"
!define HAS_EXAMPLE "1"
!define SAMPLE_VOLUME "SFormDemo"
!define INPUT_TYPE "SOURCE"
!define REGISTER_PRODUCT "0"

!include "..\standard\zzInstall - header.nsi"

Section "S/Form Programs" SEC01
  SectionIn RO
  call doInstall
  SetOutPath "$INSTDIR"
  SetOverwrite try
  File "SForm Readme.txt"
  SetOutPath "$INSTDIR\Icons"
  File "icons\*.*"
  SetOutPath "$INSTDIR\bmps"
  File "bmps\*.*"
  SetOutPath "$INSTDIR\zzide.res"
  File "zzide.res\*.*"
SectionEnd

Section "Example Reports & Data" EXAMPLE_SECTION
  SetOutPath "$INSTDIR\SFormDemo"
  SetOverwrite try
  File "Source\DemoFiles\*.*"
SectionEnd

!include "..\standard\zzInstall - functions.nsi"

The Sprezzatura Group

World leaders in all things RevSoft

View this thread on the Works forum...