VNC project idea request

[Felts, Roger]

-----Original Message-----
From: Jay R Ashworth
Sent: Monday, November 22, 1999 2:04 PM

>On 11/20/99 12:43:26 AM, "Roger Felts"  said:

>>> Because the apps and the UI aren't part of the OS, which 
>>> isn't true on Windows.   That 
>>> is, you won't have to fight the OS, as well, _just_ the app design.

>>Which guarantees that the update doesn't abort half way ... how?

>Roughly, because they operating system itself is almost certainly not
making use of 
>the pieces which need to be replaced, a condition which is difficult if not

>impossible to guarantee in the Windows environment.

Which addresses things like the connection going down which can abort such
an upgrade ... how?

Or perhaps you simply have an alternative definition for "guarantee" you'd
like to share?

And perhaps you can also point out specifically which parts of VNC that
Windows itself uses, which would make this upgrade abort half way through.

>You want me to admit, it's clear, that this isn't _really_ Windows' fault,
and I'm 
>afraid I'm _just_ not going to do it.  ;-0

No, I'd just like you to admit that your advice to the original poster to
use an OS other than Windows to facilitate an automated upgrade to VNC is
based more on a desire to bash Redmond that on any objective fact.

You seem to be under the impression that such an update already has
problems, and that these are the fault of Windows.

If you prefer that little fantasy, at least have the decency to label it so.

Hint:  such an automated upgrade is possible under Windows with existing
free tools, and is as reliable as such can be made on any platform.  It is
more elegant on NT with an administrative login, but can be accomplished
regardless.

---------------------------------------------------------------------
The VNC mailing list - see http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------