Sorry, wrong sender again :-((Admin of pskmail@xxxxxxxxxxxxx: please delete mail from kl@xxxxxxxxxx if it is not done automatically
-------- Original-Nachricht --------Betreff: Re: [pskmail] Aw: Re: Windows client v2.1.0-e: rigctl does not work
Datum: Mon, 16 Sep 2013 11:26:59 +0200 Von: Klaus Lohmann <kl@xxxxxxxxxx> An: pskmail@xxxxxxxxxxxxx I have C:\Program Files (x86)\hamlib-win32-18.104.22.168\bin in the path of my home computer (W7 64). Hardware- and Software PTT work with ICOM IC-7000.On the boat I use Software PTT, W7 32, IC-7000. That works also. Will look at the path variable next weekend.
Klaus DL4OAH Am 16.09.2013 11:11, schrieb Rein Couperus:
The software in V2 implements the 'rigctl' command. Normally, when rigctl works from a terminal (CMD window in windows) it should work. I am in the process to set up a test with window7 again (sigh...) to see what could be the problem. Does win8 have different ownership/permissions problems than Win7? Rein PA0R ___Original Message_________________________________________ From: Ian Wade G3NRW <g3nrw-radio@xxxxxxxxxxxx> Date: Tue, 10 Sep 2013 Time: 19:42:54 >Win 8/64 >TS-590S >jpskmail client v2.1.0-e > >When attempting to set up the rig for rigctl, this message pops up: >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >Problem >Message: Cannot run program "rigctl": Create_process error=2, The >system cannot find the file specified. >From class: class java.io.IOException >Case: java.io.IOException: Create_process error=2, The >system cannot find the file specified. >Hamlib get frequency failed: rigctl -m 231 -s 115200 -r COM4 f >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >After clicking on "OK", the popup disappears, but then immediately >re-appears. > >The only way out of this loop is to kill the app with Windows Task >Manager. > Sorry, I get the exact same results with v2.1.0-f. Stand-alone rigctl, stand-alone fldigi and many other digital apps all work fine. Is there anybody here who has successfully made the Windows client v2 work under Windows 8/64? I don't know where to go from here. -- 73 Ian, G3NRW