View or change the Windows Internet Options. The dialog presented is identical to the
Internet Options accessible from the Windows Control Panel or the Internet Explorer
application. Options of particular interest in this dialog include:
General tab
Register iRider as the default browser
If checked, this option causes all Internet-related document types to be opened in
iRider. This includes URLs, local HTML files, GIF or JPEG image files, shortcuts to such
files, or Favorites referring to such files.
To unregister iRider as the default browser, you must open another browser application
such as Internet Explorer or Netscape Navigator and designate it as the default browser.
Retain pinned pages across iRider sessions
If checked, this option causes any pages that were pinned in the last iRider window you
closed to be reopened when you launch iRider again.
Mark retained pages as visited
If checked, this option causes any pages retained between iRider sessions to be marked
"visited" when iRider is launched, and thus ignored by the Go/Next Page command.
Search page location
Specifies the address of your search page, which is opened when you use the Go/Search command or button. The Set Default button restores
this to the iRider factory default search page, iRider Search.
Your search pages and any pages in the same sites can be treated specially by the Go/Next Page command. See the Navigation tab/Next Done
Command, below.
Address Bar search URL pattern
Specifies how searches made from the Address Bar will be
performed. When you enter a simple word or phrase or an explicit search command in the
Address Bar, a search engine query address (URL) is generated using this pattern. The
"%1" sequence in the pattern is replaced with the search key entered in the
Address Bar.
To make your own pattern, go to your preferred search site and enter an arbitrary
keyword in its search field; copy the URL of the resulting page and replace your arbitrary
keyword with "%1" (without quotes). The Set Default button restores this to the
iRider factory default search pattern.
Your search pages and any pages in the same sites can be treated specially by the Go/Next Page command. See the Navigation tab/Next Done
Command, below.
Navigation tab
Normal Navigation
Controls what happens when you click on a link normally, i.e., with the left mouse
button (right button on a mouse configured for left-handed use). By default, iRider will
create a new page in the Page List. You can change this so that normal navigation occurs
within the current page.
Please note that you are strongly advised to leave this setting on the default, and let
iRider create a new page on normal navigation. We believe that the alternative makes for
complicated and confusing browsing sessions, especially when you use Surf-Ahead. One of
the crucial usability decisions in iRider's development was the consistent access to pages
in the Page List.
Surf-Ahead
(The following description assumes that you're using a mouse configured for
right-handed use. If your mouse is configured for the left hand, the functions of the left
and right mouse buttons are reversed.)
These options let you control which mouse buttons are used for Surf-Ahead. You can use the right button, middle button,
both or neither. If neither button is configured for Surf-Ahead, you can still Surf-Ahead
by holding down the Ctrl key and clicking on a link with the left mouse button.
If the right button is configured for Surf-Ahead, you can access context menus by
either holding down the right button for a moment or by holding down the Menu key ( 
) while right-clicking. If the right
button isn't assigned, you can use it to access context menus using the familiar
single-click.
Next Page Command
These options control the order in which the Go/Next Page
command visits completed pages. If neither option is checked, Next Page will visit pages
strictly in the order that they were created. Checking Visit pages in the current
site first causes Next Page to stay within the current website as long as there
are completed, unvisited pages there. Checking Visit pages in the current branch
first causes Next Page to first visit pages that are children or siblings of the
current page.
Checking Except search sites excludes the search sites from any branch
or site precedence indicated by the other Next Page options. This makes Next Page visit
any content pages discovered in a search before visiting any additional search results
pages that were opened after them. If this option is not checked, Next Page could
indefinitely direct you to search results pages instead of content pages, especially on a
fast connection.
Connection tab
Number of pages to download simultaneously
These values control how many pages iRider will try to download simultaneously under
various conditions. iRider will normally download the minimum number of pages, but if
pages are slow to download, it will start to download more pages, up to the maximum.
On fast connections, it's usually best to use a Minimum of 1, because the simultaneous
expansion of multiple downloading pages can make the program less responsive.
A low Maximum, between 4 and 6, is usually a good idea because if too many pages start
to download simultaneously, they will tend to complete too slowly and even fail to
download completely because connections time out.
These settings only affect the automatic downloading of pages. There are no limits on
the number of pages that can be downloaded immediately through normal navigation or by
using the Pages/Download Now command.
Memory tab
These options limit the amount of memory iRider will use. iRider will transparently
discard web pages and reload them from the local disk-based cache as necessary to stay
within these limits. It uses a sophisticated algorithm to decide which pages to discard
based on your usage patterns.
If no memory limits are enabled, the Windows virtual memory system will swap web pages
you've opened to and from the system paging file when available physical memory runs low.
While this will work — up to the limits specified for your system paging file —
it's usually far less efficient than telling iRider to limit its memory usage, and can
very adversely impact the performance of other applications. (Web pages swapped to the
system paging file are in fully expanded and decompressed form, often ten or more times
their compressed size. They also need to be written to the swap file as well as read,
unlike the browser cache, which only needs to be read.)
Under Windows 95, 98 or Me, iRider will also discard web pages if free system resources
drop too low. This may occur before other memory limits are reached.
Keep at least X % physical memory available
When checked, this option tells iRider to keep at least the specified amount of
physical (as opposed to virtual) memory available system-wide. iRider will release memory
if available memory drops below this limit, either because other applications or iRider
itself needs memory for other purposes.
This value can usually be set low (2 to 8%) unless you're using software or web pages
that may have very sudden needs for large amounts of memory (a rare case). If you notice
excessive disk activity during normal usage in all applications after opening many pages,
you may want to gradually increase this limit. If moving between pages in iRider becomes
too slow, you may want to decrease this limit.
Limit iRider memory usage to X MB
(This option is only available under Windows NT, 2000 and XP.)
When checked, this option tells iRider to never use more than the specified amount of
memory (i.e., its working set should never exceed this amount).
This limit generally doesn't need to be used, unless you want to specifically limit the
amount of memory iRider uses. It's usually better to let iRider use any available memory,
up to the limit specified in the previous option. Remember that iRider does notice if
available memory starts to be used by other applications, and correspondingly reduces its
usage.
Depending on the number and types of pages you open, memory limits may be impossible to
meet. Some web pages are marked "don't cache," and aren't cached in the local
disk-based cache, and so can't be discarded without re-fetching them from the network.
(Some web sites can be very capricious about which pages they mark "don't
cache.") Pages with modified form fields or that are the results of a form posting
also can't be discarded.
