Sv: firstruninstall

Bo Carleö bo at
Fri Jan 20 21:44:41 UTC 2023

Hi Daniel

Here is my path to it:
Users > mail > Appdaata > Local > Omnis Software

A bit odd with the mail folder here but you should be able
to find it under the User folder.

Best regards

Bo Carleo
Corbisoft AB            

Tappvagen 34                  139 35  Varmdo      Sweden
Tel  +46 8 722 88 00 

På 20 januari 2023 kl. 18:50:10, Daniel Sananes (daniel.s at skrev:

Hi Mike  
I reinstalled Studio 10.22, build 31896, into program files.  
No FirstRunInstall-folder exists.  
There are 11 folders in my dev-installation.  

-----Ursprungligt meddelande-----  
Från: omnisdev-en <omnisdev-en-bounces at> För Mike Matthews - Omnis via omnisdev-en  
Skickat: den 20 januari 2023 18:01  
Till: OmnisDev List - English <omnisdev-en at>  
Kopia: Mike Matthews - Omnis <omnis at>  
Ämne: Re: firstruninstall  

Hello Daniel,  

I think it is only recent versions of Studio for Windows that has this feature. Certainly I have noticed when I instal Studio, there is a prompt with the current build, v10.22 (31840). I don’t recall it being there in earlier installers. But that doesn’t mean the feature didn’t work.  

If you have a FirstRunInstall folder in the Omnis root, it will copy the contents, update missing items, into the folder inside Application Support (OSX) or AppData/Local (Windows).  

In the Runtime Client version, there are 17 folders and a file.  

In the Dev version, I have 18 folder and 1 file.  

If you added a FirstRuntimeInstall folder to older versions, I think it worked as advertised, certainly for v10.  

Don’t put xComps into the FirstRunInstall folder for Widows, but fine for OSX, which means there are two places for xComps to live in OSX machines.  

There is a Studio folder inside the FirstRunInstall folder, which has local prefs, omnis.cfg (your prefs & serial no), and some SQL session prefs (VCS, etc), and some others.  

So add the folder and see what happens.  

Mike Matthews  

Lineal Software Solutions  
Commercial House, The Strand<x-apple-data-detectors://1/1> Barnstaple, Devon, EX31 1EU<x-apple-data-detectors://1/1>  

omnis at<mailto:mike.matthews at><><>  

On 20 Jan 2023, at 16:47, Daniel Sananes <daniel.s at<mailto:daniel.s at>> wrote:  

Caution: This is a message which has originated from outside the organisation. Ensure the sender is trusted and the content is safe before opening links or attachments.  

Hi Paul  

Now i get even more confused.  
Is there supposed to be a folder called FirstRunInstall?  
When user launches my app? What is an app? I only know omnis.exe and myprogram.lbs.  
Launching the app (?) copies the content of FirstRunInstall to users Local App Data folder?  
I do not have a FirstRunInstall folder.  
Maybe the runtime installation is different.  

Best regards  

-----Ursprungligt meddelande-----  
Från: omnisdev-en <omnisdev-en-bounces at<mailto:omnisdev-en-bounces at>> För Paul Mulroney via omnisdev-en  
Skickat: den 20 januari 2023 05:50  
Till: Omnis-dev list <omnisdev-en at<mailto:omnisdev-en at>>  
Kopia: Paul Mulroney <pmulroney at<mailto:pmulroney at>>  
Ämne: Re: firstruninstall  

Hi Daniel,  

This split structure is because the program files folder is supposed to be read-only. Since Omnis always writes to library files, it separates the files that need to have write access and places them in the user's profile in the "Local App Data" folder. If you open windows explorer and in the address bar type "%localappdata%" (without the quotes), it will jump to that location. Inside there will be an Omnis folder, and inside that is your particular application instance. What this means is that when a user launches your app, the contents of the FirstRunInstall folder is copied to their Local App Data folder. This means that there can be (potentially) multiple copies of your Omnis library floating around the computer. You will need to have some kind of version control in place to make sure that users don't start your app with an older version of the library.  

if you don't want to do that, you can move all the files in the firstruninstall folder up one level. One catch is that the files must be writable. You can move the entire Omnis installation to somewhere else outside the Program Files folder, or you can get the properties for the folder and mark all files with read/write access. This option is not recommended by Microsoft - they want you to use option 1 above instead.  

"Application data is stored a minimum of two times on the disk where Omnis installed." This means that when you install Omnis, there's a copy of the writable files in the FirstRunInstall folder, and when a user starts Omnis for the first time, it's copied into their Local App Data folder. If there are multiple users on the machine, then there will be a copy of this for each user that has launched Omnis.  

There should be a tech note about this on the Omnis website, something about User Access Control.,1,eQWyPXBFKduHPR0kRfKqbMi1cd2oRbnJZ5G2U4uizpQhDAWrSVkwucL2nfY4qjYXiPmjpFb2Zckszwf4vW-C1DCeRuFvCC4WTLPF64SuxFO-Y81BR6Yv9LtpnQ,,&typo=1,1,sKie-cVRZ7Ne80NnxAV7vhcxI_tCH1MWOgfhoe9j9ugw8nqEAhA6k3val4piGmO-Ik7kZAeHryzFawaXYwkJSEEBYpDCY2qYZsfOzN71DMEAuOdMfjcg-NLAbg,,&typo=1  

Once you get the hang of it, it's not so bad.  


On 20 Jan 2023, at 12:15 pm, Daniel Sananes <daniel.s at> wrote:  

Hi all  

I find the installation of Studio (10.22) very confusing.  
Hoping for an explanation that rests my dizzy head. Or rather, my stupid head.  

In the omnis.exe directory-structure, sys(215), there are 11 subdirectories.  
(clientserver, external, htmlcontrols, iconsets, idehelp, jscomp, jsidehelp, license, logcomp, uninstall and xcomp).  
I have installed this at C:\OmnisStudio\Studio1022 instead of in \Programfiles.  

In the firstruninstall directory-structure, sys(115), there are 18 subdirectories.  
(adhoc, chromiumembedded, clientserver, convert, help, html, icons, iconsets, jsworker, local, logs, omnispdf, ports, python, secure, startup, studio, welcome).  

Catalogues clientserver and iconsets exists in both places.  

I place omnis-libraries and sqlite-databases in C:\OmnisStudio\MyPrograms.  

Am I supposed to place my libraries in the sys(115) structure?  

Alex Clay has written about 'Omnis installation locations' at,1,_Vbs5TCJ7RCEIpM3B7vTXdCMOdTWmCb2SQTsHldBHYQsJPs6yBD7Crj1ML41oXluKH3lXFsysN2Lha4xwECdPADaZgtX3orZ_pvKoRIMi2fiecJzCAE,&typo=1  
The 'Single Location Alternative' states that:  
"To bypass the split installation, install the contents of firstruninstall one level higher, into the program directory. On macOS, this means into /Applications/[your app name].app/Contents/MacOS.  
Install and run this app from a location that does not restrict read/write access, such as ${HOME}/Applications on macOS or %USERPROFILE%\Programs on Windows."  

How do I install the contents of firstruninstall so I don't have to bother with sys(115)-structure?  

And what does this mean?  
"Application data is stored a minimum of two times on the disk where Omnis installed. A master copy of this data is located in the Program Directory under firstruninstall. A copy is also placed in the location listed above for each user on the computer who runs the application."  

Best regards  
0736 704070  

A bicycle can't stand alone; it's just two tired.  
Paul W. Mulroney We Don't Do Simple Pty Ltd  
pmulroney at Trading as Logical Developments,1,IKiuTYCWY1axHha71FP7CsJ87EycOFby2BOsp24nYKktHjPf4UZ8o_oOBopI7G5U0ZVwPgafaJGb31SOftWsKbQ1NJFlHRZPPWyW2scziNEa7Xy6g4w,&typo=1 ACN 161 009 374  
Ph: +61 8 9458 3889 86 Coolgardie Street  

Manage your list subscriptions at,1,Qx9FHHH-JNxjyrtbgZFf08tp7CAIFZgPc6rwT39WYTzf3whlLQakwIjyJyqfoP8sSlbTTG_sIqnSTyoeQIzf6aLTzmkCq5sfKpzESOLXGQ,,&typo=1 Start a new message -> mailto:omnisdev-en at  
VARNING: Det här e-postmeddelandet kommer från en extern avsändare. KLICKA INTE på länkar eller bilagor om du inte känner igen avsändaren och vet att innehållet är säkert.  
Manage your list subscriptions at,1,Rz6kN0HjR1NQTOkV1i-cm9jc6ZsZNU-ZllZmTM6WOj4kJIFcBwfsLAkyScpaKqzawC8L7aj7u16eQWMC4P2HwDaqBafHGCFsI-62_2urGVBapvnDMg,,&typo=1  
Start a new message -> mailto:omnisdev-en at  

Manage your list subscriptions at Start a new message -> mailto:omnisdev-en at  
VARNING: Det här e-postmeddelandet kommer från en extern avsändare. KLICKA INTE på länkar eller bilagor om du inte känner igen avsändaren och vet att innehållet är säkert.  
Manage your list subscriptions at
Start a new message -> mailto:omnisdev-en at  

More information about the omnisdev-en mailing list