There is no list of “Hidden Changes”, I’m not sure why you would think we would intentionally create such changes? If there is a known (to us) change in behavior we would certainly make it known to you. What usually happens is we work very hard not to change the behavior in any way that would not be backwards compatible.
I just had a look at the code for this, both FB6 and FB7 call the windows API function GetSystemDirectory, the only difference being that FB6 calls GetSystemDirectoryA (ansi version) and FB7 calls GetSystemDirectoryW (unicode version).
I don’t have an explanation as as to why windows is returning different values… however since FinalBuilder is a 32 bit app, I’m not sure it matters since windows will redirect any 32bit program accessing system32 to SysWow64 - http://en.wikipedia.org/wiki/WoW64
Sorry for my previous words. They were not relevant, especially in computer science. More over we are using finalbuilder for many year and it we process all of our products without problem.
But, there is still a problem with the way finalbuilder process %sysdir%
Here is a way to reproduce it :
create an empty project with 2 actions 1- Run DOS Command / Batch File [ c:\windows\system32\notepad.exe ] (with no wait) 2- Copy File(s) [ %SYSDIR%\notepad.exe -> d:\temp ]
the first action will run cmd.exe in 64bits mode. This will switch something in FB7 and the second action will now access c:\windows\system32 rather than c:\windows\syswow64 In FB6 it works without problem.