hi,

Am Dienstag, 7. Oktober 2014, 17:58:15 schrieb Thomas Friedrichsmeier:
> - Start from the command line using rkward.exe --debug-level 4. This should
> print a bit more info.

that helped. it turned out the installer set completely wrong paths, namely to 
a non-existent drive K:

we had already found that for the .lnk file to rkward.exe, but the debug 
messages showed us that rkward.ini also looked for R on drive K:

> - Does any window show up, at all? Is that literally the whole error
> message?

yes, it was the whole message. i started R in cmd.exe then, this is what was 
returned:

<snip>
c:\RKWard>RKWard.exe.lnk
Debug: path of the process "dbus-daemon" seems to be outside of the 
installPath: "C:/Program Files/RKWard/KDE/bin" "C:/RKWard/KDE/"
Debug: path of the process "klauncher" seems to be outside of the 
installPath:"
C:/Program Files/RKWard/KDE/bin" "C:/RKWard/KDE/"
Debug: path of the process "kded4" seems to be outside of the installPath: 
"C:/Program Files/RKWard/KDE/bin" "C:/RKWard/KDE/"
</snip>

and by the way, i now see why windows users tend to send screenshots instead 
of text like above: microsoft successfully managed to make copy&paste from 
that console like impossible, "select all" was the only thing that worked and 
we had to strip the whole history. adding to that, magically translating 
folder names seems like a terrible "feature"; "C:/Program Files/" is shown as 
"C:/Programme/" in german, but using that path in cmd.exe caused really 
strange errors.

so in essence, the problem was wrong paths. the installer did not use the 
installation path selected at the beginning of the process.


viele grüße :: m.eik

-- 
  dipl. psych. meik michalke
  institut f"ur experimentelle psychologie
  abt. f"ur diagnostik und differentielle psychologie
  heinrich-heine-universit"at d-40204 d"usseldorf

Attachment: signature.asc
Description: This is a digitally signed message part.

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
RKWard-devel mailing list
RKWard-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rkward-devel

Reply via email to