|
|
Post by Stefan on Oct 19, 2021 4:56:18 GMT -5
Please treat this as a FYI rather than a bug.
I'll say up front... this is a circumventable issue that probably only affects me.
I think it started shortly before v2.5 came along, but can't really remember. I probably should have mentioned it before, but as I say - maybe it's just me.
My HOMEDATA and HOMEFOLDER folders are split across different drives, with HOMEDATA on a shared NAS drive, and HOMEFOLDER on the 'local' C:\ drive. (Reason: I wanted to share SPFLITE 'data' across several machines, so placed both folders on the NAS.
One of my laptops travels and uses Windows' "Always available offline", for both folders, but the periodic SYNC messed up the CFG file's integrity.
So each machine now uses a shared HOMEDATA folder and a 'local' HOMEFOLDER for the CFG file)Anyway, currently every SPFLITE installation, on any of my machines, fails when it tries to access the shared HOMEDATA folder (S:\SPFLITE\). It reports " Cannot create S:\SPFLITE directory!"
There's no need to create it, as it is already there. Is there something different in the more recent installer process that fails to recognize a mapped drive's (S:\) resources? Or perhaps there is an access permissions mismatch of some sort. My userid has full access to the NAS resource, so I wonder if the installation is being performed under a different userid these days and NAS security blocks it. Anyway, as I say, it is easily circumvented. I use OPTIONS CONFIG to point the HOMEDATA folder to the same folder as HOMEFOLDER (on the local drive), install SPFLITE, then point it back at the NAS instance. |
|
|
|
Post by George on Oct 19, 2021 8:40:25 GMT -5
Stefan: This error is from the actual Installer program, right? I can't see anything odd in the setup, it fetches the HOMEDATA from the registry and the files are flagged 'replace if newer'.
I don't have a NAS drive anymore to est with, mine died and I replaced it with a simple USB external, which looks "local". My laptop is now a Chromebook, so all my sharing is via Google Drive rather than NAS.
I'll contact CreateInstall and pose the question to them.
George
|
|
|
|
Post by Stefan on Oct 19, 2021 11:06:11 GMT -5
Yes George,
Installation sequence is...
Welcome to the SPFLite 2.5.21258 Installation screen -> I click <NEXT> Licence agreement screen -> I tick the 'I agree...' box and click <NEXT>
Then the Installing files screen is immediately overlaid by the error message box, e.g.
In my case, drive S:\ has been mapped to \\WoodsideNAS\Q-Shared\ and SPFLITE\ is a folder in Q-Shared
Installation only needs to populate the HOMEDATA folder with a handful of sub-folders and possibly the sample macros (can't remember if I once put them there or if the install process does it). But the error says 'cannot CREATE the HOMEDATA folder', which suggests it didn't find it in the first place.
Once I've successfully installed a new version, it operates just fine, reading and writing to the shared HOMEDATA folder on the NAS.
BY THE WAY... I Love the addition of AUTOCASE.
|
|
|
|
Post by George on Oct 19, 2021 12:26:59 GMT -5
Stefan: I contacted CreateInstall, and their only answer is that it is most likely a UAC problem. Maybe the installer has to be explicitely run as Administrator? Or maybe some kind of access rule tweak?
No other suggestions from them.
George
|
|
|
|
Post by Stefan on Nov 8, 2021 3:14:54 GMT -5
Hmm... I did run the Installation process as "Administrator", but that made no diffeerence. I'm not really surprised, because the install .EXE usually pops up the "User Account Control" window anyway. So the mystery continues. I'll just carry on pointing the 'Data' Folder at a local drive before running the install and copying it to where I want it afterwards. Thanks for your efforts, but it's not worth you spending any more time on this one.
PS: Has my 'Problems and Bugs' post titled "Several observations on enhanced AUTO colorisation " escaped your attention?
|
|
|
|
Post by George on Nov 8, 2021 9:20:50 GMT -5
Stefan: Yes, I missed your colorisation post. Not sure why I don't see it as a new post. I'll have a look.
George
|
|
