Liveware Publishing Support Forum

Hello,__ some weeks ago we changed install directory for rrw.ini from c:windows to the directory where R&R executable and dlls reside. This helped us to fix a problem on terminal servers with different windows directory for every terminal user. It seems to work on w2003 servers and also on our test on WinXP.____Now we have 1 client with XP SP2 where DLL interface does not work when rrw.ini is in R&R executable directory: message says "Cannot execute Viewer exe Error code 2" .__Works ok when rrw.ini is in c:windows\__Any ideas?____Taavi.____

What is PROGDIR32 set to in the INI?____Is is that setting that is used to locate the runtime executable.____Kathleen__R&R Support

>What is PROGDIR32 set to in the INI? __>Is is that setting that is used to locate the runtime __>executable. __Yes. On our software startup it will verify that we have this line in rrw.ini to ensure R&R runtime can find DLL-s. If there is no PROGDIR32 line, our software will add it. (It^s the only reason why we deal with rrw.ini).____Lately we got a problem with terminalservers where windows creates it^s own windows settings dir for every user. And seems that moving rrw.ini to rrwrun directory worked on some installations. So we decided we do^nt need it in windows dir any more.____Now we have got some clients where rrw.ini needs to be in c:windows dir. Have not found yet why...____Taavi.__