Family Historian User Group

Mike

I have in fact set it to E:\ for the projects folder. I have other mapped folders on my Mac HDD for other Windows apps to access. It seems as though it is FH that is reporting the location \\VBOXSVR\Family_Historian_Projects as that is what is set in the Project Window. I have now set it to E:\ BUT FH still reports the location as \\VBOXSVR\Family_Historian_Projects in your plugin. Most odd.

@Mervyn ~ Crossover is almost certainly not running the ICACLS command, nor the WHOAMI /GROUPS command at all.
So nothing gets into the log file except the ECHO %UserDomain%\\%UserName% command.
Unless those ICACLS and WHOAMI commands can be installed in Crossover that is the way it is.
Eventually, the script I am developing will try this command prompt method and if it fails will revert to the current method of saving & deleting a file to the folder and suffer the change to the Date modified.

@Colin ~ Have you tried closing and re-opening FH which might reset things?

tatewise wrote: ↑

18 May 2020 13:20

@Colin ~ Have you tried closing and re-opening FH which might reset things?

Spot on @Mike that has fixed it now reports as E:\

@Colin ~ Excellent! Is that something we need to add as advice in:- how_to:family_historian_v6_on_crossover_wine|> Family Historian V6 & Ancestral Sources V5 on Crossover, PlayOnLinux/Mac & Wine

Does Saturday's Plugin Version 0.7 now work without today's Version 0.8 fix for the network link?

@Mike

No such luck unfortunately this is the result with 0.7
Whereas v0.8 still works fine.

Colin/Mike,

Could this be significant:

"Shared folders physically reside on the host and are then shared with the guest, which uses a special file system driver in the Guest Additions to talk to the host. For Windows guests, shared folders are implemented as a pseudo-network redirector. For Linux and Oracle Solaris guests, the Guest Additions provide a virtual file system."

Source: VirtualBox User Manual Section 4.3

I'm sure the way shared Folders/Drives were presented changed some time ago, possibly when VirtualBox version 6.0.0 was introduced. Now it's up to 6.1.8

If I remember correctly, setting up shared drives in a Windows VM used to result in the automatic allocation of Drive letters starting with the next in the alpha sequence, but from 6.0.0 (I believe) things changed to allocation using the more normal networking convention of working backwards form Z: for attached Drives and displaying the 'network' address with the allocated Windows Drive Letter in brackets. In Windows programs running in a Windows VM you can select Drives by their Letter Code, but if you examine the actual address what you see is the full network path. 'File Manager' Images attached showing how shared Drives (Folders) are presented in Linux and Windows.

Mervyn

@Colin ~ Thank you ~ I'll stick with the Version 0.8 script.

@Mervyn ~ It seems that drive configuration is not relevant to this permissions scenario.

Just for my edification, what is the issue faced with updating the date?

Ron, see the latter postings in Backup and Restore Plug-In (17642) that discuss Date modified.