Change file associations in XP-CC4

[Ambient]

Hi Guys

 

This is my first post on here

 

I've come up against a brick wall with the issue of making sure that all .cip files are set to open up in Communicate in Print (software). At present, .cip files have to be opened using the File/Open method in the software, however, staff at the school would like to be able to double click any .cip file stored in a shared drive, and then have it open in the software automatically.

 

At present, this doesnt work, and when a .cip file is double clicked, nothing happens. Because most of the users are restricted with CC4, they dont even have the open to select the correct application (Communicate in Print) from the list.

 

Any ideas?

 

I can imagine it will be some sort of reg change, but i dont know where to start. I'm happy with the process of pushing out the reg file with CC4, but i just dont know what to put in the reg file itself.

 

Many thanks

[howartp]

Hi Ambient,

 

Windows Registry Editor Version 5.00

 

[HKEY_CLASSES_ROOT\.cip]

@="CommunicateInPrint"

 

[HKEY_CLASSES_ROOT\CommunicateInPrint\shell]

 

[HKEY_CLASSES_ROOT\CommunicateInPrint\shell\open]

 

[HKEY_CLASSES_ROOT\CommunicateInPrint\shell\open\command]

@="\"c:\\Communicate\\CommInPrint.exe\" \"%1\""

 

That should start you off.

 

The last line needs to point to the .exe of Communicate In Print, with double \\ where you would normally have single.

 

It says "a .cip file is a CommunicateInPrint file type. In order to open one, I will call c:\Communicate\CommInPrint.exe and tell it to open the .cip file"

 

You can rename CommunicateInPrint in all references if you want.

 

Peter

 

(Edit: watch out for the space in 'command' which the forum has entered)

[Michael]

You'd be right normally, but opening a Communicate InPrint file from Windows Explorer will open, but the document will appear blank. You have to open Communicate InPrint first, then open the file within the application for it to appear correctly.

 

This happens when running version: 2.8.3xx. The latest build is 2.8.625, but I don't know if this fixes the issue or not.

[Ambient]

Opening a .cip file in my situation does nothing when logged on as a normal user....it doesnt open a blank document as you say.

[Michael]

Opening a .cip file in my situation does nothing when logged on as a normal user....it doesnt open a blank document as you say.

 

But what I am saying is even if you managed to get files to open, it won't work correctly. The user still has to open Communicate InPrint first, then open up a file you were working on earlier (for example).

[Ambient]

Ah right ok, i see what you're saying.

 

Strange one. I've now logged a call with the software maker to see what they can do to help the situation.

 

Thanks for everyones help