home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 4 Drivers
/
04-Drivers.zip
/
1142a.zip
/
INSTALL.DOC
< prev
next >
Wrap
Text File
|
1994-06-21
|
28KB
|
980 lines
This read.me file covers installing the DigiBoard LAN Distance
driver on LAN Distance Servers and Remote Workstations.
- HARDWARE SUPPORTED
The driver supports the following DigiBoard Hardware products to
a maximum of 4 Host adapter cards and a maximun of 256 ports.
ISA Bus :
PC/16i, PC/8i, PC/16e, PC/8e, PC/4e, PC/2e, PC/Xem, and C/X.
EISA Bus :
PC/16i, PC/8i, PC/16e, PC/8e, PC/4e, PC/2e, PC/Xem, EISA/Xem,
C/X and EISA C/X.
MCA Bus :
MC/16i, MC/8i, MC/4i, MC/8e, MC/4e, MC/2e, MC/Xem, MC C/X
- HARDWARE INSTALLATION
Hardware installation should be done in accordance with the DigiBoard
Hardware Installation manual that you received with your DigiBoard
product.
You should choose a memory address and I/O port that does not conflict
with other devices in your system. You may address ISA and MCA bus
products up to the 16 Megabyte boundary if your computer does not
have system memory installed that high. On EISA computers, memory
addresses may be selected through the 4th Gigabyte range.
On MCA computers beware of configuring I/O ports in the 100 - 10f
range as they may conflict with POS I/O space.
- SOFTWARE INSTALLATION
The installation process consists of
1) Copying files to your \IBMCOM\MACS directory.
2) Automatically Updating your CONFIG.SYS
3) Installing support for the DigiBoard driver under LAPS.
4) Configuring the LAN Distance product to use the DigiBoard ports.
5) Manually Updating your CONFIG.SYS
* STARTING THE INSTALL PROCESS
This process will begin when you run INSTALL.CMD found on the Digi-
Board driver diskette. Insert the diskette into a floppy drive on
your system and make that drive the current drive. Then simply type
INSTALL < LAN Distance Drive: > [< CONFIG.SYS Drive: >]
where
< LAN Distance Drive: > is the drive LAN distance is
installed on.
[< CONFIG.SYS Drive: >] is the drive where your CONFIG.SYS
is located. If it is the same a the LAN Distance Drive,
you may omit this parameter.
* Step 1 : COPYING FILES
Several files will be copied to your C:\IBMCOM\MACS directory. These
files are as follows :
DGAFGP.OS2
DGPOLLER.EXE
*.BIN
* Step 2: AUTOMATICALLY UPDATING CONFIG.SYS
The next action that the INSTALL.CMD script will perform is to
update your CONFIG.SYS with the following lines :
rem DigiBoard PC/16e, PC & MC/8e, 4e, 2e, and PC/Xi
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:320
rem DigiBoard MC/16i, MC/8i, MC/4i
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:C0000 /P:F1F0
rem DigiBoard PC/Xem, MC/Xem
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:324 /T:P
rem DigiBoard EISA Xem, slot 3
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:3005 /T:P
rem DigiBoard ISA C/X 1 concentrator
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:328 /T:I10
rem DigiBoard EISA C/X 1 concentrator, slot 3
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:3005 /T:E10
rem DigiBoard Micro Channel C/X 1 concentrator
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:328 /T:M10
RUN=C:\IBMCOM\MACS\DGPOLLER.EXE
Note : Several of the lines a remarked out and thus inactive. This
will be dealt with in the last part of the install process.
* Step 3 : LAPS INSTALLATION
Next, LAPS will be run to install the DigiBoard MAC driver so that
the DigiBoard ports will be available to LAN Distance. This will
require some minimal user interaction. When LAPS is run you will see
a LAPS screen with the following options :
Install Configure Remove Exit Help
* You should click on the "Install" option.
When you do, you will see a box titled "Install Additional Network
Drivers" and a dialog box where you should indicate the source drive.
* Enter the drive letter in which the DigiBoard Driver Diskette is
located and click on "OK".
At this point, more files will be transfered and you will be notified
that the installation is complete and that LAPS has successfully
installed the "DigiBoard Communication Ports".
* Click "OK" again.
You will return to the first LAPS screen you saw.
* Click "Exit"
You will see another dialog box titled "CONFIG.SYS Updates"
* Click "Exit" again.
You will see the final LAPS message informing you that you are
"Exiting LAPS".
* Step 4 : CONFIGURING THE LAN DISTANCE PRODUCT
After INSTALL.CMD finishes, you will be required to configure
LAN Distance for the DigiBoard Ports you wish to use. The
configuration process is virtually the same for a Server or a
Remote Workstation.
* Start LAN Distance
* From the "LAN Distance - Workstations" Box
Select "Selected" from the menu bar.
Select "Open As ->".
Select "Settings".
* From the "MyWorkStation - Settings" Box
Select "Ports" Tab.
Push "Add..." Button.
Highlight "OEM DigiBoard Communications Ports".
If this option is not shown, you have not properly
installed the DigiBoard Driver using LAPS in Step 2.
You should go to an OS/2 command prompt and run
\ibmcom\laps, or click on the "OS\2 System" icon
and run LAPS from the "System Setup" folder.
Push "OK..." Button.
* From the "DigiBoard Communications Ports - Settings" Box
Push "LAPS" Button.
* You are now in the "Configure Workstation" Box in the "LAN Adapter
and Protocol Support Settings" window.
Scroll Down the "Network Adapters" List and highlight the
"DigiBoard Communications Ports" selection.
Press the "Add" button.
Make sure that the "DigiBoard Communication Ports..." entry
has been added and highlighted in the "Current
Configuration" window.
Press the "Edit" button.
Enter a new Portname if the default name "DIGI1" is not to
your liking. If there is an error with the name you
choose, LAPS will warn you. Be sure to use different
names if adding more than one port.
Press the "OK" button when finished.
You must repeat this process for each DigiBoard Port you wish
to add.
Press the "OK" button to exit.
If you are configuring a LAN Distance Server you may get an
error message upon attempting to exit. The message will say
something like
"All LAN Adapter and Protocol Support combinations
in the Current Configuration must contain at least
one protocol driver."
Click on the "OK". Most likely, the problem lies with the
entry that looks like this :
LAN Distance Logical Adapter ....
[BRIDGEFH]....
1 - [SR_BRIDGE]
You may highlight these lines one at a time starting with
the last line and press the "Remove" button. These are
entries in your \ibmcom\protocol.ini file that are inserted
by LAN Distance but apparently not liked by LAPS. Removing
them will cause no harm because LAN Distance will reinsert
them before you exit. Now you may press the "OK" button to
exit without further ado.
* Now, back in the "DigiBoard Communications Ports - Settings" Box,
Double-Click on the box's upper left hand corner button to
close it.
* Now, you should be back in the "MyWorkStation - Settings" Box and
should see the "DigiBoard Communication Ports" entry in the
"Configured ports" window. If this is the case, you have success-
fully added your DigiBoard ports.
* You are now ready to complete the LAN Distance configuration to your
liking. This will include assigning modems to each port you added,
as well as setting up "Dial" and "Answer" parameters and making
"Phone Book" entries using the "MyWorkstation - Setting" tabs.
Please refer to your LAN DIstance documentation for information on
these topics.
****
When you have finished configuring LAN Distance, you MUST shut down
LAN Distance and save the settings.
****
* Step 5 : MANUALLY UPDATING CONFIG.SYS
Finally the time has come to update your CONFIG.SYS file to indicate
the type of DigiBoard you will be installing. Using your favorite
editor, bring up your CONFIG.SYS file. Near the bottom of the file
you will see the following entries that have been made.
rem DigiBoard PC/16e, PC & MC/8e, 4e, 2e, and PC/Xi
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:320
rem DigiBoard MC/16i, MC/8i, MC/4i
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:C0000 /P:F1F0
rem DigiBoard PC/Xem, MC/Xem
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:324 /T:P
rem DigiBoard EISA Xem, slot 3
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:3005 /T:P
rem DigiBoard ISA C/X 1 concentrator
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:328 /T:I10
rem DigiBoard EISA C/X 1 concentrator, slot 3
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:3005 /T:E10
rem DigiBoard Micro Channel C/X 1 concentrator
rem DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /M:D0000 /P:328 /T:M10
RUN=C:\IBMCOM\MACS\DGPOLLER.EXE
DEVICE=C:\IBMCOM\MACS\DGANDIS.OS2
Your task will be to uncomment and modify one of the "rem"ed "DEVICE="
lines to indicate the type and configuration of the DigiBoard you will
be installing. The lines that have been added to you CONFIG.SYS are
examples of typical configurations for the various DigiBoard products
supported by the LAN Distance Driver. One of these entries may very
well match the configuration you are using, in which case you need to
just delete the "rem" statement in front of that entry. Once you are
satisfied with your entry, you may delete the other entries or you
may leave them as is for future reference.
Below is information on how to determine the entry you need to make :
All DigiCHANNEL intelligent asynchronous serial communications boards
must be installed from a single command line, which contains complete
set-up information for each board. The format of the command line is:
DEVICE=[d:][Path]DGAFGP.OS2 /a:a /m:mem /p:port /t:card
[,/m:mem /p:port /t:card ]
[, ...]
The above command line must appear on a single command line in the
CONFIG.SYS file. This line may be up to 255 characters long.
* Global Parameter.
This type of parameter affects all boards installed. These parameters
are optional, and may be omitted. If omitted, default values will be
used.
- Parameter /a:a
Enable the alternate pin assignment of Data Carrier Detect
(DCD) for all ports. Alt-Pin is a feature that swaps the
meaning of the DSR and DCD input pins on each DigiBoard port.
This is useful when using an 8-pin RJ-45 plug in a DigiBoard
10-pin RJ-45 jack. In this configuration, pins 1 and 10 in
jack are not accessible to the 8-pin plug. Pin 10 is DCD and
very useful when attaching to a modem. Enabling the Alt-Pin
option causes the DigiBoard driver to interpret pin 2
(usually DSR) as DCD and pin 10 (usually DCD) as DSR. In
order to use this feature, your cables must be made to run
the real DCD signal into pin 2 of the DigiBoard jack (pin 1
on the 8-pin plug).
* Per-Card Parameters.
The remaining three parameters are per-card parameters, and are used
to inform the driver of the type of board and where it is to be
addressed in the hosts I/O and memory buses. These parameters are
mandatory, and must be given for each board! The per-card parameters
must be given in complete sets, and the sets must be separated by
commas.
- Parameter /m:mem
Dual-ported memory starting address. This is the full
32-bit hexadecimal address of the beginning of the boards
dual-ported memory.
/m:d0000 Sets dual-ported memory start address to
0D0000h (in the BIOS expansion area between
640K and 1 megabyte).
/m:e80000 Sets start address of E80000h (in the
fifteenth megabyte). EISA and ISA boards
may all share the same memory starting address.
Micro Channel boards must each have unique
memory addresses.
- Parameter /p:port
Defines the I/O port address for the card.
/p:300 Board is addressed at I/O port 300h.
/p:2005 EISA board (EISA C/X or EISA/Xem host adapter)
is in slot 2 (EISA I/O addresses are 4
digits : the slot number, followed by 005).
When plugging an ISA board (PC/Xe, ISA
C/X host adapter, etc.) into an EISA
machine, the /p parameter must contain the
3-digit I/O address as set by the DIP switches
on the board, and not the 4-digit address
based on the EISA slot number.
- Parameter /t:card
Defines the card type to the driver. Legal values for card are:
i for the ISA C/X,
e for the EISA C/X,
m for the MC C/X,
p for Xem (PC/Xem, MC/Xem or EISA/Xem)
This parameter must be omitted for PC/Xe, PC/Xi, MC/Xe and MC/Xi
boards. The designators i, e, and m must be followed by an
additional two digits defining the number and arrangement of
DigiCHANNEL C/CON-16 or C/CON-16e concentrators on each host
adapter channel. If the concentrator(s) are connected to the
host adapter via a dial-up or leased line (remote concentra-
tors), each of the two digits must be followed by a parameter,
enclosed in parentheses, specifying the synchronous commun-
ications mode to be used for that line. See below for a list of
available synchronous communications modes.
/t:i10 ISA C/X, one local concentrator on line 1 only.
/t:e11 EISA C/X, one local concentrator on each of
lines 1 and 2.
/t:m21 MC C/X, two local concentrators on line 1 and
1 on line 2.
/t:e12 EISA C/X, one local concentrator on line 1,
and two on line 2.
/t:i22 ISA C/X, two local concentrators on each of
lines 1 and 2.
/t:p PC/Xem, MC/Xem or EISA Xem
/t:i2(21)3(27)
ISA C/X, two remote concentrators on line 1,
and two remote concentrators on line 2.
The concentrators on line 1 will use mode
#21 (76,800 baud, 8-wire, external clock) to
communicate with the host adapter, and the
concentrators on line 2 will use mode #27
(614,400 baud, 8-wire, internal clock). See
below for a list of synchronous communications
modes.
C/X Synchronous Communicatio Modes
----------------------------------------------------
| 8-Wire 8-Wire 4-Wire |
| Internal Clock External Clock Self-Clock |
----------------------------------------------------
| Mode Baud Mode Baud Mode Baud |
|---------------------------------------------------
| |
| 0 115k 15 2400 1 230k |
| |
| 3 2400 16 4800 2 460k |
| |
| 4 4800 17 9600 |
| |
| 5 9600 18 19.2k |
| |
| 6 19.2k 19 38.4k |
| |
| 7 38.4k 20 57.6k |
| |
| 8 57.6k 21 76.8k |
| |
| 9 76.8k 22 115k |
| |
| 10 115k 23 230k |
| |
| 11 230k 24 460k |
| |
| 12 460k 25 920k |
| |
| 13 920k 26 1.2M |
| |
| 14 1.2M |
| |
| 29 614k |
| |
| 30 737k |
| |
| 27 614k |
| |
| 28 737k |
| |
----------------------------------------------------
* Examples
The following examples start out with just the minimum to install a
DigiCHANNEL board. After locating an example for your type of board,
read the rest of the examples for optional situations that may be
appropriate to your application. Default options will be altered by
LAN DIstance.
Example 1:
PC/Xe, PC/Xi One PC/Xe (or PC/Xi) at I/O port 220h, memory address
D0000h.
DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /m:d0000 /p:220
Example 2:
MC/Xi One MC/Xi at I/O port F1F0h, memory address FC0000h.
DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /m:FC0000 /p:F1F0
Example 3:
Two board installation with Alt-Pin optional global parameter.
Two PC/Xe or PC/Xi boards at I/O ports 320h and 300h, with
dual-ported memory of both starting at D0000h.
DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /a:a /m:D0000 /p:320,
/m:D0000 /p:300
(Note that the above must all appear on one line in CONFIG.SYS)
Example 4:
Two board installation with Alt-Pin optional global parameter.
One MC/Xe and one MC/Xi boards at I/O ports F1F0h and 320h, with
different (can't be the same) dual-ported memory addresses. Alt-Pin
enabled.
DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /a:a /m:C0000 /p:F1F0,
/m:C8000 /p:300
(Note that the above must all appear on one line in CONFIG.SYS)
Example 5:
PC/Xem One PC/Xem at I/O port 224h, memory start address C8000h;
DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /m:C8000 /p:224 /t:p
Example 6:
ISA C/X One ISA C/X host adapter at I/O port 228h, memory address
D0000h, with one concentrator on line 1 and two on line 2.
DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /m:d0000 /p:228 /t:i12
Example 7:
EISA C/X with a remote concentrator via an RS-232 synchronous modem.
One EISA C/X host adapter in slot 3, memory address D8000h, with two
local concentrators on line 1 and one remote concentrator at 9600
baud and external clocking on line 2.
DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /m:d8000 /p:3005 /t:e21(17)
Example 8:
MC C/X and MC/Xem One MC C/X host adapter at I/O port 228h, memory
address D8000h, with one concentrator on line 1 and one concentrator
on line 2; one MC/Xem at I/O Port 304h, memory address D0000h.
Alt-Pin enabled
DEVICE=C:\IBMCOM\MACS\DGAFGP.OS2 /a:a /m:d8000 /p:228 /t:m11,
/m:d0000 /p:304 /t:p
(Note that the above must all appear on one line in CONFIG.SYS)
- DRIVER LOAD
As you may have noticed from the CONFIG.SYS file, the DigiBoard LAN
Distance driver is made up of 2 drivers. One driver that interacts
with the Protocol driver (DGANDIS.OS2) and one driver that interacts
with the hardware (DGAFGP.OS2). So when you boot your system, you
will see two drivers load. The order in which they load will follow
their order in the CONFIG.SYS file and should be DGAFGP.OS2 followed
sometime thereafter by DGANDIS.OS2, however, they can be loaded in
either order.
Loading DGAFGP.OS2 -
When this driver loads, it's primary goal is to find the DigiBoard
hardware specified on the "DEVICE=" line in CONFIG.SYS, initialize
it, and assure that it is functional. The driver displays the banner
shown below when the driver loads successfully.
-----------------------------------------------------------
| DigiBoard ANDIS Intelligent Board Driver V 0.0.1 |
| DGAFGP.OS2 Copyright (C) 1994 |
| All Rights Reserved. |
-----------------------------------------------------------
-----------------------------------------------------------
| RESTRICTED RIGHTS LEGEND: |
| Use, duplication, or disclosure by the Government is |
| subject to restrictions set forth in sub-paragraph (c) |
| (1) (ii) of the Rights in Technical Data and Computer |
| Software clause at DFARS 252.227-7013. |
| |
| Digi International Inc. d/b/a DigiBoard, 6400 Flying |
| Cloud Drive, Eden Prairie, MN 55344 |
-----------------------------------------------------------
-----------------------------------------------------------
| Board Type I/O Address Memory Address Channels |
-----------------------------------------------------------
PC/Xem 324 0x000D0000 16
If there are any errors encountered as the driver loads, error
messages will be posted to alert you of the condition and OS/2
should stop the boot process and prompt you to continue.
Possible error messages include :
* CONFIG.SYS errors
"Incomplete specification: need IO port AND memory for each board."
"Unexpected character: "
"Too many boards: Only 4 Intelligent boards supported."
"Unknown value assigned"
"Multiple IO port specifications: (/p:_)"
"Duplicate IO port address specifications: (/p:_)"
"Invalid IO port address specification: (/p:_)"
"Multiple memory address specifications: (/m:_)"
"Invalid memory address specification: (/m:_)"
"Invalid board type code: (/t:_)"
"No DigiBoards Specified on command line"
"Invalid Command Line Arguments"
"Zero DigiBoards Configured"
"Too many channels: maximum = 256"
- Cause & Remedy
The driver has encountered the specified error as it was parsing the
CONFIG.SYS "DEVICE= line". You should check your CONFIG.SYS for
accuracy.
* Hardware Errors
"Failed to RESET the I/O PORT"
"IO Port Not Responding"
"Failed Shared Memory Test near OFFSET: 0xXXXX"
"Failed to write to shared memory"
- Cause & Remedy
There is a memory or I/O port conflict with an other device in your
system or you have a defective board. Try a different I/O port or
memory address.
* FEP and BIOS Binary file problems
"Invalid DATA FILES DIRECTORY"
"Failed to locate data files"
"Failed to STAT file"
- Cause & Remedy
These messages usually occur while the driver is attempting to locate
and open the *.bin files for download to the DigiBoard card. First,
make sure that the *.bin files on your driver diskette have been
copied to the \ibmcom\macs directory. If they are there, you may need
to recopy them from the driver diskette in case a file was corrupted.
If this fails to remedy th condition, you may need to add another
command line argument to your "DEVICE=" statement in the CONFIG.SYS
file. The argument is " /f:<path to *.bin files> ". This tells the
driver where the files are located. If the errors persist, you may
have a conflict with the DigiBoard hardware and your disk controller.
Move the DigiBoard to another I/O port and memory address.
* DigiBoard Initialization Errors
"Failed to BOOT the BIOS"
"Failed to BOOT the uploaded FEPOS"
"Failed to Read Initialization Information"
"DigiBoard FEPOS will not execute commands"
"DigiBoard BIOS Will Not Boot"
"DigiBoard BIOS Will Not Respond"
"DigiBoard FEPOS Will Not Boot"
"Unknown Fatal Error"
- Cause & Remedy
These messages usually indicate problems initializing the card's on-
board software and are usually the results of a memory conflict with
another device in your system, a corrupt *.bin file, or a faulty
board. First, recopy the *.bin files from your driver diskette and
reboot your system. If this doen not work, relocated your board to
another I/O port and/or memory address. If none of this works, you
may have a bad board.
* OS/2 System Errors
"System Cannot Allocate Memory"
"Driver Failed to hook Timer",
"System Cannot Allocate Ctx Hook",
"Failed to make upload FILE memory"
- Cause & Remedy
Chances are your system resources are depleted. Try unloading any
unnecessary drivers to see if the problem goes away. If this doesn't
work, get a bigger computer!
* Possible Hardware problems
"Zero channels installed."
- Cause & Remedy
This usually means that the card's on-board code could not locate
any ports. Usually you will see this message with the Xem and C/X
products when you forget to connect the EBI or concentrators. Check
this to see if that may be the case. Other wise you may have a faulty
card.
Loading DGANDIS.OS2 -
When this driver loads, it's primary goal is to determine the LAN
Distance ports you have configured using LAPS, and register these
with the protocol driver. The driver internal tables and memory
are also allocated and initialized. The driver displays the banner
shown below when the driver loads successfully.
-----------------------------------------------------------
| DigiBoard Intelligent Board ANDIS MAC Driver V 0.0.1 |
| DGANDIS.OS2 Copyright (C) 1994 |
| All Rights Reserved. |
-----------------------------------------------------------
Installing DGANDIS
Initializing port: DIGI1
Initializing port: DIGI2
DGANDIS is installed
If the driver encounters an error while loading, one of the following
messages will be displayed. Since this driver does not initialize
any hardware the sources of error are usually software in nature
and fairly difficult for you to remedy but some suggestions may help.
* Driver Registration Problems
"Can not open PROTMAN"
"PROTMAN returns error on config read"
"Register port to PROTMAN returns Failure"
"DosDevIOCtl Fails on register to PROTMAN"
"PROTMAN does not support PPAT"
"PPAT registration Failed"
"DosDevIOCtl Failed on GetPMInfo"
- Cause & Remedy
PROTMAN.OS2, the protocol manager, and the driver are having some
interaction difficulties. First, check to see that a
"DEVICE=PROTMAN.OS2"
statement is in your CONFIG.SYS file. Try recopying the DGANDIS.OS2
driver from the driver diskette. Also, you may have a wrong version
PROTMAN.OS2.
* PROTOCOL.INI Problems
"ProcessKeyWords Failed"
- Cause & Remedy
Check to see that your \ibmcom\protocol.ini file has a "PORTNAME="
line under [DGANDIS_nif] entry.
* OS/2 System Errors
"DGANDIS Failed to install"
"Internal Error"
"AllocPhysMem Failed"
"AllocGDT Failed"
"Phys2GDT Failed"
"VirtualAddr Failed"
"AllocSpareGDT Failed"
- Cause & Remedy
Chances are your system resources are depleted. Try unloading any
unnecessary drivers to see if the problem goes away. If this doesn't
work, get a bigger computer!