First I had a blank window with the text “Internal Server Error”.
On reinstall I had the setup screen. I chose a small folder with just a handful of photos to scan manually, set the library location in a subfolder of my user, and clicked ok.
v1.0.0-beta.2 added several new timeouts that may help you if you have several attached external drives, or lots of network mounted volumes, or if any of your volumes are especially slow to spin up from sleep.
This will set your command and mountpoint timeouts to a minute, and volume metadata to be cached for 20 minutes.
Here are descriptions for these settings:
##############################################################################
#
# Settings for System.timeouts:
#
# +--------------------+
# | commandTimeoutMs |
# +--------------------+
#
# How long should PhotoStructure wait for a command that touches the
# filesystem (and doesn't do anything computationally expensive)? Note that
# external hard drives can take 10-15 seconds to spin up, so values less than
# that may result in timeouts.
#
# environment: "PS_COMMAND_TIMEOUT_MS"
#
commandTimeoutMs = 60000
# +--------------------+
# | mountpointsTtlMs |
# +--------------------+
#
# How frequently should PhotoStructure scan for new volumes (so PhotoStructure
# can detect when drives are inserted or ejected)? Shorter than 10-15 seconds
# may cause issues on Windows.
#
# environment: "PS_MOUNTPOINTS_TTL_MS"
#
mountpointsTtlMs = 60000
# +-----------------------+
# | volumeMetadataTtlMs |
# +-----------------------+
#
# How frequently should PhotoStructure reload volume metadata (like
# bytes-free, which is used in a health check?) Values less than a minute are
# probably not necessary.
#
# environment: "PS_VOLUME_METADATA_TTL_MS"
#
volumeMetadataTtlMs = 1200000
I tried the Alpha build of v1.0.0-alpha.7 like you said. It worked.
I was experiencing disk problems with an external drive (slow reads). This seems to be the cause (as reflected in the timeouts you added for drives with these problems).