From: "Nick Bane" <nick@cecomputing.co.uk>
Date: Fri, 15 Feb 2002 23:00:07 -0000
Debby: No criticism implied for antique device driver stuff. Linux USB
transfers working a treat of course.
No criticism taken. I just felt a very large caveat emptor was called
for.
I dug up the documentation for setting up the USB driver. It doesn't mean
much to me, but hopefully it will be of use to someone...
-Debby
======================================================================
USB Drivers
To communicate between a host machine and an Itsy you will require 2
drivers: a client driver which runs on Itsy and a host driver for your
particular host. Currently only Windows 98/2000 are supported.
======================================================================
Network Configuration
There are two network configurations that I have used: giving the Itsy a
valid IP address for my LAN and giving the Itsy a private LAN address
(e.g. 192.168.0.2). In both cases I have configured the host driver with a
private IP address because there is no need for any machine on the LAN to
talk to it. Using Microsoft Internet Connection Sharing capabilities you
can give the Itsy a private IP address and when you plug the Itsy into the
host Windows will set up routing for you automatically but you cannot
initiate a connection from the LAN to the Itsy unless you create and
install an INF file. When developing I generally want to telnet/ftp into
my Itsy from my linux host so the configurability advantage of ICS is lost.
The other mode of use is to give the Itsy a valid LAN address which then
requires some manual configuration of routes but allows your Itsy to talk
to anything on the LAN.
======================================================================
Windows (98/2000)
Download the driver, and expand into target directory.
1. First time install : When you plug in the Itsy with the client USB
driver installed Windows will ask you for the drivers. You must point the
installation script at the place where you expanded the Win98 driver.
2. Upgrading 98: Expand the new drivers into a new directory, and
manually copy itsyeth.sys into c:\windows\system32\drivers and netitsy.inf
to c:\windows\inf\other\compaqnetitsy.inf
3. Upgrading 2000: Expand the new drivers into a new directory, and
manually copy itsyeth.sys into c:\windows\system32\drivers and netitsy.inf
to c:\windows\inf\oem?.inf
4. Simulating first time install (Windows 98 only): remove the following
files: c:\windows\system32\drivers\itsyeth.sys, c:\windows\inf\netitsy.inf,
c:\windows\inf\other\CompaqNetItsy.INF, and the following registry entries:
\HKEY_LOCAL_MACHINE\Enum\USB\VID_049F&PID_505A,
\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Class\Net\XXXX - where
the entry for XXXX describes the Itsy net device, DriverDesc entry for an
Itsy is "Itsy Pocket Computer USB/Ethernet Link". Now when you plug an
Itsy into the host you should see the same behaviour as for a first time
install.
----------------------------------------------------------------------
Configuration (98):
After installing the Itsy host drivers you must go to the control panel and
manually setup an IP address. There are a many network configurations you
could use here, I will just explain the configuration I use and hopefully
that will be enough for you to go on.
Assign IP Addresses
1. Assign Itsy a valid IP address for the local environment
(xxx.xxx.xxx.xxx) by editing the S12usbd script in rc.Itsy. Modify the line
ifconfig eth0 192.168.0.2 up.
2. Assign Win98 Itsy/NIC a private IP address, as nothing on the LAN
needs to access this. (See Control Panel, Networks, TCP/IP -> Itsy Pocket
Computer, Properties, Specify an IP address eg. 192.168.0.1).
Add Static Routes
1. On Win 98 machine add a route to Itsy through the Itsy NIC
adapter. (If you give Itsy a private 192.168.xxx.xxx address you can skip
this step). From a DOS window execute:
route add xxx.xxx.xxx.xxx 192.168.0.1
and verify addition with
route print
2. On the Itsy you can either make the Win98 host the default gateway by
editing /etc/sysconfig/networks or you can add a static route. The command
I used to add a static route is:
route add -net 16.0.0.0 netmask 255.0.0.0 gw 192.168.0.1
Switching on Windows 98 IP Forwarding
Windows 98 can do IP forwarding; to enable it you need to edit the
registry using regedit. Set the data value
Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP\EnableRouting
to 1 and reboot. You will then need to add a static route to Itsy using
your host as the gateway on every machine you want the Itsy to contact.
Alternatively you could add the static route on your LAN's default gateway.
----------------------------------------------------------------------
Configuration (2000):
After installing the Itsy host drivers you must go to the control panel and
manually setup an IP address. There are a many network configurations you
could use here, I will just explain the configuration I use and hopefully
that will be enough for you to go on.
Assign IP Addresses
1. Assign Itsy a valid IP address for the local environment
(xxx.xxx.xxx.xxx) by editing the S12usbd script in rc.itsy. Modify the line
ifconfig eth0 192.168.0.2 up.
2. Assign Win2000 Itsy/NIC a private IP address, as nothing on the LAN
needs to access this. (See Start Menu -> Settings -> Network and Dial-up
Connections -> Local Area Connection 2 -> Properties -> TCP/IP, Specify an
IP address eg. 192.168.0.1). The Itsy must be connected for the Local Area
2 icon to be present.
Add Static Routes
1.On Win 98 machine add a route to Itsy through the Itsy NIC
adapter. (If you give Itsy a private 192.168.xxx.xxx address you can skip
this step). From a DOS window execute:
route add xxx.xxx.xxx.xxx 192.168.0.1
and verify with
route print
You can make the route persistent across reboots with the -p argument:
route -p add xxx.xxx.xxx.xxx 192.168.0.1
2. On the Itsy you can either make the Win2000 host the default gateway
by editing /etc/sysconfig/networks or you can add a static route. The
command I used to add a static route is:
route add -net 16.0.0.0 netmask 255.0.0.0 gw 192.168.0.1
Switching on Windows 2000 IP Forwarding
Windows 2000 can do IP forwarding, to enable it you need to edit the
registry using regedit. Set the data value
\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\IPEnableRouter
to 1 and reboot. You will then need to add a static route to Itsy using
your host as the gateway on every machine you want the Itsy to contact.
Alternatively you could add the static route on your LAN's default
gateway.
----------------------------------------------------------------------
Internet Connection Sharing Configuration
Windows 2000
Follw the configuration steps above and then enable Internet
Connection Sharing on the host by following
Network and Dial-up Connections -> Local Area Connection -> Properties ->
Internet Connection Sharing -> Enable
Ensure an Itsy is connected at the time or you will not be given the
option of Internet Connection Sharing.
Window 98 (SE)
Install Internet Connection Sharing after you have installed the Itsy
drivers, without an Itsy connected
Control Panel -> Add/Remove Programs -> Windows Setup -> Internet
Tools -> Internet Connection Sharing
Follow the Internet Connection Sharing Wizard and set you LAN Adapter
to be the internet connection. After a reboot you should be ready to go.
To configure ICS start Internet Explorer and
Tools -> Internet Options -> Connections -> Sharing
2. Add routes on the Itsy
route add 16.255.255.255 gw 192.168.0.1
----------------------------------------------------------------------
Release Notes:
1. Win 98 1st edition has a bug that only allows you to reconnect an
Itsy up to 5 times before requiring a reboot of the Win 98 machine. This
problem has been fixed in 2nd Edition Win 98 and it is recommended you run
this release. 2nd edition also has NAT which will allow your Itsy to
connect to the greater LAN that your host is connected to.
2. Do not disconnect the Itsy when transferring data, it may cause the
host to crash.
3. On Windows systems the driver is associated with the actual port the
device is plugged into, thus if you unplug your Itsy and plug it back into
a different USB port the driver will be reloaded. Thus you may need to
reconfigure the IP address etc. This is a Windows problem reported in the
newsgroups and may be fixed in some variations and upcoming releases of
Win2000 and Win98.
4. Some Windows machines have shown problems with transferring data at
slow rates, the easiest way to see this is try a ping and see if packets
are lost. This is a problem with the way the Windows stack asks the Itsy
for data and should not affect high speed throughput. I believe the
problem is in how the UHCI transaction error number is set, but I cannot
find a way to change this from the Windows interface.
======================================================================
Received on Fri Feb 15 16:06:32 2002
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:44:32 EDT