
During the last few months we have handled a wide variety of questions. The following is a list of commonly asked questions and their associated answers in order to help users to help themselves. Please carefully read through this document before sending us an email.
When I run the install program I get the following error...
Why is there no Mac version?
Why is there no Linux version?
Can I install ITP 2.0 Professional on more than one computer?
Why is my transmitter running at 11mbps?
Which antenae can be used with my camera?
What is the difference between FTP and PTP/IP?
Does ITP support PTP/IP?
What are the differences between PocketITP and ITP?
What do I set the folder parameter in my transmitter to?
What is the root folder?
Why can't I download files?
I would like to see x feature...
How do I become a beta tester?
This indicates that the .NET Framework is not present on your computer. The framework is a set
of libraries that are required by ITP and its installers to work correctly. You can easilly rectify
this problem by
downloading and installing
the framework directly from Microsoft. Once it is installed, ITP should install without further
incidents. 
The application failed to initialize properly (0xc0000135). Click on OK to terminate the application.
 
We currently have a Macintosh on order, and as soon as it is delivered we plan to begin producing a version
of our software for this platform. In the meantime, if you are interested in beta testing this product
please give us a shout.
We do not currently see a significant demand for such a product at this stage. If you are interested
please give us a shout so that we can get a feel for the interest level in such a version - if enough people
are interested we will certainly look into it.
Yes, the licence you purchased for ITP 2.0 Professional allows you to install it on up to three
computers as long as it is only used on one of them at any given time.
Both the Nikon WT-2/2A and Canon WFT-E1/1A will revert to 802.11b speeds when used in their ad-hoc
mode. If you would like to make use of the full 54mbps performance of these transmitters, they
must be used with an infrastructure network. See our setup guides
for more information on these two modes. Note that if you need to operate in the field, you
might want to consider the various portable access points
that are on the market.
Both the Nikon and Canon transmitters currently use a RP-SMA antenna connector. This connector
is also used on a number of other WiFi devices so aftermarket antenae can be purchased from a
several different sources.
FTP (File Transfer Protocol) and PTP/IP (Picture Transfer Protocol over Internet Protocol) are
two different methods that wireless transmitters use to send images. When the camera opperates
in FTP mode, it is the one that initiates the connection and manages the transfer
of images. As such, it allows you to control which images are transmitted via the camera's
interface. It also has the advantage of being able to transmit images over the Internet if
desired.
When opperating in PTP/IP mode, the camera will behave as if it were teathered to the computer.
This allows you to remotely control the camera from your computer as well as retrieve images, however
since the computer manages the connection there is less control within the camera. With currently
available software, for instance, there is no way to instruct the camera to only send JPEG images
when shooting in a JPEG+RAW mode.
The current version of ITP only makes use of the FTP protocol for recieving images. With that said,
we are currently in the process of finalizing a powerful new PTP/IP implementation that will appear
in future packages. Expect this to appear in PocketITP first (allowing remote control of your cameras
from your PocketPC) and into powerful new products in the near future. If interested, please
register with us and you will be notified
as soon as these products become available!
The only difference between these two versions is the user interface! Functionally, both platforms
use the same core server routines and have the same functionality. PocketITP has a few features
suited to it's platform such as the ability to shut down the screen and failover to a second root
folder, however users will not be able to tell the difference. Additionally, configuration files
are compatible between the two versions, so if you have a setup you like for one it is simply a
matter of copying the appropriate files over (just watch the directories you select, as the file
systems of the PocketPC and Win32 OSes are quite different). Also note that a newer version of
ITP is currently available and some features may not have trickled down to PocketITP yet.
In most situations you should leave this blank - the location of the files is controlled by the server's
root and home folder settings. You can use the camera's setting to select a location contained within
the home folder, however ITP will not allow you to navigate outside of that file system. For security
reasons, you cannot use this to specify an absolute path on the host computer - use the root or home
setting to do this.
The root folder is the location where all of the home directories will be placed relative to. As
such, it is effectively the location on your system where you would like to place the images that
are uploaded to the server. By default, the files for each user will be placed in a subdirectory
named for it's owner.
Since this product was designed primarily for receiving and processing files, the download functionality
was not implemented. Asside from saving development time and system resources, the fact that downloading
is not enabled also adds an additional level of security to the system. If an unauthorized user was to
gain access, he would be unable to retrieve files from the system - so your confidential information is
safe.
I am very interested in hearing what features people would like to see, what they like/dislike about the
current versions. If you have any suggestions or comments about my software, please feel free to
contact me!
If you are interested in becoming a beta tester, contact us with
information about yourself, what you use the software for and what hardware you have available to you. If you
are an organization you can also request beta versions to allow staff to evaluate upcoming versions and be
prepared to train employees when later versions are announced. Note that beta testers will have to agree to
a confidentiality agreement.