Clarion 8 – NetTalk 11 to NetTalk 14 Configuration Issue

questions
1

Hi Everyone,
I am using Clarion 8.0.9759 and currently my IDE is configured with NetTalk 11.
I have recently downloaded and installed NetTalk 14 (Desktop version 14.36). The installer completed successfully and NetTalk 14 files are present in the Clarion 8 accessory folders.
However, I am facing the following issues:

When I open Tools → Template Registry or Global Extensions, Clarion still shows NetTalk Version 11.18.

When I open the NETTALK.TPL file directly from disk, it clearly shows NetTalk 14.

In the Template Registry window, all buttons such as Register / Unregister / Enable / Disable are disabled.

According to Clarion Help, these buttons are disabled in Multi-Developer mode, but Multi-Developer mode is NOT enabled in my Application Options (I have verified and attached screenshots).

I am running Clarion as Administrator.

I want to completely switch my Clarion IDE from NetTalk 11 to NetTalk 14, but I am unable to edit the Template Registry.

My Questions:

Why does Clarion still show NetTalk 11 in Template Registry even after installing NetTalk 14?

Why are the Register/Unregister buttons disabled when Multi-Developer mode is not enabled?

What are the exact steps to correctly configure NetTalk 14 in Clarion 8 and remove NetTalk 11 safely?

Any guidance or step-by-step instructions would be greatly appreciated.

Thanks in advance.

2

Because your registry is locked.

3

All you need to do is run the install. After the template registry is updated your app will automatically update.

4

I dont know what Multi-Developer mode is, but check Application Options to see what’s set there.

Also, make sure your Clarion is not in \Program Files\

5

How to unlock registry?

6

check this

image
image854×545 17.7 KB

7

image
image388×551 14.4 KB

Its already unchecked.

8

What folder is your clarion 8 installed into?

What OS permissions do you have for files in the \clarion\template\win folder?

9

This is the location where clarion8 installed.
C:\Program Files (x86)\SoftVelocity\Clarion8
This is the location where NetTalk.tpl and other files are present
C:\Program Files (x86)\SoftVelocity\Clarion8\accessory\template\win

10

did you saw this:

image
image779×291 12.7 KB

11

image
both are different location.

12

Both Program Files locations are “protected” folders by Windows.

So anything that attempts to write there gets virtualized by the operating system and most programs don’t play well when that happens.

You end up with data being read from the original copy instead of the (updated) virtualized copy much of the time.

I suggest you install Clarion to C:\Clarion8 and your life will be much easier!

FYI - newer copies of Clarion install off the root folder for this very reason.

13

If the app has a manifest with requestedExecutionLevel set to asInvoker, highestAvailable, or requireAdministrator, Windows treats it as UAC-aware ⇒ virtualization is off.

14

Hi guys
finally I’m able to update template registry.
I just change the property of TemplateRegistry.trf file and it worked.
Thanks all

15

That is true.

However, the best reason to install under something like C:\Clarion8 and avoid running Clarion elevated is that the normal write, compile, run cycle will launch your target EXE elevated too.

That means you can end up testing a different runtime environment than your users will have. Files and settings that land in per user locations (AppData, ProgramData, etc.) and registry keys (HKCU) can end up written under the elevated context, so later when you start the EXE normally, it can look like settings vanished or data moved.

Sure, you can choose to make your app always run elevated via a manifest, but that is not the default and it is not what most apps should do.

Also, if any non-Clarion program such as an editor is not UAC-aware and tries to write into Program Files, you are back in virtualization land, and now you have two copies of the same file in two different places. That is where the real confusion starts.

IMHO it’s just easier to move Clarion out of Program Files, run it non-elevated and spend your time chasing real bugs in code instead of tilting at windmills.

:slight_smile:

2 Likes
16

We can only offer advice here. People are free to take it or leave it. Unfortunately experience cannot be transferred, and some people have to learn things the hard way.

On the other hand, he’s using Clarion 8, so obviously likes the hard way :slight_smile: