Mail Archives: opendos/1997/08/29/14:39:46
I got permission to post the readme from the new version of OD. Lots of
new things. Enjoy.
g.
---
OpenDOS 7.02 Release Notes
==========================
These release notes contain information about the following topics. This
information is NOT included in the OpenDOS User Guide or in DOSBook.
- Installing on systems running Windows 95
- Year 2000 support
- FDISK enhancements
- Windows 95 long filename support
- Using the NWCACHE delayed write mode
- Enabling CD-ROM drives
- Full-screen programs on non-standard VGAs
- Undeleting files across the network
- Configuring the EMM386 memory manager to increase EMS handles
- DOS Protected Mode Services (DPMS) loading order
- Task Manager - loading LOCK as a permanent task
- network drive mappings
- LAN Workplace for DOS support
- running 4DOS
- using the task switcher and server
- Setting up "one-time login"
- Connecting to NetWare 2 and 3 servers
- Using a network copy of MS Windows on the local server
- Increasing the number of file handles when required
- Using OEM-supplied network board drivers
- Running Personal NetWare with other networking products
- Modifications made to MS Windows .INI files by Personal NetWare
- Using remote computers on the network
- Enhanced NetWars Game
Installing on systems running Windows 95
========================================
The installation program for OpenDOS 7.02 can detect that Windows 95
is installed and automatically installs the Caldera OpenDOS dual boot
program "LOADER". When your computer is started, LOADER allows you to
select OpenDOS or your previous operating system, Windows 95. In dual
boot mode, OpenDOS reads configuration information from DCONFIG.SYS and
AUTODOS7.BAT.
Also, if Windows 95 is detected, the install program will not install any
Windows 3.x utilities which can cause problems when run under Windows 95.
NOTE. Never run STACKER, DISKOPT, CHKDSK, DISKMAP, DELWATCH, or
UNDELETE on disk volumes accessed by Windows 95. Use Windows 95
management tools only.
Year 2000 support
=================
The OpenDOS kernel will now correct any year 2000 problems you may have,
even if your BIOS does not support the year 2000.
Year 2000 support comes in two forms:
1. If the BIOS reports the year is 1900 - 1980, OpenDOS will set the century
to 20xx. For example, 1900 becomes 2000, 1917 becomes 2017 and so forth.
2. If OpenDOS is running at midnight on the 31st of December 1999, it will
still report the year 2000, even if the BIOS reports 1900.
FDISK enhancements
==================
FDISK has been greatly enhanced, and now has two modes of operation.
The default mode is STANDARD, which works in the same way as previous
versions and is the recommended way of using FDISK.
FDISK /x puts you into EXTENDED mode, which allows you to add and remove
non-DOS partitions.
FDISK will also display blocks of free space, and recognises many
partitions from different systems, such as Linux or BSD.
Windows 95 long filename support
================================
Windows 95 Long Filenames are stored in a non-standard disk format. If
you are using OpenDOS on a system which has been used by Windows 95,
you should not attempt to use the OpenDOS utilities DISKOPT, DELWATCH
or CHKDSK since these will misinterpret the Windows 95 file
directory entries. This could lead to a loss of data. OpenDOS will
otherwise work correctly with long filenames. Caldera is addressing
this issue and will update these utilities to work with long
filenames in a subsequent release of OpenDOS.
NWCACHE
=======
Delayed write mode is disabled as part of the default configuration
for NWCACHE. This is a safety feature to prevent loss of data if the
computer is switched off before disk writes have been completed. Enabling
delayed write mode will improve performance but you must make sure you do
NOT switch off your computer before all data is written to the disk. Do
this in one of the following ways:
1. Perform a "soft boot" (press Ctrl+Alt+Del) before switching the
computer off. A soft boot automatically flushes all pending data to
disk.
2. Wait beyond the delayed write time you specified, after the disk access
light goes out.
3. Wait for the system prompt to return (see below).
When delayed write mode is enabled, the cache is 'flushed' (all data is
written to the disk) BEFORE the system prompt returns, by default. This is
a safety feature. You can disable (or re-enable) this feature by specifying
the following option in the NWCACHE start-up or control command at the
system prompt:
/FLUSH=ON|OFF
If delayed write is enabled (on a computer that is running the Personal
NetWare server software), you can also save memory by setting the number
of I/O buffers to zero via the NET ADMIN program.
Using CD-ROM Drives
===================
To use a CD-ROM drive with OpenDOS, the device driver for your
CD-ROM drive must be loaded. CONFIG.SYS must include a DEVICE (or
DEVICEHIGH) statement that loads the appropriate driver (the one that
came with your CD-ROM drive). The DEVICE statement must include a
/D:drivername parameter, where drivername is the 'signature' assigned
to the driver.
OpenDOS includes the NWCDEX program to provide access to CD-ROM
drives. You can load NWCDEX at the system prompt or in the AUTOEXEC.BAT
file. Note that the device driver that came with your CD-ROM drive must
be loaded BEFORE you load NWCDEX (see previous paragraph).
Note: You can use MSCDEX to access CD-ROM drives, but using NWCDEX allows
you to use DPMS and saves memory.
The syntax of NWCDEX is as follows:
NWCDEX [/?|/H] /D:drivername [/E] [/L:letter] [/M:number] [/N] [/V]
/?|/H Displays help text.
/D:drivername Specifies the name of the CD-ROM driver. This name matches
the drivername specified in the DEVICE statement that loads
the driver.
/E Specifies the use of expanded memory (if available) when
DPMS is not available.
/L:letter Specifies the drive letter to assign to the CD-ROM drive.
The default is to use the first available (unused) drive.
/M:number Specifies the number of sector buffers to allocate. The
default is 14.
/N Disables the use of DPMS. By default, NWCDEX will use
extended memory if DPMS is not available.
/V Prints debug information during initialization.
Example
-------
The following examples show the appropriate statements in CONFIG.SYS and
AUTOEXEC.BAT to load and access a CD-ROM drive. In this example, the CD-ROM
driver supplied with the drive is CDROMDRV.SYS and it is to be accessed as
drive G:
in CONFIG.SYS:
DEVICE=C:\OPENDOS\CDROMDRV.SYS /D:NWCD000
in AUTOEXEC.BAT:
NWCDEX /D:NWCD000 /L:G
Full-Screen Programs and Non-Standard VGAs
==========================================
Some portable, laptop, and notebook computers with LCD or TFT displays
support a non-standard VGA text mode known as 'Expanded' or 'Stretched'
text. This mode 'stretches' the standard 80x25 (400 pixels high) text
mode so that it fills the entire physical screen which is 480 pixels
high. This mode, if used, may interfere with the enhanced text mode of
the full screen programs, such as NET ADMIN.
If you encounter problems, it is recommended that you disable the
'Stretched' text on your computer. Refer to the documentation for your
computer for information about CMOS setup configuration.
If you cannot disable this mode or prefer to keep 'Stretched'
mode enabled, you can disable the enhanced text mode of the full
screen programs in one of three ways:
1. By entering the name of the program followed by the /N switch
at the system prompt
2. By selecting to disable the enhanced text mode globally from within
the SETUP program
3. By editing the OPENDOS.INI file to change NewUI = ON to NewUI = OFF
Undeleting Files Across the Network
===================================
You can use UNDELETE to recover deleted files across the network on both
Personal NetWare, NetWare 2, 3, 4 and IntranetWare servers. To undelete a file from
a Personal NetWare server, the file must have been saved as a pending
delete file by DELWATCH and DELWATCH must have been run on the Personal
NetWare server prior to the file being deleted. Note that it is NOT
necessary to run DELWATCH on the client computer from which UNDELETE is
being run.
EMM386 Memory Manager
=====================
For applications that require more EMS/XMS handles, add the following
option to the EMM386 DEVICE statement in CONFIG.SYS to increase the
number of handles available:
HANDLES=n (where n is a number from 0 to 255)
DOS Protected Mode Services (DPMS)
==================================
Be aware that the DPMS driver must always be loaded before the software
that uses it (NWCACHE, SERVER.EXE, etc.).
Loading LOCK Permanently Under the Task Manager
===============================================
You can load LOCK as a permanent task under the Task Manager by
using the LOCK /P option with the TASKMGR /C command as follows:
TASKMGR /C LOCK password /P
where password is the password you use to unlock the system.
Network Drive Mappings under the Task Manager
=============================================
The Task Manager defaults to global NetWare drive mappings. Changes
made to drive mappings in one DOS session are duplicated to ALL DOS
sessions.
LAN Workplace for DOS Support under the Task Manager
====================================================
The Task Manager supports LAN Workplace for DOS. To enable it, you
must edit the TASKMGR.INI file. Uncomment the following two lines:
vxd=c:\lwfd\vtcpip.386
and
GlobalPages=2
Refer to the instructions contained in the TASKMGR.INI file for more
information.
Load the network drivers (including TCPIP.EXE) before loading the Task
Manager.
Running 4DOS under the Task Manager
===================================
To run 4DOS under the Task Manager (multitasker), you must edit the
TASKMGR.INI file to make the following change in the [Shell] section:
Exec=FALSE
to
Exec=TRUE
Using the Task Switcher and Personal NetWare Server
===================================================
If you are using the task switcher with the Personal NetWare server,
it is recommended that you add the following line to your NET.CFG file:
ALTERNATE CALLDOS = ON
One-time Login
==============
"One-time login" is a facility that allows a user to log in to both the
local computer and multiple network servers (and a workgroup) by entering
a username and password ONCE only.
One-time login works by remaking the network connections previously saved
in a local login script. When the login script is rerun, the one-time
login username and password are substituted each time they are requested
by a LOGIN command in the login script. One-time login requires that the
same username and password are used on all servers and the workgroup. By
default, the LOCK program also uses the one-time login password.
To use the one-time login facility, your computer must be configured so
that OpenDOS security is enabled and the Personal NetWare server
is loaded. A local user must be defined, as documented in the "Creating
and Modifying User Accounts" section of the "Setting Up the Network"
chapter in the OpenDOS User Guide and DOSBook.
To set up one-time login, do the following:
1. Reboot the computer.
2. You will be prompted for a username and password; enter the correct
username and password for the defined local user.
3. When you are logged in to the computer, you will be prompted to load
the network software; answer Y to this prompt.
You will be logged in to your workgroup automatically.
4. Make any required connections to other NetWare or IntranetWare
servers and map drives.
This is documented in the "Logging In" section of the "Using the
Network" chapter of the OpenDOS User Guide and DOSBook.
5. Save your current network settings to your local login script. This is
documented in the "Saving Connections" section of the "Using the
Network" chapter in the OpenDOS User Guide and DOSBook.
The next time you reboot your computer and log in, you will be logged
back in to the workgroup and servers automatically and drives will be
remapped automatically.
Connecting to NetWare 2 and 3 Servers
=====================================
If you experience difficulty connecting to NetWare 2 or 3 servers, ask
your system administrator to check that you have the correct Frame settings
for your network in NET.CFG.
Notes for Existing NetWare 2 and 3 Users
========================================
1. Do not use NETX.COM or related shells with Personal NetWare. The
Personal NetWare client gives you simultaneous access to NetWare 2, 3,
and 4 servers as well as Personal NetWare servers.
2. Path names must be less than 64 characters long. VLMs cannot support
a path name of more than 64 characters. To use longer paths, map a root
drive and continue from there.
Using a Network Copy of MS Windows on the Local Server
======================================================
If you run a network installation of MS Windows on your the local server
and you want to use that version of MS Windows at the server, you must map
a drive to the server and make sure that your path statement references
both the network copy of MS Windows and your own MS Windows directory.
Increasing the Number of File Handles
=====================================
If, as you run more applications and add more users, you encounter
problems running applications across the network, be aware that the
number of file handles allocated in the CONFIG.SYS file at the server
may not be sufficient. This may also be true when you are running the
server under MS Windows. An indication that this situation has occurred
would be getting unexpected "File not found" or "Directory not found"
error messages when doing a DIR command to a drive on that server.
The documentation for your applications should indicate the number of
file handles required per user; make sure that you allow the correct number
in the server's CONFIG.SYS, given the number of users running the
application and the number of times the application is run. If necessary,
change the FILES value. If a value greater than 255 is required, use
NET ADMIN to reconfigure the server so that it does not use the CONFIG.SYS
FILES value and set the required value.
OEM-supplied Network Board Drivers
==================================
To use a third-party network board driver that does not include a .INS
file, do the following:
1. Copy the driver file to the directory into which you installed
Personal NetWare. For example:
COPY A:\MYDRIVER.COM C:\NWCLIENT
2. Change to the Personal NetWare directory and rename the INS.OEM file
to xxxxxxxx.INS, where xxxxxxxx is the name of the driver file. For
example:
REN INS.OEM MYDRIVER.INS
3. Edit the new .INS file with an ASCII text editor and replace the two
references to 3RDPARTY.COM with the file name of your driver. The .INS
file looks like this:
InS_StArT
3RDPARTY.COM
1.0
^ Third Party Driver without .INS file,3RDPARTY.COM,IE0
!RIE0(INT)
2
@3
4
5
10
11
12
15
!RIE0(PORT)
@300
320
340
360
240
280
2C0
InS_EnD
4. Run SETUP. On the screen that allows you to choose the primary
network interface board, display the list of drivers and choose
'Third party driver without .INS file'.
5. Choose to accept the changes and continue, to confirm your choice.
Running Personal NetWare with Other Networking Products
=======================================================
The name (NET.EXE) of the Personal NetWare NET program is likely to
exist in other networking products. After you install OpenDOS with
Personal NetWare, the PATH command will cause the operating system to
search the NWCLIENT directory first. NWCLIENT contains NET.EXE. If you
want to use a different NET.EXE program, edit the PATH command so that
the appropriate directory is searched BEFORE the NWCLIENT directory.
Alternatively, you may find that if you install a different networking
product (or MS Windows), the PATH command is changed so that the NWCLIENT
directory is no longer searched first and a different NET.EXE program
is run instead of Personal NetWare NET.EXE. If you want the Personal
NetWare NET program to run, edit the PATH command so that NWCLIENT is
searched first.
Modifications to MS Windows INI Files
=====================================
When you install the MS Windows element of Personal NetWare,
the following files are modified automatically: SYSTEM.INI,
WIN.INI, and PROGMAN.INI.
The following modifications are made to SYSTEM.INI:
in the [boot] section: network.drv= is replaced by
network.drv=netware.drv
(This loads the NetWare user tools)
in the [boot.description]: network.drv= is replaced by
network.drv=Personal NetWare
(This defines which Personal NetWare
device version you are using)
in the [386Enh] section: network=dosnet is replaced by
network=*vnetbios;vipx.386;vnetware.386
(This specifies the type of network
used with MS Windows 386 Enhanced mode)
TimerCriticalSection= is replaced by
TimerCriticalSection=10000
(Personal NetWare uses this setting to
ensure that network traffic on your
computer runs smoothly)
ReflectDOSInt2A=TRUE is added.
OverlappedIO=OFF is added.
PSPIncrement=5 is added.
UniqueDOSPSP=TRUE is added.
The following modifications are made to WIN.INI:
in the [windows] section: load= is replaced by
load=nwpopup.exe
(This allows network messages to display
in MS Windows)
Netwarn=1 is added.
(If this is set but the network is not
loaded, MS Windows will display a pop-up
indicating that the network is not loaded)
The following modifications are made to PROGMAN.INI:
in the [groups] section: Groupx=C:\windows\pnw.grp is added to
the list of group files.
(This causes MS Windows to load the
Personal NetWare program group in
Program Manager).
Using Remote Computers on the Network
=====================================
For information about how to set up the network so that remote diskless
computers can boot from the Remote Boot disk image files stored on a
Personal NetWare server's hard disk, read the file called RPLDOC.TXT.
Advanced NetWars Game
=====================
Advanced NetWars has the following major new features over the original
NetWars shipped with Personal NetWare and Novell DOS 7:
1. Six players can now take part in the Multi-Player game.
2. There are computer controlled ships in the Multi-Player game, 1 per
player. So the maximum number of ships in a game is 12!. Computer
controlled ships can be disabled from the options menu.
3. The Multi-Player game now has a 'Shoot-Out' mode which forces all
players to start at the same time and prevents them from rejoining the
game once they have been killed. The last player alive is the shoot-out
winner. Shoot-Out mode is enabled from the options menu.
4. Players can fire missiles in the Multi-Player game.
5. Shape editor software is included (see NWDRAW.EXE). Players can
design their own ship using the shape editor, save it as a file,
then load it into the Multi-Player game from the options menu. Help
for the shape editor is included.
6. There is support for Sound-Blaster compatible sound cards.
7. There is support for Joystick control.
8. The Single-Player game has been enhanced. Play it to find out more!
9. Players can see external views of their ship in the control panel by
pressing the F1 key during a game.
- Raw text -