|
|
|
PART 3 - Setting up Your User Account
INTERNET
SETTING UP YOUR INTERNAL MODEM
Assuming your machine is using standard serial ports and IRQ's, set the modem jumpers to a free IRQ and COM port address. Lets assume a standard COM3 definition: 3e8 IRQ: 5
First, let the serial I/O manager (Dev.ser) know about this device. Start Dev.ser in your sysinit.<node> in the following way with the above hardware settings:
Dev.ser 3f8,4 2f8,3 3e8,5 & ( COM1 COM2 COM3 )
Now the COM ports are defined as above in sequential order. An "ls" of /dev/ should show ser1, ser2 and ser3.
Now set the baud with the stty command set.
stty baud=115200 < /dev/ser3
"baud" is the speed your computer communicates with the modem, not the line speed of the modem. You are now set up to use your modem with QNX:
>qtalk -m /dev/ser3
You are now in the qtalk program. For more information about qtalk and modems, see "Help with qtalk"
| at> | Should get "OK" reply |
| atz | Resets the modem. "OK" reply |
| atdt0016135910934 | A dial tone and the BBS menu as displayed below. |
Your modem will dial QUICS; and you will be prompted to log-in. The 'at' commands are built into the firmware of your modem. If you have difficulty using the at command set, consult your modem manual. If your telephone system requires a dial string, such as '9' to get an outside line, use the following dial string instead.
atdt9w16135910934
The 'w' provides a wait state while a dial tone is being obtained.
|
Note: You can replace steps above with: qtalk -m /dev/ser3 quics where the dial string "quics" is resolved from the file: /etc/config/qtalk
|
log-in to QUICS with your user ID, and Password.
To quit your session:
logout
<CTRL A> q
Modems are known to hang on occasion, a cold boot reset can often cure a temperamental modem. If your modem is not responding to the AT command set, it could be an MS-Windows modem only, which relies on software rather than firmware to implement the AT command
set.
The following is the log-in greeting from QUICS, complete with our access phone numbers and Internet address:
Welcome to the QNX Users Interactive Conferencing System.
Internet: quics.qnx.com / 198.53.31.1
Modem (Hunt Group):
+1 613 591 0934 V34+/VFC/V32bis/Terbo/HST
+1 613 591 0935 V34+/VFC/V32bis/Terbo/HST
+1 613 591 0940 V34+/VFC/V32bis/Terbo/HST
+1 613 591 1735 V34+/VFC/V32bis/Terbo/HST
+1 613 591 3009 V34+/VFC/V32bis/Terbo/HST
+1 613 591 3128 V34+/VFC/V32bis/Terbo/HST
+1 613 591 6093 V34+/VFC/V32bis/Terbo/HST
Log-in as 'newuser' if you're a first time caller.
Welcome to QNX 4.23 Copyright (c) QNX Software Systems Ltd.
SETTING UP YOUR EXTERNAL MODEM
Your external modem will be connected to a standard serial port. If the serial port you wish to use is not at a standard address/IRQ, you may have to pass required arguments to Dev.ser Otherwise, use the internal modem instructions above.
HELP WITH qtalk
Once the modem is configured, and a connection is made, you will want to know what qtalk can do for you. See the usage message for qtalk as well as the "Utilities Reference"
use qtalk
from within the qtalk program:
<ctrl> <a>
produces:
Qtalk [4.81]
----------------------------------------------------------
Modem : //37/dev/ser2
Local echo : disabled
Logging : disabled
Top bit : displayed
Xfer protocol : qcp
Command char : 0x01 (^a)
Delete char : 0x7f
Terminal type : <not set>
-----------------------------------------------------------
b)rk, c)d, d)ial, h)angup, l)og,o)protocol options, q)uit
w/hangup, r)eceive s)end, t)ransfer protocol, w)rite,
x)exit w/o hangup, T)erm emul ?)more cmds
Selecting ? at the Command(?) prompt displays the interactive command set available with qtalk.
Command(?):?
b - Send Break q - Quit & Hangup c - Change directory r - Receive a file d - Dial System s - Send File e - Toggle Local Echo t - Select transfer protocol h - Hangup w - Write File to Modem l - Log File On/Off x - Exit w/o Hangup o - Modify protocol options ! - Escape to shell p - Toggle Parity Filter I - Show current info C - Command Character D - Delete Character T - Switch terminal emulation between QNX4, QNXS, and ANSI
For a complete discussion of what the interactive command set does, see the "Utilities Reference" guide. The section on "Modem File Transfers" makes use of the <s> - Send File option.
When downloading files from QUICS, always get the original check-sum from the target file before downloading. This way you can verify the file you received is an exact duplicate (no file transfer errors) by comparing its check-sum with the original file's.
cksum target_file
produces:
980841296 3478 target_file
where: 980841296 is the "check-sum" and 3478 is the byte size
DOWNLOADING: QUICS to local machine
You can access files for downloading from two primary directory trees:
/usr/free/
/updates/
Once you're logged into QUICS with the modem, cd to the desired directory and download the file using the qcp protocol.
qcp se target_file
The target file will be sent to your local machine's current working directory.
UPLOADING: QUICS from local machine
You will typically need to upload files to QUICS so that a developer or tech-support representative can obtain a binary file from you. Do not mail binary (non text) files to us. We do not use Microsoft Mailers, and don't like receiving executables mailed to us as attachments. If you must send a binary file (compressed or otherwise), use the following instructions, and send the QNX recipient notification through e-mail that the requested files are in your user account; don't forget to state what your user account directory name is (typically its the same as your user id).
After logging in, cause the QUICS server to go into receive file mode:
qcp re
You will see a spade symbol to start scrolling across the screen. Return to qtalk's command menu with <ctrl> <a> and invoke the send command:
Command(?):s
Indicate the file name(s) from your local host's current directory ready for uploading:
Send file(s):this that other*
Wait for the prompt to return. The above sequence would have sent the files: this, that and all files starting with 'other', e.g.:
other1,
other2,
other3.
CONNECTING TO QUICS FROM A NON QNX SYSTEM
MODEM PROTOCOLS
If you are trying to make a modem connection from a NON QNX system, the QCP protocol will not work, and the terminal emulation may need adjusting. If you're sending files to the QUICS server, the "X-modem" " Y-modem" and "Z-modem" protocols can be used, and will automatically be detected by QUICS. If you want to retrieve a file from QUICS using one of these protocols:
FILE TRANSFER TO THE QNX FILESYSTEM
Once the file is on your local system, you can move it to the QNX Partition, if one exists, using the following procedure:
Dosfsys &
| Note: Older
versions of Dosfsys will only work with standard DOS FAT16 file
systems. A newer release of Dosfsys will support the FAT32 for
Win95.
|
cp /dos/c/temp/target.file ./
will copy the file into the current working directory. If the file is a binary file (executable), check the file for transfer errors.
If the above method can not be used because QNX is not installed to the same computer, you may want to try one of the following alternative methods:
Using "Hyperterminal" under Win95, we suggest using the " ANSI" emulation. This emulation will give you the ability to read the QUICS news groups, but on screen editing will be difficult; other modem software may give better results. Hyperterminal gives you the option to select "ANSI" emulation by selecting:
Your QUICS profile editor should be used to select "ANSI" for the QUICS server. Note, any changes to your 'profile', will not be effected until your next logged in session (see "Setting up your User Account"). If you're having difficulties posting to QUICS, because of poor terminal emulation, you can try this offline procedure.
textto -l target_file.txt
tin
and select the newsgroup you wish to post to or reply to ('w' to post a new thread, 'f' to follow up on the current thread you have open).
<shift> <:>
for command mode. Read the uploaded file into the editor:
r target_file.txt
target_file.txt will be read into the editor from the current working directory. Go back to command mode again
< shift > < : >
Write and quit out of vi
wq
NEW ACCOUNTS
There is no cost or restriction for setting up accounts on our BBS, though you must register a product license to use QUICS.
Access QUICS using telnet or a modem connection. As a first time user, log-in as 'newuser' and follow the instructions provided. When you're done, you will be assigned a unique user ID, and a self chosen password. We recommend you write this information down on the inside cover of your QNX manuals. PLEASE NOTE: your user account is not private, all QNX personnel have access to your account. This facilitates file transfers between you and QNX.
When setting up the account, you will be automatically prompted to include service plan information and serial numbers for your QNX software. You can update this information at any time by using the 'profile' command from within QUICS. See the section on "Maintaining your Account".
Some users may have faxed their software registration form back to QNX - this does not update you QUICS account privileges. QUICS account privileges must be obtained by registering on-line.
MAINTAINING YOUR ACCOUNT
When you update your user profile, your new account privileges will not take effect until your next active session.
log-in to QUICS via telnet or a modem connection which ever is convenient. Your account privileges are maintained with the profile command.
profile
Profile Editor
--------------
<E>ditor (Default: vi)
<T>erminal Type (vt100)
<H>eight (25)
<W>idth (80)
<D>ownload Command (Default: qcp se)
<U>pload Command (Default: qcp re)
<L>ast Updated (197001010000.00)
<J>oin a service plan
<R>esign from a service plan
<S>erial Numbers
<Q>uit
Your choice?s
Serial Numbers
--------------
<A>dd a serial number to your profile
<D>elete a serial number from your profile
<L>ist serial numbers in your profile
<Q>uit
Your choice?a
At this point you would add the serial number and password combination located on the back side of your product installation disk.
Since this information is only required to determine your /updates/ directory tree privileges, you are not required to register multiple licenses for the same product. Multiple users may register the same serial number and password for QUICS privileges.
'tin' is your access to our news groups. It, like other news group services provides an efficient method of communicating with QNX's own development team, as well as other QNX users.
The service plan you have chosen determines your privileges to write to the various news groups. If you have not purchased a service plan, you can only post to non 'experts' conferences, such as the 'user2user' groups (see " Service Plans").
OFFLINE NEWS
You may wish to download the newsgroups to your local. machine. A "Simple Local New Reader" is available from:
/usr/free/QUICS/slnr-src.tgz
To download the newsgroups for your newsreader, see:
/usr/quics/docs/offline.doc
/usr/quics/docs/offline.news.doc
POSTING TO THE NEWS GROUPS
This section provides some general guidelines to use when posting questions or replying in the news groups. An average of 200 postings are made to the news groups daily, following these guidelines will make it easier for everyone reading your article.
BEFORE YOU POST
ARTICLE GUIDELINES
WHAT TO POST
Include relevant information. This may or may not include the output from the following debug utilities. If you're not sure if the debug utility output is relevant, post it anyway. For any kind of software configuration issue, a "sin ver" is a must.
| General Problems | sin sin ver sin in |
| Hardware Problems | show_pci -v traceinfo sin ir |
| Networking Problems | netinfo -l netinfo |
| TCP/IP Problems | netstat -an netstat -rn syslog file |
| PCMCIA Problems | pin |
| Photon Graphics Driver Problems | crttrap |
| SIGSEGV Problems | The SIGSEGV Message as it appeared on your console. The steps leading to the error and, if possible, a reproducible case. The dump file captured by dumper & - don't post the contents upload it to your home directory. The output of traceinfo. |
If you are having difficulties configuring a hardware driver, remember to report the explicit error messages that you're getting, as well as how the driver is being invoked, i.e. what options are being used. Check the 'usage' statement for the driver in question, there is likely a "-v" option for verbose output. Capture the verbose output. Fsys and Net drivers have undocumented extra verbose options, start these drivers with -vvvvv to get this extra debug information.
If you're having difficulties with any part of the QNX API, refrain from posting large samples of source code. Example code should not exceed 50 lines and should be written in 'C'. Don't forget to include the version of operating system and tools that you're using. Your 'makefile' should also be provided.
WHAT TO EXPECT FROM THE 'EXPERTS' NEWS GROUPS
If you have followed the above guidelines, you can expect a reply to your question within two business days, sometimes within the hour.
| Q) I posted a question yesterday to the news groups, but I no longer see it among the list of articles. | A) If you have read your own article, it becomes deleted from your list of unread articles. Articles are deleted with time, but never overnight. See "Using Tin Commands", 'r' to toggle. |
| Q) I don't see very many news groups. | A) See "Using Tin Commands", 'y' to yank. There are over 90 news groups that you can freely read provided you have subscribed (no charge) to them all. |
| Q) My article in the experts newsgroup has not been answered, now what do I do? | A) Your article may have not been answered for several
legitimate reasons, such as:
In any case, if you do not receive an answer within the two business day guideline, we suggest you follow up you own question with a simple " ping" message. Following up your own thread in this way ensures your message is added to the "unread list" of newsgroup threads, thereby drawing attention to your unanswered issue. |
| Q) My question uncovered a bug in the shipped utility set, how do I recover the credit I used up from my Standard service plan? | A) Anytime you discover an error in the documentation, or a bug in our software, you are entitled to have your credit returned. Just follow-up your article requesting the return of your credit and we will gladly oblige. |
| Q) Another user has posted a question in the experts newsgroup, and I would like to add some relevant information without using up any credits. | A) Credits are only used when starting a new thread, following up will not cause any credits to be deducted, though you must have a service plan for write permissions to use the experts news groups. |
USING TIN COMMANDS
In order to read the QUICS news groups, you will invoke the "tin" command. If you're a first time user, and would like some practice manipulating tin, post to: "quics.info.test"; this newsgroup was specifically designed for this purpose. All articles posted there are ignored. "tin" has three layers of context sensitive help, the following outlines some of the available commands. Using the 'h' command at anytime will provide you with a complete command list available for your use. The commands highlighted below with an '*' are worth trying out to discover their utility.
No News Group selected help:
<CR> Read current group <TAB> * Goto next group with unread news and enter it c Mark group read g Choose a new group by name j * Down a line k * Up a line hH Command help (H=toggle mini help menu) qQ Quit r * Toggle display to show all subscribed to groups s * Subscribe to current group u Unsubscribe to current group w Post an article to current group W List articles posted by user y * Yank in subscribed/unsubscribed from .newsrc z Mark current group as unread
News Group Selected help:
<CR> Read current article <TAB> Goto next unread article or group <SPACE> forward a page hH Command help (H=toggle mini help menu) j Down a line k Up a line m Mail article/thread/hot/pattern/tagged articles q Return to previous level Q Quit r * Toggle display to show all / only unread articles s * Save article/thread/tagged articles to file t Tag current article for crossposting/mailing/saving U Untag all tagged articles w * Post an article to current group
Help when article is open for reading:
<CR> Goto to next thread <TAB> Goto next unread article <SPACE> forward a page D * Delete (cancel) current article that must have been posted by you fF * Post (f=copy text) a followup hH Command help (H=toggle mini help menu) m Mail article/thread/tagged articles to someone q Return to previous level Q Quit rR Reply through mail (r=copy text) to author s Save article/thread/tagged articles to file w Post an article to current group W * List articles posted by user x Crosspost current article to another group zZ Mark article (Z=thread) as unread
FREE
STANDARD
GOLD
Please contact your QNX distributor for further details of these plans.
Many product directories such as /updates/qnx42/ have sub-directories such as "Alpha" and "Beta". Alpha software has not been widely tested in a Beta program or gone through any rigorous quality assurance testing. Software placed there typically addresses new problem reports and must be fully tested before it becomes part of the general release. Consult technical support before using. Software that is considered part of the general release is in the "Released" directory.
The Beta and Released directories typically contain 'readme' files and an "Update_info" file. The Update_info file is your guide to navigating the chosen directory. It tells you what's included in the specific archives and why; it may also include some installation information. You're always better off reading this file while you're connected to QUICS before downloading - this will ensure that you don't waste your time and money downloading the wrong files.
/usr/free and /usr/free2 is NOT supported by QNX technical support.
Getting the archive installed on your hard drive after downloading:
gunzip -c target_file.tgz | pax -vr -f -
or
gzip -cd target_file.tgz | pax -vr
or
zcat target_file.tgz | pax -vr
gunzip and zcat are links to gzip, and are shipped with 4.23. gzip can be downloaded from:
/usr/free/qnx4/os/utils/archivers/
If the file you're downloading is not an archive of files, that is, it does not contain 't' in its file extension, you can uncompress using:
gunzip target.gz
or
gzip -d target.gz
To see the usage message for gzip:
gzip -h
Software in /usr/free2 is software that works with the QNX 2 operating system. This is not accessible from the web.
In the /usr/free and /usr/free2 directories, you will notice two files: ls-Rl and find-ls. These two text files contain the text output of the commands that generated them (the files' namesakes). You can open these files with QNX editor of your choice and quickly search for programs of interest, and then move to the appropriate directory to download the target files.
If you would like to post some software of your own creation to this directory tree, follow the instructions in /usr/free/README, and then send mail to freesoft@qnx.com to get it posted.
This way you can delete unnecessary files as required. Glen (our QUICS sys-op) greatly appreciates this courtesy. QSSL reserves the right to recover disk space at any time with out warning.
Remember, your home directory on QUICS is not private.All QNX personnel have access to it. We give you these accounts so that you can upload "test case" software to tech support and download software as required.
| elm/ | a directory containing a Reference guide for the electronic mailer. |
| newuser | The note you are presented the first time you login to QUICS |
| offline.doc | How to set up tin batcher, the offline newsreader. |
| offline_news.doc | How to post with the offline newsreader. |
| QUICS | A note describing all of the commands available to the QUICS user. |
| tin | The "man" page for tin. To properly view this document: more tin |
All of the above technotes, with the exception of "newuser", are archived in /usr/free/QUICS/quics_docs.tgz
From the Beta Agreement:
"Please keep in mind that this is a beta, not a general release of the Beta Product. It will be unreliable and should not be used for any purpose other than its evaluation. The feedback we receive from our beta sites will help us produce a more stable product for general release. As a beta tester, you are asked to test the Beta Product under operating conditions simulating those you normally expect. However, you must take adequate precautions to prevent damage to your resources in the event the Beta Product fails."
The Beta Agreement expires 30 days after commercial release of the software.
Support for the Beta software is done entirely through QUICS newsgroups. After signing up, you will have unlimited access to read/write to the specific Beta newsgroup. Your questions, suggestions, and problem reporting will help us to perfect the final product.
The purchase of commercially released software may be a prerequisite for inclusion.
If you are interested in joining a Beta program and purchase your QNX products from an authorized QNX distributor, you should contact your distributor.
Special Thanks to Allan Kleywegt (apkleyegt@qnx.com) for this information.