> >> I had a few of my users ask why the Windows OpenVPN connection was in a
> >> Command Prompt window and not just a Systray Icon with a status window.
> I think it would be cleanest if such a gui could be created as a
> standalone application that just calls the openvpn binary. What I'm not
>
Quoting Denis Vlasenko :
I had a few of my users ask why the Windows OpenVPN connection was in a
Command Prompt window and not just a Systray Icon with a status window.
It can be run as a service. It is documented.
I think implementing a systray icon to controll OpenVPN would be a great
fea
Quoting Denis Vlasenko :
> > I had a few of my users ask why the Windows OpenVPN connection was in a
> > Command Prompt window and not just a Systray Icon with a status window.
> It can be run as a service. It is documented.
I guess this makes sense for the server/gateway side, but I don't think
On Saturday 12 June 2004 08:16, Brandon Knitter wrote:
> I had a few of my users ask why the Windows OpenVPN connection was in a
> Command Prompt window and not just a Systray Icon with a status window.
>
> You know, that's a great question. I was going to look into the code and
> see what it woul
I had a few of my users ask why the Windows OpenVPN connection was in a Command
Prompt window and not just a Systray Icon with a status window.
You know, that's a great question. I was going to look into the code and see
what it would take, but of course I do that I figured I'd ask if anyone look
