Jump to content

- - - - -

Client 5.6.5 Now Uses Registry

3 replies to this topic

#1 Ross Bevin

Ross Bevin

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 235 posts
  • Gender:Male
  • Location:Manzanillo, Colima, Mexico

Posted 11 February 2005 - 04:46 PM

It looks like Pro-IV is now moving away from .ini files to Windows Registry. Mike Monsef sent me the following information.

The PROIV Windows Client does not use the proiv.ini file to save or retain any values. The PROIV Windows Client now uses the Windows Registry to retain the values that were previously held in the proiv.ini file. The Client currently does not have a user interface to create or maintain many of the settings that were previously defined in the proiv.ini file. To modify or create these entries the Windows Registry Editor utility will be utilized.

Please contact you System Administrator prior to any modification of the Windows Registry.

Prior to modifying any Windows Registry entry it is STRONGLY recommended that the Windows Registry be backed up.

For information to back up, edit and restore the Windows Registry please use the following URL: http://support.micro...om/?kbid=322756

Close the PROIV Windows Client.
Back up the Windows Registry.
Run the RegEdit32.exe, normally found in the \Windows\System32 folder or \WinNT\System32 folder.
Locate the appropriate Windows Registry Folder, look for the section name used previously in the proiv.ini file:

HKEY_CURRENT_USER\Software\PROIV Technology, Inc\PROIV Windows Client\ActiveX Licensing

HKEY_CURRENT_USER\Software\PROIV Technology, Inc\PROIV Windows Client\DDE

HKEY_CURRENT_USER\Software\PROIV Technology, Inc\PROIV Windows Client\Default Connections

HKEY_CURRENT_USER\Software\PROIV Technology, Inc\PROIV Windows Client\Kernel

HKEY_CURRENT_USER\Software\PROIV Technology, Inc\PROIV Windows Client\Key Mapping

HKEY_CURRENT_USER\Software\PROIV Technology, Inc\PROIV Windows Client\Logging

HKEY_CURRENT_USER\Software\PROIV Technology, Inc\PROIV Windows Client\Print Margin

HKEY_CURRENT_USER\Software\PROIV Technology, Inc\PROIV Windows Client\Settings

Modification of existing Variables:

1. Select the appropriate section name folder to display the contents in the right pane.

2. Select the Variable name to be modified in the right pane.

3. Select Edit in the menu bar, select the ‘Modify’ option.

4. Enter the new value for the Variable and click OK

Adding new Variables:

1. Select the appropriate section name folder in the left pane.

2. Select Edit in the menu bar, select the ‘New’ option.

3. Select the ‘DWORD Value’ option, if the new Variable requires a numeric value or select the ‘Sting Value’ option, if the new Variable requires an alphanumeric string value.

5. Enter the Variable name in the newly created object.

6. Select the new Variable name.

7. Select Edit in the menu bar, select the ‘Modify’ option.

8. Enter the new value for the Variable and click OK

Exit the RegEdit32.exe utility
Verify the new values are detected by the Windows Client.

#2 hendo



  • Members
  • PipPip
  • 17 posts

Posted 11 February 2005 - 05:54 PM

Just tested and put ReportEditor to open WINWORD when sending reports out to screen and it works.

If anybody wants the registry details they are shown below
but only change your registry if you know exactly what you are doing as this may cause problems later
goto START then Run
Enter REGEDIT and
go to
HKEY_CURRENT_USER\Software\PROIV Technology, Inc\PROIV Windows Client\Settings
and add a new string value called ReportEditor
then edit that string with
c:\Program Files\Microsoft Office\Office10\Winword.exe
check for the correct directory of winword before entering details

#3 Mike Schoen

Mike Schoen


  • Members
  • PipPipPipPip
  • 198 posts
  • Gender:Male
  • Location:Guelph, Canada

Posted 11 February 2005 - 06:14 PM

We currently use multitple .ini files to connect to different instances ( production, training, test) on customer systems.
Does this mean that the latest windows client no longer supports saving settings for multple servers on one client?

This would be a major loss of functionality for us, both in-house and on-site. :D

I really need to start reading the screen, I thought that said .ini file :p

It's still a pain in the neck though, as we have some automated processing that uses gui client and and auto-generates .piv/ini pairs for logins. Dealing with the registry adds a new layer of security we have to deal with on installs now.

Edited by Mike Schoen, 11 February 2005 - 06:18 PM.

#4 Wim Soutendijk

Wim Soutendijk

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 214 posts
  • Gender:Male
  • Location:Netherlands

Posted 14 February 2005 - 12:21 PM

I think the client upgrade should have seen the existing .ini file, and update the registry accordingly.

Any comments on that?

Reply to this topic


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users