home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
network
/
3commisc.zip
/
APP_PS2.DOC
next >
Wrap
Text File
|
1992-01-02
|
8KB
|
183 lines
Application Notes for use of All Chargecard on a PS/2 Model 30-
286, 50, 50Z, or 60 running 3Com 3+ or 3+Open DOS workstation
software.
Configuration 1 - 3+ DOS workstation OR
(see also config.w3p and autoexec.w3p)
3+Open DOS workstation - XNS protocols
(see also config.w3o and autoexec.w3o)
Full NetBIOS or partial (not shown)
Windows/286 (No EMS, no Smartdrive)
VGA
1MB of motherboard memory
3Com EtherLink/MC network adapter
Configuration 2 - 3+ DOS workstation OR
(see also config.3p and autoexec.3p)
3+Open DOS workstation - XNS protocols
Full NetBIOS or partial (not shown)
VGA
1MB of motherboard memory
3Com EtherLink/MC network adapter
*** CAVEATS:
1) On 3Com's 3+ network operating system, if full NetBIOS must be
loaded high, you must use NetBIOS 1.2.1H, available
for 3+ customers from 3Com by dialing XXX-XXX-XXXX.
(This module is included with 3Com 3+Open systems.)
2) In a Model 50Z, both the LCC and PLCC adapters must be used.
Both are available separately from All Computer. You lose the
use of two expansion slots.
3) In a Model 30-286, the PLCC adapter must be used. This
adapter is available separately from All Computer.
INSTALLATION AND CONFIGURATION PROCEDURE - Configuration 1
1) Install the All ChargeCard hardware per instructions. Follow
the instructions VERY CAREFULLY.
2) Use the IBM PS/2 Model 30-286 or 50/60 Reference diskette move
the Packet Buffer RAM of the EtherLink/MC card to address
C000-C5FF.
3) Add
device=<path>\allemm4.sys /RAM /FR=NONE /X=C000-C5FF /EXT=64
line to config.sys. Do not load any network drivers high
at this time.
/RAM - tells allemm4 to find any available logical RAM between
640K and 1MB. On a '286 PS/2, VGA memory (A000-AFFF,
and B800-BFFF) is not available, neither is extra ROM
BIOS memory (in which there are no ROMS, thanks PS/2)
(E000-EFFF) is not available either. /RAM figures this
out all by itself.
/X=C000-C5FF - eXcludes the 24K RAM Packet Buffer area of the
EtherLink/MC card.This leaves the largest
contiguous area (104K) available (C600-DFFF).
**This parameter MUST match the RAM Packet
Buffer area assigned using the PS/2 Reference
Diskette.
/EXT=64 - Reserves the first 64K of extended memory (above
1MB) for use by himem.sys.
4) Install Windows/286, telling it that extended and expanded
memory are available.
5) Add remaining lines to config.sys and autoexec.bat per the
appropriate config and autoexec files. The first line of
config.sys MUST be "device=himem.sys". The second line of
config.sys MUST be the "device=<path>\allemm4.sys..." line.
The remaining "device =..." lines are in autoexec.bat. All
operating software includes its own "device," "files,"
"buffers," and "lastdriv" 'commands.' That is why these are
in autoexec.bat rather than config.sys.
The "alload" command loads drivers high.
3+Open only: In the \3open\doswksta\lanman\lanman.ini file,
find the line containing the "redir" command. Add to the
front of it the full path to the alload command:
i.e. \<path>\alload redir .....
6) At this point you may want to experiment with loading drivers
in different spots to obtain the best fit; you may also use
the PS/2 Reference Diskette to move the location of the
Packet Buffer RAM. Don't forget to change the /X:...
parameter of the "device=<path>\allemm4.sys..." line of
config.sys to reflect the new location. Use the alload,
device, or xexamem commands interactively with no parameters
to look at how memory is used.
Useful parameters to load drivers in different places are:
device /LM - loads driver into Low Memory (below 640K)
device /AF - Assigns (loads) driver into First available
segment
device /AT - Assigns (loads) driver into starting from the
end (Top) of available memory
alload (includes above parameters)
alload /SG:XX00 - loads driver into specified memory segment
(e.g. /SG:B000)
***Experiments have shown that spp.sys wants to be loaded
first using the /AF command. The order of the other device
drivers does not matter, but the included autoexec.bat were
designed to obtain the best fit.
INSTALLATION AND CONFIGURATION PROCEDURE - Configuration 2
1) Install the All ChargeCard hardware per instructions. Follow
the instructions VERY CAREFULLY.
2) Use the IBM PS/2 Model 30-286 or 50/60 Reference diskette move
the Packet Buffer RAM of the EtherLink/MC card to address C000-
C5FF. This leaves the largest contiguous area (104K)
available (C600-DFFF).
3) Add
device=<path>\allemm4.sys /RAM /FR=NONE /X=C000-C5FF
line to config.sys.
/RAM - tells allemm4 to find any available logical RAM between
640K and 1MB. On a '286 PS/2, VGA memory (A000-AFFF,
and B800-BFFF) is not available, neither is extra ROM
BIOS memory (in which there are no ROMS, thanks PS/2)
(E000-EFFF) is not available either. /RAM figures this
out all by itself.
/X=C000-C5FF - eXcludes the 24K RAM Packet Buffer area of the
EtherLink/MC card.
**This parameter MUST match the RAM Packet
Buffer area assigned using the PS/2 Reference
Diskette.
4) Add remaining lines to config.sys and autoexec.bat per
attached files. The first line of config.sys MUST be the
"device=<path>\allemm4.sys..." line. The remaining "device
=..." lines are in autoexec.bat. All operating software
includes its own "device," "files," "buffers," and "lastdriv"
'commands.' That is why these are in autoexec.bat rather than
config.sys.
The "alload" command loads drivers high.
3+Open only: In the \3open\doswksta\lanman\lanman.ini file,
find the line containing the "redir" command. Add to the
front of it the full path to the alload command:
i.e. \<path>\alload redir .....
5) At this point you may want to experiment with loading drivers
in different spots to obtain the best fit; you may also use
the PS/2 Reference Diskette to move the location of the
Packet Buffer RAM. Don't forget to change the /X:...
parameter of the "device=<path>\allemm4.sys..." line of
config.sys to reflect the new location. Use the alload,
device, or xexamem commands interactively with no parameters
to look at how memory is used.
Useful parameters to load drivers in different places are:
device /LM - loads driver into Low Memory (below 640K)
device /AF - Assigns (loads) driver into First available
segment
device /AT - Assigns (loads) driver into starting from the
end (Top) of available memory
alload (includes above parameters)
alload /SG:XX00 - loads driver into specified memory segment
(e.g. /SG:B000)
***Experiments have shown that spp.sys wants to be loaded
first using the /AF command. The order of the other device
drivers does not matter, but the included autoexec.bats were
designed to obtain the best fit.