Article Title	 	: wireless proxim
Creation Date		: 09/11/97
Message ID		: KGFNJQ
Last Update		: 09/11/97
Expiration Rules	: unknown
Location		: NCD_X_Terminals
=================================================================

This techtip discusses installing and using
NCDware in the wireless environment that
Proxim has.  Proxim is a company that markets
wireless technology. The techtip is based on
the experience of actually doing it at Proxim.  

Proxim uses a version of WinFrame from Cruise
technologies, NOT Citrix.  Cruise technologies
OEMs to WYSE.  

So, Proxim will have an NT server setup, with a
Cruise technology version of WinFrame installed.
You install NCDs WinCenter Connect 1.0.34 on top of
this WinFrame. At Proxim, it was the first time we ever
tried installing WinCenter on top of Cruise
technologies WinFrame, but the install was
successful.  Now, very, very important - to 
use wireless you must have NCDware 5.x.x in
order for it to work.  So, after you have
installed WinCenter 1.0.34 you need to go
in and delete out the NCDware 4.1.141 server
and mods files, and manually replace them
with NCDware 5.x.x files.  We used NCDware 5.0.125.
The rest of the NCDware stuff you can just keep
the NCDware 4.1.141 stuff - this includes anything
under usr, such as fonts, configs, rgb.txt and 
so on.  Also you can keep the tftp that came with
NCDware 4.1.141; it will work fine. 

The NCD Explora should be equipped with Proxim's special
PCMCIA card. This PCMCIA card has a wire coming out of
it and at the end of it is a little antenna.  The 
Explora will also be equipped with special boot proms,
something like 2.8.1w. They should have this all set up. 

Now, at the boot monitor prompt, hit Setup and go in 
and setup to boot from NVRAM just like you would if
you were on ethernet.  Set the IP address of the NCD,  
and use the IP of the WinCenter host as your host to 
boot from.  Then type in bt at the boot monitor prompt.

The bootup will be very slow. After it is booted then you
can go in and log on as you normally would if you were
on a ethernet network.         

We successfully got up a WinCenter session using rsh and
also by using login. We got up Unix windows as well, so
it was complete success.  The only problems might be
if you have lot of radio traffic in the area it may
slow down.  Proxim's radio bandwidth is a lot less
than ethernet, so it will be about 1/2 to 1/3 slower,
but is still works fine.  

Proxim people are very knowledgable about their product
and will be able to carry their side of it very easily.

NOTES:

  note 1.  If you try using the NCDware 4.1.141 what will happen is
           that it will boot the server okay, but you will not be able
           to read in any of the other files, such as rgb.txt, configs,
           even the modsxpl files.  The reason for this is that within
           the PCMCIA card is enough logic to download the server via
           wireless, but right after the server gets booted, the
           server takes over and NCDware 4.1.41 server does not have
           the wireless logic in it and cannot load any files at all.
           The solution of course is to use NCDware 5.x.x 
 
  note 2.  About clearing NVRAM. You tech support types who like
           to clear NVRAM, be a little bit careful here.  Wireless
           PROMs have boot parameters that set the wireless domain
           and security codes; make sure you know these before you
           clear out NVRAM.  The new boot monitor parameters are
           wd, ws, wr, and wi.  The wd parameter gives domain; the
           range is 0-15.  This will be set to something which
           will match the number on the receiving station. Proxim
           does not use ws which is the security code. But make sure
           you have these things before clearing nvram.  wi may give
           them to you. 

  note 3.  The wireless model does not necessary go from NCD to 
           the WinCenter host.  A more typical environment is to
           have a station on  network which receives the radio
           signals, then that station is networked to other systems
           such as your WinCenter host.  
  
  note 4.  If you get an error message when you boot saying bad match
           then you need to get your wd and ws parameters set right
           to match those on the receiving station.  The people who 
           set it up should know those.