Networking Real/32 to a Windows
This can be achieved using the IPX protocol by:
Windows NT Client for DOS can also be used to connect Real32 to
other Windows systems (it has been
used to connect to 95/98 & NT
workstations but may also work on ME
Connecting to Windows NT Servers.
Connecting REAL/32 DOS sessions to a Windows NT server
be done in one of two ways.
Using the NetWare Client
To use the NetWare Client supplied, it is necessary to
Windows NT services for NetWare on your Windows NT Connectivity
Windows NT services for NetWare is a Microsoft product designed to make a
Windows NT server compatible with existing NetWare Clients on the network. It is
available from any Microsoft distributor.
NetWare Client software as you would for connecting to a true NetWare Server.
This is described in the section Connecting to NetWare Servers in the
R32CONF.PDF file on the Real32 CD.
Personal NetWare ®
intend to run multiple Personal NetWare client VLMs then you should follow the
above instructions as per connection to full NetWare.
Server and PNWSERVER.BAT
task for Personal NetWare should only be run in one DOS session. If you attempt
to run more than one copy of the server program REAL/32 will behave
The Personal NetWare server program is a terminate and stay resident program. If
you run the server in a DOS session that DOS Session should not be used for any
other task. The operating system may behave unpredictably if you do. You are
advised to run the Personal NetWare server in a phantom session. A program
called banner.exe has been included on the distribution disks to stop other
tasks from running on the server session.
following batch file example should be used for loading the server program. An
example of this batch file is located in real32\bin called nwserver.bat.
REM LSL.COM AND THE MLID ARE LOADED IN
Using Windows NT Client for
Note: This connection only works with the IPX protocol.
As well as supporting the NetWare Client, REAL/32 also
the native NT client. Before starting the installation
sure you can answer the following questions:
is the NT Server Workgroup Name?
is the NT Server Workgroup Domain Name?
the Windows NT Server network adapter bound to the
Ask your network administrator if you are not sure.
Follow this procedure to install the Windows NT Client
for use with
i) Install the REAL/32 Connectivity Extension as
You will need to load the IFSHLP.SYS from the
file. Make sure the following line is the last entry in
ii) Reboot and ensure the ODI drivers are installed and
iii) Load the IPXODI driver from the command line:
iv) Format two floppy disks.
v) The Windows NT Client for DOS is available on your
NT Server CD-ROM usually in the directory:
Copy the contents of directories DISK1 and DISK2 to the
vi) Insert disk 1 into your floppy drive and run:
Follow the instructions on the screen for installation.
vii) At the SETUP menu select Change Network
Remove any existing protocols and adapters detected by the SETUP program.
Change Adapter and select IPX/SPX Support Driver from the list supplied.
selection is only possible if IPXODI is loaded before you run the SETUP program.
If the option is not accepted then restart REAL/32 and run IPXODI before running
SETUP from the floppies.
settings and return to the main menu. The NT Client must be set to use the
"BASIC" redirector. This can be done using the NT Client SETUP
program, Select "Change Setup Options" and set "Change ReDir
Options" to "Use the Basic Redirector". The alternative is to use
the "Full Redirector" which may result in an error message "error
1: an internal error occurred"
Configure the other parameters as required for your Windows NT SETUP. You may
need to consult your Windows NT documentation for information regarding
Workgroup names etc. Each REAL/32 DOS session will require a unique user name.
the changes and reboot.
the Windows NT Client is done from the command line by typing :
NET START WORKSTATION
bug in the MS NT Client software will cause the connection to time out. The way
to prevent this is to keep a file open at all times.