Okay, today I attempted to replicate my previous issue by doing two different image attachments. First, I used Ancestral Sources to add a census entry and attached a newly downloaded image (saved to my ".../Media/census/" folder the same as before) . Upon saving the census entry, I reviewed the new media path in the properties box, the Records window media tab, and the External File Links listing. In each, the media path was relative as usual, i.e. "Media\census\FILENAME.jpg". I then ran Validate and got no errors at all.
I also manually added a recently downloaded image to a new citation; same process, but saved in a different subfolder, i.e. \Media\military\FILENAME.jpg. After adding the image via the "Show Media...Add Media for Citation" dialogue, I checked the same three areas noted above and the path was accurate. Once again, on running Validate, I got no errors.
About 30 minutes later, I reopened FH to add another citation image, same process as before. This time, I got a Validate error. All areas indicate the attached image is appropriately attached and all paths are accurate and relative to "Media\...". Tools...External File Links does NOT show any issue. Yet, the Validate function reports an error:
Code: Select all
Family Historian Validation Report - Monday 11 May 2020
===============================================================
Media Record Id=3540 (draft-card-wwI-Paul-E-Turnell): bad link to Media record found. This has not been fixed.
- (001).png (189.54 KiB) Viewed 10390 times
- (002).png (18.98 KiB) Viewed 10390 times
- (003).png (60.32 KiB) Viewed 10390 times
The link to the individual record/event citation also appears to be okay:
This has caused me to rethink my FH sessions over the past few days, which reminded me of something. There is a known bug in VirtualBox (
https://www.virtualbox.org/ticket/15478) where the executable "VBoxTray.exe" causes the guest VM to use excessive CPU cycles, eventually causing the entire VM to slow to the point of termination. This bug has been around for over two years now and is still not resolved in all configuration, mine included. VBoxTray.exe manages shared
features, such as drag and drop, file copy and Clipboard sharing between Host and Guest. My solution to the bug has been to simply disable VBoxTray.exe when the system starts becoming sluggish. This only disables the features mentioned, which are not required for VM operation, and the guest system returns to normal operation instantly.
I do not think that disabling this is causing the path problem. Indeed, it is NOT disabled when the issue does appear above. But, I'm starting to think that the bug itself may be causing a problem. That is purely a guess, and based only on the fact that I cannot duplicate this problem during today's session.