Jimmy:
Heya. Installing a video driver is a tricky thing, as it seems to
create a "virtual display adapter" (in a manner similar to how making
a VPN connection creates a "virtual network adapter"). If you open
the Device Manager after installing, there will be a new video
adapter in the hardware list, after the mirage driver is installed.
Anyhow...that flicker is due to the addition of the video adapter,
is my understanding. Perhaps if you were connected to the RDP
session with the /console switch, you'd remain connected...
Otherwise, yes, you can tell EchoVNC to not install the video
hook driver when it installs. Then there's no flicker. :)
-Scott
On Jul 22, 2008, at 2:21 AM, Jimmy E. Kongskov - DATAJEK wrote:
>
> Hello!
>
> Most of the time when installing EchoVNC I do it through RDP. When
> doing
> that the mirage/mirror driver is always giving me problems as it
> tends to
> "stop" the installation.
>
> When I get the "flicker" notification popup and press OK the
> installation
> hangs and I have to kill the process.
>
> However, EchoVNC IS being installed in the background so what
> happens? Is
> it the flickering part that stops my RDP session regarding the EchoVNC
> installation (everything else is working)?
>
> Is there a way to fix this or can I perhaps choose not to install the
> mirage/mirror driver?
>
> Jimmy
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
