|
|
Post by George on Feb 24, 2021 10:53:14 GMT -5
Hi, Another bug fix release, we've accumulated a few lately, time to roll them out. Check the Change Log for details. George |
|
|
|
Post by Stefan on Feb 25, 2021 14:00:07 GMT -5
Hi George,
Possibly just me, but when installing the setup package of v21053 I get a pop-up error saying Cannot create S:\Documents directory!
My SPFLITE 'Data' Directory' is on S:\DOCUMENTS\SPFLITE\.... But the directory obviously already exists - so no surprise it couldn't be created.
Installation process hiccup?
|
|
|
|
Post by George on Feb 26, 2021 11:57:18 GMT -5
Stefan: This release had the install change which looks up your existing HomeData location (if already installed) and uses it. The setting for files located there is set to "Overwrite if newer".
Did the install continue, or did it abort at that point?
Anyone else have install problems?
George
|
|
|
|
Post by Stefan on Feb 26, 2021 13:25:49 GMT -5
Did the install continue or stop before finishing? I think it stopped prematurely.
In C:\Program Files (x386)\SPFLITE2\ I do have version 2.3.21053 SPFLite2.EXE. So that bit worked, but it may well be done before the Homedata folder.
In the forum discussion about sample macro location, you mentioned that you'll put a SAMPLES/MACROS folder structure in the same install folder. I do not have such a folders in C:\Program Files (x386)\SPFLITE2\ I also do not have the sample macros in my 'data' folder, S:\Documents\SPFLite\MACROS, so they were NOT copied into there either.
That would suggest that the install stopped prematurely.
|
|
|
|
Post by George on Feb 26, 2021 15:55:10 GMT -5
The install des not yet create a \SAMPLES\ folder, coming someday when I have time.
I'm going to fire a question off to the Installer guys, everything looks fine in the settings. And I had no problems running the Installer on my system, but then, I use all the standard locations.
George
|
|
|
|
Post by George on Feb 27, 2021 11:05:38 GMT -5
Stefan: Got an initial reply from the Installer support. First thought was that it was a real permission problem since your S: drive is, I'm sure, a network drive.
They indicated the installer runs at the root level. Is there a possibility it may be something like that?
George
|
|
|
|
Post by Stefan on Mar 22, 2021 6:27:19 GMT -5
George,
Apologies, I only just found your question above from 27th Feb.
Yes, S: is mapped to a folder structure on my Synology NAS.
Permission-wise I don't see a problem.
From a Windows perspective, there's nothing 'special' about the S: drive or its contents. Everyone/thing has FULL access.
From a Synology perspective, I'm just a user (as defined to the NAS) with FULL access. In any case, the NAS security profiles for the shared resource give FULL access to all users.
Your question is almost a month old and I cannot recall exactly what happened subsequently.
Suffice to say I did install v2.3.21053 eventually, so must have got around it somehow and not told you.
If you haven't already, please forget all about it.
|
|
