The problem has to do with the host containing the folder.
Some network attached storage device (NAS), like the DROBO
for example, run internally on Linux and their SAMBA network
shell does not respect nor correctly implement the standard
windows file attributes (R,S,H,A,I).
So relative paths will NOT help if the desktop.ini file
is not read in the first place !!!
Because the host device, RAID, NAS or drive does not
correctly report the "System" or "Read only" bit
which windows expects to trigger the processing
of the desktop.ini file, the file is never read
and its contents do not matter.
Have found no solution to this problem yet.