About the only thing I can think of that vnc changes is the load on the machine and the network connection to it. This might affect speed of opening dialog boxes and other responses. Could your script be failing on that? To test, perhaps you could make something that kick's off the test after 5 sec, then minimize or close the viewer (that should remove the load).
(This might be especially so on older/slower machines) Arnt > -----Original Message----- > From: Bjvrn Persson [mailto:[EMAIL PROTECTED] > Sent: maandag 31 maart 2003 14:35 > To: [EMAIL PROTECTED] > Subject: Re: using vnc for remote testing > > > Forwarded reply from Diane Fahr: > > the test scripts are located on the test machine. the file > in question is > > on the test machine. the script tries to open the file, > but the message > > returns file not found. I am using vnc to start the > automation procedure > > and watch it run. I used vnc to open the file by hand and that was > > successful. > > so, I really dont understand how using vnc to kick off a > regression test > > could cause this to fail, but when i use desktop on call, > running the same > > regression it works. > > > > thanks, diane > > In that case my only idea is that there might be a difference > in search path > or access permissions. > > If you would give us more information on operating systems > and VNC versions, > the chance that someone else knows what to do might increase. > > Bjvrn Persson > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
