Creating a symlink at the default Rainmeter 'Skins' location that points to the NAS share works and prevents the behavior. I've tested this with a portable Rainmeter install.Is there anything i can do it about it, without writing script for rainmeter.ini to change the path on NAS detection?
1. Delete the 'Skins' directory at the default Rainmeter location.
2. Open a new CMD (or Terminal/Powershell) prompt with admin privileges and use the following template (don't use as-is):
Code:
mklink /d "<path to default Rainmeter skins directory>" "<path to NAS share skins directory>"
Code:
mklink /d "C:\Apps\Rainmeter\Skins" "\\mynas\Rainmeter\Skins"
To Rainmeter it thinks the skins are in its default location now but really they're pointing to the NAS.
If you launch Rainmeter without the NAS powered it will error with 'There are no available skins at: <path>' but since you created the symlink at the default location no config change will occur. If you power on the NAS and restart Rainmeter it will detect the skins again.
You can delete the symlink any time (if you no longer want to use this technique) by simply deleting the symlink file that was created.
Statistics: Posted by Crest — Today, 2:13 am