≪ View Page

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
multiple_nodes:multiple_nodes_using_multitasking_software [2024-01-18 12:56] – created stimpymultiple_nodes:multiple_nodes_using_multitasking_software [2024-01-18 12:58] (current) – [Automatically Loading The Nodes at Bootup] stimpy
Line 4: Line 4:
 Whether you are using standard serial ports or intelligent serial boards, multitasking enables you to run several nodes on a single computer.  This type of setup may seem complicated at first, but after reading this explanation the majority of your questions about setting up a multi-node system should be answered. Whether you are using standard serial ports or intelligent serial boards, multitasking enables you to run several nodes on a single computer.  This type of setup may seem complicated at first, but after reading this explanation the majority of your questions about setting up a multi-node system should be answered.
  
-==== Recommended Hardware: ====+==== Recommended Hardware ====
   * 80386 (or better) based computer with 1 megabyte of memory for each node.   * 80386 (or better) based computer with 1 megabyte of memory for each node.
   * One serial port for each modem you plan to use per machine.  If you are using standard serial ports, use serial ports with NS16550AFN UARTs.  Each standard serial port must use a unique base address and unique IRQ.  If you are using any other type of serial board (such as an intelligent Arnet or DigiBoard card), make sure it is supported by the multiport version of PCBoard before purchasing.   * One serial port for each modem you plan to use per machine.  If you are using standard serial ports, use serial ports with NS16550AFN UARTs.  Each standard serial port must use a unique base address and unique IRQ.  If you are using any other type of serial board (such as an intelligent Arnet or DigiBoard card), make sure it is supported by the multiport version of PCBoard before purchasing.
Line 14: Line 14:
 **NOTE:** If you are going to be using OS/2 for your multitasker and you have the multiport version of PCBoard, you cannot make use of the COMMTSR software because it is a DOS device driver. This means that under OS/2 you are limited to using standard COM ports that use unique base address and IRQ settings. **NOTE:** If you are going to be using OS/2 for your multitasker and you have the multiport version of PCBoard, you cannot make use of the COMMTSR software because it is a DOS device driver. This means that under OS/2 you are limited to using standard COM ports that use unique base address and IRQ settings.
  
-==== Necessary Software: ====+==== Necessary Software ====
   * MS-DOS (V3.3 or higher)   * MS-DOS (V3.3 or higher)
   * Multitasking Software (e.g., DESQview or Windows)   * Multitasking Software (e.g., DESQview or Windows)
Line 20: Line 20:
  
  
-===== Disk caching software =====+==== Disk caching software ====
  
 ===== Modifying System Files ===== ===== Modifying System Files =====
Line 207: Line 207:
 Adding this line will assure that when you exit to DOS through the call-waiting screen the window on your multitasker will close.  If you wish for it to stay open, you should make sure you do not add this line and also make sure you setup your multitasker so it does not close the window upon completion of the program. Adding this line will assure that when you exit to DOS through the call-waiting screen the window on your multitasker will close.  If you wish for it to stay open, you should make sure you do not add this line and also make sure you setup your multitasker so it does not close the window upon completion of the program.
  
-==== Setting Up Your Nodes Under a Specific Multitasker ====+===== Setting Up Your Nodes Under a Specific Multitasker =====
 The instructions that follow detail the steps you need to take in order to add nodes to DESQview, Windows 3.1, and OS/2.  This first section details how to setup the PIF files for both DESQview and Windows 3.x.  This same section also details how to setup the icon for your nodes under OS/2.  The next section details how to automatically load your nodes each time you you run your multitasker.  Each section also lists any special considerations you should be aware of with each multitasker. The other information provided throughout this section (except where appropriately titled) is independent of the multitasker you are using. The instructions that follow detail the steps you need to take in order to add nodes to DESQview, Windows 3.1, and OS/2.  This first section details how to setup the PIF files for both DESQview and Windows 3.x.  This same section also details how to setup the icon for your nodes under OS/2.  The next section details how to automatically load your nodes each time you you run your multitasker.  Each section also lists any special considerations you should be aware of with each multitasker. The other information provided throughout this section (except where appropriately titled) is independent of the multitasker you are using.
  
 Once you have followed the instructions detailed in the specific section for the multitasker you are using, proceed to the section entitled Automatically Loading Your Nodes at Bootup. Once you have followed the instructions detailed in the specific section for the multitasker you are using, proceed to the section entitled Automatically Loading Your Nodes at Bootup.
  
