Further issues with the Divvun 2.2 installer & Windows 7 + possible solution (Bugzilla Bug 1310)

[albbas]

This issue was created automatically with bugzilla2github

Bugzilla Bug 1310

Date: 2012-03-28T15:34:41+02:00 From: Sjur Nørstebø Moshagen <> To: Børre Gaup <> CC: borre.gaup, trond.trosterud

Last updated: 2018-05-16T14:39:59+02:00

[albbas]

Comment 5950

Date: 2012-03-28 15:34:41 +0200 From: Sjur Nørstebø Moshagen <>

The IT team at the University of Tromsø has tried to deploy the Divvun tools, and ran into problems. Here is a brief recap of what they found, and their suggestion for a solution.

First step:

"Hei, nå har jeg lagd en MSI-pakke på denne. Og får denne feilen, dvs at får «Not installed» på Proofing. Når jeg installerer manuelt på klient så får jeg «Installed», men når jeg kjører ut pakken til klienten (med LANDesk) så feiler dette."

Short translation: They made an MSI package to deploy Divvun, but got the error "Not installed". Installing manually goes ok (result: "Installed"), but not using LANDesk. See attachment for a screenshot of the result.

[albbas]

Comment 5951

Date: 2012-03-28 15:35:29 +0200 From: Sjur Nørstebø Moshagen <>

Created attachment 124 Screen shot of LANDesk installation result

Attached file: image001.jpg (image/jpeg, 63842 bytes) Description: Screen shot of LANDesk installation result

[albbas]

Comment 5952

Date: 2012-03-28 15:39:13 +0200 From: Sjur Nørstebø Moshagen <>

The next comment from the IT gang:

"Hei, vi har isolert problemet til å være register-relatert. Det som skjer pr nå er at når pakken kjøres ut som «system» så blir det installert i «system»-kontekst. Og da får ikke andre brukere tilgang til de registernøklene."

Translation: we have isolated the problem to be registry-related. Divvun is installed in the SYSTEM context, which prohibits other local users access to the registry keys.

[albbas]

Comment 5953

Date: 2012-03-28 15:53:02 +0200 From: Sjur Nørstebø Moshagen <>

Next comment:

"Dette er helt klart et registerproblem. Vi har vært flere stk som har jobbet med dette nå. Problemet er at Divvun-programmet insisterer på å bruke HKCU (Hkey_Current_User) og opprette registernøkler der. Dvs at brukeren selv må initiere installasjonen av de registernøklene for at de skal kunne installeres riktig. Og det må hver bruker gjøre som skal bruke Divvun, om de deler pc. Hadde registernøklene kunne blitt plassert under HKLM (HKey_Local_Machine) så ville det gjelde for alle brukere, og da vil hele prosessen kunne automatiseres.

Så slik som det er nå så skjer følgende når programmet kjøres ut via LANDesk (utkjøringsverktøyet vårt): · Stavekontroll-filene blir plassert riktig på c:-disken på klient · Registernøklene blir IKKE installert siden det er lokal systemkonto som installerer programmet · Bruker må selv legge inn registernøkler fra et VBS-script for at samisk stavekontroll skal kunne brukes

Dette blir tungvint og hele tanken med automatisering av installasjon faller da bort.

Forslag til løsning: · Få leverandør til å legge registernøklene under HKEY_Local_Machine slik at ALLE brukere får tilgang uten å måtte initiere noe selv · Evt vente til ny versjon av Divvun, og imens installere Divvun 2.2 manuelt til de som trenger det. Men da må det, hvis det er flere brukere på samme pc, installeres av hver enkelt bruker."

Translation:

This is definitely a registry problem. Several of us have looked at the issue now. The problem is that the Divvun installer insists on using HKCU (Hkey_Current_User) and create register keys there. This requires the actual user to initiate the installation themself to make the registry keys available and correctly installed. This also means that each local user of the machine will have to install Divvun, otherwise any previous installation won't be accessible.

If the registry keys had been placed uner HKLM (HKey_Local_Machine) they would have been valid for all users, and the whole installation process could have been automated.

As it is now, the following happens when Divvun is deployed using LANDesk: · Proofing tool files are correctly installed on the C: disk on the client computer · The registry keys are NOT installed because the installation is done using local system account · The user must add the registry keys themself using a VBS script to make the Sámi proofing tools usable

Suggested solution: · Make the subcontractor store the registry keys under HKEY_Local_Machine such that ALL users will have access to the tools without having to initiate anything themself · Possibly wait for a new version of Divvun, and only manually install Divvun 2.2 for users needing it. This requires all users of the same computer to install Divvun.

[albbas]

Comment 5954

Date: 2012-03-28 17:25:11 +0200 From: Sjur Nørstebø Moshagen <>

The following update:

"Prøvde en hel annen innfallsvinkel og da virket installasjonen. Dvs at registernøkler ble satt korrekt og både stavekontroll og ordbok virker på samisk. Og ved test på klient så så det ut til å virke helt ok for meg, men bør testes av noen med erfaring med StarDict og Divvun.

