This is a workaround at best but as EchoVNC server does not work correctly with Windows 98 or older and there are no plans to add this ability I found one workaround. The server does work locally with win98, it's just the EchoServer connection portion that messes up. So I just leave the system in question without an echo server and connect to it from another machine that has a later operating system (actually NT4 so I'm not sure how that's later[yeah I get that NT->2000->XP]). Anyway I create a session with the NT4 machine and then create a session from it to the Win98 box. A little goofy, but then I'm generally checking the NT4 machine first anyway. I guess I could also hook up the server ports on the Win98 box to work with the router and do things that way, but this solution is workable. I've logged on a couple times and it seems to work fine.
Now if the 15-20 minute lost session bug could be eliminated I would be real happy. "There probably isn't any meaning in life. Perhaps you can find something interesting to do while you are alive." - Orochimaru (Naruto) ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Echovnc-users mailing list Echovnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/echovnc-users