-=== DESQview (R) ===+==== DESQview (R) ====
 Before proceeding with a setup under DESQview you should first become familiar with how to add programs in your DESQview environment if you are not already familiar with that topic. Before proceeding with a setup under DESQview you should first become familiar with how to add programs in your DESQview environment if you are not already familiar with that topic.
  
Line 355: Line 355:
 In this field, enter an N for any PIFs you are setting up for communications programs (such as PCBoard).  If you set this field to Y, it may eventually cause a hard system lock. In this field, enter an N for any PIFs you are setting up for communications programs (such as PCBoard).  If you set this field to Y, it may eventually cause a hard system lock.
  
-=== Microsoft Windows (R) v3.1 ===+==== Microsoft Windows (R) v3.1 ====
  
 In order to run multiple nodes under Windows you will need to create a PIF file for each node.  It is assumed you have some knowledge on how to create a PIF file under Windows.  If this area is new to you, it is suggested you first read the section in your Windows manual detailing how to create a PIF file before continuing with your configuration. In order to run multiple nodes under Windows you will need to create a PIF file for each node.  It is assumed you have some knowledge on how to create a PIF file under Windows.  If this area is new to you, it is suggested you first read the section in your Windows manual detailing how to create a PIF file before continuing with your configuration.
Line 447: Line 447:
 Once you have the PIF files defined, add each node as an icon to Program Manager.  Consult your Windows manual for further information on adding programs to Program Manager. Once you have the PIF files defined, add each node as an icon to Program Manager.  Consult your Windows manual for further information on adding programs to Program Manager.
  
-=== OS/2 v2.x ===+==== OS/2 v2.x ====
  
 To run multiple nodes under OS/2 you will want to create program objects for each of your nodes and store them in a folder on the desktop for easy access.  It is assumed you have a good knowledge of how to work with objects in the Workplace Shell environment.  If this area is new to you, it is suggested that you first read the section in your manual detailing how to use the Workplace Shell. To run multiple nodes under OS/2 you will want to create program objects for each of your nodes and store them in a folder on the desktop for easy access.  It is assumed you have a good knowledge of how to work with objects in the Workplace Shell environment.  If this area is new to you, it is suggested that you first read the section in your manual detailing how to use the Workplace Shell.
Line 578: Line 578:
  
  
-==== Automatically Loading The Nodes at Bootup ====+===== Automatically Loading The Nodes at Bootup =====
 Since, for the most part, your bulletin board will be unattended, you will want your nodes to automatically load when you boot your machine.  This will prevent events like power outages from bringing down your system until you can manually bring up your bulletin board system.  This section gives you detailed instructions for automatically bringing up your system under DESQview, Windows, and OS/2. Since, for the most part, your bulletin board will be unattended, you will want your nodes to automatically load when you boot your machine.  This will prevent events like power outages from bringing down your system until you can manually bring up your bulletin board system.  This section gives you detailed instructions for automatically bringing up your system under DESQview, Windows, and OS/2.
  
-=== DESQview ===+==== DESQview ====
 In order to have all of your nodes load up every time you start DESQview, you will need to use a script.  The following key sequence will create a script for starting up your nodes on one machine. In order to have all of your nodes load up every time you start DESQview, you will need to use a script.  The following key sequence will create a script for starting up your nodes on one machine.
  
Line 596: Line 596:
 Quit DESQview.  When quitting, you will be informed you have some scripts that have not been saved and you are asked if you wish to save them.  Save the scripts to a filename called DESQVIEW.DVS. Quit DESQview.  When quitting, you will be informed you have some scripts that have not been saved and you are asked if you wish to save them.  Save the scripts to a filename called DESQVIEW.DVS.
  
-=== Microsoft Windows v3.1 ===+==== Microsoft Windows v3.1 ====
 To automatically load your nodes under Microsoft Windows, simply move the icons for your nodes to the Startup folder in Program Manager.  When Windows loads, it will automatically load all programs that are in your Startup folder. To automatically load your nodes under Microsoft Windows, simply move the icons for your nodes to the Startup folder in Program Manager.  When Windows loads, it will automatically load all programs that are in your Startup folder.
  
-=== OS/2 v2.x ===+==== OS/2 v2.x ====
 Select all of your node objects (but not the node template) and hold down the CTRL key while dragging them to the Startup folder in your OS/2 System folder.  The program objects will be moved to that folder.  When OS/2 loads, it will execute any programs in your Startup folder. Select all of your node objects (but not the node template) and hold down the CTRL key while dragging them to the Startup folder in your OS/2 System folder.  The program objects will be moved to that folder.  When OS/2 loads, it will execute any programs in your Startup folder.