Why does the Installshield setup claim that it can find a JavaCOMM 2.0 installation when I do have one?
The setup looks for the file called JAVAHOME/lib/javax.comm.properties where JAVAHOME is defined by the registry key HKEY_LOCAL_MACHINE/JavaSoft/Java Development Kit/1.4/JavaHome. While JAVAHOME/lib works, a better location is ‘JAVAHOME/jre/lib’ and yours may be there. This is really a bug in the Installshield setup as we also recommend putting javax.comm.properties in JAVAHOME/jre/lib. The upshot is that you can ignore that warning if you’re certain you have a JAVACOMM 2.0 installation. After I install tinyos, I can’t write in the directories as a non-Administrator user. In a cygwin shell, cd to the directory that your tinyos-1.x tree is in (usually /opt), do this: $ chmod -R a+rw tinyos-1.x The above will make the tinyos-1.x directory and all the files in it accessible for reading and writing for all users. You can adapt the permissions to your security policy. See ‘info chmod’ for more information on the chmod command.
Related Questions
- During installation of the device portion of the software I get error message stating that setup file is invalid and the cab file is not copied to the desktop. Can I fix it?
- If necessary, are TSI representatives willing to travel to our site to assist in the installation and setup of the product? Does TSI offer training in the use of PROFILER?
- Do agents need to setup a new account for Post installation?
