Skip to main content
K.Daube
Community Expert
Community Expert
January 31, 2023
Answered

What's wrong with FM-16 update > 2 and FrameScript?

  • January 31, 2023
  • 2 replies
  • 227 views

Dear all,

I  am struggling to run FrameScript on FM-16, update 3 and higher. While everything works fine in the initially released version up to update 2, in higher updates FrameScript does not accept options any more. There are no such problems in FM ≤ 15 and FM-17.

→ Any ideas what's going on here?

Environment

Operating system: 10.0.19044 64 bit

FrameScript: H:\Adobe\FM-addons\Fscript_7\fsl7_160_64.dll (file version 7.0.1.25; Modification date 2020-08-30; file size 2'662'400)

Running FM 16.0.0.754 (initial release) Console log shows:

FrameScript--Version 7.0R1p25 ElmSoft
FrameScript--Registered to Klaus Daube
FrameScript--Starting on Windows 10 Pro-FrameMaker Version 16.0
FrameScript--Start Folder H:\Adobe\FM-addons\Fscript_7\
FrameScript--Using Client Name--fsl
FrameScript--Initial Script-H:\Adobe\FM-addons\itl-i-frame\_InstallScriptsInFolder.fsl
- - - - - - - - - - -
* FrameScript encoding mode: FrameRoman
* FrameMaker 2020 (16.0.0.754) (UKEnglish)
? Edit > Preferences > Global: Alerts:
'File contains unresolved cross-references' is disabled
'File contains Unavailable Fonts' is disabled
'Dictionary Provide Mismatch' is disabled
* _InstallScriptsInFolder.fsl 5.6:
Scripts found and installed: 74 (1s)
- - - - - - - - - - -
→ _[i]_FM-Commands_16.0.0.754_UKE_FDK.fm can be produced
Checking for updates → FM U5! → don't use this function.

Running FM 16.0.1.817 (upd 1)

→ Same situation as in 16.0.0.754

Running FM 16.0.2.916 (upd 2)

→ Same situation as in 16.0.0.754

Running FM 16.0.3.979 (upd 3)

→ menu FrameScript exists, but Option is not functional
→ console log is empty (although messages concerning disabled alerts are expected)
• Explicit run of ...\itl-i-frame\_InstallScriptsInFolder.fsl fails with various erros, starting with this:
FrameScript: Missing Parm (Object Type) on command (New) At Line(448) in File(H:\Adobe\FM-addons\itl-i-frame\_InstallScriptsInFolder.fsl)
C:\Users\klaus\AppData\Roaming\ElmSoft\Esl\v7\Fm160\fscript.ini:
Delete setting of InitScript
→ At start of FM console log still empty; FrameScript > Options still not functional
• Remove API entry fsl in maker.ini:
→ console log is empty (although messages concerning disabled alerts are expected)

Running FM 16.0.4.1062 (upd 4)

→ Same situation as in 16.0.3.979 (upd 3)

Running FM 16.0.5.1096 (upd 5)

→ Same situation as in 16.0.3.979 (upd 3) and 16.0.4.1062 (upd 4)

This topic has been closed for replies.
Correct answer K.Daube

Solution communicted by Frank Elmore

Adobe changed their FDK for FM 16 when they released 16.3. It made the old clients incompatible. We downloaded the new FDK for 16.3 and recompiled our code.

We now have two Fm 16 clients. I am enclosing (inside zip files) both of these clients. Even though the zip files have different names, the actual client file name is still fsl7_160_64.dll, so unzip them to different folders, so they won't overwrite each other. The fsl7_160_64_12.zip is for the FM versions .1 and .2. The fsl7_160_64_3.zip is for FM 16.3

2 replies

K.Daube
Community Expert
K.DaubeCommunity ExpertAuthorCorrect answer
Community Expert
February 1, 2023

Solution communicted by Frank Elmore

Adobe changed their FDK for FM 16 when they released 16.3. It made the old clients incompatible. We downloaded the new FDK for 16.3 and recompiled our code.

We now have two Fm 16 clients. I am enclosing (inside zip files) both of these clients. Even though the zip files have different names, the actual client file name is still fsl7_160_64.dll, so unzip them to different folders, so they won't overwrite each other. The fsl7_160_64_12.zip is for the FM versions .1 and .2. The fsl7_160_64_3.zip is for FM 16.3

Community Expert
January 31, 2023

Hm. I could install itl 's i-frame with every update of FrameMaker 16. And also my own scripts ran well.