Getting Connected to IPASS with Windows CE
This document provides a method for using IPASS with Windows CE, which IPASS does not currently support. However, their web site does contain information on a CE "work-around" which is included just belgw. This information provides the groundwork for getting connected, but is not enough to get you up and running. In addition, you will most likely be unable to find the older dialer mentioned in the work-around. I should warn you that there are tons of details included. It is not complicated, just a bit tedious to get it all set up. IPASS provides a great service though, so itís worth it until they come up with a dialer.
Hopefully this will get you up and running. If you have any problems, please e-mail me and I will try to help. I will be out of the country between October and April so I will get back to you as soon as possible.
I would like to thank Bruce Chun and Peter Koch (from Dialup Master) for helping me with the script modifications.
From the IPASS web site
"Some technical users may want to use an unsupported work-around appropriate for connecting each device to the Internet via the iPass network with their handheld devices. These work-arounds normally require that the user locate and manually enter a script to identify the dial-in user as an iPass user. (This scripting is handled invisibly and automatically on iPass dialers for Windows 95/98/NT and Macintosh.) Handheld users can follow these directions for Windows CE, Palm Pilot, and Psion. This can give access to iPass' entire network of 3000+ POPs. Windows CE Work-Around for iPass Network Connections iPass does not currently support Windows CE because Windows CE dialers can not implement dial-in scripts and the majority of iPass POPs require the running of scripts after modem negotiation. The contents of the scripts, however, can be entered manually. There are some users doing this successfully, although we do not recommend that non-technical users attempt this work-around. If you want to try accessing the iPass network via Windows CE, you should first install iPass Dial Wizard (our older dialer, provided by your ISP or company) on a Windows 95/98 machine so that you can get the following files:
Normally, these files will be found in the \Program Files\iPass\iPass Dial Wizard\ folder. All files with .scp extension are script files. As stated earlier, most of iPass POPs require the running of one of these files (scripts). POP-specific information is provided in the ipass.ipb phonebook. The contents of the scripts are case sensitive. An entry from the ipass.ipb may look like the following, with fields separated by |.
(You can open *.ipb files with WordPad or similar applications.)
This is the detailed explanation of each field:
ISP code|country code|TAPI country id|area code|phone|city|region|unique POP id|script file|username prefix|username suffix|flags|price
First, you will need to identify the city/state (field 6 & 7) you want to dial into, the POP number (field 3, 4, 5), the prefix to insert in front of the username (field 10), and the script to run after the modem negotiates (field 9). If the prefix and script fields are blank, then they are not required to access that number. For example, to connect to the above location from within Algiers, dial 741200. After modem picks up, run through the contents of the sci-w95.scp script and enter in [email protected] with password when called upon to do so by the script."
What you will need to get connected:
What to do:
After you have gotten your account established with an IPASS ISP, pull down the dialer software and install it to your PC. The software will be installed to the following directory: (NT) c:\winnt\profiles\all users\application data\microsoft\network\connections\cm\ipasscm2 (95/98) c:\windows\all users\application data\microsoft\network\connections\cm\ipasscm2. You will want to make an IPASS connection with the dialer software on your PC before you go any further so that you will have the most current phonebook files available. (They should be automatically updated when you connect with the dialer).
Phonebooks: With the current version of the dialer software, there are now 2 phonebook files - mdmCH-np.pbk and mdmCH-p.pbk. Open notepad. From notepad, open each of these files and save them as a text file. I would suggest that you then open the text files in Excel and parse them out to make them easier to sort through when you are looking for a particular city. You will notice that mdmCH-np phonebook contains connection information for all ISP's requiring a script and some that do not use scripts. None of the mdmCH-p phonebook ISP connections use scripts. I am guessing that the -np indicates that no username prefix is required and that -p indicates that a username is required. See discussion about the .cms files below for more information.
This is an example line from the mdmCH-np.pbk file:
You will need to know what most of these fields are. The field descriptions can be used as column headings for your Excel file. I am not certain what the flags are for Ė so just use unique column headings for them. Here are the descriptions:
ISP code, country code, TAPI code, city, area code, phone number, flag?, connection speed, flag?, flag?, script
To figure out what countries the numerical country codes represent, open the dialer on your PC and look through the country listings under properties, then the phonebook button. The country code is listed next to each country (i.e. Mexico (52)). My suggestion is to parse out your phonebook in Excel, put some headings at the top of your columns (as listed above) and convert the countries you will need from a number to a name. Then you can sort it easily when using it on your HPC. You should only need to do this again if the phonebook is updated - which you will only obtain if you connect with the actual dialer software.
To use the dialer software on your 95/98/NT PC, you select the city you want to connect to. The dialer software pulls the information for the connection from the appropriate .pbk file. The dialer also uses the files called mdmCH-np.cms/mdmCH-p.cms. These files contain information on which username prefix is required. You should save these files as text files also. You will notice that in the example from IPASS's web site above, a username prefix of S104408 (S plus the unique POP id) is used with the ISP listed (which uses sci-w95.scp). With the old dialer, all connections requiring the sci-w95 script required a username prefix like this. You will not find these username prefixes anymore with the new dialer. I spoke with 2 different people at IPASS that confirmed that these particular prefixes are no longer needed. I have tried one ISP that uses sci-w95.scp and it worked both with and without the prefix.
After you have saved your .pbk files and .cms files as excel or text files, copy them to your HPC.
Script Files: The first thing you should know is that Windows CE doesn't support scripts on it's own. So, the next step is to pull down, pay for, and install Dialup Master (www.moreinfo.com.au\peterepeat) on your HPC. This is your key to making it all happen.
In your IPASS installation directory (see above)- you will find all of the .scp files. This document will only address the use of the uun-w95 and sci-w95 scripts, which are the most commonly used. However, you should be able to modify the other scripts with modifications similar to those made to the sci-w95 script.
Some ISPís donít require a script at all. You like these. Most require the username prefix "IPASS" ([email protected]). There are some in the mdmCH-np.pbk file though that shouldn't require it.
Uun-w95: this script is used by almost all US ISP's. You will notice that it is used with providers offering a 56K connection. With the old phonebook, most uun-w95 connections used the username prefix "IPASS" so [email protected] With the new dialer, you will find that the .cms file does not call for a username prefix (for ISP's requiring scripts). I have only tested one connection without the prefix and it failed. It worked fine with the prefix.
I did not need to modify the uun-w95 script to get it to work with Dialup Master. I am assuming that you will not need to modify it either. Therefore, copy it (as is) to your HPC.
Sci-w95: this script is primarily used by ISP's that have a 28.8K connection, which happens to be most ISPís outside the US (although some have 56k dialup). As mentioned above, when using the old phonebook, all ISPís that required sci-w95.scp had a username prefix of S+unique POP id. IPASS tells me that these username prefixes are no longer required and you will not find any in the .cms file. I have tried one connection without a username prefix and it worked. When using it with the old phonebook username prefix, it still works.
You will now need to edit the original sci-w95 file (or just create a new one in any text editor and save it as sci-w95.scp). The contents need to be as follows:
Now, copy it to your HPC.
LETíS GET CONNECTED!
O.k., youíre almost ready to rumble. On your HPC, you should now have the two phonebook files saved as text, word or excel files. You should also have your script files (with modifications, if necessary Ė you can always try them as is to see if you can get away without modification). You can bring over the .cms files you saved as text files also if you canít remember which username prefix is needed (or not needed). Lastly, you should have Dialup Master installed.
Now, pick a city, say San Jose, Costa Rica. You will need to look in your phonebook file for the connection info (start in the mdmCH-np.pbk file - you will appreciate this being an excel spreadsheet right about now). This is the excerpt from the .pbk file:
1097,506,0,San Jose,,287 0800,0,28800,0,40,sci-w95
In this case, you find that San Joseís number is 506-287-0800 (506=country code). You also see that itís a 28.8 connection and uses the sci-w95.scp. Now, remember that the mdmCH-np.cms file shows a blank for the username prefix so you will not use one. Now that you have your information, you will need to create a connection in Remote Networking.EXAMPLE USING SCI-W95:
Remote Networking Connection settings:
EXAMPLE WITHOUT SCRIPT: