I have noticed various target fields of DOPUS shortcuts pointing to my 32bit progam files folder rather than the 64bit one. see the following:
all take the form of:
"C:\Program Files (x86)\GPSoftware\Directory Opus\dopusrt.exe" /cmd Copy TO "coll://Video" FILE
where "Video" is the variable collection name
The correct Target directory should be C:\Program Files\
These are apparently SEND TO links
What does the Properties dialog show for one of the links?
What program are you using to show the shortcut paths? If it's a 32-bit program it could be it that isn't resolving them properly.
A) This is strange. If I open up EXPLORER thru the WINUTILITIES program and examine properties there, then I get one result.
If I open EXPLORER directly and then go to properties, I get another.
I guess it is probably a WINUTILITIES feature. 
see image below
So does this actually have anything to do with Opus at all? 
WINUTILITIES must be a 32-bit app which is opening a 32-bit copy of Explorer instead of the usual 64-bit Explorer you'd get via the Start Menu etc.
Why would the actual field data change ? If I change it thru the 32bit explorer it remains changed . Is it that the path data is not really what it says and using an environment variable and then once change to a direct path, it stays set ?
I understand this is not directly a DOPUS problem but maybe an indication of how DOPUS should write these fields to avoid confusion.
I don't think it's anything to do with Opus.
Open (normal, 64-bit) Explorer and right-click drag a folder out of C:\Program Files to create a shortcut to it on your desktop. Check the shortcut and it'll point to something below C:\Program Files.
Now open a 32-bit version of Explorer by typing this into the start menu:
C:\Windows\SysWOW64\explorer.exe /separateCheck the shortcut again. It will point to something below C:\Program Files (x86).
Opus not involved at any stage of that.
It's just part of how the 32-on-64 filesystem virtualisation works in Windows.