Scott, et. al..:
RE: InstantVNC 2.x Build date Jan. 27, 2012
Suggestions and issues are listed below.
But first, I want to say "thanks" for the excellent work
on InstantVNC.
InstantVNC is an elegant idea. It clearly has much
potential. I think it, combined with Echogent's relay
server, will become one of my business' more valuable
customer support tools.
Thanks for your attention,
Bill
<<=============>>
William P. Price, Jr.
William Price Consultants
<<=============>>
Suggestions:
1. Install and uninstall:
a.) Please consider installing all files to
"%systemdrive%\%programfiles%\Echogent\InstantVNC" or a
similar folder.
b.) Please consider providing a customizable installer. A
customizable installer will allowed me, the support
provider, to include the machine name, passwords, relay
server URL, custom icons and other options in the original
installation system (the original "exe" file or similar.)
Very handy.
c.) Please provide a comprehensive uninstaller to remove
all files, all
registry entries, etc.
2. Windows service:
Please fix the windows service install and service
auto-start issues. Both are critical for after-hours
remote support.
3. Support-provider information disclosure:
Please eliminate disclosure of passwords, IP address and
the like.
InstantVNC now shows all this information when you hover
the mouse cursor over the InstantVNC system-tray icon.
4. Supported operating systems:
Please consider supporting InstantVNC operation in the
following: Server 2003 and 2008, XP Pro, and Win7 Pro. (32
and 64-bit for all but XP).
5. Documentation:
Please document installation, operation, purpose of
installed files, etc., for all supported operating
systems.
Issues:
1. Windows service installation fails about 90% of the
time:
To date, I have tried to install InstantVNC on about 40
Windows equipped computers. These computers run either XP
SP3 or the Win7 Pro, 64-bit, operating system (OS). All
OSs are fully patched and up to date.
The original windows service install fails about half the
time. The service auto-start feature fails almost all the
time. The most common service auto-start error is "cannot
find file."
Among other things, I tried moving all files
(InstantVNC.exe, miniwinVNC.exe, .dlls, etc.) to a single
"%programfiles%" folder, then editing the InstantVNC
service entry in the registry to reflect this move.
Sometimes this worked, most of the time it has not work.
2. Program component installation locations:
Sometimes, the installer puts files into a current user's
"temp" folder like "C:\Docs&Settings\CurrentUser\local
setting\temp" while putting other files in a
"C:\Docs&Settings\CurrentUser\InstantVNC" folder. Other
times installed files appear in other folders. Most
confusing for us old guys.
Installing files to a temp folder is an issue because temp
folders get emptied.
The "%programfiles%" folder is the standard folder for
program. Therefore, it seems reasonable to install all
InstantVNC files in a folder like
"%programfiles\Echogent\InstantVNC".
3. No uninstall system:
If the original installation fails or if there are
post-install problems, there is no way to insure that all
program components can be cleanly and completely
uninstalled.
Consequently, it is impossible to determine whether or
not, after re-installation, failures are due to bugs or
are due to leftover "bits" from earlier installs.
4. Documentation:
Without documentation I do not know how the program is
supposed to be installed. I do not understand what files
and folders the installation is supposed to produce. I do
not know how the software is supposed to work, etc.
Consequently, I am not sure what to report when I have a
problem. Is it a glitch that I should report or did I
install it improperly?
A concrete example: Once installed, should "options" be
accessed via the InstantVNC file or via the minwinVNC
file, or from both? Documentation would help.
5. Disclosure of passwords, relay server information and
similar:
Disclosing this information is a major issue for me. I
would prefer that none of this information be accessible.
Relay server identification and password disclosure are
especially troubling.
Thanks all - Bill
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
