Post by Stefan on Aug 3, 2020 10:15:38 GMT -5
Hi Guys,
Sorry - I couldn't decide where else to ask this...
What processing do you do at SPFLite startup in relation to each of the files listed - for example - in the FLIST RECENT category?
I noticed that if there is one or more file entries in an FLIST category, which are on network attached devices, and those devices are 'asleep', SPFLite startup is very SLOW.
I have 2 NAS boxes. One is backup to the other, so most of the time, it is ON but the drives are sleeping (not spinning). When I notice the SPFLite startup lethargy, I usually find a file entry to the backup NAS in a FLIST. If I remove it, startup operates normally.
I share the SPFLITE folder across multiple machines (only the CFG file is unique to each machine). So all home systems use the same FILELIST and suffer the same impact when any one of them has caused a 'rogue' entry to appear in a list. In my case it's just one sleeping NAS, but folks with files on remote networks may encounter a similar experience.
I appreciate that if you just issue a file system request to check their presence (or whatever), Windows won't refuse it because the device is available, but you'll incur a delay while the drives spin up.
I guess you could sub-task the request and start a timer to help the code move on if the request for a particular entry takes an extraordinary time to complete, but there's probably a lot going on asynchronously at startup already. Hence I ask - why do you look inside the FLIST categories rather than just load them asis?
I just thought I'd mention it. It still trips me up wondering what's going on when SPFLite doesn't start promptly. Note to self: Write a routine to clear out 'rogue' entries at user logon.