Programmet blir kjørt ut som 3 del-programmer. En for Divvun, en for StarDict og en som setter korrekte registernøkler."

Translation:

Tried another solution, and got the installation to work. That is, both register keys were added correctly, and spell checker and dictionary [StarDict] worked in Sámi. And upon further testing the client, everything looked fine, but someone more experienced with the software should test it further.

The installation is done in three steps: 1) install Divvun; 2) install StarDict; and 3) enter correct registry keys.

[albbas]

Comment 5955

Date: 2012-03-28 17:28:41 +0200 From: Sjur Nørstebø Moshagen <>

Final comment:

"Her er registernøklene som jeg må legge inn for at Divvun skal virke. Om de på en eller annen må kunne vært under HKey_Local_Machine så hadde det vært det beste"

Translation:

Here are the registry keys I used to get Divvun to work. If they could be stored under HKey_Local_Machine that would have been the best.

---

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Override]

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Override\se-FI] "DLL"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiNorthern-NO.dll" "LEX"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiNorthern.lex"

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Override\se-NO] "DLL"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiNorthern-NO.dll" "LEX"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiNorthern.lex"

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Override\se-SE] "DLL"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiNorthern-NO.dll" "LEX"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiNorthern.lex"

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Override\sma-NO] "DLL"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiSouthern-SE.dll" "LEX"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiSouthern.lex"

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Override\sma-SE] "DLL"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiSouthern-SE.dll" "LEX"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiSouthern.lex"

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Override\smj-NO] "DLL"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiLule-SE.dll" "LEX"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiLule.lex"

[HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Override\smj-SE] "DLL"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiLule-SE.dll" "LEX"="C:\Program Files (x86)\Microsoft Office\Office14\\Proof\mssp3samiLule.lex"

[albbas]

Comment 5960

Date: 2012-03-29 11:17:35 +0200 From: Sjur Nørstebø Moshagen <>

I now tested changing the domain/context from HKCU (Current User) to HKLM (Local Machine) for the Office2010 registry settings - and installation on my setup didn't work any more:

No signs of proofing tools in the Office language menus, but the uninstaller is there, and the software is there. It is just not properly registered, and thus not available.

I changed back to Current User, and then installation worked again - the registry was correct for my installation, the tools showed up in the language menu in Office, and the speller worked as expected (e.g. on the input 'nuvviDspeller').

What I did was to change lines like the following:

WriteRegStr HKCU "$o2010_base\${locale_SamiNortNO}" "DLL" "$OvcProofDir\${SP_ENG_NORT}"
WriteRegStr HKCU "$o2010_base\${locale_SamiNortNO}" "LEX" "$OvcProofDir\${SP_DIC_NORT}"

to the following:

WriteRegStr HKLM "$o2010_base\${locale_SamiNortNO}" "DLL" "$OvcProofDir\${SP_ENG_NORT}"
WriteRegStr HKLM "$o2010_base\${locale_SamiNortNO}" "LEX" "$OvcProofDir\${SP_DIC_NORT}"

(all ${xyz} strings are variables.

The registry keys in Comment #5 are exactly the ones I get when I install on my computer, using the present (locally working) installer. So - nothing new in the registry settings as such.

The question remains: what can we do (if anything) to make the registry keys work for the LOCAL MACHINE domain? This seems to be the key to make unsuperwised or centrally managed installations work as they should.

[albbas]

Comment 7298

Date: 2012-11-05 10:56:23 +0100 From: Børre Gaup <>

(In reply to comment #4)

The following update:

"Prøvde en hel annen innfallsvinkel og da virket installasjonen. Dvs at registernøkler ble satt korrekt og både stavekontroll og ordbok virker på samisk. Og ved test på klient så så det ut til å virke helt ok for meg, men bør testes av noen med erfaring med StarDict og Divvun.

Programmet blir kjørt ut som 3 del-programmer. En for Divvun, en for StarDict og en som setter korrekte registernøkler."

Translation:

Tried another solution, and got the installation to work. That is, both register keys were added correctly, and spell checker and dictionary [StarDict] worked in Sámi. And upon further testing the client, everything looked fine, but someone more experienced with the software should test it further.

The installation is done in three steps: 1) install Divvun; 2) install StarDict; and 3) enter correct registry keys.

Do you have more information on the solution, more a step by step instruction? We have at least two more users having troubles with Divvun in terminal server environments, and a howto would be useful for those users, too.

[albbas]

Comment 7384

Date: 2012-11-13 15:04:53 +0100 From: Børre Gaup <>

64 bits windows 7, 2007 funker dårlig, ikke alle maskiner 2010, funker bra CAPA installer sentralt manuell installering fungerer windows7, office 2013 funker perfekt windows8, office 2013 funker ikke

[albbas]

Comment 8792

Date: 2013-12-17 10:53:46 +0100 From: Sjur Nørstebø Moshagen <>

This bug is solved by the Divvun 3.0 installer. Closed.