NetWare v3.11
Undocumented Features
Special Warning About Redirection Blocks
========================================
If you ever see a system message warning you that the server is
low on redirection blocks, WARN USERS TO SAVE TO A LOCAL DRIVE
and then DOWN THE FILE SERVER. The system message indicates your
disk drive is on the verge of failure. Back up all the drive's
data and reinitialize the drive.
System Administration Manual
============================
Changed SET parameters:
The default for Maximum Physical Receive Packet Size was
changed from 1130 to 1514 (page 251).
The default for Maximum Extended Attributes Per File or Path
was changed from 32 to 8 (page 255).
The minimum value for Delay Between Watchdog Packets was
changed from 1 second to 10 seconds (page 250).
New SET parameters (add to page 250):
Reserved Buffers Below 16 Meg: 16 (8-200)
(Setable only in STARTUP.NCF file)
This sets the number of cache buffers to be kept for
device drivers unable to access memory above 16
megabytes.
Reply To Get Nearest Server: ON (ON/OFF)
When set to ON, the server responds to GET NEAREST
SERVER requests from workstations that are attempting
to locate a server.
Display Incomplete IPX Packet Alerts: ON (ON/OFF)
(Also setable in STARTUP.NCF)
When set to ON, the file server displays alert messages
when IPX receives incomplete packets.
Clarified SET parameters:
Minimum File Delete Wait Time (page 275):
This parameter controls automatic purging of deleted
files. Manual purging of deleted files by a user is
not affected by this SET parameter. The file server
will automatically purge a deleted file when the
following three conditions are met:
o It is the oldest deleted file.
o The volume is out of disk space.
o The file has been deleted at least the amount
of time specified by the SET parameter
"Minimum File Delete Wait Time."
Maximum Outstanding NCP searches (page 290)
DOS only allows for a maximum of 32K directory entries
per volume. This is also true for NetWare v2.x. This
is because a 16 bit file handle is used (signed 16 bits
will give only 32K). NetWare v3.x, however, offers a
maximum of 2 million directory entries per volume.
Therefore, it is necessary for the v3.x OS to maintain
a table to map the DOS 16 bit requests to the NetWare
v3.x 32-bit directory entries. This table is used
during DOS Find Firsts, Find Nexts, File Opens, and
directory scans for file information.
When any of these searches is initiated by a program at
the workstation, an entry is placed into this table and
is only released if the exact file name is specified,
the workstation issues an End Of Job or the workstation
finishes Find Nexts by reaching the end of the
directory. Each time a workstation initiates a Find
First, an entry is placed into this table in NetWare.
The default table size is 51 entries and can be
increased using the "Maximum Outstanding NCP Searches"
settable parameter. Increasing this table uses server
memory, since each entry is 24 bytes and there is one
table per each connection. This means with the table
size set to 100 and with 250 workstations logged in,
that the server will set aside 600K of memory for the
NCP search tables.
DOS applications which do not handle file searches
cleanly can fill up this table and possibly result in a
warning message broadcast from the server of "You
exceeded your outstanding NCP directory search limit".
If this occurs, information has been lost about one or
more of the initiated (but not yet completed) file
searches. The result to the application is usually
that "File Not Found" may be returned by the server
when in reality it does exist.
New tracked resource displayed in MONITOR (page 479):
Cache Memory Below 16 Meg (Bytes): This is the amount of
cache memory kept below 16 Megabytes, for hardware adapters
unable to access memory above 16 megabytes.
LAN driver not listed in System Administration manual:
TOKENDMA.LAN. See the NetWare Installation Supplement for
IBM Token-Ring Network for more information.
Load switches for ISADISK.DSK (page 111):
Due to inconsistencies in ISA disk controllers we have
implemented some command line parameters to support a small
subset of these controllers.
/b BIOSOnly: This command line parameter will cause the
driver to use only the system BIOS in scanning for a
drive type. The driver will not scan for NetWareReady
and CCM (Novell's Common Configuration Method). This
parameter can be typed anywhere on the command line
following the driver name.
SYNTAX:
load isadisk /b
or load isadisk port=<PORT#>, int=<INT#>, /b
/l Low drive table: This command line parameter is used
for systems that want to use a secondary controller
that does do not have the BIOS in the system located
above 0F000. This will allow the driver to look for a
drive table down to 0C800.
Use this option with caution, since using it with a
machine that has an incomplete drive table could cause
the drives to be registered incorrectly. Incorrectly
registered drives will produce unpredictable results.
Since some machines or controllers support only one
table entry instead of a whole contiguous table,
Novell's suggested method to solve this problem is
either NetWare Ready or CCM. This parameter can also
be typed anywhere on the command line following the
driver name.
SYNTAX:
load isadisk /l
or load isadisk port=<PORT#>,int=<INT#>, /l
PCN2LRPL.NLM not shipped (page 208):
PCN2LRPL.NLM was documented in the System Administration
manual, but is not included in the product. PCN2LRPL.NLM
and PCN2L.RPL will be available on NetWire.
PCN2.LAN changed to PCN2L.LAN (pages 124, 138, and 469):
The PCN2L LAN driver is documented incorrectly in the System
Administration manual as PCN2. Change the references from
PCN2 to PCN2L.
Ethernet LAN drivers and large packet sizes:
If your network uses either TCP/IP or OSI stacks and large
packets (greater than 1506 bytes) with any Novell Ethernet driver
using Ethernet frame type 802.2 or 802.2 SNAP, you must increase
the default Maximum Physical Receive Packet Size to 1530.
Otherwise, the file server will not receive the packets and the
No ECBs Available count will increment.
New PCN2L LAN driver statistics shown in MONITOR (pages 469 and
470):
BadReceiveConditionCodeCount: Indicates the number of times
the driver receives a condition code from the hardware that
is unrecognizable. You can expect this counter to
increment, although it should not increment rapidly.
TotalCollisionCount: This count is the number of times the
PCN2 card tried to start a transmit and found the line busy.
This counter indicates no problem in itself, and may
increment in normal operation.
MaxCollisionCount: This is a count of the number of times
the card gave up on a transmit because of too many
collisions. This is not a serious problem, since the driver
retries the transmit.
HardTransmitErrorCount: This counter increments each time
the driver gives up and the transmit actually fails. This
counter indicates a real problem on the network.
UnsupportedMediaPacketCount: This counter was incorrectly
documented in the System Administration manual (p. 470) as
UnsupportedFramePacketCount.
RCONSOLE (page 374)
If you are copying SYSTEM and PUBLIC files using RCONSOLE,
subdirectories are automatically created. This is an
undocumented feature.
NetWare Installation Supplement for IBM Token-Ring
==================================================
The Supplement refers to the DOWNLOAD.COM file on page 81,
used to transfer microcode to the adapter board. The file
is actually called FIRMLOAD.COM. Therefore, change all
references on page 81 from DOWNLOAD.COM to FIRMLOAD.COM.
Installation Manual
===================
Running INSTALL.NLM on a v2.x partition
There is a known problem when running INSTALL.NLM against a
drive that already has a NetWare v2.x Partition on an IBM
ESDI or SCSI disk. The partition editor in INSTALL will
inform you that the partition is invalid and ask if you want
to create a new v3.x partition. If you answer "YES", the
v2.x partition will be lost and a v3.x partition created. If
you answer "NO" then the v2.x partition will be left intact.
This ONLY affects the IBM PS2 SCSI and ESDI drives. In all
other cases, the v3.x partition editor will show that a
valid pre-NetWare v3.0 partition exists on the drive. If
there is no additional free space, INSTALL will indicate
that the pre-NetWare v3.0 partition MUST be deleted before a
v3.x partition can be created.
UPGRADE.EXE warning:
If you have two working directories and only one destination
directory specified, both working directories will restore
to the same destination directory. This potentially could
result in older files overwriting newer ones.
INSTALL option (page 142):
The "J" option allows you to load SYSTEM and PUBLIC files
from a drive other than A:. Use the "J" option as follows:
LOAD INSTALL J <Enter>
The "J" option affects INSTALL when you select "Copy System
and Public Files." The operating system checks the default
drive for directories corresponding to diskette names.
If the directories are found, the path is displayed for
reading files. At that point you may:
o Press <Esc> to abort
o Press <Enter> to continue
o Press <F6> to specify a different source drive or
directory.
If the directories are not found, you are prompted to insert
the SYSTEM-2 diskette.
Login script feature (Appendix A)
The login script identifier table does not show the
SHELL_TYPE identifier option. A use of SHELL_TYPE might be
as follows:
IF SHELL_TYPE != "V3.02" THEN WRITE "DO YOU WANT TO RUN
WSUPDATE?"
Upgrading a server with NetWare Name Service (NNS) (page 98):
After installing NetWare 3.11, you must recopy the NNS
utilities SETPASS (UTILITIES_3), LOGIN (UTILITIES_2), ATTACH
(UTILITIES_1), USERDEF (UTILITIES_5), and MAKEUSER
(UTILITIES_2) from the original NNS diskettes to your file
server.
Upgrading a file server that contains an ISA disk controller:
If you are upgrading a file server that contains an ISA disk
controller, you should be aware that configuration options 0
and 1 are reversed in NetWare v3.11. Configuration option 0
now sets verification off, and option 1 sets verification
on.
Most ISA controllers built since 1986 automatically verify
disk transactions. Therefore, it is no longer necessary to
make the system perform that task. Consult the
documentation for your ISA disk controller to see if it
automatically verifies disk transactions.
System Messages Manual
======================
The System Messages manual occasionally contains the
following action statement: "See the information on
consistency checks at the beginning of this document." Use
the following instructions instead:
Action: Complete one or more of the following.
o Reboot the file server.
o Use INSTALL to reinstall the operating system.
o Check the system board, memory, memory chips,
power supplies, and power conditioning equipment.
Replace any faulty hardware. o If new hardware has been recently installed in the
file server, remove the hardware. If the error
does not recur, run diagnostics on the removed
hardware. Check for conflicts (interrupts, memory
addresses, I/O ports, DMA) between the hardware in
the computer and the new hardware.
o If the error persists, record all the hardware
installed in the file server and all actions you
have taken to correct the problem. Then contact
your Novell Service Representative.
NetWare ODI Shell for DOS
=========================
Remote Program Load for DOS ODI:
If you wish to use DOS ODI and need RPL capabilities,
you must include the RPLODI.COM module in your
workstation RPL image. RPLODI.COM is located on the
WSGEN diskette under the DOSODI subdirectory.
RPLODI.COM must be loaded immediately after the LSL.COM
module and before any ODI LAN drivers are loaded. An
example AUTOEXEC.BAT file for an IPX/NCP workstation
boot image is as follows:
PROMPT $P$G
LSL.COM
RPLODI.COM
NE1000.COM
IPXODI.COM
NET3.COM
RPLODI.COM does not affect the amount of memory
available for applications. In most cases, you can
remotely load protocol suites other than IPX/NCP when
using DOS ODI. Consult the protocol's documentation
for further information on this capability.
NetWare Utilities Reference
===========================
REVOKE optional parameters (page 318)
Use the SUB (subdirectories) and F (files) options with a
forward slash (/SUB or /F) rather than a dash.
REMOVE optional parameters (page 308)
Use the SUB (subdirectories) and F (files) options with a
forward slash (/SUB or /F) rather than a dash. Installation Supplement for Novell Ethernet (page 79)
=====================================================
NE3200 performance:
For maximum performance when installing NE3200 LAN drivers
on a NetWare v3.11 server, do the following:
1. In the STARTUP.NCF file, change the Minimum Packet
Receive Buffers from the default value of 10 to 100.
This allows the driver to process large numbers of
packets as soon as the NetWare server is brought up.
2. Change the Maximum Packet Receive Buffers from the
default setting of 100 to at least 100 plus 10
additional buffers for each NE3200 installed in the
server. A server with two NE3200 boards, for example,
should have at least 120 packet receive buffers.
Additional buffers should also be allocated for busy
networks.
3. The NE3200 LAN driver can run with or without
interrupts. The recommended mode of operation is WITH
interrupts. This ensures that the NE3200 gets the best
performance under all NetWare environments.
These performance tips should work for all Busmaster LAN
adapters.
Miscellaneous
=============
DOS COPY problem:
WARNING: If you use DOS COPY running DOS verson 3.3x to
copy File A over existing File B and you do not have the
Read right for File A, you get the message "0 files copied"
and the contents of File B will be erased and will not be
recoverable by SALVAGE (unless you have the Read right to
file B). DOS truncates file B in preparation for writing
File A, but File A cannot be opened for copying. This
condition has been tested with DOS v3.30, 3.31, 4.0, and
5.0; only 3.3x causes the problem. NetWare NCOPY does not
cause this problem. PRINT SERVER v1.21
==================
Print Server Installation, page 22. Replace the first paragraph
with:
If you chose to service queues on more than one file server
when you installed the print server on the original file
server (step 3 on page 19), you must now set up print server
accounts and queues on each additional file server. You
must have supervisor rights or enlist the help of the
network supervisor for each file server.
Print Server Installation, page 23. Insert a new paragraph
(checklist) at the bottom of the page (after step 5e):
At this point, you should have completed the following
tasks:
o Defined an identically named print server on each of
the file servers that will be serviced
o Configured printers with identical numbers on those
file servers with "Defined elsewhere" in the Type field
o Mapped each of the defined printers to the queue to be
serviced
Print Server Installation, page 24. Replace the first sentence
under "Load PSERVER.NLM" with:
PSERVER.NLM was copied into SYS:SYSTEM during installation.
PSERVER.NLM requires two other files, CLIB.NLM and NUT.NLM.
Make sure you use the version of these files that are
automatically loaded by PSERVER.NLM and copied into
SYS:SYSTEM during installation or upgrade.
Print Server Installation, page 25 (applies to NetWare v2.x
servers only). Replace the paragraph under "On a file server"
with:
PSERVER.VAP was copied to SYS:PUBLIC during installation.
To load the print server, copy PSERVER.VAP to SYS:SYSTEM.
When you boot the file server you see the following prompt:
CAPTURE, page 52. Replace the second sentence under "Copies=n"
with:
Replace n with the number of copies (1 to 255). PRINTDEF, page 125. Delete HPLASER.PDF and import the following:
HP2.PDF Hewlett-Packard LaserJet II/IID
HP2PS.PDF Hewlett-Packard LaserJet PostScript Cartridge
HP3.PDF Hewlett-Packard LaserJet III/IIID
HP3SIPCL.PDF Hewlett-Packard LaserJet IIISi-PCL
HP3SIPS.PDF Hewlett-Packard LaserJet IIISi-PostScript
PRINTDEF, page 134. Replace step 12 with:
Repeat Steps 1 through 11 for each function or escape
sequence you want to enter.
PSC, page 143. Replace the heading "Mark [character]" with:
MArk [character]
PSERVER.VAP, page 155. Replace the second sentence of the second
paragraph under "Additional information" with:
See "Print Server Installation" on page 15 for more
information.
RPRINTER, page 157. Replace the explanation for the -s command
format with:
The -s option displays the status of the RPRINTER program.
(To view the status of the print server or printer, use
PCONSOLE. If you are using PSERVER.EXE or PSERVER.NLM, you
can view the printer status at the file server console.)
Server Backup
=============
Page 2 Add driver and DIBI interface NLMs for SCSI
boards to the host software list. New SCSI
tape drivers are ADAPTEC.NLM and AHAnnnn.DSK.
Page 6 The error and backup log files now display
both the DOS-equivalent name and the name
space used to create the directory or file.
Page 7 The list of tape device/controller
combinations is incorrect. As of this
release, all devices using a DIBI-2 certified
driver are supported. Drivers supporting
QIC-02 and SCSI boards are included with this
version of the Server Backup product.
Page 8 Correction to the Note. The DIBI2$DV.DAT
file now contains information about all
supported device drivers. You should edit
this file to remove the lines for drivers
that you do not need.
Before you can edit the DIBI2$DV.DAT file,
change the file's flag to "N." Then, load
EDIT and edit the file. After editing the
file, change the flags back to Read Only.
Page 12 When you specify a File Server as "What to
back up," all subdirectories are backed up,
even if you exclude subdirectories as an
option. If you specify the Bindery to be
backed up, excluding the bindery as an option
is ignored.
Page 18 If you use "Destination Path" to restore
files to a different location, you must also
change the path in "Directories to include"
(or exclude) and "Path/Files to include" (or
exclude). These options are in the "Include
Exclude" list.
Page 22 The buffer size range is now 16KB to 256KB.
The default is 64KB.
If you have a device driver that uses low
memory, the buffers will be automatically
allocated; however, if you get an "Out of
Memory" message, you will have to use the
"SET Reserved Buffers Below 16MB" command to
increase the number of low memory buffers
available. This SET command is documented
earlier in this README file.
Page 23 If you set the maximum subdirectory level (in
the AUTOEXEC.NCF file), you should also use
the "SET MINIMUM CACHE BUFFERS" command to be
equal to or greater than the subdirectory
level setting.
NOTE: SBACKUP creates temporary files (SYS:SYSTEM\TSA$TMP.*)
on the target server that may be used to store
information during backup. These temporary files may
get quite large if you have extended attributes or
linked UNIX files. Make sure you have enough disk space
on the SYS volume for these temporary files.
Server Backup SCSI Tape Drivers:
The following additional software was added to Server Backup after
the manual was printed. These modules and files allow Server Backup
to work with industry standard SCSI tape drives using ADAPTEC host
adapters.
ADAPTEC.NLM This loadable module is a SCSI tape device
driver. It controls the operation of a tape
device attached to a compatible host adapter.
USE TAPEDC00.NLM WITH THIS DRIVER.
TAPEDC00.NLM This loadable module is the DIBI-2 interface
between the SCSI tape device driver
(ADAPTEC.NLM) and SBACKUP.NLM.
-------------------------------------------------
AHAnnnn.DSK This is a SCSI tape device driver. It is on
the HP driver diskette that came with your
device. The nnnn is replaced by the host
adapter number, such as 1540, 1640, or 1740.
ASPITRAN.DSK This is the interface between the device driver
(AHAnnnn.DSK) and the DIBI-2 interface module
(NOVADIBI.NLM). It is on the HP driver diskette
that came with your device.
NOVADIBI.NLM This loadable module is the DIBI-2 interface
used with ASPITRAN.DSK and AHAnnnn.DSK.
Server Backup supports most devices that are DIBI-2 driver
compatible. For a complete list of compatible devices, contact
your reseller.
Compatible SCSI host adapters:
1540A (ISA)
1540B (ISA)
1542A (ISA)
1542B (ISA)
1640 (Microchannel)
Before loading backup device drivers and modules:
Install and set up hardware. Refer to the documentation
that came with your adapter for installation instructions
and jumper settings. Use unique I/O port address, IRQ, and
DMA settings.
Complete the NetWare installation or upgrade procedure.
Server Backup software is installed automatically on the
file server.
If you are using the .DSK files described above, copy the two
files from the HP driver diskette that came with your device to
one of the following directories:
If you want to place commands in an AUTOEXEC.BAT file to
load the .DSK files automatically, copy the files to
SYS:SYSTEM.
If you want to place commands in the DOS STARTUP.NCF file
to load the .DSK files automatically, copy the files to the
DOS directory that contains STARTUP.EXE.
Optional: Edit the DIBI$DV.DAT file to specify the driver
module you will use. Before you can edit the DIBI2$DV.DAT file,
change the file's flag to "N." Then, load EDIT and edit the
file. After editing the file, change the flags back to Read
Only. If you leave all of the driver lines in the file, you can
select the driver you want to link after you enter SBACKUP.
1. Loading modules.
****IMPORTANT: The ADAPTEC.NLM driver does not allow you to
share I/O. If you have multiple SCSIs running from the same
controller, do not load ADAPTEC.NLM --- use AHAnnnn.DSK with
NOVADIBI.NLM instead.****
a. Load the driver. Type
LOAD ADAPTEC P=xxx <Enter>
or
LOAD AHAnnnn P=xxx <Enter>
Replace nnnn with the adapter number if you are
loading the AHAnnn.DSK file.
Replace xxx with the port I/O address. If the
default port I/O address was used when you
installed the host adapter, you do not need to
enter the address. If you specified a different
port address, replace "xxx" with the address you
selected.
To load the drivers automatically after the file
server boots, put the commands in your STARTUP.NCF
or AUTOEXEC.NCF file.
The driver you load automatically loads the
modules and files it needs to run.
b. IF YOU ARE USING ADAPTEC.NLM and you want to
initialize a tape device, erase data from a tape,
adjust tape tension, or test component
interoperability, access the Tape Driver
Console Screen by pressing <Alt> <Esc>.
(Instructions for using this screen are on the
following page).
Only one backup device can be run at a time.
c. Follow the instructions on page 9 of the NetWare
Server Backup manual to load the TSA and SBACKUP
modules.
The DIBI interface modules (TAPEDC00.NLM) or
NOVADIBI.NLM) load automatically.
2. Backing up and restoring data
Follow the instructions in the NetWare Server Backup manual.
3. Unloading modules
a. Unload SBACKUP as explained in NetWare Server Backup.
This unloads DIBI interface (TAPEDC00.NLM or
NOVADIBI.NLM automatically.
IMPORTANT: If you want to unload a driver (such as
ADAPTEC.NLM or AHAnnn.DSK), you must first unload SBACKUP.
Otherwise, you will abend the file server.
Using the ADAPTEC Tape device driver:
After the ADAPTEC device driver is loaded, you can control it
by using a special console screen at the host file server
console.
1. To access the screen, press <Ctrl> <Esc> to display the
current selection of screens.
2. Select the Tape Driver Console screen from the list.
3. Select a command from the Tape Driver Console screen by
typing the appropriate letter and pressing <Enter>.
INITIALIZE Use this command to initialize the tape
device if the device was not turned on
when ADAPTEC.NLM was loaded. This
command also reinitializes a device if
it does not respond properly.
ERASE Use this command to erase data from a
tape (including the tape name). If you
are using 4mm or 8mm tape devices,
ERASE can take several hours. Refer to
your tape device manual for more
information.
RETENSION Use this command to adjust the tension
of the tape within a cartridge. Refer
to your tape device manual for more
information.
TEST Use this command to verify the
interoperability of ADAPTEC.NLM, the
host adapter, and the tape device.
After entering the command, the message
"Tape contents will be destroyed.
Continue Y/N?" is displayed. Type "Y"
to continue.
The tape device generates and writes
sample data to the tape and then
verifies the data. If the tape device
supports random access, four seek
operations with verification are
performed. The sample data is then
erased. When the test is completed,
the message "TAPEDRV: Tape Test
Completed Successfully" appears. Press
any key to return to the menu. NetWare v3.11 TCP/IP Transport Version 1.0
1. TCP/IP may have trouble with LAN drivers not delivered with
NetWare v3.11 and not certified to run with NetWare 3.11. The LAN
drivers which may exhibit problems include both third-party LAN
drivers certified only for earlier versions of NetWare 386 and Novell
LAN drivers delivered with earlier versions of NetWare 386. The
specific symptoms vary from driver to driver, but generally the
problems revolve around an inability to send or receive large packets.
In some cases, the driver may simply not support a required framing
type such as Ethernet_II or Token-Ring_SNAP.
If you have trouble with an older LAN driver, you should try to
upgrade to LAN driver certified for use with NetWare v3.11. Contact
the LAN board supplier for information about getting upgraded LAN
drivers for your board.
2. Appendix A of "NetWare v3.11 TCP/IP Transport Supervisor's
Guide" refers to a compatible IP Tunnel product by Schneider
& Koch which uses UDP port 59139. The appendix recommends specifying
port 59139 when loading a NetWare IP Tunnel to allow it to talk to the
S&K product. Beginning with version 1.3 of the S&K drivers, the S&K
product now uses the same UDP port as NetWare's IP Tunnel, port 213.
If you are using version 1.3 or later of the S&K drivers, you will
not need to specify the UDP port to the NetWare IP Tunnel; the IP
Tunnel's default port will be correct.
3. Appendix A also contains a sample NET.CFG file for setting up a
DOS IP Tunnel. The following two lines were omitted from that sample
file and should be added at the end of it:
Protocol IPX
Bind IPTunnel
4. The system will fail if the TCPIP.NLM is unloaded while any
application is actively using the AT&T Streams interface for TCP, UDP,
or IP communications. Currently, no Novell products use streams to
access TCP/IP, so you will not encounter this problem unless you have
installed add-on TCP/IP products on your system. If any such
application is present, TCP/IP will issue the following warning:
Warning: Some utilities have streams open to the TCP/IP protocols.
TCP/IP service to those utilities will be terminated,
and SYSTEM INTEGRITY MAY BE COMPROMISED.
Unload module anyway? n
We strongly discourage you from unloading TCP/IP until you have found
the utilities using the streams interface and have unloaded them.
5. Under some conditions, a message similar to the following will
appear when the TCPCON.NLM is unloaded:
2/1/91 12:05pm: 1.1.14 Module did not release 304 resources
Module: TCP/IP Console v1.00 (910131)
Resource: Small memory allocations
Description: Alloc Short Term Memory (Bytes)
This message does not indicate a problem. It can be ignored.
6. Although the "Bind IP" command allows the system administrator to
specify different IP subnetwork masks for different IP subnets of the
same IP network, such configurations are not supported. The BIND
command issues the following warning to inform the
administrator of conflicts between subnet masks:
"Warning: Subnetwork mask disagrees with mask used with <IP address>."
If you receive this warning, you should rebind all interfaces
connected to subnets of this IP network, and use the same MASK
parameter in each BIND command.
NETWARE SFT III v3.11 B
January 1993
This file contains information about the SFT III Release (v3.11 B) to supplement
the SFT III document. In addition to this file, be sure you read and understand
the list of Limitations at the beginning of Chapter 2 and the Troubleshooting
Tips in Chapter 3 of the NetWare SFT III manual.
[1] WORKSTATION SHELLS: (See also p.2-15) Any client workstation that will be
accessing the SFT III mirrored servers should use the new versions of
NETX, BNETX, EMSNETX or XMSNETX. These new (v3.31) shells are named *.EXE
whereas previous versions of NETX and BNETX have .COM extensions. Remember
to delete the .COM shells so that the workstation will use the new .EXE
versions. (Using older versions of the client shells will cause the
clients to pause and display the Abort/Retry message instead of switching
over automatically to the new server after a failure.)
[2] BNETX: In the Novell test labs, Packet Burst (the BNETX.EXE shell) has
occasionally exhibited uneven load sharing with more than 40 clients under
very heavy load conditions. If you are using Packet Burst under these
conditions, some clients may experience sluggish performance.
[3] SHELL TIME OUT: (See also p.3-54) If client workstations time out during
server synchronization, increase the IPX Retry Count value in the client's
NET.CFG file. You may want to set the parameter Notify Users Of Mirrored
Server Synchronization = ON, which will broadcast a message to all users
when synchronization occurs.
[4] BACKUP DEVICES REQUIRING DIBIDAI: The DIBIDAI.NLM is not supported with
SFT III v3.11, and is not included on the Controlled Release diskettes. In
some cases, you may use the NOVADIBI.NLM instead. The TAPEDAI.DSK driver
is also not supported.
[5] TOKEN RING LAN DRIVER: SFT III v3.11 includes the 4.0 version of this
driver. Three files are required: MSM311.NLM, TOKENTSM.NLM, and TOKEN.LAN
or TOKENDMA.LAN. Start by loading TOKENTSM.NLM (which auto-loads MSM311),
then load the .LAN driver.
[6] Added the following NetWare v3.11 patches to SFT III code:
ASNCRDFX BIGRFIX CIPHFIX DIRLPFIX DOSUNFIX DOTFIX
DUPFIX EAERRFIX EAINFIX EVENTFIX FATFIX GETSEFIX
HDLNKFIX HTFXFX MAXCDCFX MDEFIX MPRPSFIX NCOMFIX
NCPSPFIX NFSFIX OBPRGFIX OS2OPNFX PPCFIX REMDEVFX
RENFIX REQFIX ROUTERFX RPLENFX TRSTFIX TTSFIX
UNLCKFIX WORMROFX WSDFIX
[7] IPX CHECKSUM AND TOKEN RING: Token Ring does not support the enabling of
IPX checksum. Do not use checksumming if you are on a Token Ring LAN.
[8] IPX CHECKSUM LIMITATION: The IPX Checksum options only apply when you are
using the client LSL and IPXODI drivers (delivered with SFT III). You
cannot use IPX checksum with the older dedicated IPX.COM, or older
versions of LSL and IPXODI.
[9] NE2000 AND NE/2-32: Do not use NE2000 or NE/2-32 LAN adapters as Mirrored
Server Links except in your test lab environments. Don't use them on
production servers. This stipulation is part of your SFT III License
Agreement for the duration of the v3.11 B Release.
[10] TEST MSLs: If you are using the NE2000 or NE/2-32 LAN adapter as your
Mirrored Server Link (in a test environment), using the RESET ROUTERS
command on a busy network may cause one of the servers to Abend. This is
because the interrupts are disabled for too long and the SFT III system
must assume that one of the servers is inactive.
[11] PACKET BURST STATISTICS: The SET parameter Enable Packet Burst Statistics
Screen (in the MSEngine) cannot be set in the MSAUTO.NCF.
[12] NEW SET PARAMETER: In the MSEngine, under the Communications category,
you'll find Clear Extra ECB Space, set to 1 by default. This parameter is
used to protect against NCP packets that are undersized. You shouldn't
need to change the default setting on this parameter.
[13] 1000-USER NETWARE USERS: SFT III utilities are compatible with 1000-user
NetWare (with the exception of some Print utilities), for customers who
may be using 1000-user NetWare elsewhere on their internet. SFT III itself
is not available in a 1000-user version at this time.
[14] BTRIEVE: The BTRIEVE.NLM loads in the MSEngine. Be sure to use the latest
version of Btrieve (v6.00a), delivered on the SFT III diskettes. Do not
try to use older versions of Btrieve or any of its dependent files on the
SFT III server. Also, do not use the SFT III Btrieve on a non-SFT III
v3.11 server.
[15] DUAL PROCESSING: Second processor drivers for SFT III should be obtained
from your hardware manufacturer. The file N2NDPROC.NLM is available on
NetWire; put it near the top of the file IOSTART.NCF, right after the IPX
Internal Net number. (You may also load the N2NDPROC.NLM at the IOEngine
console prompt.) If the NLM loads without errors, the second processor is
activated and servicing the MSEngine.
[16] REMOTE BOOT: If you need to use the remote boot feature of NetWare, follow
the steps below.
1 - Load the LAN driver (must use 802.2 frame type)
2 - Load RPL.NLM in both IOEngines
3 - BIND RPL (LAN driver)
4 - Follow the instructions for creating a boot image file (see DOSGEN
instructions in the 3.11 NetWare documentation)
[17] Added one SET parameter, to disable the use of the diagnostic responder
to validate LAN health: "Use Diagnostic Responder To Validate LAN
Functionality = OFF" (ON is the default)
[18] SET parameters: Increased the Maximum for "Reserved Buffers Below 16 Meg"
from 200 to 300; changed "Maximum Percent of Volume Space Allowed for
Extended Attributes" to allow it to be set in the startup NCF file.
[END]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* NETWARE BASIC MHS 1.0 *
* Copyright (C) 1993 by Novell Inc. *
* May 20, 1993 *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
For information about the FirstMail product, refer to the file
README.FM on the second installation diskette, or in the
BASICMHS subdirectory on the CD-ROM.
----------------------------------------------------------------
NETWARE BASIC MHS DOCUMENTATION
----------------------------------------------------------------
The NetWare Basic MHS documentation is in the MHS\SYS
subdirectory, which is created during installation. The
documentation consists of the following file:
* ADMIN.DOC - "NetWare Basic MHS Administration"
* MESSAGES.DOC - "NetWare Basic MHS Messages"
----------------------------------------------------------------
INSTALLING NETWARE BASIC MHS
----------------------------------------------------------------
Before installing Basic MHS, refer to the "Getting Started with
NetWare Messaging" manual. Follow the instructions in this
manual to install the software from a floppy diskette. To
install the software from a CD-ROM or network drive, refer to
the Basic MHS Release Note.
Before beginning the install, check the PRODUCTS.DAT file in the
SYSTEM directory, to ensure that it is marked read/write.
(Previous beta versions of NetWare 3.12 incorrectly marked
this file read-only.)
If you are installing Basic MHS from a network drive, enter
the path to the Basic MHS software in the format
<vol>:<pathname>. DO NOT include the server name in the path.
----------------------------------------------------------------
UNLOADING NETWARE BASIC MHS
----------------------------------------------------------------
If you attempt to unload BASICMHS.NLM while a message is being
processed, BASICMHS generates the following system message:
Basic MHS will unload as soon as the current message is
delivered
No action is necessary. Basic MHS will unload when processing
is completed.
----------------------------------------------------------------
DISMOUNTING THE VOLUME ON WHICH BASIC MHS IS INSTALLED
----------------------------------------------------------------
Before dismounting the volume on which Basic MHS is installed,
you must unload BASICMHS.NLM. If you do not, Basic MHS will
not be unloaded properly; to unload it you must restart the
server.
----------------------------------------------------------------
INSUFFICIENT DIRECTORY ENTRIES
----------------------------------------------------------------
If the file server runs out of directory entries while
BASICMHS is running, an out-of-space error occurs. If users on
the network are reporting out-of-space errors, but there is
sufficient space on the network, you might be running out of
directory entries. To avoid this problem, you can increase the
percentage of the volume used for directory entries. Use the
following SET command:
SET MAXIMUM PERCENT OF VOLUME USED BY DIRECTORY =
The default percentage is 13. However, you can enter a number
from 5 to 50.
Enter this command in the AUTOEXEC.NCF. It will not take
effect until you restart your server. For more information
about the command, refer to your NetWare documentation.
----------------------------------------------------------------
INABILITY TO CREATE EXTRACT FILE
----------------------------------------------------------------
MESSAGES.DOC does not list all the conditions that can result
in the error:
9503 Unable to create extract file.
In addition to lack of disk space, insufficient directory
entries, or disk error, this message can also result if an
application has the extract file open. If this error occurs,
ensure that no users have the directory list open in their
MHS-compatible applications.
----------------------------------------------------------------
IF YOU HAVE QUESTIONS ON BASIC MHS
----------------------------------------------------------------
If you have questions on Basic MHS, call Novell Technical
Support (800-NETWARE, outside the U.S., call 801-429-5588).
The README.UPG file is now part of the README.40 file on: a) the INSTALL diskette, or b) in the \NETWARE.40\ENGLISH directory on the CDROM media. It contains key information that should be read before starting any UPGRADE process.
NetWare Lite 1.0 -- README file (09/12/91)
--------------------------------------------
***************************************************************************
************ Print this file and save it for future reference. ************
***************************************************************************
This file contains hints and suggested conventions for how NetWare
Lite might be setup on a network and how it might be used.
Table of Contents
-----------------
1. Shared Resources
2. Printing
3. Network Applications
4. Compatibility with the NetWare Shell
5. SERVER optimization and functions
6. Using CD-ROMs
7. IPXODI
8. Auxiliary NetWare Lite files
9. Logging in after INSTALL
10. Windows compatibility
11. Documentation Errors (Errata)
1. Shared Resources (Network Directories and Printers)
------------------------------------------------------
Shared resources are those resources (Network Directories or Network
Printers) that are shared with CLIENTs on a network. We suggest that
Network Directories and Printers be given descriptive names. Good
names for Network Directories might be: TURBOC, WORDPERFECT, GAMES,
IBM_DOS_310 or PUBLIC. Good names for Network Printers might be:
LASERJET_II, EPSON_DOT. Names that might not be good are CDRIVE,
PRINTER1, PRINTER2. These names provide no indication of what
applications or what kind of printers are being made available. You
will notice that during NetWare Lite installation we create a CDRIVE
Network Directory for you. When you become familiar with the product
this resource ought to be removed and one or more descriptive Network
Directories created in its place.
Assisting Floppy-based CLIENTs
If there are workstations on the network that don't have hard disks
then we suggest that NetWork Directories be set up to help those
workstations. A DOS shared Network Directory should be created so that
workstations with no hard disks can load DOS commands from the network.
A Network Directory sharing IBM DOS version 3.10 (named IBM_DOS_310
perhaps) would be useful for those CLIENTs with only floppy drives to
get to their version of DOS. In conjunction with this the DOS
environment variable "comspec" should be set so as to allow the loading
of DOS COMMAND.COM from across the network; for better performance.
For example, these lines could be included in an AUTOEXEC.BAT or
STARTNET.BAT file:
NET MAP F: IBM_DOS_310
SET COMSPEC=F:\COMMAND.COM
In addition, workstations that only have floppies can be assisted by
creating a Network Directory where the NetWare Lite utility (NET.EXE,
NET.OVL, NET.HLP and LITE$RUN.OVL) can be loaded from; instead of
always loading them from the floppy. We suggest that a Network
Directory called NWLITE be created. This directory should be a
SERVER's C:\NWLITE directory. We also suggest that this Network
Directory be given default rights of READ and not the default of ALL.
All floppy-only CLIENTs should map a drive to this resource and add the
drive to their DOS path. This will allow the loading of the NET
utility from across the network; a much better solution than loading
from floppy. For example, these lines could be included in an
AUTOEXEC.BAT or STARTNET.BAT file:
NET MAP M: NWLITE
PATH=M:.;%PATH%
If you want to run the CLIENT from a floppy drive and have that
diskette be the boot diskette, the following configuration is
suggested. Where ever NE2000.COM appears, replace it with the
appropriate driver name you are using. Also, L: and M: are simply used
as examples; you may use any other valid driver letters. We map drive
M: to the Network Directory NWLITE as described above. Similarly, L:
is mapped to the Network Directory IBM_DOS_310 as described above.
1) Create a bootable diskette using the FORMAT A: /S command.
2) Copy the following NetWare Lite files to the diskette.
LSL.COM
NE2000.COM
IPXODI.COM
CLIENT.EXE
NET.EXE
3) Create an AUTOEXEC.BAT with the following lines added to it.
LSL
NE2000
IPXODI A
NET LOGIN
NET MAP L: IBM_DOS_310
NET MAP M: NWLITE
PATH=L:\;M:\;%PATH%
SET COMSPEC=L:\COMMAND.COM
4) Create an CONFIG.SYS with the following line added to it.
LASTDRIVE=M
For those Network Directories that contain applications (executables)
the drives used to map to these applications should be included in the
DOS environment variable PATH. For example, these lines could also be
included in an AUTOEXEC.BAT or STARTNET.BAT file:
NET MAP G: TURBOC
NET MAP H: WORDPERFECT
NET MAP I: GAMES
SET PATH=G:\BIN;H:.;I:\TETRIS;%PATH%
Make Shared Executables Read-Only
Executable files that will be run by more than one user at a time need
to be marked as read-only. If they are not, then you may notice at
times that you are temporarily denied access to a file you wish to run.
For example, you may get a message that access was denied or that the
EXE file could not be run. If this happens, mark the executable files
read-only using the DOS ATTRIB command. Type ATTRIB +R *.EXE in the
directory where the executable files reside. This example marks the
*.EXE files read-only. All shared .COMs, .BATs, and .OVLs should be
marked as well. The read-only attribute can be cleared using the same
command replacing the +R with -R. (See DOS documentation for
information on the ATTRIB command).
Location Independence
You will notice that our resources are location independent. Suppose
you create a Network Directory named ALL_APPS on a server named
DEPT_SERVER. Server DEPT_SERVER is a 8 MHz 286 machine with a 40 MB
hard disk. All CLIENTs map drives to ALL_APPS and use it every day.
Now suppose you buy a 50 MHz 486 machine with a 1 GB disk drive on it.
You want to move the Network Directory ALL_APPS to this new machine.
You install this new machine and call it HOT_SERVER. You can then
create a new Network Directory on this new server and call it ALL_APPS
(same name as before). You then copy the files from DEPT_SERVER to
HOT_SERVER. ALL_APPS can now be removed from DEPT_SERVER. All your
CLIENTs will now use ALL_APPS from HOT_SERVER and nothing need be
changed from the CLIENT's perspective. The CLIENTs don't need to know
that the location of the Network Directory ALL_APPS has moved. This
same principle applies to Network Printers.
2. Printing -- Conventions and Suggestions
-----------
Chances are that you bought this product to share one or more printers.
For this reason, give special attention to the following remarks.
Local Network Printers
Once a printer is assigned as a Network Printer, you should only access
that printer through the network. You may have a printer attached to
your workstation that has been defined as a Network Printer. In this
case, you should capture a port when you wish to print to it. If you
print to it directly (not using capture), you may cause print job
corruption.
Characters Per Second and Print Buffers
Network Printers are created in the NET menu utility in the "Supervise
the Network" category. When a printer is created, you can configure
the performance of the printer relative to the DOS running on the same
machine where the printer is attached. This is done by modifying the
"Chars per second" parameter in conjunction with the "Print buffer
size" parameter of the server configuration. The print buffer is an
area in memory where characters are stored before being printed. The
larger the print buffer size, the less often the SERVER will need to go
to disk to read more characters to print. If the "Chars per second"
value is high (relatively speaking) and the "Print buffer size" is
large (relatively speaking) then the printer will be driven faster and
the DOS running on that machine will be interrupted more often to send
characters to the printer. The converse is also true if the value of
"Chars per second" is low and "Print buffer size" is small. These
values should also be tuned to the speed, or desired speed, of the
printer. If the printer is physically a "slow" printer then setting
the "Chars per second" parameter to a high number will have no effect.
Additionally, if the "Chars per second" is set higher than the "Print
buffer size" parameter then this will have little effect, as well.
Setup Strings
One of the options available on Network Printers is setup strings. You
can define up to ten setup strings for each Network Printer. In short,
a setup string is a series of characters that put the printer into a
particular mode (i.e. landscape mode, large characters mode). By
default, the DEFAULT setup string is set to nothing. The DEFAULT setup
string should be set to a sequence of values which reset the printer.
Many printers use the string "1E 45" (<ESC>E) to reset the printer
(check the documentation for your printer to find out what sequence
resets the printer). The manual that came with the printer should
describe the values that place the printer into different modes. Setup
strings are always entered using hexadecimal codes.
By defining more than one setup string for a Network Printer it is
possible to submit jobs that will print in different printer modes.
Setup strings can be used as part of the "NET CAPTURE" command or in
the "Print" category of the NET menu utility. An example of its use
with "NET CAPTURE" is provided below.
Capture Settings
CLIENTs can access Network Printers with the "NET CAPTURE" command.
There are several options available with this utility. Special
attention should be given to the options available with the "NET
CAPTURE" command. They are discussed in the manual, as well as in the
on-line help in the NET menu utility and on the command-line when "NET
CAPTURE HELP" is typed. A sample command-line might look like this:
NET CAPTURE LPT1 LASERJET B=N D=Y S=LANDSCAPE
This means that all jobs sent to LPT1 of the local machine will be
redirected to the Network Printer LASERJET. It also means that for all
print jobs sent to LPT1 (LASERJET), there should be NO banner printed
and each job should start printing before the job has been completely
submitted (direct printing). Finally this job is printed using the
LANDSCAPE setup string (created previously on printer LASERJET). The
LANDSCAPE setup string values are sent to the printer just previous to
the data of each print job sent to LPT1. The DEFAULT setup string
values are sent to the printer after each print job is printed (thus
resetting the printer for the next job sent to this printer).
From the NET menu utility it is also possible to submit a print job and
have the job immediately go on hold. When a print job is on hold it is
placed on the queue but not printed. It can be taken off hold (and
thus printed) by selecting the job from the print job list and changing
the flags of the job.
Postscript printing
Because of the nature of postscript printers, special care must be
taken when sending print jobs. You should make sure your capture has
the following set:
BANNER=No
TABS=0
FORMFEED=No
You may also want to set the WAIT parameter to a value higher than 10
seconds. If your print job gets split to multiple jobs when printing
to a postscript printer, you will want to increase the WAIT value.
Increase it until your print job comes out all in one job.
Using WAIT=0
The WAIT=0 should only be used if the application you are using will
close the print job. If the application does not close the print job,
using WAIT=0 will keep the print job open until it is closed
explicitly. A print job on LPT1 can be closed manually from the DOS
command-line by sending a formfeed or <Ctrl>-L, displayed ^L (press and
hold the Ctrl key while pressing the L key, then release the L key and
Ctrl key). Type "ECHO ^L > LPT1". This sends a form feed character to
LPT1 and closes the job. Generally using a WAIT value of 10 or so is
adequate. CAUTION: If you use WAIT=0 and DIRECT=Y you will hold the
printer until the print job is explicitly closed.
Capturing Ports
The documentation incorrectly states that as a CLIENT, you can capture
COM1 or COM2. The COM1 and COM2 ports can only be used by a SERVER. A
Network Printer can be assigned to the COM1 or COM2 port. CLIENTs can
then capture LPT1, LPT2, or LPT3 to a Network Printer that has been
created and assigned to COM1 or COM2.
3. Network Applications
-----------------------
Installation
Installing applications on NetWare Lite may be different than
installing applications on NetWare. NetWare is, as you know, a very
popular LAN. Many applications have NetWare specific installation
options. These installation options DO NOT apply to NetWare Lite
networks. NetWare Lite is a DOS peer-to-peer network. If the
application being installed has network specific installations then
"Other networks.." or "DOS Peer to peer network" or the like, should be
selected. DO NOT select NetWare or Novell installation options. See
Appendix B in the documentation for more details.
In general, some consideration should be given when installing
applications. If the application requires configuration information at
the time it is installed, then consideration should be given to which
CLIENTs (machines) will use the application. For example, say
application TESTAPP.EXE is being installed and it asks what kind of
monitor will be used with this application. Suppose that the machine
you are sitting on has a VGA screen but no other machines on the
network have VGA screens. If you were to select VGA then when this
application is run from across the network from an CGA screen, say, it
may not function properly. We have no specific guidelines on this
subject, as a general solution may not be possible. This is a general
problem with configuration of applications on a network.
4. Compatibility with the NetWare Shell
---------------------------------------
If your site is currently using Novell NetWare and you are installing
NetWare Lite on the same LAN, then there are some guidelines that
should be followed in order for both to function properly.
NetWare Lite functions on a single LAN segment. In other words,
NetWare Lite packets DO NOT cross Novell bridges (NetWare Lite packets
do cross MAC layer bridges or repeaters, however.) In a site that has
existing NetWare, each NetWare Lite network will be constrained to a
single LAN segment.
If there are workstations that will load both the NetWare shell and
NetWare Lite software we suggest the following load order:
IPX (either the IPX you had or IPXODI that came with
NetWare Lite; either one but NOT both)
DOS Share (SHARE.EXE, if becoming a SERVER)
NetWare Lite Server (SERVER.EXE, if desired)
NetWare Lite Client (CLIENT.EXE, if desired)
NetWare Shell (NETx.COM)
Once you have installed the CLIENT to a workstation that will also be
running the NetWare Shell, you will need to modify your AUTOEXEC.BAT or
appropriate batch file to load the files in the correct order. Note:
with LASTDRIVE set, the NetWare Shell will map the first drive past
LASTDRIVE to the SYS:LOGIN directory of the NetWare server for you to
login. If LASTDRIVE is not set, DOS defaults it to E:, thus F: would
be mapped to SYS:LOGIN. Also, if you use the MAP *1:= command in your
login script, *1 means the first drive past LASTDRIVE. If you are
dependant on certain drives being mapped with certain letters, the
changing of LASTDRIVE may change which drive letters are mapped. Be
aware that all drive letters, A: - Z:, can be mapped to NetWare servers
(NetWare Lite can only map A: - LASTDRIVE).
See Network Applications in this README file for installing network
applications.
5. SERVER Optimization and Functions
------------------------------------
Disk Caches
NetWare Lite does not ship with a disk cache. We have tested with
several (read many) commercially available disk cache products and
found them to be quite inexpensive while adding significant performance
to the NetWare Lite SERVER software. We suggest for higher performance
of the NetWare Lite SERVER that a disk cache be acquired and installed
on the SERVER machines. Some cache tuning may be necessary for best
results.
Server Configuration
For best performance we suggest that receive buffer and read buffer
sizes be increased to what is supported by the network topology (i.e.
ethernet, token ring) up to a maximum of 4096 bytes using a multiple of
512 bytes. In fact, if 4096 is selected then the SERVER will truncate
the value to the maximum value supported by the topology. This tuning
allows CLIENTs to request more data from (or send more data to) the
SERVER with each read (write) operation. When more data is sent, fewer
requests are necessary and better performance is obtained. This
enhancement does increase the size of the SERVER when it is resident in
DOS.
Depending on the "load" being placed on the server, it may be
beneficial to increase the number of receive buffers and read buffers.
In general, we have found that 8-12 receive buffers is enough for even
the most heavily loaded server. Similarly, 5-10 read buffers is
sufficient. These values need not be more than one or two above the
number of simultaneous connections (up to our suggested maximums of 8-
12 receive buffers and 5-10 read buffers).
Mapping vs. SUBSTing
If your machine is a SERVER and you map to yourself, it is recommended
that you SUBST to yourself instead of mapping to yourself. SUBST is a
DOS command that lets you assign a drive letter to a directory on
another drive. For example, if you usually map to yourself with G: to
the Network Directory APPS, and if APPS is actually the C:\APPS
directory, the NET MAP G: APPS could be replaced by SUBST G: C:\APPS.
To remove this substitution, you would type SUBST G: /D. Using this
substitution, rather than a mapping, will result in better performance
for operations done on drive G:.
Mapping Local Drive
You can map drives that are local, for example A: or B:, and use them
temporarily as network drives. However as a general practice, it is
not recommended. If you run out of drive letters to map, increase
LASTDRIVE in your CONFIG.SYS.
Use of ASSIGN
Do not use ASSIGN with NetWare Lite. The DOS reference manual (3.3)
recommends that you use SUBST instead of ASSIGN and explains how to do
so.
Remove a SERVER from your hard drive
If you installed the SERVER on your hard drive and no longer want it
there, you can remove it by doing the following:
1) Boot your machine without loading the SERVER.
2) Run the original INSTALL.EXE that came on a floppy.
3) Select "Make this machine a SERVER". When asked to select the
network interface card, press ESC and exit the INSTALL utility.
The SERVER is now removed from your hard disk drive.
Improving SERVER performance
It has been found that fragmented file on the hard disk drive of a
SERVER can adversely affect performance. It is suggested that you
periodically unfragment the files on the hard disk drive of each
SERVER. This can be done using any of a number of disk optimizing or
disk compression tools available in the market place. MAKE SURE THE
SERVER IS NOT RUNNING WHEN THIS TYPE OF OPERATION IS DONE!!!
NEVER run any low-level disk repair utilities on the hard disk drive of
the SERVER while the SERVER is loaded. This can cause corruption of
data stored on the hard disk drive. This includes CHKDSK /F, disk
doctor utilities, and disk optimizing utilities. Low-level utilities
can only be run directly on the SERVER machine. You cannot run them
from CLIENTs that have a drive mapped to the SERVER.
Renaming SERVERs and Reconnection
Whenever a SERVER is renamed, you should reboot that SERVER as soon as
possible and have the CLIENTs that were connected to that SERVER, re-
login. CLIENTs cannot reconnect to a SERVER that was renamed.
Disabling the SERVER
There is no way to remove the SERVER or CLIENT from memory once either
is loaded. The SERVER can be disabled once loaded. Press CTRL-ALT-
DEL, as if you were rebooting. When the Reboot window comes up, press
1 to disable the SERVER. This simply turns the functionality of the
SERVER off, it is not removed from memory.
SHARE.EXE -- Status Report 5
When loading the SERVER, you may get "Status Report 5", which talks
about SHARE.EXE not being loaded when the SERVER.EXE was run.
SHARE.EXE is a program that comes with DOS 3.1 or above. If you get
Status Report 5, you do not have SHARE.EXE in your PATH. Either add
the appropriate directory to your PATH (where SHARE.EXE is located) or
copy SHARE.EXE to the directory where NetWare Lite is installed. SHARE
should be loaded before the SERVER. SHARE is the mechanism that allows
files to be accessed simultaneously from multiple CLIENTs. It is not
required to be loaded for the SERVER to run, though strongly suggested.
SHARE.EXE should be tuned for proper behavior. You may need to
increase the values for locks (/L) and files (/F) for SHARE if you run
database applications, or if you have more than 4 users. Configuration
of SHARE.EXE is documented with your DOS manual. The CLIENT does not
need SHARE.EXE to be loaded.
Workstation Time
To keep time of CLIENT machines on the network synchronized we suggest
that "NET TIME <server_name>" be placed in everyone's AUTOEXEC.BAT or
STARTNET.BAT file. <server_name> should be a machine that keeps
"pretty good" time. This becomes especially important if NetWare Lite
is being used in a software development environment where MAKE.EXE is
being used. MAKE.EXE requires strict time synchronization. If "NET
TIME" is used then MAKE.EXE will function smoothly. Further more, the
time on all SERVERs can be synchronized by using the "Time
Synchronization" option in the "Supervise the Network" menu.
6. CD-ROM Support
-----------------
NetWare Lite does support CD-ROM drives. You can use CD-ROM drives
with the SERVER and/or CLIENT. If you will be running the CLIENT on
the same machine as the CD-ROM drive, you MUST load the CLIENT before
loading the CD-ROM redirector (e.g. MSCDEX). You may attach a CD-ROM
to a SERVER workstation and create a Network Directory that point to
the CD-ROM drive. This way remote CLIENTs can access the CD-ROM.
7. Loading IPXODI
-----------------
In the STARTNET.BAT file that is created for you, the line "IPXODI A"
appears. The parameter "A" tells IPXODI to only load IPX, this makes
it so IPXODI takes up less memory. If you have an application that
needs SPX to run, remove the "A" from this line when loading IPXODI
then SPX will also be loaded. You can type "IPXODI ?" to see a list of
all available options for IPXODI.
8. Auxiliary NetWare Lite Files
-------------------------------
Included with NetWare Lite are four extra programs that are not
documented. These files are not needed for NetWare Lite to run, but
add fun and functionality. They are: DEDICATE.COM, DEMO.EXE,
NETBIOS.EXE, and NLSNIPES.EXE.
DEDICATE.COM -- DEDICATE is a little program that can be run on a
SERVER to improve performance. It is a useful program to be run on
NetWare Lite machines that are acting as dedicated servers; or if a
machine is a CLIENT/SERVER and the CLIENT is not going to be active for
a while. To run DEDICATE, type DEDICATE when in the C:\NWLITE
subdirectory on the machine running SERVER.EXE.
DEMO.EXE -- DEMO is a networking demonstration program that shows how
workstations can communicate using shared file access. When run, a
"worm" is shown moving around on the screens of the workstations
running DEMO.EXE. As the "worm" covers each screen, eventually the
word "LITE" is shown. To run DEMO, change to the same directory on the
same SERVER on each machine that will be running DEMO. With DEMO.EXE
in your PATH, type DEMO and press ENTER on each workstation. DEMO
works best if run in a Left-to-Right fashion. That is, starting on the
left-most workstation, run DEMO.EXE and move right running DEMO on each
machine. The screens are "connected" starting left and moving right in
the order which DEMO was started. Once running, you can drive your
"worm" using the arrow key. DEMO will only support 9 workstations
running simultaneously.
NETBIOS.EXE -- This is the NETBIOS that is included with regular
NetWare. It can be loaded any time after IPXODI is loaded. Some
applications require the presence of NETBIOS. For this reason NETBIOS
is provided with NetWare Lite. For more documentation on NETBIOS.EXE,
contact the nearest Novell Authorized Reseller.
NLSNIPES.EXE -- NLSNIPES is a game. One to five users can play at a
time. Everyone that wants to play NLSNIPES must map a drive to the
same Network directory on the same SERVER. To run, type NLSNIPES. You
will then be asked for two initials, this uniquely identifies your
"man" as you play. The first person to run NLSNIPES is the "starter".
As people run NLSNIPES and enter their initials, they will see the
initials of the other players that are entering the game. Once the
desired group is ready, the "starter" will press ENTER to begin. Move
your "man" through the maze killing snipes, generators, and other
"men". For instructions on how to move and shoot, type "NLSNIPES /H"
at the command-line.
9. Logging in after INSTALL
---------------------------
The first time you login to a newly installed network there will be
only one user defined on the network, SUPERVISOR. To login, type NET
LOGIN SUPERVISOR or type NET and enter SUPERVISOR when prompted for a
username.
If you are installing on a network where other SERVERs are already
running, the user accounts defined on the network will also be defined
on SERVERs you install. You will need to consult with the
administrator of the network to find out what user accounts are defined
and how you may login.
Note: The SUPERVISOR account on a newly installed network has no
password. For security reasons it is recommended that you set a
password on the SUPERVISOR account soon after installation. DO NOT
FORGET THIS PASSWORD!
10. Windows 3.0 Compatibility
-----------------------------
This section contains information about using NetWare Lite with Windows
3.0. Follow the suggestions outlined below to operate your Windows 3.0
environment.
Network vs. Local installation of Windows
Install Windows locally, do not attempt to install it from a Network
Directory. Follow the regular installation procedures using Windows
diskettes. Windows INSTALL may indicate the presence of a "Microsoft
Network (or 100% compatible)" network, change this selection to "No
Network Installed".
Before Entering Windows
It is suggested that you set up your NetWare Lite environment before
running Windows. Such operations include: logging into the network,
mapping drives, and capturing ports.
Mapping Drives
If a SERVER to which you have mapped a drive goes down, Windows will
display a message indicating that the drive does not contain any files.
Any attempt to access that drive will fail. Under regular DOS, this
error is trapped and the CLIENT saves enough information to
automatically restore the connection to that Network Directory when the
downed SERVER returns to the network. Windows prevents regular DOS
from trapping this error.
To restore connections to your mapped drive, exit Windows and re-issue
the NET MAP command when the SERVER is back on the network.
Printing
Use the NET CAPTURE command described in your NetWare Lite User Guide
to re-direct printing from your LPT1 or LPT2 ports to a network printer
before you enter Windows. Configure your printer in Windows to either
the LPT1.OS2 or LPT2.OS2 ports depending on which port you captured
before entering Windows.
Workstations that are configured as both SERVER and CLIENT should use
LPT1.OS2 or LPT2.OS2 to print from Windows. (See the note on Local
Network Printers above)
NetWare Lite SEND messages
NetWare Lite SEND messages will only appear when you open a DOS prompt
or exit Windows.
11. Documentation Errors (Errata)
---------------------------------
Your manual may contain one or more of the following errors.
Page 7 -- In the "Log in to NetWare Lite" section step 3, "NET LOGIN"
should read "NET LOGIN SUPERVISOR". See section 9 above.
Pages 36 and 60 -- Incorrectly state that the supervisor privileges are not
required. That is not correct. Supervisor privileges are required
unless you are running on your own machine.
Page 106 -- Incorrectly states that COM1 and COM2 can be captured using the
NET CAPTURE command. This is not true, only LPT1, LPT2, and LPT3 can
be captured by a CLIENT. NOTE: Serial printers are supported at the
SERVER as Network Printers.
Page 107 -- Is missing the "notify" capture setting. You can specify the
notify option using "N=Y" or "NOTIFY=Y". If set, the SERVER will send
you a message when the print job is done.
Page 149 -- The discussion of network configuration files is not needed.
The NetWare Lite INSTALL utility generates the correct NET.CFG file
from the options you select during installation. After installation,
you can edit the NET.CFG file using any standard ASCII text editor.
WE HOPE YOU LIKE THIS PRODUCT!
Readme file for the
NetWare Requester for OS/2 v2.0
included in the
NetWare Workstation Kit for OS/2 v2.0
June 1992
This Readme file explains known software problems and issues, as
well as corrections to the documentation.
General
-------
#1 This release does not support the remote-boot (RIPL) feature.
Remote-boot support will be included in an NSD at a later date.
#2 If you want to establish file server connections and map drives
before executing the OS/2 startup folder or the STARTUP.CMD file,
add the following line to your AUTOEXEC.BAT file:
CALL=C:\NETWARE\LOGIN.EXE SERVER\USER
If you installed the Requester files in a location other than the
default, replace "C:\NETWARE" with the location of the Requester
files. This capability is useful for automatically starting
programs from network drives.
#3 The NetWare Requester manual incorrectly states that
DBNMPIPE.EXE is found on the NetWare Requester for OS/2 v2.0
diskette. DBNMPIPE.EXE is part of the SQL Server software from
Microsoft.
Virtual DOS and Windows Sessions
--------------------------------
#4 Network support in virtual sessions can be private, global, or
IPX/SPX-only. When you install the NetWare Requester with support
for virtual sessions, the default support is for IPX/SPX-only. IPX/SPX-only
becomes private support when you run NETX.COM in a session.
Note: By default, the NetWare Resources Property will be set to
Private. However, until you run NETX.COM, the support is
actually IPX/SPX-only.
IPX/SPX-ONLY. All DOS and Windows sessions set up for IPX/SPX-only
support do not have a NetWare connection, but they do provide
support for DOS IPX and SPX applications and access to OS/2-redirected
NetWare resources such as drives and printers. IPX/SPX-only support
uses the DOSVIPX.SYS (for VM Boot sessions) and VIPX.SYS
programs included on the NetWare Requester diskette.
PRIVATE. All DOS and Windows sessions set up for private login
support have their own connection to the NetWare network. Private
login support uses the DOSVIPX.SYS, VIPX.SYS, and NETX.COM programs
included on the NetWare Requester for OS/2 diskette.
GLOBAL. All DOS, and Windows sessions set up for global login
support share a single connection to a NetWare network with OS/2
sessions. Global login support uses the DOSVIPX.SYS, VIPX.SYS,
VSHELL.SYS, and DOSVSHLL.SYS programs included on the NetWare
Requester diskette.
#5 Many of your non-NetWare-aware programs will function in an IPX/
SPX-only environment, and since this environment requires the least
setup, you should try your programs in this environment first. If
the programs do not run properly in an IPX/SPX-only environment,
run them in a private or global environment. The private login
environment provides support for all NetWare features and utilities.
The global environment does not currently support the FILER utility and
programs that use temporary drive connections. Support for these
features will be provided at a later time.
#6 For all virtual sessions you start, the COMSPEC variable must
point to the correct version of DOS. If you are running the version
of DOS included with OS/2, the COMSPEC variable should be set as
follows:
SET COMSPEC=drive:\OS2\MDOS\COMMAND.COM
Replace "drive" with the letter of your boot drive. If you are
running another version of DOS, the COMSPEC variable should point
to the location of the COMMAND.COM file for that version. Be sure
to check the COMSPEC variable definition AFTER logging in.
#7 If you are running a Windows program that uses the IPX or SPX
protocol but does not access a NetWare server, you must load the
TBMI.COM program BEFORE running the program. Load TBMI
automatically before each session by including the following line
in your AUTOEXEC.BAT file:
drive:\path\TBMI.COM
Replace "drive:\path" with the location of the TBMI.COM file. By
default, TBMI.COM is copied to the \NETWARE directory with the
other Requester files. For more information about TBMI, see the
NetWare documentation for Windows workstations.
#8 When you log out from an OS/2 session, the drive for your login
directory is drive L:. When you log out from a virtual DOS session,
the drive for your login directory is the last physical drive plus
one. For example, if your last physical drive is C:, the drive for
your login directory will be D:. This means that the drive you see
after logging out depends on whether you log out from a DOS or an
OS/2 session.
Private Virtual Sessions
------------------------
#9 To set up private login support, do the following steps.
A) Make sure network support for virtual sessions was installed
when you installed the Requester. If it wasn't installed, use the
Requester installation procedure to edit the CONFIG.SYS and install
virtual session support.
B) Open the DOS Settings Notebook for a DOS or Windows icon on your
desktop. Modify the Settings notebook for each DOS and Windows
icon you want to have private support.
C) Select the DOS_LASTDRIVE property and type a drive letter other
than Z. The letter should name the last drive you want to appear
as local in this session. In this session, NetWare can use all
drives occurring after the letter you specify.
D) Select the DOS_FILES property and type 255.
E) To enable the NetWare CAPTURE command, select the DOS_DEVICE
property and type the following line:
drive:\OS2\MDOS\LPTDD.SYS
Replace "drive" with the drive letter of your boot drive.
F) Exit the DOS Settings Notebook.
G) Load the NETX.COM program in each session. To load NETX.COM
automatically in ALL DOS and Windows sessions, put the following
command in an AUTOEXEC.BAT file in the root of your boot drive:
drive:\path\NETX.COM
Replace "drive:\path" with the location of NETX.COM. By default,
NETX.COM is installed in \NETWARE with the other Requester files.
To load NETX.COM automatically for every session you start from a
particular icon, use the Optional Parameters feature on the
Settings Notebook for that icon. In the Optional Parameters text
entry box, type /K followed by a space, the directory path, and the
NETX.COM filename. The file will then be executed at the start of
every session opened from that icon. For example, to load NETX.COM
from the default location, type the following:
/K C:\NETWARE\NETX.COM
For more information about Optional Parameters, see your OS/2
documentation.
#10 To access the network from a private session booted with a
version of DOS other than the one included in OS/2, type the
following lines in the CONFIG.SYS file on the DOS diskette or
partition you will boot from:
DEVICE=drive:\OS2\MDOS\FSFILTER.SYS
DEVICE=drive:\path\DOSVIPX.SYS
FILES=255
Replace "drive:\path" with the drive and directory where the
NetWare Requester files are located.
Global Virtual Sessions
-----------------------
#11 To set up global login support, do the following steps.
A) Make sure network support for virtual sessions was installed
when you installed the Requester. If it wasn't installed, use the
Requester installation procedure to edit the CONFIG.SYS and install
virtual session support.
B) Open the DOS Settings Notebook for a DOS or Windows icon on your
desktop. Modify the Settings notebook for each DOS and Windows icon
you want to have global support.
C) Select the NETWARE_RESOURCES property and choose the GLOBAL
button.
D) Exit the DOS Settings Notebook.
#12 To access the network from a global session booted with a
version of DOS other than the one included in OS/2, type the
following lines in the CONFIG.SYS file on the DOS diskette or
partition you will boot from:
DEVICE=drive:\OS2\MDOS\FSFILTER.SYS
DEVICE=drive:\path\DOSVSHLL.SYS
DEVICE=drive:\path\DOSVIPX.SYS
Replace "drive:\path" with the drive and directory where the
NetWare Requester files are located.
#13 The global login support provided with VSHELL does not support
programs, such as NETWARE.DRV, that use temporary drive
connections. Therefore, run Windows programs that are NetWare-
aware--and other programs that encounter problems--in a private
rather than a global environment.
#14 Drive mappings in DOS differ slightly from drive mappings in
OS/2. In OS/2, all mapped drives function like root drives, so
drives mapped in OS/2 sessions will show up as root drives in global
DOS sessions. Root drives mapped in global DOS sessions will show
up as normal drives in OS/2 sessions.
Search drive mappings are not used in OS/2. Therefore, search
drives mapped in global DOS sessions are ignored in OS/2 sessions.
Also, search drives mapped in one DOS session do not apply to other
DOS sessions. To eliminate confusion, avoid using search drives
completely in a global environment. Instead, obtain the same
functionality by setting up your environment as follows:
A) If you want to use both global and private login support from
the same machine, create two "DOS Full Screen" icons on your
desktop. Name one icon for global and one for private.
B) Follow the instructions in the NetWare Requester manual to set
up the DOS Settings for both the global and private icons.
C) Decide which drives you want mapped in your global environment.
Decide which of those drives need to be included in a search path.
D) Edit your OS/2 login script and include map statements for all
NetWare drives.
E) Edit your DOS login script and include map root statements for
all NetWare drives. Use MAP ROOT rather than MAP for consistency
between DOS and OS/2. For easiest maintenance, both login scripts
should contain identical map statements.
F) Create an OS/2 .CMD file which includes a path statement and
the drive letters you want included in the path. The path is where
OS/2 searches for .EXE, .CMD, and .COM files. For example, to
include drive P: in the search path, type the following line in
your .CMD file:
SET PATH=%PATH%;p:\;
Note: The "%PATH%;" appends whatever you type to the directories
that already exist in the PATH statement.
If needed, you can also include a drive letter in the data path
(DPATH). The DPATH is where OS/2 searches for non-executable,
non-.DLL types of files. To include drive P: in the DATH, you would
type the following line in your .CMD file:
SET DPATH=%DPATH%;p:\;
G) Create a DOS .BAT file which includes the same PATH statements
you included in the OS/2 .CMD file. You cannot include DPATH
statements in the DOS .BAT file. DOS PATH statements are limited
to 123 characters, so try to map drives to the exact directories
you need and minimize the number of subdirectories you specify.
H) Run the .CMD file each time you open an OS/2 session. Run the
.BAT file each time you open a DOS global session. One way to do
this is to use the Optional Parameters feature on the Settings
Notebook. In the Optional Parameters text entry box, type /K
followed by a space and the name of the .CMD or .BAT file. The
file will then be executed at the start of every session opened
from that icon.
For more information about PATH, DPATH, Settings, or Optional
Parameters, see your OS/2 documentation.
#15 DOS applications using VSHELL may not be able to open files
on a NetWare v3.11 server if you do not have file scan rights in
the directory where the files are located. If your application
cannot open a file, check your file scan rights. This does not
apply to applications using NETX.
#16 The VSHELL program is compatible with 3.x DOS programs. It is
not compatible with earlier versions of DOS programs that use
NetWare FCB function calls.
Named Pipes and SPX
-------------------
#17 The maximum number of Named Pipes servers supported on a single
network is 100.
#18 The "abort timeout," "listen timeout," "send timeout," and
"verify timeout" settings for the Protocol Stack SPX option have
an upper limit of 65,535 milliseconds.
NetBIOS
---------
#19 Some defaults for the NetWare NetBIOS option in the NET.CFG
file are incorrectly documented in the NetWare Requester manual.
The correct defaults are:
COMMANDS Default=128 commands
NAMES Default=32 names
SESSIONS Default =64 sessions, maximum allowed=64 sessions
#20 Chapter 7 of the NetWare Requester manual shows two incorrect
examples of modifying the PROTOCOL.INI file. In both cases, you
do not need to type "LM10," although "LM10" is shown in the example.
The lines added to PROTOCOL.INI should read:
[NETBIOS]
DriverName = NETBIOS$
ADAPTER0 = IPXNB$,0,16,16,8
#21 To run NetBIOS applications from a virtual session when
Extended Services/LAN Services are NOT loaded, do not install
Novell's NETBIOS.SYS as instructed in the NetWare Requester manual.
Just run the NETBIOS.EXE program in the virtual session. You can only
have one NetBIOS connection per OS/2 machine. It can be either one
DOS/Windows connection or one OS/2 connection.
#22 NetBIOS requests from a virtual Windows session do not go
through Novell's Windows NETAPI.DLL as documented in the NetWare
Requester manual. The requests go directly to NETBIOS.EXE.
Using ODINSUP (Interoperability)
--------------------------------
#23 Each time you install IBM communications and networking
software, install or reinstall the NetWare Requester afterward.
The order that components load in the CONFIG.SYS file is important
when running ODINSUP, NetBIOS, or LANSUP. The NetWare Requester
installation program automatically orders the statements
correctly.
#24 The CONFIG.SYS interoperability example in the NetWare
Requester manual is incorrect. When running the NetWare Requester
with Extended Services or LAN Services, IBM's NETWKSTA.200 file
should load after the NWIFS.IFS in the CONFIG.SYS file. Following
is a new CONFIG.SYS example:
LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\NETWARE;
SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;
C:\;C:\OS2\MDOS;C:\OS2\APPS;C:\NETWARE;L:\OS2;P:\OS2;
SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;
C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS;C:\NETWARE;
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
DEVICE=C:\IBMCOM\PROTOCOL\LANDD.OS2
DEVICE=C:IBMCOM\PROTOCOL\NETBEUI.OS2
rem DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2
RUN=C:\IBMCOM\PROTOCOL\LANDLL.EXE
RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
DEVICE=C:\IBMLAN\NETPROG\RDHELP.200
rem --- NetWare Requester statements BEGIN ---
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
DEVICE=C:\NETWARE\TOKEN.SYS
DEVICE=C:\NETWARE\ODINSUP.SYS
DEVICE=C:\NETWARE\IPX.SYS
DEVICE=C:\NETWARE\SPX.SYS
RUN=C:\NETWARE\SPDAEMON.EXE
rem DEVICE=C:\NETWARE\NMPIPE.SYS
rem DEVICE=C:\NETWARE\NPSERVER.SYS
rem RUN=C:\NETWARE\NPDAEMON.EXE NP_COMPUTERNAME
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE
rem DEVICE=C:\NETWARE\NETBIOS.SYS
rem RUN=C:\NETWARE\NBDAEMON.EXE
DEVICE=C:\NETWARE\VIPX.SYS
RUN=C:\NETWARE\NWSPOOL.EXE
rem --- NetWare Requester statements END ---
IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2
#25 If you are using Token-Ring network boards that support frame
sizes up to 4 KB, type the following lines in your NET.CFG file:
Link Support
buffers 14 4210
The manual incorrectly says to use "15" instead of "14".
#26 If you are using ODINSUP, you do not need to make sure that
the Communications Manager transmit buffers are 6 bytes larger than
your NetWare Requester Link Support buffers. The NetWare Requester
manual is incorrect.
#27 The directions in chapter 6 of the manual for increasing the
packet size are incorrect for network boards that support frame
sizes up to 2 KB. Follow these instructions. If the network boards
you're using support only frame sizes up to 2 KB, the default size
(buffers 20 1514) is adequate for Ethernet boards. If Token-Ring
boards require 2 KB, the size must be increased to
Link Support
buffers n 2154
Replace "n" with a number less than or equal to 28, so that the
maximum memory size of 64 KB is not exceeded.
Using LANSUP (Interoperability)
-------------------------------
#28 Novell's LAN Support (LANSUP) device driver replaces the
CMGRLAN and TOKENEE modules used in the NetWare Requester v1.3.
CMGRLAN and TOKENEE are not supported in the NetWare Requester
v2.0. LANSUP meets the needs of IBM LAN users who would like to
access NetWare but do not have an ODI-compliant network board
driver for the board in the workstation.
LANSUP supports PC Network II in addition to Ethernet and Token-
Ring compatible drivers. ODINSUP and LANSUP provide essentially the
same functionality, but each targets a different communications
interoperability environment (LANSUP for primary IBM LAN users or
ODINSUP for primary NetWare users).
To use LANSUP, do the following:
A) Install all IBM communication and database products that will
be used.
B) Install the NetWare Requester for OS/2 v2.0
C) Modify the CONFIG.SYS file by doing the following:
- Make sure that LANSUP.SYS is loaded after PROTMAN.OS2 and
LSL.SYS. If the CONFIG.SYS contains a statement to load an
ODI driver, replace the ODI driver name with LANSUP.SYS. If
the CONFIG.SYS does not contain an ODI driver, add the
statement to load LANSUP.SYS.
- Make sure that the NetWare NWIFS.IFS loads before the OS/2
NETWKSTA.200 file.
Following is a sample CONFIG.SYS file for using LANSUP:
LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\NETWARE;
SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;
C:\;C:\OS2\MDOS;C:\OS2\APPS;C:\NETWARE;L:\OS2;P:\OS2;
SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;
C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS;C:\NETWARE;
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
DEVICE=C:\IBMCOM\PROTOCOL\LANDD.OS2
DEVICE=C:IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2
RUN=C:\IBMCOM\PROTOCOL\LANDLL.EXE
RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
DEVICE=C:\IBMLAN\NETPROG\RDHELP.200
rem --- NetWare Requester statements BEGIN ---
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
rem Replace TOKEN.SYS with LANSUP.SYS
DEVICE=C:\NETWARE\LANSUP.SYS
DEVICE=C:\NETWARE\IPX.SYS
DEVICE=C:\NETWARE\SPX.SYS
RUN=C:\NETWARE\SPDAEMON.EXE
rem DEVICE=C:\NETWARE\NMPIPE.SYS
rem DEVICE=C:\NETWARE\NPSERVER.SYS
rem RUN=C:\NETWARE\NPDAEMON.EXE NP_COMPUTERNAME
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE
rem DEVICE=C:\NETWARE\NETBIOS.SYS
rem RUN=C:\NETWARE\NBDAEMON.EXE
DEVICE=C:\NETWARE\VIPX.SYS
rem --- NetWare Requester statements END ---
IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2
D) Modify the NET.CFG file by doing the following:
- Use the Link Driver option to enable the frame types supported
by Token-Ring, Ethernet, or PC Network II. You must enable at
least one frame type. Supported frame types are:
token-ring, token-ring_snap for Token-Ring
ethernet_802.2 and ethernet_snap for Ethernet
ibm_pcn2_802.2 and ibm_pcn2_snap for PC Network II
For example, to enable both allowable frame types for Token-Ring,
type the following:
Link Driver LANSUP
frame token_ring
frame token_ring_snap
- Use the Link Driver statement to specify the node address
used by the network board. The node address is normally
printed on the board. For example, to enable one PC Network II
frame type and set the node address, type the following:
Link Driver LANSUP
node address 080000A564CBL
frame ibm_pcn2_802.2
The node address must be a 6-byte hexadecimal number (12
characters) followed by the letter L or M (standing for LSB
or MSB). Note: If you do not know the node address, you can type
a "dummy" address and reboot the machine. At machine start-up,
the correct address will be displayed.
- Use the Link Support statement to increase the size of the packet
to be transmitted. For Ethernet network boards that only support
frame sizes up to 2 KB, the default size (buffers 20 1514) is
adequate. If Token-Ring boards require 2 KB, the size must be
increased to
Link Support
buffers n 2154
Replace "n" with a number less than or equal to 28, so that the
maximum memory size of 64 KB is not exceeded. For Token-Ring
boards that support frame sizes up to 4 KB, type the following
statement:
Link Support
buffers 14 4210
- (Optional) Change the default for whether addresses are
transmitted in canonical (least significant bit first) or
non-canonical (most significant bit first) form. By default,
Token-Ring and PC Network II frames are in non-canonical (or
MSB) format and Ethernet frames are canonical (LSB).
To change the default, add an LSB or MSB keyword after the
frame statement. For example, to enable both Token-Ring frame
types, and override the non-canonical form for one of the
frame types, add the following statement:
Link Driver LANSUP
frame token_ring
frame token_ring_snap lsb
Note: MSB and LSB can only be used if the network board
driver supports Octet Bit Reversal (OBR).
Microsoft LAN Manager
Version 2.1
Supplemental Information for Remoteboot Users
Copyright 1991 Microsoft Corporation.
All rights reserved.
Microsoft, MS, and MS-DOS are registered trademarks and
Windows is a trademark of Microsoft Corporation.
Operating System/2 and OS/2 are registered trademarks
licensed to Microsoft Corporation.
U.S. Patent Number 4955066.
Introduction
------------
This file reflects last-minute enhancements and tips for using
the Remoteboot service in Microsoft LAN Manager 2.1. For general
information, see also the file README.TXT on the OS/2 SETUP disk
included with Microsoft LAN Manager 2.1.
This file includes the following sections:
- Upgrading from an Installation Running the Remoteboot Service
- Copying Remoteboot System Files
- The PROTOCOL.INI file on MS-DOS Remoteboot Workstations
- TSRs and Remoteboot Workstations
- Using TCP/IP Protocols on Remoteboot Workstations
- Running PING and Other TCP Utilities from a Remoteboot Workstation
- Setting up Windows on a Remoteboot Workstation
Upgrading from an Installation Running the Remoteboot Service
-------------------------------------------------------------
The following extra steps should be taken when upgrading a
LAN Manager server that is running the Remoteboot service:
1. If Remoteboot is listed as a SRVSERVICE in the [server] section of
LANMAN.INI, remove it.
2. Follow the upgrade instructions in the Microsoft LAN Manager
Installation and Configuration Guide.
3. After completing the installation, run SETUP.EXE from the
LAN Manager root directory.
4. Choose Configure.
5. Choose Network Drivers.
6. Choose the configuration that contains the Remoteboot protocol.
7. Choose <Add/Remove Protocols>.
8. Remove and then immediately re-add Remoteboot.
9. Select <OK>, then <OK>, and then <Save>.
10. When you are prompted to insert the Microsoft LAN Manager OS/2
Drivers disk, insert it. The necessary files will be copied.
11. After the files have been copied, exit the Setup program.
12. Run RPLSETUP.
Copying Remoteboot System Files
-------------------------------
When copying operating system files to the \RPL tree, you must remove
the system (S) attributes, as well as the hidden (H) attributes, so that
the files can be found by the remoteboot workstation.
The PROTOCOL.INI file on MS-DOS Remoteboot Workstations
-------------------------------------------------------
The LANMAN.DOS\PROTOCOL.INI file used by an MS-DOS remoteboot workstation
is created each time the workstation boots. If you edit the workstation
copy of this file, the changes will disappear the next time you
remotely boot the workstation. To make permanent changes, edit the
LANMAN\RPL\BBLOCK\NETBEUI\adapter\PROTOCOL.INI file on the server.
TSRs and Remoteboot Workstations
--------------------------------
Certain TSR (terminate-and-stay-resident) programs and device drivers
should not be loaded before the NET START WORKSTATION line runs on
remoteboot workstations. If you encounter problems while attempting to
boot a remoteboot workstation, check the AUTOEXEC.BAT file for the
remoteboot workstation, and move TSRs below the NET START WORKSTATION
command. If you still encounter problems, check the CONFIG.SYS file, and
comment out device drivers (particularly disk-caching drivers) that may
be causing problems.
Using TCP/IP Protocols on Remoteboot Workstations
-------------------------------------------------
By default, the NetBEUI protocol is statically loaded and bound on
remotely booted workstations. In addition, you can set up the Remoteboot
service so that users at remoteboot MS-DOS workstations can dynamically
load and unload the other protocols (one at a time).
To use TCP/IP in addition to NetBEUI, your Remoteboot server's
LAN Manager root directory must have the subdirectory
\RPL\RPLFILES\BINFILES\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP. Create any
directories in this path that do not exist. Then follow these steps
(before running RPLINST):
1. Copy all files from the \DRIVERS\PROTOCOL\TCPIP subdirectory
on the LAN Manager MS-DOS Drivers disk to the
\RPL\RPLFILES\BINFILES\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP
subdirectory of the server's LAN Manager root directory.
Type DECOMP input_file output_file to decompress the files
with extensions ending in "$."
- All .EX$ files should be decompressed to .EXE files,
and UNLOAD.EXE should then be renamed UNLOADT.EXE.
- All .86$ files should be decompressed to .86 files.
- All .CO$ files should be decompressed to .COM files.
- All .DO$ files should be decompressed to .DOS files.
2. After the files are decompressed, you may delete all files ending
in "$" to recover disk space. If you have already run RPLINST, run
it again to set the protections for these files.
3. Remotely boot an MS-DOS workstation, log on as administrator, and
edit the profile's AUTOEXEC.BAT file, removing REM from the
beginning of the UMB.COM line. Edit the profile's CONFIG.SYS file,
removing REM from the beginning of the DEVICE=NEMM.DOS line.
4. From the Remoteboot Manager screen, choose New workstation.
For those workstations that will use TCP/IP, define an IP
address, a subnet mask, and a gateway in the boxes provided.
The next time the workstation is remotely booted, the user can load the
TCP/IP protocol using the command LOAD TCPIP.
Running PING and Other TCP Utilities from a Remoteboot Workstation
------------------------------------------------------------------
TCP utilities such as PING require that the NMTSR.EXE terminate-and-stay-
resident program be running. On remoteboot workstations, you must load
this program explicitly after loading the TCP/IP protocol and before
using a TCP utility. NMTSR.EXE is located in the \DRIVERS\PROTOCOL\TCPIP
subdirectory of the LAN Manager root directory for the workstation.
Setting up Windows on a Remoteboot Workstation
----------------------------------------------
When setting up the Microsoft Windows 3.0 environment on a remoteboot
workstation that does not have an A: drive or B: drive, you must use
the ASSIGN command to create the drives before running the Windows
SETUP program. To do this, type
ASSIGN A=C
ASSIGN B=C
Note: This is required only for the Windows SETUP program.
LAN Manager 2.2 Readme Files The information that follows supplements the LAN Manager 2.2 Release Notes and documentation set. The README.DOC and README.TXT files contain identical information. If Your Workstation Hangs During Background Operations If your workstation hangs during background network operations, you may want to install COMNDIS.COM, which is included on your LAN Manager 2.2 installation disks. COMNDIS.COM is a terminate-and-stay-resident (TSR) program that prevents multiple processes from accessing the adapter card while the card is handling an MS-DOS command. COMNDIS.COM must be started before any LAN Manager commands are issued, with the exception of the netbind command. If you want to use COMNDIS.COM, you should start it with a command in the AUTOEXEC.BAT file. If you are using netbind, the following command should appear after the netbind command, but it should appear, before any other LAN Manager commands. The command is of the form: comndis x where x is the interrupt number for the LAN Manager adapter. If You Are Using Windows for Workgroups with MS TCP/IP If you are using Windows for Workgroups and MS TCP/IP, you may want to use the PING utility. To run PING.EXE you must first run NMTSR.EXE. NMTSR is a terminate-and-stay-resident (TSR) program that must be loaded before the Windows operating system is started. You may wish to start it with an appropriately placed line in the AUTOEXEC.BAT file.
README FILE FOR VIRTUAL DEVICE VPCTCP.386 AND DATALINK LIBRARY PCTCPAPI.DLL --------------------------------------------------------------------------- The device driver VPCTCP.386 enclosed on this diskette allows multiple PC/TCP applications to access the PC/TCP kernel while running Microsoft Windows in 386 Enhanced mode. The DLL, PCTCPAPI.DLL, enclosed on this diskette is for use with vendor written Windows applications. See the sample SYSTEM.INI, and PCTCP.INI also enclosed on this diskette, for more information on setting up your Windows environment. The PCTCP.GRP file contains entries for all of the enclosed .PIF files. Adding this group to your PROGMAN.INI configuration file will allow you to access the PC/TCP applications via the mouse as well as from the DOS prompt. Version 3 - wcl 19-Jul-91
PC-NFS(R) RELEASE NOTES
(C)1992 by Sun Microsystems, Inc. - Printed in the United
States of America.
All rights reserved. No part of this work may be reproduced
in any form or by any means - graphic, electronic or mechanical,
including photocopying, recording, taping, or storage in an
information retrieval system - without prior written permission
of the copyright owner.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by
the government is subject to restrictions as set forth in
subparagraph (c)(1)(ii) of the Rights in Technical Data and
Computer Software clause at DFARS 252.277-7013 (October 1988)
and FAR 52.277-19 (June 1987).
The product described in these Release Notes may be protected
by one or more U.S. patents, foreign patents, and/or pending
applications.
PC-NFS and NFS are registered trademarks of Sun Microsystems,
Inc. in the United States and other countries. All other
products and services mentioned in these Release Notes are
identified by the trademarks as designated by the companies
that market those products or services. Inquiries concerning
such trademarks should be made directly to those companies.
**OVERVIEW**
Please read these Release Notes before installing PC-NFS 4.0
software. These notes describe:
o Installation
o Configuration
o Locking Services and PCNFSD
o General Notes
o Microsoft(R) Windows(TM) Support
o Printing
o Applications Compatibility
**INSTALLATION**
BEFORE A "BASIC" UPGRADE REMOVE CERTAIN PC-NFS FILES
The "basic" upgrade installation procedure does not remove
the following files installed by earlier versions of PC-NFS
software. To avoid any conflicts with PC-NFS 4.0 software,
delete these files before upgrading PC-NFS software.
(Consult the "PC-NFS Installation Guide" for a definition of
"basic" installation.)
ARP.EXE FTP.EXE NFSPING.EXE RCP.EXE
CHMOD.EXE HANGUP.EXE NFSRUN.EXE RDATE.EXE
CONNECT.EXE LPD.EXE NFSSTAT.EXE RPCINFO.EXE
DOS2UNIX.EXE LPT.EXE NISCAT.EXE RSH.EXE
EM.COM LS.EXE NISMATCH.EXE SHOWMNT.EXE
EM.SES MV.EXE PCNFSCFG.EXE SNMP.EXE
EMTELNET.EXE MYEADDR.EXE PCNFSLPD.EXE TELNET.EXE
EM_MSG.TXT NETSTAT.EXE PING.EXE UNIX2DOS.EXE
After you have deleted the files listed above, follow the basic
upgrade installation procedure described in Chapter 4 of the
"PC-NFS Installation Guide."
REMOVE /Y OPTION IN CONFIG.SYS WHEN UPGRADING PC-NFS SOFTWARE
If you are running MS-Windows, and you plan to upgrade from PC-NFS
Version 3.5, you must remove the /y option from the PCNFS.SYS
line in the CONFIG.SYS file before upgrading. Refer to the "PC-NFS
Reference Manual" for details about the /y option.
INSTALLING PC-NFS SOFTWARE WITH AN NDIS DRIVER
QUIKNDIS is a utility supplied with PC-NFS software which assists
you in configuring an NDIS driver for use with PC-NFS software. If
you plan to use an NDIS driver, you may use the QUIKNDIS utility
on the QUIKNDIS diskette. If your system administrator has installed
QUIKNDIS on the network, you may run it from the network instead.
Read the QUIKNDIS README file before you install PC-NFS software for
important information about installing PC-NFS software for use with
an NDIS driver.
EXIT MS-WINDOWS BEFORE REBOOTING PC
When prompted to reboot after installing or configuring PC-NFS
software within MS-Windows, exit MS-Windows before rebooting
your PC.
THIRD-PARTY MEMORY MANAGER LOAD-HIGH LINES OVERWRITTEN
If you are using a third-party memory manager with PC-NFS software,
e.g., QEMM (TM), any lines in AUTOEXEC.BAT or CONFIG.SYS that load
PC-NFS device drivers or TSRs into high memory will be overwritten
when you upgrade PC-NFS software. After upgrading, manually edit the
lines in AUTOEXEC.BAT or CONFIG.SYS so that these programs will be
loaded into high memory.
**CONFIGURATION**
DO NOT LOAD PROTMAN.SYS INTO HIGH MEMORY
If you reconfigure any of the PC-NFS drivers to load high using
MS-DOS(R) 5.0, DR DOS(TM), or a third-party memory manager, make
sure that PROTMAN.SYS is not loaded high.
SOME SERVER NAMES IN NFSCONF CANNOT EXCEED 15 CHARACTERS
When defining a PCNFSD server, NIS server, or gateway in the
NFSCONF Advanced Questions screen, you cannot enter a server name
that exceeds 15 characters. PC-NFS software will accept server names
up to 64 characters, but not in the NFSCONF program. You must enter
any server name exceeding 15 characters in the appropriate line in
the NETWORK.BAT file, as described below.
If you are configuring PC-NFS software for the first time, follow
these steps:
1. Proceed according to the configuration instructions in the "PC-NFS
Installation Guide" with the following exception: in the Advanced
Questions screen, leave the server name field blank if you intend
to use a server name that exceeds 15 characters.
2. When prompted, press N to defer a reboot and exit to DOS.
3. Using a text editor, modify the NETWORK.BAT file as necessary to
contain lines similar to the following:
NET ROUTE shishkebob.East.Sun.COM
NET NISSET baklava.East.Sun.COM
NET PCNFSD souvlaki.East.Sun.COM
4. Reboot the PC for your changes to take effect.
If you are reconfiguring PC-NFS software, modify NETWORK.BAT as
described in the previous instructions, and do not use the Advanced
Questions screen to change your configuration.
GATEWAY AND PCNFSD SERVER NAME FIELDS SHOULD NOT BE BLANK IN NFSCONF
If your network uses a gateway, enter the gateway name in the Advanced
Questions screen of the installation program, or edit the name manually
in the NETWORK.BAT file as described in the preceding note. If you do
not, an incorrect gateway name may be used (with NIS), or your PC will
not be able to reach machines outside of the local network (without NIS).
USE DEFAULT SETTINGS FOR IBM(R) TOKEN RING(TM) ADAPTER ON MICROCHANNEL PC
If you are using an IBM PS/2(R) or other Microchannel PC and an IBM Token
Ring adapter with the PC-NFS (non-NDIS) driver TRDRIVEM.SYS, the Token
Ring adapter must be configured with the default ROM and RAM settings.
To do this, reboot your PC with the system reference diskette supplied
with the PC, choose the menu options to view the current configuration,
and verify that the ROM address is CC000H and that the RAM is configured
with 16 Kbytes of RAM based at D8000H. If the adapter settings are
different from this, use the menu options to change them. Consult your
PC and adapter documentation for more information.
If you cannot reconfigure your Token Ring adapter for any reason, you
can still run PC-NFS software using the NDIS driver. Consult the
"PC-NFS Installation Guide" for instructions.
**LOCKING SERVICES AND PCNFSD**
INSTALLING THE LOCK DAEMON
Read this note if you are a system administrator who wants to install
PC-NFS locking services on an NFS(R) server. The dolockd.sh script
should only be run on a server with SunOS(TM) 4.1 or 4.1.1, and a
Sun-3x, Sun-4(TM), or Sun-4c architecture.
The dolockd.sh script does not install a lock daemon for the Sun-3(TM)
architecture. If you are using a server with the Sun-3 architecture,
you can run the lock daemon from PC-NFS 3.5 software. If you do not
have PC-NFS Version 3.5 software, you can obtain a patch from your
local support representative.
To determine the server's architecture, run the following command:
arch -k
PC-NFS 4.0 ships a lockd and kernel patch (release 100075-06) on the
distribution diskette. If a later patch has been installed
(e.g., release 100075-07), do not run the dolockd.sh script.
The dolockd.sh script does not support the Sun-4m architecture. Servers
with this architecture should be running SunOS 4.1.2 or greater, which
supplies an appropriate lock daemon.
COMPILING PCNFSD ON AN IBM RS6000
To compile PCNFSD Version 2 on an IBM RS6000, modify the PCNFSD
Makefile by adding the -D_BSD option to the CFLAGS line below:
CFLAGS= -g -DUSER_CACHE -DWTMP -DUSE_YP -D_BSD
For more information about installing PCNFSD, refer to the "PC-NFS
Administration Guide."
**GENERAL NOTES**
RUNNING PC-NFS UTILITIES WITH LIMITED MEMORY
Many PC-NFS utilities require the resident transport module (RTM)
and the resident naming module (RNMFILE or RNMNIS) to be installed
in order to operate. These utilities automatically load RTM and the
resident naming module if they are not already loaded. When these
modules are automatically loaded, the utilities reserve more than
the required amount of memory. When you load them from the command
line, they do not require as much memory.
If a PC-NFS application fails unexpectedly, e.g., you cannot mount
a printer by using NFSCONF, exit the application. Load RTM and then
load either RNMFILE or RNMNIS from the DOS command line and rerun
the application. Refer to the "PC-NFS Reference Manual" for
information about RTM, RNMFILE, and RNMNIS.
MV COMMAND WITH LOCAL FILES MAY GENERATE INCORRECT ERROR MESSAGE
When renaming local files and directories, the MV command sometimes
displays the following message even though the file or directory was
renamed correctly:
NFS081F : File not found, or access violation.
PROBLEMS WITH LONG ICMP PACKETS
PC-NFS software does not correctly handle ICMP packets (e.g., PING)
with 256 bytes or more of data. Two problems can occur: (1) any
PING reply will be incorrectly formatted, and (2) if using a 3Com
adapter with a non-NDIS driver, the PC may ignore all subsequent ICMP
packets.
Using an NDIS driver prevents the second problem from occurring, but
not the first. For details about configuring PC-NFS software for use
with an NDIS driver, refer to the "PC-NFS Installation Guide" or the
README file on the QUIKNDIS diskette supplied with PC-NFS software.
PC MAY HANG IF CTRL-BREAK IS USED TO ABORT PROGRAM WHILE LOADING
Your PC may hang if you use CTRL-BREAK to stop a large executable file
from loading. This is true with any application - not just those
supplied with PC-NFS software.
MYEADDR UTILITY HANGS PC WITH 3COM(R) 3C505 BOARD
Do not use the MYEADDR command if your PC has a 3Com 3c505 board.
To determine the board's Ethernet(R) address, use the diagnostic
program supplied with the board.
SHOWMNT -L COMMAND MAY CAUSE PC TO HANG
Do not use the SHOWMNT -L command. Doing so may cause your PC to hang.
USE LATEST RTM AND RNM MODULES
If you install both PC-NFS 4.0 and the PC-NFS Programmer's Toolkit 2.0
on the same PC, or if you use an application which is distributed
with the resident modules (RTM and either RNMFILE or RNMNIS), verify
that you are using the most recent resident modules.
You can check the version of each module using the -v option: the files
distributed with the Toolkit are identified as 2.0, while those shipped
with PC-NFS Release 4.0 are identified as version 3.0.
If you install the PC-NFS Programmer's Toolkit 2.0 after you have
installed PC-NFS software, make sure that the resident modules supplied
with PC-NFS 4.0 are not overwritten.
**MICROSOFT WINDOWS SUPPORT**
USE PRINT MANAGER TO CONTROL PRINTING
When configuring Printers to be used with PC-NFS software, it is
recommended that you use the Print Manager. You can do so by selecting
"Use Print Manager" in Control Panel. Print Manager correctly handles
output redirection to a local or remote printer. If you have problems
printing to a local printer (i.e., one attached to your machine), go
to Print Manager and verify that "Print Net Jobs Direct" is disabled.
In Windows 3.1, select "Options" and then select "Network Settings."
In Windows 3.0, select "Options" and then select "Network."
MANUALLY UPDATE NETWORK QUEUE STATUS WHEN USING PRINT MANAGER
If you are viewing a network print queue using Print Manager, the
status of the print job will not be automatically updated by Print
Manager. To update the status of the print queue manually, follow
one of these procedures:
o If using MS-Windows 3.0, choose Update Net Queues from the View
menu.
o If using MS-Windows 3.1, choose Refresh from the View menu.
TELNET IN MS-WINDOWS DOES NOT SCROLL PROPERLY
If you are running TELNET within MS-Windows, scrolling may work
incorrectly and the bottom half of the screen may appear blank.
This problem appears to be associated with particular MS-Windows
video drivers.
If this occurs, you can iconize TELNET and reopen the window, or
maximize the window. If you are running an application in your
TELNET session, enter the appropriate keystrokes for your
application to refresh the screen. For example, to refresh the
screen when you are using vi, enter command mode and type CTRL-L.
FILE MANAGER DRIVE ICON INCORRECTLY APPEARS TO BE A LOCAL DRIVE
If the network path of the file system you are mounting exceeds
64 characters, MS-Windows File Manager will incorrectly display
the Disk-drive icon in the Directory Tree window as a local drive,
rather than as a network drive. This has no effect on operation.
INCORRECT DATE AND TIME DISPLAYED WHEN VIEWING PRINT QUEUE
When you view a print queue using MS-Windows Print Manager, the date
and time are incorrectly displayed. You may turn off the date and
time display by using the View submenu in Print Manager.
CANCELLING PRINTING FROM MS-WINDOWS APPLICATIONS LEAVES PART OF JOB
IN QUEUE
This applies if you decide not to use Print Manager and instead,
you print network jobs directly. If you print from an MS-Windows
application, a dialog box is displayed while the job is being spooled,
enabling you to cancel the print job. If you select "Cancel," the job
stops spooling; however, the portion of the file that is already
spooled to the print queue will be printed.
PING COMMAND DOES NOT WORK WITHIN MS-WINDOWS WITH 3C501 BOARD
If your PC has a 3Com 3c501 board and you are running MS-Windows,
you cannot use the PING command to reach a machine on your network.
To avoid this problem use an NDIS driver with this board.
**PRINTING**
USING INCORRECT SYNTAX FOR TIME-OUT OPTION CAUSES PC TO HANG
Any time you change the time-out option -Tnnn for the PRT.COM program,
make sure that you do not enter a space between the -T option and the
<nnn> variable. Doing so causes your PC to hang.
Use the syntax:
PRT -Tnnn *
where <nnn> is the number of seconds that PC-NFS software waits before
spooling the print job.
DIRECTIONS FOR INSTALLING AN HP LASERJET(TM) PRINTER ON A SUN SERVER
To set up an HP LaserJet printer on a Sun server and make the printer
available for printing from PC applications configured for HP LaserJet
printers, follow this procedure:
1. Make the following entry in the /etc/printcap file on the Sun
server and save the file:
hplaser|hplaser|HP LaserJet in PGL mode:\
:lp=/dev/ttya:br#9600:
:ms=pass8,ixon,raw:\
:sh:\
:sd=/var/spool/hplaser:\
:lf=/var/spool/lpd/log:
2. Make this printer available to PC-NFS software users by creating
the spool directory /var/spool/hplaser.
3. Export the spool directory by adding the directory name to the
/etc/exports file.
When you mount the LaserJet printer from a PC, use the print filter
option, Raw (unfiltered).
SPECIFYING TRAILER OPTION WHEN USING PC PRINT SERVER
When the PC print server sends a print job to the local printer, it
uses the CTRL-L (form feed) character as the default end-of-job
character. If you do not want to send this character to the printer
(because you do not want a page eject, because you want to send
different end-of-job characters, or because CTRL-L hangs the printer),
you can use the trailer option when starting the print server.
To start the print server from the command line with the trailer
option, use the following syntax:
pcnfslpd -P<printdevice unixname> -t[<printername>] {<filename> or NUL}
where:
<printername> is the name of the printer to which the trailer option
applies. If <printername> is not specified, the trailer option applies
to all printers.
<filename> is the name of the file residing in the \NFS directory which
contains the end-of-job characters that you want to send to the printer.
If you do not specify a filename, the default end-of-job character
CTRL-L (form feed) will be sent to the printer. If you do not want the
default to be sent to the printer, specify NUL.
To start the print server using a PCNFSLPD.INI file with the trailer
option, add the following line to the file:
TRAILER [<printername>] {<filename> or NUL}
For example, to start the print server and send CTRL-L to printer lp1,
and prevent CTRL-L from being sent to printer ps2, enter the following
command:
pcnfslpd -PLPT1: lp1 -PCOM1: ps2 -tCOM1: NUL
To start the print server using the PCNFSLPD.INI file, and to send
the end-of-job characters contained in the file named TRAIL.LP to
the printers lp1 and lp2, add the following lines to PCNFSLPD.INI:
PRINTER LPT1: lp1
PRINTER LPT2: lp2
TRAILER TRAIL.LP
For more information about the print server start-up options,
refer to Chapter 4 of the "PC-NFS User's Guide."
PRINT JOBS SENT TO SERIAL PORT MAY BE LOST WHEN USING PRINT SERVER
Your print jobs may be lost if you use the print server on a printer
attached to a serial port and the following conditions apply:
o The printer has generated an error condition (e.g., "out of
paper"), and
o There are other print jobs in the queue.
As a workaround, re-send the print job.
USE LPT D COMMAND ONLY TO DELETE JOBS SENT TO PC PRINT SERVER
The LPT D command can only be used to delete jobs that are sent to
a PC print server. To delete other jobs, use the NET CANCEL command.
Refer to the "PC-NFS Reference Manual" for information about the
NET CANCEL command.
**APPLICATIONS COMPATIBILITY**
MS-DOS 5.0 DOSSHELL PROGRAM COPIES FILE TO INCORRECT LOCATION
When you use the MS-DOS 5.0 DOSSHELL program to copy a file to
a subdirectory on a network drive, the file is copied to the root of
that network drive, instead of the subdirectory.
MS-DOS 5.0 BACKUP COMMAND WORKS INCORRECTLY ON NETWORK DRIVES
The MS-DOS 5.0 BACKUP command does not work correctly when you attempt
to back up files to a network drive.
HARVARD GRAPHICS(TM) DOES NOT RETRIEVE FILES WITH SHORT NAMES
When using Harvard Graphics with certain versions of DOS, you
cannot retrieve a previously created file if the file name consists
of fewer than eight characters before the extension or fewer than
three characters after the extension. This is due to the way some
versions of DOS treat short file names. To access these files,
change the file name or use the /s option in the PCNFS.SYS line
in CONFIG.SYS. (See the "PC-NFS Reference Manual" for information
about using the /s option in the CONFIG.SYS file.)
DO NOT USE PC-NFS UTILITIES AFTER ISSUING DOS ASSIGN COMMAND
If you use the ASSIGN command after PC-NFS software has been started,
you will be unable to use PC-NFS applications or utilities that require
RTM to be loaded. There are two ways to avoid this problem if you need
to use the ASSIGN command: (1) Use the ASSIGN command before you start
PC-NFS software, or (2) Load RTM after you start PC-NFS software but
before you use the ASSIGN command. Note that PC-NFS software does not
support the use of the ASSIGN command to map network drives.
PC-NFS SOFTWARE MAY NOT DETECT FILES LOCKED WITH DBASE(R) IV VERSION 1.1
Although a file has been locked with dBase IV Version 1.1, PC-NFS
software may not detect that the file has been locked. Users
experiencing this problem should use a later version of dBase IV.
Part No. 800-6928-10
Revision A, March 1992
Ps/2 lotus 123 软件可在 Ps/2 的 Dos 3.3 操作系统支持下运行，
第一次起动时必须键入 lotus，否则程序执行中会出错。第一次装入之
后，以后只要不重新启动（冷、热）系统，直接键入 123便可重新进入
123 系统。Ps/2 lotus 123除上述同西文版的使用区别外，还有以下几
个功能键同原西文版的定义有所区别，下表列出了这些功能键在本软件
中得定义：
Alt+F1 区位码输入 Alt+F2 首尾码输入
Alt+F3 拼音码输入 AlT+F4 快速码输入
Alt+F6 ASCII码输入 Ctrl+F6 背景色开关键
Ctrl+F7 英文方式键 Ctrl+F8 光标开关键
Ctrl+F9 纯中文方式键 Ctrl+F10 打印控制键
上述各功能键是由中文操作系统定义，Ps/2 lotus 123 将原Alt+F1和
Alt+F2 的功能用 Alt+F11和 Alt+F12代替、Alt+F3 和 Alt+F4的功能
用 Ctrl+F11和 Ctrl+F12代替。
Thank you for your purchasing our pointing device. In order to use the pointing device driver version 8.03 correctly and efficiently the driver commands are listting as belows: Usage : MOUSE [1-4] [/X] [P,B] [0,U] [/H/?] 1. Help : /H (or /?) --- Display Help Screen 2. Device port setting : /1 --- COM1:(03F8,IRQ4) /2 --- COM2:(02F8,IRQ3) /3 --- COM3:(03E8,IRQ4) /4 --- COM4:(02E8,IRQ3) 3. Mouse type setting : /P --- Use PS2 & compatible Mouse on Pointing Device Port /B --- Use Bus Mouse (2 button) on Bus Mouse Port /B3 --- Use Bus Mouse (3 button) on Bus Mouse Port 4. Mode setting : for auto-switching mouse only no parameter --- Default on Microsoft Mode /X --- Switch to Mouse system Mode 5. Release driver : /0 (or OFF)--- Uninstall Mouse Driver and Free memory
1-2-3 Release 4 中文版 自述文件 (README.TXT)
**目录**
1. 安装
升级说明信息
网络安装
用 CD-ROM 驱动器安装
2. Windows 与可用内存
3. 有关图表的升级说明信息
4. 打印操作的信息
打印机设备与驱动程序
打印机分辨率
5. DataLens 与 ODBC 驱动程序
ODBC 驱动程序
IBM 数据库管理程序 (IBM Database Manager)
环境变量
LOTUS.BCF 文件
6. 版本管理器
7. 求解器
8. 命令行参数
9. 字体用法
字体的对映
字体操作的提示
安装及删除 ATM
10. CUI 命令
11. 新的@函数
12. 日期格式
13. Lotus 应用软件的整合
14. 「按范例填充」功能的范例
**1. 安装**
升级说明信息
1-2-3 Release 4 中文版需要使用中文版 Windows 3.1 (以下的 Windows 均指中文版)
或以后的版本。
如果您的机器已安装其他版本的 1-2-3 Release 4 (如英文版)，请先将其他版本的程
序文件清除干净，并将 Windows 目录下的 123r4.ini 删除，再安装新版的 1-2-3。
如果您的 Windows 目录与您的 1-2-3 目录分别在不同的磁盘上，则您的 Windows
目录所在的磁盘至少须有 1.5MB 到 2MB 的空间。
网络安装
若希望在多台单机式计算机上以最便捷的方式安装 1-2-3，请将 1-2-3 Release 4
所有的文件拷贝到网络服务器上，让已经获取使用授权的用户能从服务器将 1-2-3
安装到他们的硬盘上。
请遵循下列指示，将 1-2-3 拷贝到服务器上：
1. 依照第 1 片磁盘上标签的指示启动安装程序。
2. 在记录您的姓名及公司名称的对话框中输入您的姓名及公司名称，然后选取
「确定」钮。
附注：每一个从服务器进行安装的用户，都必须在安装时输入他(她)的姓名，
但这时候输入的公司名称会永久保留下来。
3. 选取「确定」钮以确认所输入的名称。
4. 选取「结束安装」可结束安装程序。
5. 结束 Microsoft Windows。
6. 在 DOS 下输入 a:crsby 并按 ENTER 键。
如果第 1 片磁盘不在驱动器 A:，请输入正确的驱动器号。
CRSBY.BAT 会将压缩过的 1-2-3 文件拷贝到服务器上，并提示您更换磁盘，直到
复制好所有的文件。
这时用户可以按照下列指示，在他们的硬盘上安装 1-2-3 Release 4。
1. 在 Windows 程序管理器中，选择[文件][运行]。
2. 在「命令行」正文框中输入 [x]:\路径\install。
「[x]:\路径」是包含所有 1-2-3 文件的服务器目录路径和驱动器号。例如：
输入 t:\C123R4W\install 可从驱动器 T: 目录名称为 \C123R4W 中启动安装程
序。
3. 选取「确定」钮。
安装程序会显示一系列的对话框，它们会提示用户安装的项目及如何安装等
信息。
用 CD-ROM 驱动器安装
如果您是在附有 CD-ROM 驱动器的计算机上安装 1-2-3，请在启动安装程序之前，先确
认是否已经关好 CD-ROM 驱动器。
**2. WINDOWS 与可用内存**
附注：Windows 3.1 所需要的内存比 Windows 3.0 多，因此，在您同起使用
Windows 3.1 和 1-2-3 之前，如有必要，请先释放额外的内存。
在您启动 1-2-3 之前，请先查看您还有多少内存可用，其方法是：打开程序管理
员，并选取[帮助][关于程序管理器]。
如果可用内存少于 1800K，便无法启动 1-2-3 Release 4。这时请关闭已打开的所
有应用软件，并删除某些常驻内存的程序，以腾出更多可用的空间。然后再次检查
可用内存的总数。
若可用内存仅稍微大于 1800K，则虽然可以启动 1-2-3，但在工作时，可能会出现
内存已满这类信息。
以下是有关如何增加可用内存容量的一些建议。
* 若要节省最多的内存空间，请删除 SMARTdrive。(若您不想拿掉 SMARTdrive，
请参考下一项，以减少 SMARTdrive 快速存取内存所占的空间。)
如果要删除 Windows 3.1 中的 SMARTdrive，请从 AUTOEXEC.BAT 中删除
[x]:\WINDOWS\SMARTDRV.EXE 这条语句。
您可以删除这条语句，或是在该语句的前面输入 REM。例如：
REM [x]:\WINDOWS\SMARTDRV.EXE
* 若不想删除 SMARTdrive，您可以将 SMARTdrive 的快速内存缩小为 256K，以
节省内存的空间。
在 Windows 3.1 中，将 AUTOEXEC.BAT 中 SMARTdrive 语句改成
[x]:\WINDOWS\SMARTDRV.EXE 1024 256。
* 仅适用于 386 的用户：加大 Windows 的交换文件 (swap file)，使它至少达
1MB。若要知道如何改变交换文件的大小，请参考 Microsoft Windows 的相关文
件。
* 仅适用于 Windows 3.1 的用户：Windows 3.1 中附有可调整的字体管理器，
因此您可以关闭 ATM 以节省大量的内存空间。如果要关闭 ATM，请双击
ATM 控制面板图标。在 ATM 之下，选取「关闭」。再选取「结束」；然后重新
启动 Windows。
提示：如果 1-2-3 显示「内存不足」或「Windows 资源不足，无法完成操作」等
信息，而且您无法使用[文件][保存]将文件保存起来，这时请用快速键 Ctrl+S。
**3. 有关图表的升级说明信息**
若要使用您在旧版的 1-2-3 for Windows 所创建的图表(但尚未将它们加到工作表中)，
请打开包含那些图表的 .WK3 文件，并选取[编辑][转移]。在「表项的类型」下拉表
中选取图表，然后在列表框中选取图表名称。
1-2-3 会将该图表加到当前在屏幕上显示的工作表区域的中央。然后，您可以将图
表移到工作表的任一处。
**4. 打印操作的信息**
使用 1-2-3 传统打印命令
1. 传统命令菜单上的打印命令，只支持单字节字符的打印操作。
2. 使果用户想通过传统命令的打印选项来打印工作表，则用户必须选取打印
命令后，选取打印结束，以结束传统命令。
打印机设备与驱动程序
打印机制造厂商通常会定期的更新打印机驱动程序。某些时候，厂商可以供应您比
Windows 3.1 所附的驱动程序还要新的版本。若想知道是否有更新的驱动程序
可供您的打印机使用，请随时查看电子布告栏，如 CompuServe ，或与您的打印机厂
商联系。
下表列出市面上较为普遍的打印机机种及最近上市的驱动程序。
打印机 新的驱动程序
====== ============
HP DeskJet Family Version 3 或以后的版本
HP LaserJet III Versions 2 及 2.1 (31.3.89 以后的产品)
HP LaserJet IV Version 31.V1.25 或以后的版本
IBM 4019/4029 Version 3.08 或以后的版本
Postscript Versions 3.5 及 3.53
若想了解您的打印机驱动程序的版本，请运行下列各项：
1. 打开 Windows 控制面板，并选取「打印机」。
Windows 会显示安装在您系统上的所有打印机清单。
2. 以亮条显示清单中的某一种打印机。
4. 选取「设置」。
即出现打印机设置对话框。
5. 选取「关于」可查看有关您的打印机的信息，其中包括驱动程序的版本。
打印机分辨率
1-2-3 Release 4 可使每一英寸 300 点 (300 dpi) 的打印操作获得最佳效果。
提示：如果您要打印 600 dpi，而且您的打印工作中包含许多不同的字体，并且在
打印进行中发生问题，这时请打开 Windows 控制面板中的「打印机」，并在[打印机]
[设置][选项]对话框中，选取「以图形方式打印 True Type 字体」复选
框。
**5. DATALENS 与 ODBC 驱动程序**
如果 1-2-3 在您查询磁盘上的工作表时，显示「字段名称无效」之类的信息，请在
使用其它任一查询命令之前，先选取「设置数据库表」。
ODBC 驱动程序
1-2-3 Release 4 可以设置成使用符合 Microsoft Open Database Connectivity
(ODBC) 规格的驱动程序。附在 1-2-3 Release 4 中的 dBASE DataLens 驱
动程序即使用 ODBC 的主程序。
附注：大部份的 ODBC 驱动程序尚未在 1-2-3 上做过检验。Lotus 不提供这类驱
动程序的技术支持。
如果您在 1-2-3 上使用 DataLens dBASE 驱动程序或其它任何 ODBC 驱动程序，
请在启动 Windows 之前先启动 SHARE.EXE。若要在每次运行 Windows 之前先运行
SHARE.EXE，请在 AUTOEXEC.BAT 文件中加上下面这行正文：
C:\DOS\SHARE
请参考 DOS 文档，以得知有关 SHARE.EXE 的信息。
您可以将 1-2-3 设置成使用所有的 ODBC 驱动程序，或者使用某一个特定的驱动
程序。若要提供存取所有 ODBC 来源的权利，请在您的 LOTUS.BCF 文件中加上下
面这行正文：
DN="ODBC" DL="DLODBC" DD="All ODBC sources";
如果只要提供某个特定的驱动程序，只需在 LOTUS.BCF 中对 ODBC 记录加入一个 DC
参数，便能加入某个特定的 ODBC 驱动程序。如果某个项目含有如上述的字符串
DL="DLODBC"，请加入形如 DC="driver=xxx" 的字符串，此后 1-2-3 只提供以 "xxx"
作为驱动程序的来源。例如：
DN="SQL Database via ODBC" DL="DLODBC" DC="driver=sql.dll" AC=UI，PW;
您也可以在 LOTUS.BCF 中加上下面这行正文，将 1-2-3 设置成对数据来源提示
输入用户识别码及口令：
DB="source name" DN="ODBC" AC=UI，PW;
若需要有关编辑您的 LOTUS.BCF 文件的其它信息，请参考 DataLens Drivers for
1-2-3。
当 1-2-3 用户选取「dBASE 的 DataLens 驱动程序」文件时，所有可用的数据库
清单包括下列项目：
* 当前的目录
* ODBC.INI 中包含 "driver=qodbf.dll" 的所有数据来源
除此之外，您也可以在 ODBC.INI 中加入新的数据库名称，并输入新的路径。
使用 DLODBC 时，您必须对 dBASE 的数据来源名称设置路径。
当您通过宏把更新后的数据传送到 ODBC-dBASE IV 表格时，您必须在 {SEND-SQL} 命
令之后加上 {COMMIT} 命令。
IBM 数据库管理程序 (IBM Database Manager)
若要用数据库管理程序 (Database Manager) 来存取 OS/2 2.0 服务器，您需要使
用 Local Area Network Support Program Version 1.3。
PCDRDLL.DLL 由 IBM 公司提供，若您没有此文件，则无法使用 IBM DB Catalog
Tool。
环境变量
1-2-3 Release 4 与其它某些 1-2-3 版本不同，它并不使用 "LOTUSBCF" 环境变量，
而且仅读取位于 \LOTUSAPPS\DATALENS 中的 LOTUS.BCF 文件上的记录。
**6. 版本管理器**
如果您要在 Lotus Notes for Windows Release 3.0 中使用「版本管理器」，请
在启动 Windows 之前先启动 SHARE.EXE。若要在每次运行 Windows 前先启动
SHARE.EXE，请在 AUTOEXEC.BAT 文件中加上下面这行正文：
C:\DOS\SHARE
请参考您的 DOS 文档，以得知有关 SHARE.EXE 的信息。
当您使用共享文件时，Lotus Notes 可能会在您的 1-2-3 操作期间，于某个特殊的未
命名错误窗口中显示某个信息。若试图关闭此窗口，将使其余的 1-2-3 作业结束与
Notes 服务器的通信。
如果 1-2-3 在您试图打开共享文件 (.NS4) 时显示信息「起动 Lotus Notes 时发生
错误」，请检查下列项目：
* 如果在您的 WIN.INI 文件中的 LotusMail 区段设置了 Notes，请确认 Notes
程序的路径是否正确。例如：
[LotusMail]
Application=Notes
Program=x:\notes\notes.exe
* 如果在您的 LOTUS.INI 文件中的 Lotus Applications 区段设置了 Notes，请确
认 Notes 程序的路径是否正确。例如：
[Lotus Applications]
Notes=x:\notes\notes.exe Lotus Notes
* 请确认您在启动 Windows 之前，是否已先启动 SHARE.EXE。
如果您在共享文件 (.NS4) 中从某个选区删除所有的版本，便无法在该选区中再
创建任何版本。请不要从选区中删除所有的版本，除非您确定不要再共享它。
**7. 求解器**
求解器通过 1-2-3 中公式单元之间的关系来求得它的答案。由于 DDE 链接是
从 1-2-3 之外的来源获取它们的数据，因此不要在可调单元或约束单元中使用
@DDELINK 公式。
**8. 命令行参数**
如果要指定 1-2-3 Release 4 的命令行参数：
1. 以亮条显示 1-2-3 Release 4 图标。
2. 从 Windows 程序管理器中选取[文件][特性]。
3. 在「命令行」正文框中，对 123W.EXE 加上一个命令行参数 (例如：
C:\C123R4W\PROGRAMS\123W.EXE -s)
您可以指定下列任一个命令行参数：
文件名
让您指定一个文件，以后每次启动 1-2-3 时，便会装入该文件。
-s
可让 1-2-3 Release 4 以软件浮点驱动程序来替换数学浮点运算器 (math
coprocessor)。如果您的计算机的数学浮点运算器有问题，或虽然您的计算机告知
1-2-3 有数学浮点运算器，但实际上并没有这样东西时，请使用此参数。在这种情况
下，您所有的公式所求得的值只会是 0ⅱERR 或 *** (星号)。
-i [filename.ini]
可让您指定 123R4.INI 以外的文件作为起始文件。例如：
C:\C123R4W\PROGRAMS\123W.EXE -iC:\C123R4W\MYINI.INI 中
指定起始文件为 C:\C123R4W\MYINI.INI。
附注：如果您在 1-2-3 Release 4 中使用 Lotus Notes Document Inset Protocol
(DIP)，便需在您的 Windows 目录中存入 123R4.INI 文件。
**9. 字体用法**
字体的对映
1-2-3 Release 4 可将 Adobe Type Manager (ATM) 字体的要求对映到 TrueType
字体，或将 TrueType 字体的要求对映到 ATM 字体。
字体的对映是由您的 123R4.INI 文件中 [TTMAPPING] 区段的 TT_MAP 语句来加以
控制的。当您第一次启动 1-2-3 时，1-2-3 会自动设置 TT_MAP。
附注：当您打开用 1-2-3 for DOS 所创建的文件时，便会使用 123R4.INI 文件中
[FONTMAPPING] 区段上的设置值，将 Wysiwyg 字体对映到 Windows 字体。
字体操作的提示
1. 当您在 1-2-3 中旋转正文块时，请使用 ATM 字体，例如： Arial MT。所有的
TrueType 字体都可以旋转。若您选用的是打印机字体 (如 CG Times，Universe
都是 HP LaserJet 的打印机字体) 或 Bitmap 字体 (如: Courier， Helv 及
TmsRmn)，正文就不能被旋转。
2. 1-2-3 支持所有字体，除了 Bitmap 字体之外。但是打印机字体所显示出来的结
果可能不正确。不过，1-2-3 虽然不支持 Bitmap 字体，只要 Windows 提供该
字体，屏幕上正文仍可旋转。
3. 如果您已启动 ATM 字体， ATM 字体只有在字体点数大于或等于您在 ATM.INI 中
SynonymPSBegin= 的设置时才有效。而且所有有效字体需列在 ATM.INI 的
[Synonyms] 区段中。
4. 当双字节字符所采用的字体不属于 GB 字符集时，Windows 会换用宋体
的 DBCS Bitmap 字型。
5. 由于 Arial 及 Times New Roman 是 Hewlett-Packard LaserJet IV 打印机的内
部字体，因此使用 TrueType 字体可以加快这类打印机的打印速度。
安装及删除 ATM
如果您是在网络节点上安装 1-2-3，则只要网络管理员将 ATM 转送到服务器上，您
便可从服务器上安装 ATM。若要安装 ATM，请运行下列各项：
1. 打开 Windows 程序管理器。
2. 选取[文件][运行]。
3. 在「命令行」正文框中输入 x:\path\ATM\install。
「x:\path」是您的服务器上 1-2-3 目录的驱动器代号和路径。例如：输入
t:\C123R4W\atm\install 就在驱动器 T 的 1-2-3 目录 \C123R4W 上
安装 ATM。
4. 选取「确定」钮。
如果您是从网络服务器上运行 Windows，则只有当您进行安装时对 WINDOWS\SYSTEM
目录拥有读写权的情况下，才能够安装 ATM。请与您的网络管理员联系，以获取读写此
目录的权限。
在您安装好 ATM 之后，由于 ATM 会用它的可调整字体替换某些特定的 Windows 点
阵字体，因此其它的 Windows 应用软件在屏幕上的外观可能略有改变。ATM 进行
替换时，则是由 ATM.INI 中的 SynonymPSBegin= 语句来控制字体大小。
SynonymPSBegin= 最初设为 9；它表示 ATM 用它的字体替换 Windows 大于 9 点
的字体。如果您将这条语句改成 SynonymPSBegin=13，则 ATM 会用它的字体替换
Windows 大于 13 点的字体。至于其它使用 10 到 12 点字体的 Windows 应用软
件，则继续保持您安装 ATM 之前的原貌。
我们建议您将 1-2-3 Release 4 中的这条语句变成 SynonymPSBegin=11。
如果您在 ATM soft 字体上遇到因难，您可以从硬盘上删除 ATM，然后重新安
装一次。
当您要从硬盘上删除 ATM 时，请运行下列各项：
1. 如果您曾经安装额外的字体，请将那些字体拷贝到一个临时目录中。
2. 从您的 WIN.INI 文件中删除所有的 Windows soft 字体。Soft 字体由已安
装的打印机显示出来。在以下的范例中，加上 * (星号) 表示要删除该行。
[PostScript，LPT2]
device=14
color=2
feed1=1
*softfonts=11
*softfont1=c:\psfonts\pfm\_a______.pfm，c:\psfonts\_a______.pfb
*softfont2=c:\psfonts\pfm\bdbc____.pfm，c:\psfonts\bdbc____.pfb
若要从您的系统中删除 ATM，请运行下列各项：
1. 结束 Microsoft Windows。
2. 在您的 Windows 目录下，于 SYSTEM.INI 文件中改变以下数行：
* 将 system.drv=atmsys.drv 变成 system.drv=system.drv
* 删除 atm.system.drv=system.drv 这一行
附注：在某些系统上 (例如：Hewlett-Packard Vectra)，这几行的写法可能
略有出入；无论如何，最后只能留下 system.drv=system.drv 这一行。
3. 删除下列文件：
* 从您的 Windows 目录下的 \SYSTEM 子目录中，删除 ATM16.DLL 及 ATM32.DLL。
* 从您的 Windows 目录中删除 ATM.INI 及 ATMCNTRL.EXE。
* 从您安装字体的目录中删除任何 .PFMⅱ.PFBⅱ.SFP 及 .SFL 文件。
4. 若要重新安装 ATM，请启动 Windows，并在驱动器 A 中插入 ATM 磁盘。请
打开 Windows 程序管理器，再选取[文件][运行]。然后在「命令行」正文框
块中输入 a:install，然后选取「确定」钮。
**10. CUI 命令 **
1-2-3 Release 4 支持类似 1-2-3 布尔运算 1.0 的传统命令菜单。
**12. 新的@函数 **
1-2-3 Release 4 提供 200 个以上的@函数。
以下是新加入的@函数：
@ATAN2ⅱ@FULLPⅱ@FV2ⅱ@HALFPⅱ@NUMBERSTRINGⅱ
@PMTIⅱ@PV2ⅱ@SPI。
**12. 日期格式 **
您可以输入日期作为标签或数值。
若要输入日期作为标签，首先请输入一个标签前缀字符 (如果该日期
是以数字开始)，然后再输入该日期。
若要输入日期作为数值，例如：您可以输入 93/07/20ⅱ93/07ⅱ07/20ⅱ
@DATE(93，7，20) 或输入日期数字。
如果日期数字 (如 34068) 出现在单元中，您可以选取[风格][数
值格式]，让该数字显示为日期的格式。
您可以使用的日期格式包括：YY/MM/DDⅱYY/MMⅱMM/DDⅱ93.05.23 及 05.23。
最后两种格式将因[用户设置]中的[国际][日期]设置值而有所不同。
**13. LOTUS 应用软件的整合 **
如果您已经安装其它的 Lotus 应用软件 (如 Ami ProⅱImprov...等等)，请在
LOTUS.INI 文件中做以下改变。当您在 WorkingTogether 便捷图标集中单击
"Ami Pro" 或 "Improv" 图标，即可从 1-2-3 Release 4 内部启动 Ami Pro
或 Improv。
[Lotus Applications]
AmiPro=c:\camipro\amipro.exe Ami Pro
Improv=c:\improv\improv.exe Improv
( 请在 "=" 符号之后，为其它 Lotus 应用软件指定正确的路径 )
**14. 「按范例填充」功能的范例**
1-2-3 所提供的范例有: 星期ⅱ月份ⅱ季ⅱ天干ⅱ地支ⅱ及九大行星的英文名。
1-2-3 Release 4 中文版 讀我檔案 (README.TXT)
**目錄**
1. 安裝
給版本更新者的資訊
網路分裝
以 CD-ROM 磁碟機安裝在電腦上
2. Windows 與可用的記憶體
3. 給版本更新者的圖表資訊
4. 列印作業的資訊
印表機設備與驅動程式
列印解析度
5. DataLens 與 ODBC 驅動程式
ODBC 驅動程式
IBM 資料庫管理員 (IBM Database Manager)
環境變數
LOTUS.BCF 檔案
6. 決策方案管理員
7. 規劃求解
8. 指令行參數
9. 修訂文件
使用手冊
試算表範例使用手冊
10. 字型用法
字型的對映
字型作業的提示
安裝及除去 ATM
11. CUI 指令
12. 新的@函數
13. 日期格式
14. Lotus 應用軟體的整合
15. 「依範例填入」功能的範例
**1. 安裝**
給版本更新者的資訊
1-2-3 Release 4 中文版需使用中文版 Windows 3.1 (以下的 Windows 均指中文版)
或以後的版本。
如果您的機器已安裝其他版本的 1-2-3 Release 4 (如英文版),請先將其
他版本的程式檔案清除乾淨，並將 Windows 目錄下的 123r4.ini 刪除，再安裝
新版的 1-2-3 Release 4.
如果您的 Windows 目錄與您的 1-2-3 目錄分別在不同的磁碟上，則您的 Windows
目錄所在的磁碟須至少有 1.5MB 到 2MB 的空間。
網路分裝
若希望在多台單機式電腦上以最便捷的方式安裝 1-2-3，請將 1-2-3 Release 4 所
有的檔案複製到網路伺服器上，讓已經取得使用授權的使用者能從伺服器將 1-2-3
安裝到他們的硬碟上。
請遵循下列指示，將 1-2-3 複製到伺服器上：
1. 依照第 1 片磁片上標籤的指示啟動安裝程式。
2. 在錄寫您的姓名及公司名稱的對話方塊中輸入您的姓名及公司名稱，然後選取
「確定」鈕。
附註：每一個從伺服器進行安裝的使用者，都必須在安裝時輸入他(她)的姓名，
但這時候輸入的公司名稱則會永久保留下來。
3. 選取「確定」鈕以確認所輸入的名稱。
4. 選取「結束安裝」可結束安裝程式。
5. 結束 Microsoft Windows。
6. 在 DOS 下輸入 a:crsby 並按 ENTER 鍵。
如果第 1 片磁片不在磁碟機 A:，請輸入正確的磁碟機代號。
CRSBY.BAT 會將壓縮過的 1-2-3 檔案複製到伺服器上，並提示您更換磁片，直到複
製好所有的檔案。
這時使用者可以依循下列指示，在他們的硬碟上安裝 1-2-3 Release 4。
1. 在 Windows 程式管理員中，選擇[檔案][執行]。
2. 在「指令行」文字方塊中輸入 [x]:\路徑\install。
「[x]:\路徑」是包含所有 1-2-3 檔案的伺服器目錄路徑和磁碟機代號。例如：
輸入 t:\C123R4W\install 可從磁碟機 T: 目錄名稱為 \C123R4W 中啟動安裝程
式。
3. 選取「確定」鈕。
安裝程式會顯示一系列的對話方塊，它們會提示使用者安裝的項目及如何安裝等
資訊。
以 CD-ROM 磁碟機安裝在電腦上
如果您是在附有 CD-ROM 磁碟機的電腦上安裝 1-2-3，請在啟動安裝程式之前，先確
認是否已經關好 CD-ROM 磁碟機。
**2. WINDOWS 與可用的記憶體**
附註：Windows 3.1 所需要的記憶體比 Windows 3.0 還要多，因此，在您一起使用
Windows 3.1 和 1-2-3 之前，如有必要，請先釋放額外的記憶體。
在您啟動 1-2-3 之前，請先察看您還有多少記憶體可用，其方法是：開啟程式管理
員，並選取[輔助說明][關於程式管理員]。
如果可用記憶體少於 1800K，便無法啟動 1-2-3 Release 4。這時請關閉已開啟的所
有應用軟體，並除去某些常駐記憶體的程式，以騰出更多可用的空間。然後再次檢查
可用記憶體的總數。
若可用記憶體僅稍微大於 1800K，則雖然可以啟動 1-2-3，但在工作時，可能會出現
記憶體已滿這類的訊息。
以下是有關如何增加可用記憶體容量的一些建議。
* 若要節省最多的記憶體空間，請除去 SMARTdrive。(若您不想拿掉 SMARTdrive，
請參考下一項，以減少 SMARTdrive 快速存取記憶體所占的空間。)
如果要除去 Windows 3.1 中的 SMARTdrive，請從 AUTOEXEC.BAT 中刪除
[x]:\WINDOWS\SMARTDRV.EXE 這段敘述。
您可以刪除這段敘述，或是在該敘述的前面輸入 REM。例如：
REM [x]:\WINDOWS\SMARTDRV.EXE
* 若不想除去 SMARTdrive，您可以將 SMARTdrive 的快速記憶體縮小為 256K，以
節省記憶體的空間。
在 Windows 3.1 中，將 AUTOEXEC.BAT 中 SMARTdrive 的敘述改成
[x]:\WINDOWS\SMARTDRV.EXE 1024 256。
* 僅適用於 386 的使用者：加大 Windows 的交換檔案 (swap file)，使它至少達
1MB。若要知道如何改變交換檔案的大小，請參考 Microsoft Windows 的相關文
件。
* 僅適用於 Windows 3.1 的使用者：Windows 3.1 中附有可調整的字形管理員，
因此您可以關閉 ATM 以節省大量的記憶體空間。如果要關閉 ATM，請按兩下
ATM 控制台圖示。在 ATM 之下，選取「關閉」。再選取「結束」；然後重新
啟動 Windows。
提示：如果 1-2-3 顯示「記憶體不足」或「Windows 資源不足，無法完成作業」等
訊息，而且您無法使用[檔案][儲存檔案]將檔案存起來，這時請用快捷鍵 Ctrl+S。
**3. 給版本更新者的圖表資訊**
若要使用您在舊版的 1-2-3 for Windows 所建立的圖表(但尚未將它們加到工作表中)，
請開啟包含那些圖表的 .WK3 檔案，並選取[編輯][移至]。在「項目的種類」下拉式選
項表中選取圖表，然後在列示方塊中選取圖表名稱。
1-2-3 會將該圖表加到目前在螢幕上顯示的工作表區域的中央。然後，您可以將圖
表移到工作表的任一處。
**4. 列印作業的資訊**
使用 1-2-3 傳統列印指令
1. 傳統指令功能表上的列印指令，只支援單位元組字元的列印作業。
2. 使果使用者想透過傳統指令的列印選項來列印工作表，則使用者必須選取列印
指令後，選取列印結束，以結束傳統指令。
印表機設備與驅動程式
印表機製造廠商通常會定期的更新印表機驅動程式。某些時候，廠商可以供應您比
Windows 3.1 所附的驅動程式還要新的版本。若想知道是否有更新的驅動程式
可供您的印表機使用，請隨時察看電子佈告欄，如 CompuServe ，或與您的印表機廠
商聯繫。
下表列出市面上較為普遍的印表機機種及最近上市的驅動程式。
印表機 新的驅動程式
====== ============
HP DeskJet Family Version 3 或以後的版本
HP LaserJet III Versions 2 及 2.1 (31.3.89 以後的產品)
HP LaserJet IV Version 31.V1.18 或以後的版本
IBM 4019/4029 Version 3.08 或以後的版本
Postscript Versions 3.5 及 3.53
若想了解您的印表機驅動程式的版本，請執行下列各項：
1. 開啟 Windows 控制台，並選取「印表機」。
Windows 會顯示安裝在您系統上的所有印表機清單。
2. 以反白顯示清單中的某一種印表機。
4. 選取「設定」。
即出現設定印表機對話方塊。
5. 選取「關於」可察看有關您的印表機的資訊，其中包括驅動程式的版本。
列印解析度
1-2-3 Release 4 可使每一英寸 300 點 (300 dpi) 的列印作業獲致最佳的效果。
提示：如果您要列印 600 dpi，而且您的列印工作中包含許多不同的字型，並且在
列印進行中發生問題，這時請開啟 Windows 控制台中的「印表機」，並在[印表機]
[設定][選項]對話方塊中，選取「以圖形方式列印 True Type 字形」核對方
塊。
**5. DATALENS 與 ODBC 驅動程式**
如果 1-2-3 在您查詢磁碟上的工作表時，顯示「欄位名稱無效」之類的訊息，請在
使用其它任一查詢指令之前，先選取「設定資料庫表格」。
ODBC 驅動程式
1-2-3 Release 4 可以設定成使用符合 Microsoft Open Database Connectivity
(ODBC) 規格的驅動程式。附在 1-2-3 Release 4 中的 dBASE DataLens 驅
動程式即使用 ODBC 的主程式。
附註：大部份的 ODBC 驅動程式尚未在 1-2-3 上做過檢驗。Lotus 不提供這類驅
動程式的技術支援。
如果您在 1-2-3 上使用 DataLens dBASE 驅動程式或其它任何 ODBC 驅動程式，
請在啟動 Windows 之前先啟動 SHARE.EXE。若要在每次執行 Windows 之前先執行
SHARE.EXE，請在 AUTOEXEC.BAT 檔案中加上下面這行文字：
C:\DOS\SHARE
請參考 DOS 文件，以得知有關 SHARE.EXE 的資訊。
您可以將 1-2-3 設定成使用所有的 ODBC 驅動程式，或者使用某一個特定的驅動
程式。若要提供存取所有 ODBC 來源的權利，請在您的 LOTUS.BCF 檔案中加上下
面這行文字：
DN="ODBC" DL="DLODBC" DD="All ODBC sources";
如果只要提供某個特定的驅動程式，只需在 LOTUS.BCF 中對 ODBC 記錄加入一個 DC
參數，便能加入某個特定的 ODBC 驅動程式。如果某個項目含有如上述的字串
DL="DLODBC"，請加入形式為 DC="driver=xxx" 的字串，此後 1-2-3 只提供以 "xxx"
作為驅動程式的來源。例如：
DN="SQL Database via ODBC" DL="DLODBC" DC="driver=sql.dll" AC=UI,PW;
您也可以在 LOTUS.BCF 中加上下面這行文字，將 1-2-3 設定成對資料來源提示
輸入使用者識別碼及密碼：
DB="source name" DN="ODBC" AC=UI,PW;
若需要有關編輯您的 LOTUS.BCF 檔案的其它資訊，請參考 DataLens Drivers for
1-2-3。
當 1-2-3 使用者選取「dBASE 的 DataLens 驅動程式」檔案時，所有可用的資料庫
清單包括下列項目：
* 目前的目錄
* ODBC.INI 中包含 "driver=qodbf.dll" 的所有資料來源
除此之外，您也可以在 ODBC.INI 中加入新的資料庫名稱，並輸入新的路徑。
使用 DLODBC 時，您必須對 dBASE 的資料來源名稱設定路徑。
當您使用巨集將更新資料傳送到 ODBC-dBASE IV 表格時，您必須在 {SEND-SQL} 指
令之後加上 {COMMIT} 指令。
IBM 資料庫管理員 (IBM Database Manager)
若要用資料庫管理員 (Database Manager) 來存取 OS/2 2.0 伺服器，您需要使
用 Local Area Network Support Program Version 1.3。
PCDRDLL.DLL 檔由 IBM 公司提供，若您沒有此檔案，則無法試用 IBM DB Catalog
Tool。
環境變數
1-2-3 Release 4 與其它某些 1-2-3 版本不同，它並不使用 "LOTUSBCF" 環境變數，
而且僅讀取位在 \LOTUSAPPS\DATALENS 中的 LOTUS.BCF 檔案上的記錄。
**6. 決策方案管理員**
如果您要在 Lotus Notes for Windows Release 3.0 中使用「決策方案管理員」，請
在啟動 Windows 之前先啟動 SHARE.EXE。若要在每次執行 Windows 前先啟動
SHARE.EXE，請在 AUTOEXEC.BAT 檔案中加上下面這行文字：
C:\DOS\SHARE
請參考您的 DOS 文件，以得知有關 SHARE.EXE 的資訊。
當您使用共用檔案時，Lotus Notes 可能會在您的 1-2-3 作業期間，於某個特殊的未
命名錯誤視窗中顯示某個訊息。若試圖關閉此視窗，將使其餘的 1-2-3 作業結束與
Notes 伺服器的通訊。
如果 1-2-3 在您試圖開啟共用檔案 (.NS4) 時顯示訊息「起始 Lotus Notes 時發生
錯誤」，請檢查下列項目：
* 如果在您的 WIN.INI 檔案中的 LotusMail 區段設定了 Notes，請確認 Notes
程式的路徑是否正確。例如：
[LotusMail]
Application=Notes
Program=x:\notes\notes.exe
* 如果在您的 LOTUS.INI 檔案中的 Lotus Applications 區段設定了 Notes，請確
認 Notes 程式的路徑是否正確。例如：
[Lotus Applications]
Notes=x:\notes\notes.exe Lotus Notes
* 請確認您在啟動 Windows 之前，是否已先啟動 SHARE.EXE。
如果您在共用檔案 (.NS4) 中從某個範圍刪除所有的決策方案，便無法在該範圍中再
建立任何決策方案。請不要從範圍中刪除所有的決策方案，除非您確定不要再共用它。
**7. 規劃求解**
規劃求解使用 1-2-3 中公式儲存格之間的關係，來求得它的解答。由於 DDE 連結是
從 1-2-3 之外的來源取得它們的資料，因此不要在變數儲存格或限制式儲存格中使用
@DDELINK 公式。
**8. 指令行參數**
如果要指定 1-2-3 Release 4 的指令行參數：
1. 以反白顯示 1-2-3 Release 4 圖示。
2. 從 Windows 程式管理員中選取[檔案][內容]。
3. 在「指令行」文字方塊中，對 123W.EXE 加上一個指令行參數 (例如：
C:\C123R4W\PROGRAMS\123W.EXE -s)
您可以指定下列任一個指令行參數：
檔案名稱
讓您指定一個檔案，以後每次啟動 1-2-3 時，便會載入該檔案。
-s
可讓 1-2-3 Release 4 以軟體浮點驅動程式來取代數學浮點運算器 (math
coprocessor)。如果您電腦的數學浮點運算器有問題，或如果您的電腦告訴
1-2-3 有數學浮點運算器，但實際上並沒有這樣東西時，請使用此參數。在這種情況
下，您所有的公式所求得的值只會是 0、ERR 或 *** (星號)。
-i [filename.ini]
可讓您指定 123R4.INI 以外的檔案作為起始檔案。例如：
C:\C123R4W\PROGRAMS\123W.EXE -iC:\C123R4W\MYINI.INI 中
指定起始檔案為 C:\C123R4W\MYINI.INI。
附註：如果您在 1-2-3 Release 4 中使用 Lotus Notes Document Inset Protocol
(DIP)，便須在您的 Windows 目錄中存有 123R4.INI 檔。
**9. 修訂文件**
使用手冊附錄C的「使用 dBASE III/III Plus 索引檔」
請將「範圍名稱」變數改成「表格名稱」。
試算表範例使用手冊
1-2-3 Release 4 所提供的試算表範例檔放在 sample 次目錄中，均為 wk4 檔，
您仍可以參考此手冊來練習相同主檔名的檔案。
**10. 字型用法**
字型的對映
1-2-3 Release 4 可將 Adobe Type Manager (ATM) 字型的要求對映到 TrueType
字型，或將 TrueType 字型的要求對映到 ATM 字型。
字型的對映是由您的 123R4.INI 檔案中 [TTMAPPING] 區段的 TT_MAP 敘述來加以
控制。當您第一次啟動 1-2-3 時，1-2-3 會根據您的架構自動設定 TT_MAP。
附註：當您開啟用 1-2-3 for DOS 所建立的檔案時，便會使用 123R4.INI 檔案中
[FONTMAPPING] 區段上的設定值，將 Wysiwyg 字型對映到 Windows 字型。
字型作業的提示
1. 當您在 1-2-3 中旋轉文字區塊時，請使用 ATM 字型，例如： Arial MT。所有的
TrueType 字型都可以旋轉。若您選用的是印表機字型 (如 CG Times，Universe
都是 HP LaserJet 的印表機字型) 或 Bitmap 字型 (如: Courier, Helv 及
TmsRmn)，文字就不能被旋轉。
2. 1-2-3 支援所有字型，除了 Bitmap 字型之外。但是印表機字型所顯示出來的結
果可能不正確。不過，1-2-3 雖然不支援 Bitmap 字型，只要 Windows 提供該
字型，螢幕上文字仍可旋轉。
3. 如果您已啟動 ATM 字型， ATM 字型只有在字型點數大於或等於您在 ATM.INI 中
SynonymPSBegin= 的設定時才有效。而且所有有效字型需列在 ATM.INI 的
[Synonyms] 區段中。
4. 當雙位元字組的字元使用不屬於 BIG-5 字元組的字型時，Windows 會套用細明體
的 DBCS Bitmap 字型。
5. 由於 Arial 及 Times New Roman 是 Hewlett-Packard LaserJet IV 印表機的內
部字型，因此使用 TrueType 字型可以加快這類印表機的列印速度。
安裝及除去 ATM
如果您是在網路節點上安裝 1-2-3，則只要網路管理者將 ATM 轉送到伺服器上，您
便可從伺服器上安裝 ATM。若要安裝 ATM，請執行下列各項：
1. 開啟 Windows 程式管理員。
2. 選取[檔案][執行]。
3. 在「指令行」文字方塊中輸入 x:\路徑\ATM\install。
「x:\路徑」是您的伺服器上 1-2-3 目錄的磁碟機代號和路徑。例如：輸入
t:\C123R4W\atm\install 是在磁碟機 T 的 1-2-3 目錄名稱 \C123R4W 上
安裝 ATM。
4. 選取「確定」鈕。
如果您是從網路伺服器上執行 Windows，則只有當您進行安裝時對 WINDOWS\SYSTEM
目錄擁有讀寫權的情形下，才能夠安裝 ATM。請洽詢您的網路管理者，以取得讀寫此
目錄的權限。
在您安裝好 ATM 之後，由於 ATM 會用它的可調整字型取代某些特定的 Windows 點
陣圖字型，因此其它的 Windows 應用軟體在螢幕上的外觀可能略有改變。ATM 進行
取代時，則是由 ATM.INI 中的 SynonymPSBegin= 敘述來控制字體大小。
SynonymPSBegin= 最初設為 9；它表示 ATM 用它的字型取代 Windows 大於 9 點
的字型。如果您將這段敘述改成 SynonymPSBegin=13，則 ATM 會用它的字型取代
Windows 大於 13 點的字型。至於其它使用 10 到 12 點字型的 Windows 應用軟
體，則繼續保持您安裝 ATM 之前的原貌。
我們建議您將 1-2-3 Release 4 中的這段敘述變成 SynonymPSBegin=11。
如果您在 ATM soft 字型上遭遇到因難，您可以從硬碟上刪除 ATM，然後重新再安
裝一次。
當您要從硬碟上刪除 ATM 時，請執行下列各項：
1. 如果您曾經安裝額外的字型，請將那些字型複製到暫存的目錄中。
2. 從您的 WIN.INI 檔案中刪除所有的 Windows soft 字型。Soft 字型是由已安
裝的印表機列示出來。在以下的範例中，加上 * (星號) 表示要刪除該行。
[PostScript,LPT2]
device=14
color=2
feed1=1
*softfonts=11
*softfont1=c:\psfonts\pfm\_a______.pfm,c:\psfonts\_a______.pfb
*softfont2=c:\psfonts\pfm\bdbc____.pfm,c:\psfonts\bdbc____.pfb
若要從您的系統中刪除 ATM，請執行下列各項：
1. 結束 Microsoft Windows。
2. 在您的 Windows 目錄下，於 SYSTEM.INI 檔案中改變以下數行：
* 將 system.drv=atmsys.drv 變成 system.drv=system.drv
* 刪除 atm.system.drv=system.drv 這一行
附註：在某些系統上 (例如：Hewlett-Packard Vectra)，這幾行的寫法可能
略有出入；無論如何，其結果只能留下 system.drv=system.drv 這一行。
3. 刪除下列檔案：
* 從您的 Windows 目錄下的 \SYSTEM 次目錄中，刪除 ATM16.DLL 及 ATM32.DLL。
* 從您的 Windows 目錄中刪除 ATM.INI 及 ATMCNTRL.EXE。
* 從您安裝字型的目錄中刪除任何 .PFM、.PFB、.SFP 及 .SFL 檔案。
4. 若要重新安裝 ATM，請啟動 Windows，並在磁碟機 A 中插入 ATM 磁片。請
開啟 Windows 程式管理員，再選取[檔案][執行]。然後在「命令行」文字方
塊中輸入 a:install，之後選取「確定」鈕。
**11. CUI 指令 **
1-2-3 Release 4 支援類似 1-2-3 易爾算 1.0 的傳統指令功能表。
**12. 新的@函數 **
1-2-3 Release 4 提供 200 個以上的@函數。
以下是新加入的@函數：
@ATAN2、@FULLP、@FV2、@HALFP、@NUMBERSTRING、
@PMTI、@PV2、@SPI。
**13. 日期格式 **
您可以輸入日期作為標記或數值。
若要輸入日期作為標記，首先請輸入一個標記前置字元 (如果該日期
是以數字開始)，然後再輸入該日期。
若要輸入日期作為值，例如：您可以輸入 93/07/20、93/07、07/20、
@DATE(93,7,20) 或輸入日期的數字。
如果日期的數字 (如 34068) 出現在儲存格中，您可以選取[樣式][數
字格式]，讓該數字顯示為日期的格式。
您可以使用的日期格式包括：YY/MM/DD、YY/MM、MM/DD、m82.07.20 及 07.20。
最後兩種格式將因[使用者設定]中的[國際][日期]設定值而有所不同。
**14. LOTUS 應用軟體的整合 **
如果您已經安裝其它的 Lotus 應用軟體 (如 Ami Pro、Improv...等等)，請在
LOTUS.INI 檔案中做以下改變。您可以從 WorkingTogether 智慧圖示集中按一
下 "Ami Pro" 或 "Improv" 圖示，即可在 1-2-3 Release 4 上啟動 Ami Pro
或 Improv。
[Lotus Applications]
AmiPro=c:\camipro\amipro.exe Ami Pro
Improv=c:\improv\improv.exe Improv
( 請在 "=" 符號之後，為其它的 Lotus 應用軟體指定正確的路徑 )
**15. 「依範例填入」功能的範例**
1-2-3 所提供的範例有: 星期、月份、季、天干、地支、及英文的九大行星。
1-2-3 Release 4 中文版 讀我檔案 (README.TXT)
**目錄**
1. 安裝
給版本更新者的資訊
網路分裝
以 CD-ROM 磁碟機安裝在電腦上
2. Windows 與可用的記憶體
3. 給版本更新者的圖表資訊
4. 列印作業的資訊
印表機設備與驅動程式
列印解析度
5. DataLens 與 ODBC 驅動程式
ODBC 驅動程式
IBM 資料庫管理員 (IBM Database Manager)
環境變數
LOTUS.BCF 檔案
6. 決策方案管理員
7. 規劃求解
8. 指令行參數
9. 修訂文件
使用手冊
試算表範例使用手冊
10. 字型用法
字型的對映
字型作業的提示
安裝及除去 ATM
11. CUI 指令
12. 新的@函數
13. 日期格式
14. Lotus 應用軟體的整合
15. 「依範例填入」功能的範例
**1. 安裝**
給版本更新者的資訊
1-2-3 Release 4 中文版需使用中文版 Windows 3.1 (以下的 Windows 均指中文版)
或以後的版本。
如果您的機器已安裝其他版本的 1-2-3 Release 4 (如英文版),請先將其
他版本的程式檔案清除乾淨，並將 Windows 目錄下的 123r4.ini 刪除，再安裝
新版的 1-2-3 Release 4.
如果您的 Windows 目錄與您的 1-2-3 目錄分別在不同的磁碟上，則您的 Windows
目錄所在的磁碟須至少有 1.5MB 到 2MB 的空間。
網路分裝
若希望在多台單機式電腦上以最便捷的方式安裝 1-2-3，請將 1-2-3 Release 4 所
有的檔案複製到網路伺服器上，讓已經取得使用授權的使用者能從伺服器將 1-2-3
安裝到他們的硬碟上。
請遵循下列指示，將 1-2-3 複製到伺服器上：
1. 依照第 1 片磁片上標籤的指示啟動安裝程式。
2. 在錄寫您的姓名及公司名稱的對話方塊中輸入您的姓名及公司名稱，然後選取
「確定」鈕。
附註：每一個從伺服器進行安裝的使用者，都必須在安裝時輸入他(她)的姓名，
但這時候輸入的公司名稱則會永久保留下來。
3. 選取「確定」鈕以確認所輸入的名稱。
4. 選取「結束安裝」可結束安裝程式。
5. 結束 Microsoft Windows。
6. 在 DOS 下輸入 a:crsby 並按 ENTER 鍵。
如果第 1 片磁片不在磁碟機 A:，請輸入正確的磁碟機代號。
CRSBY.BAT 會將壓縮過的 1-2-3 檔案複製到伺服器上，並提示您更換磁片，直到複
製好所有的檔案。
這時使用者可以依循下列指示，在他們的硬碟上安裝 1-2-3 Release 4。
1. 在 Windows 程式管理員中，選擇[檔案][執行]。
2. 在「指令行」文字方塊中輸入 [x]:\路徑\install。
「[x]:\路徑」是包含所有 1-2-3 檔案的伺服器目錄路徑和磁碟機代號。例如：
輸入 t:\C123R4W\install 可從磁碟機 T: 目錄名稱為 \C123R4W 中啟動安裝程
式。
3. 選取「確定」鈕。
安裝程式會顯示一系列的對話方塊，它們會提示使用者安裝的項目及如何安裝等
資訊。
以 CD-ROM 磁碟機安裝在電腦上
如果您是在附有 CD-ROM 磁碟機的電腦上安裝 1-2-3，請在啟動安裝程式之前，先確
認是否已經關好 CD-ROM 磁碟機。
**2. WINDOWS 與可用的記憶體**
附註：Windows 3.1 所需要的記憶體比 Windows 3.0 還要多，因此，在您一起使用
Windows 3.1 和 1-2-3 之前，如有必要，請先釋放額外的記憶體。
在您啟動 1-2-3 之前，請先察看您還有多少記憶體可用，其方法是：開啟程式管理
員，並選取[輔助說明][關於程式管理員]。
如果可用記憶體少於 1800K，便無法啟動 1-2-3 Release 4。這時請關閉已開啟的所
有應用軟體，並除去某些常駐記憶體的程式，以騰出更多可用的空間。然後再次檢查
可用記憶體的總數。
若可用記憶體僅稍微大於 1800K，則雖然可以啟動 1-2-3，但在工作時，可能會出現
記憶體已滿這類的訊息。
以下是有關如何增加可用記憶體容量的一些建議。
* 若要節省最多的記憶體空間，請除去 SMARTdrive。(若您不想拿掉 SMARTdrive，
請參考下一項，以減少 SMARTdrive 快速存取記憶體所占的空間。)
如果要除去 Windows 3.1 中的 SMARTdrive，請從 AUTOEXEC.BAT 中刪除
[x]:\WINDOWS\SMARTDRV.EXE 這段敘述。
您可以刪除這段敘述，或是在該敘述的前面輸入 REM。例如：
REM [x]:\WINDOWS\SMARTDRV.EXE
* 若不想除去 SMARTdrive，您可以將 SMARTdrive 的快速記憶體縮小為 256K，以
節省記憶體的空間。
在 Windows 3.1 中，將 AUTOEXEC.BAT 中 SMARTdrive 的敘述改成
[x]:\WINDOWS\SMARTDRV.EXE 1024 256。
* 僅適用於 386 的使用者：加大 Windows 的交換檔案 (swap file)，使它至少達
1MB。若要知道如何改變交換檔案的大小，請參考 Microsoft Windows 的相關文
件。
* 僅適用於 Windows 3.1 的使用者：Windows 3.1 中附有可調整的字形管理員，
因此您可以關閉 ATM 以節省大量的記憶體空間。如果要關閉 ATM，請按兩下
ATM 控制台圖示。在 ATM 之下，選取「關閉」。再選取「結束」；然後重新
啟動 Windows。
提示：如果 1-2-3 顯示「記憶體不足」或「Windows 資源不足，無法完成作業」等
訊息，而且您無法使用[檔案][儲存檔案]將檔案存起來，這時請用快捷鍵 Ctrl+S。
**3. 給版本更新者的圖表資訊**
若要使用您在舊版的 1-2-3 for Windows 所建立的圖表(但尚未將它們加到工作表中)，
請開啟包含那些圖表的 .WK3 檔案，並選取[編輯][移至]。在「項目的種類」下拉式選
項表中選取圖表，然後在列示方塊中選取圖表名稱。
1-2-3 會將該圖表加到目前在螢幕上顯示的工作表區域的中央。然後，您可以將圖
表移到工作表的任一處。
**4. 列印作業的資訊**
使用 1-2-3 傳統列印指令
1. 傳統指令功能表上的列印指令，只支援單位元組字元的列印作業。
2. 使果使用者想透過傳統指令的列印選項來列印工作表，則使用者必須選取列印
指令後，選取列印結束，以結束傳統指令。
印表機設備與驅動程式
印表機製造廠商通常會定期的更新印表機驅動程式。某些時候，廠商可以供應您比
Windows 3.1 所附的驅動程式還要新的版本。若想知道是否有更新的驅動程式
可供您的印表機使用，請隨時察看電子佈告欄，如 CompuServe ，或與您的印表機廠
商聯繫。
下表列出市面上較為普遍的印表機機種及最近上市的驅動程式。
印表機 新的驅動程式
====== ============
HP DeskJet Family Version 3 或以後的版本
HP LaserJet III Versions 2 及 2.1 (31.3.89 以後的產品)
HP LaserJet IV Version 31.V1.18 或以後的版本
IBM 4019/4029 Version 3.08 或以後的版本
Postscript Versions 3.5 及 3.53
若想了解您的印表機驅動程式的版本，請執行下列各項：
1. 開啟 Windows 控制台，並選取「印表機」。
Windows 會顯示安裝在您系統上的所有印表機清單。
2. 以反白顯示清單中的某一種印表機。
4. 選取「設定」。
即出現設定印表機對話方塊。
5. 選取「關於」可察看有關您的印表機的資訊，其中包括驅動程式的版本。
列印解析度
1-2-3 Release 4 可使每一英寸 300 點 (300 dpi) 的列印作業獲致最佳的效果。
提示：如果您要列印 600 dpi，而且您的列印工作中包含許多不同的字型，並且在
列印進行中發生問題，這時請開啟 Windows 控制台中的「印表機」，並在[印表機]
[設定][選項]對話方塊中，選取「以圖形方式列印 True Type 字形」核對方
塊。
**5. DATALENS 與 ODBC 驅動程式**
如果 1-2-3 在您查詢磁碟上的工作表時，顯示「欄位名稱無效」之類的訊息，請在
使用其它任一查詢指令之前，先選取「設定資料庫表格」。
ODBC 驅動程式
1-2-3 Release 4 可以設定成使用符合 Microsoft Open Database Connectivity
(ODBC) 規格的驅動程式。附在 1-2-3 Release 4 中的 dBASE DataLens 驅
動程式即使用 ODBC 的主程式。
附註：大部份的 ODBC 驅動程式尚未在 1-2-3 上做過檢驗。Lotus 不提供這類驅
動程式的技術支援。
如果您在 1-2-3 上使用 DataLens dBASE 驅動程式或其它任何 ODBC 驅動程式，
請在啟動 Windows 之前先啟動 SHARE.EXE。若要在每次執行 Windows 之前先執行
SHARE.EXE，請在 AUTOEXEC.BAT 檔案中加上下面這行文字：
C:\DOS\SHARE
請參考 DOS 文件，以得知有關 SHARE.EXE 的資訊。
您可以將 1-2-3 設定成使用所有的 ODBC 驅動程式，或者使用某一個特定的驅動
程式。若要提供存取所有 ODBC 來源的權利，請在您的 LOTUS.BCF 檔案中加上下
面這行文字：
DN="ODBC" DL="DLODBC" DD="All ODBC sources";
如果只要提供某個特定的驅動程式，只需在 LOTUS.BCF 中對 ODBC 記錄加入一個 DC
參數，便能加入某個特定的 ODBC 驅動程式。如果某個項目含有如上述的字串
DL="DLODBC"，請加入形式為 DC="driver=xxx" 的字串，此後 1-2-3 只提供以 "xxx"
作為驅動程式的來源。例如：
DN="SQL Database via ODBC" DL="DLODBC" DC="driver=sql.dll" AC=UI,PW;
您也可以在 LOTUS.BCF 中加上下面這行文字，將 1-2-3 設定成對資料來源提示
輸入使用者識別碼及密碼：
DB="source name" DN="ODBC" AC=UI,PW;
若需要有關編輯您的 LOTUS.BCF 檔案的其它資訊，請參考 DataLens Drivers for
1-2-3。
當 1-2-3 使用者選取「dBASE 的 DataLens 驅動程式」檔案時，所有可用的資料庫
清單包括下列項目：
* 目前的目錄
* ODBC.INI 中包含 "driver=qodbf.dll" 的所有資料來源
除此之外，您也可以在 ODBC.INI 中加入新的資料庫名稱，並輸入新的路徑。
使用 DLODBC 時，您必須對 dBASE 的資料來源名稱設定路徑。
當您使用巨集將更新資料傳送到 ODBC-dBASE IV 表格時，您必須在 {SEND-SQL} 指
令之後加上 {COMMIT} 指令。
IBM 資料庫管理員 (IBM Database Manager)
若要用資料庫管理員 (Database Manager) 來存取 OS/2 2.0 伺服器，您需要使
用 Local Area Network Support Program Version 1.3。
PCDRDLL.DLL 檔由 IBM 公司提供，若您沒有此檔案，則無法試用 IBM DB Catalog
Tool。
環境變數
1-2-3 Release 4 與其它某些 1-2-3 版本不同，它並不使用 "LOTUSBCF" 環境變數，
而且僅讀取位在 \LOTUSAPPS\DATALENS 中的 LOTUS.BCF 檔案上的記錄。
**6. 決策方案管理員**
如果您要在 Lotus Notes for Windows Release 3.0 中使用「決策方案管理員」，請
在啟動 Windows 之前先啟動 SHARE.EXE。若要在每次執行 Windows 前先啟動
SHARE.EXE，請在 AUTOEXEC.BAT 檔案中加上下面這行文字：
C:\DOS\SHARE
請參考您的 DOS 文件，以得知有關 SHARE.EXE 的資訊。
當您使用共用檔案時，Lotus Notes 可能會在您的 1-2-3 作業期間，於某個特殊的未
命名錯誤視窗中顯示某個訊息。若試圖關閉此視窗，將使其餘的 1-2-3 作業結束與
Notes 伺服器的通訊。
如果 1-2-3 在您試圖開啟共用檔案 (.NS4) 時顯示訊息「起始 Lotus Notes 時發生
錯誤」，請檢查下列項目：
* 如果在您的 WIN.INI 檔案中的 LotusMail 區段設定了 Notes，請確認 Notes
程式的路徑是否正確。例如：
[LotusMail]
Application=Notes
Program=x:\notes\notes.exe
* 如果在您的 LOTUS.INI 檔案中的 Lotus Applications 區段設定了 Notes，請確
認 Notes 程式的路徑是否正確。例如：
[Lotus Applications]
Notes=x:\notes\notes.exe Lotus Notes
* 請確認您在啟動 Windows 之前，是否已先啟動 SHARE.EXE。
如果您在共用檔案 (.NS4) 中從某個範圍刪除所有的決策方案，便無法在該範圍中再
建立任何決策方案。請不要從範圍中刪除所有的決策方案，除非您確定不要再共用它。
**7. 規劃求解**
規劃求解使用 1-2-3 中公式儲存格之間的關係，來求得它的解答。由於 DDE 連結是
從 1-2-3 之外的來源取得它們的資料，因此不要在變數儲存格或限制式儲存格中使用
@DDELINK 公式。
**8. 指令行參數**
如果要指定 1-2-3 Release 4 的指令行參數：
1. 以反白顯示 1-2-3 Release 4 圖示。
2. 從 Windows 程式管理員中選取[檔案][內容]。
3. 在「指令行」文字方塊中，對 123W.EXE 加上一個指令行參數 (例如：
C:\C123R4W\PROGRAMS\123W.EXE -s)
您可以指定下列任一個指令行參數：
檔案名稱
讓您指定一個檔案，以後每次啟動 1-2-3 時，便會載入該檔案。
-s
可讓 1-2-3 Release 4 以軟體浮點驅動程式來取代數學浮點運算器 (math
coprocessor)。如果您電腦的數學浮點運算器有問題，或如果您的電腦告訴
1-2-3 有數學浮點運算器，但實際上並沒有這樣東西時，請使用此參數。在這種情況
下，您所有的公式所求得的值只會是 0、ERR 或 *** (星號)。
-i [filename.ini]
可讓您指定 123R4.INI 以外的檔案作為起始檔案。例如：
C:\C123R4W\PROGRAMS\123W.EXE -iC:\C123R4W\MYINI.INI 中
指定起始檔案為 C:\C123R4W\MYINI.INI。
附註：如果您在 1-2-3 Release 4 中使用 Lotus Notes Document Inset Protocol
(DIP)，便須在您的 Windows 目錄中存有 123R4.INI 檔。
**9. 修訂文件**
使用手冊附錄C的「使用 dBASE III/III Plus 索引檔」
請將「範圍名稱」變數改成「表格名稱」。
試算表範例使用手冊
1-2-3 Release 4 所提供的試算表範例檔放在 sample 次目錄中，均為 wk4 檔，
您仍可以參考此手冊來練習相同主檔名的檔案。
**10. 字型用法**
字型的對映
1-2-3 Release 4 可將 Adobe Type Manager (ATM) 字型的要求對映到 TrueType
字型，或將 TrueType 字型的要求對映到 ATM 字型。
字型的對映是由您的 123R4.INI 檔案中 [TTMAPPING] 區段的 TT_MAP 敘述來加以
控制。當您第一次啟動 1-2-3 時，1-2-3 會根據您的架構自動設定 TT_MAP。
附註：當您開啟用 1-2-3 for DOS 所建立的檔案時，便會使用 123R4.INI 檔案中
[FONTMAPPING] 區段上的設定值，將 Wysiwyg 字型對映到 Windows 字型。
字型作業的提示
1. 當您在 1-2-3 中旋轉文字區塊時，請使用 ATM 字型，例如： Arial MT。所有的
TrueType 字型都可以旋轉。若您選用的是印表機字型 (如 CG Times，Universe
都是 HP LaserJet 的印表機字型) 或 Bitmap 字型 (如: Courier, Helv 及
TmsRmn)，文字就不能被旋轉。
2. 1-2-3 支援所有字型，除了 Bitmap 字型之外。但是印表機字型所顯示出來的結
果可能不正確。不過，1-2-3 雖然不支援 Bitmap 字型，只要 Windows 提供該
字型，螢幕上文字仍可旋轉。
3. 如果您已啟動 ATM 字型， ATM 字型只有在字型點數大於或等於您在 ATM.INI 中
SynonymPSBegin= 的設定時才有效。而且所有有效字型需列在 ATM.INI 的
[Synonyms] 區段中。
4. 當雙位元字組的字元使用不屬於 BIG-5 字元組的字型時，Windows 會套用細明體
的 DBCS Bitmap 字型。
5. 由於 Arial 及 Times New Roman 是 Hewlett-Packard LaserJet IV 印表機的內
部字型，因此使用 TrueType 字型可以加快這類印表機的列印速度。
安裝及除去 ATM
如果您是在網路節點上安裝 1-2-3，則只要網路管理者將 ATM 轉送到伺服器上，您
便可從伺服器上安裝 ATM。若要安裝 ATM，請執行下列各項：
1. 開啟 Windows 程式管理員。
2. 選取[檔案][執行]。
3. 在「指令行」文字方塊中輸入 x:\路徑\ATM\install。
「x:\路徑」是您的伺服器上 1-2-3 目錄的磁碟機代號和路徑。例如：輸入
t:\C123R4W\atm\install 是在磁碟機 T 的 1-2-3 目錄名稱 \C123R4W 上
安裝 ATM。
4. 選取「確定」鈕。
如果您是從網路伺服器上執行 Windows，則只有當您進行安裝時對 WINDOWS\SYSTEM
目錄擁有讀寫權的情形下，才能夠安裝 ATM。請洽詢您的網路管理者，以取得讀寫此
目錄的權限。
在您安裝好 ATM 之後，由於 ATM 會用它的可調整字型取代某些特定的 Windows 點
陣圖字型，因此其它的 Windows 應用軟體在螢幕上的外觀可能略有改變。ATM 進行
取代時，則是由 ATM.INI 中的 SynonymPSBegin= 敘述來控制字體大小。
SynonymPSBegin= 最初設為 9；它表示 ATM 用它的字型取代 Windows 大於 9 點
的字型。如果您將這段敘述改成 SynonymPSBegin=13，則 ATM 會用它的字型取代
Windows 大於 13 點的字型。至於其它使用 10 到 12 點字型的 Windows 應用軟
體，則繼續保持您安裝 ATM 之前的原貌。
我們建議您將 1-2-3 Release 4 中的這段敘述變成 SynonymPSBegin=11。
如果您在 ATM soft 字型上遭遇到因難，您可以從硬碟上刪除 ATM，然後重新再安
裝一次。
當您要從硬碟上刪除 ATM 時，請執行下列各項：
1. 如果您曾經安裝額外的字型，請將那些字型複製到暫存的目錄中。
2. 從您的 WIN.INI 檔案中刪除所有的 Windows soft 字型。Soft 字型是由已安
裝的印表機列示出來。在以下的範例中，加上 * (星號) 表示要刪除該行。
[PostScript,LPT2]
device=14
color=2
feed1=1
*softfonts=11
*softfont1=c:\psfonts\pfm\_a______.pfm,c:\psfonts\_a______.pfb
*softfont2=c:\psfonts\pfm\bdbc____.pfm,c:\psfonts\bdbc____.pfb
若要從您的系統中刪除 ATM，請執行下列各項：
1. 結束 Microsoft Windows。
2. 在您的 Windows 目錄下，於 SYSTEM.INI 檔案中改變以下數行：
* 將 system.drv=atmsys.drv 變成 system.drv=system.drv
* 刪除 atm.system.drv=system.drv 這一行
附註：在某些系統上 (例如：Hewlett-Packard Vectra)，這幾行的寫法可能
略有出入；無論如何，其結果只能留下 system.drv=system.drv 這一行。
3. 刪除下列檔案：
* 從您的 Windows 目錄下的 \SYSTEM 次目錄中，刪除 ATM16.DLL 及 ATM32.DLL。
* 從您的 Windows 目錄中刪除 ATM.INI 及 ATMCNTRL.EXE。
* 從您安裝字型的目錄中刪除任何 .PFM、.PFB、.SFP 及 .SFL 檔案。
4. 若要重新安裝 ATM，請啟動 Windows，並在磁碟機 A 中插入 ATM 磁片。請
開啟 Windows 程式管理員，再選取[檔案][執行]。然後在「命令行」文字方
塊中輸入 a:install，之後選取「確定」鈕。
**11. CUI 指令 **
1-2-3 Release 4 支援類似 1-2-3 易爾算 1.0 的傳統指令功能表。
**12. 新的@函數 **
1-2-3 Release 4 提供 200 個以上的@函數。
以下是新加入的@函數：
@ATAN2、@FULLP、@FV2、@HALFP、@NUMBERSTRING、
@PMTI、@PV2、@SPI。
**13. 日期格式 **
您可以輸入日期作為標記或數值。
若要輸入日期作為標記，首先請輸入一個標記前置字元 (如果該日期
是以數字開始)，然後再輸入該日期。
若要輸入日期作為值，例如：您可以輸入 93/07/20、93/07、07/20、
@DATE(93,7,20) 或輸入日期的數字。
如果日期的數字 (如 34068) 出現在儲存格中，您可以選取[樣式][數
字格式]，讓該數字顯示為日期的格式。
您可以使用的日期格式包括：YY/MM/DD、YY/MM、MM/DD、m82.07.20 及 07.20。
最後兩種格式將因[使用者設定]中的[國際][日期]設定值而有所不同。
**14. LOTUS 應用軟體的整合 **
如果您已經安裝其它的 Lotus 應用軟體 (如 Ami Pro、Improv...等等)，請在
LOTUS.INI 檔案中做以下改變。您可以從 WorkingTogether 智慧圖示集中按一
下 "Ami Pro" 或 "Improv" 圖示，即可在 1-2-3 Release 4 上啟動 Ami Pro
或 Improv。
[Lotus Applications]
AmiPro=c:\camipro\amipro.exe Ami Pro
Improv=c:\improv\improv.exe Improv
( 請在 "=" 符號之後，為其它的 Lotus 應用軟體指定正確的路徑 )
**15. 「依範例填入」功能的範例**
1-2-3 所提供的範例有: 星期、月份、季、天干、地支、及英文的九大行星。
Welcome to Quattro Pro version 4
---------------------------------
This file contains important information--please read all of it.
All information here supersedes information in the Quattro Pro
manuals.
Table of Contents
-----------------
1. Installation
2. How to contact Technical Support
3. Upgrading from Quattro Pro 3
4. Bitstream fonts
5. WYSIWYG mode
6. Problems using a mouse
7. Running under Windows
8. Sound files
9. Slide transitions
10. Using expanded memory
11. Printing
12. Links in a 1-2-3 version 2.2 file
13. Importing a .WK1 file
14. Allways formatting
15. Cell references in a 1-2-3 version 3x file
16. Importing LICS and LMBCS
17. Sample .QLL file
18. Selecting blocks in macros
19. Documentation corrections
20. Solve For improvements
21. Optimizer tip
22. Dual values in Optimizer
23. Who should use Overstrike Print
24. Printing from Audit
25. Pre-formatting cells
26. Format code for a number in scientific notation
27. Network users
28. How to customize an overriding graph type
29. The Borland Print Spooler
30. Exporting to a Harvard Graphics file
31. Installing different character sets
32. Enhanced fonts
33. Clearing a custom style
1. Installation
---------------
To install Quattro Pro on your hard disk:
o Place Disk 1 in drive A.
o Type A:INSTALL and press ENTER.
o Follow the directions that appear onscreen.
If you have trouble reading the installation screens, use the
optional command line parameter /B to run INSTALL in a black and
white display mode:
o Type A:INSTALL /B and press ENTER
It may be necessary to use /B if you're using an LCD screen or a
system that has a color graphics adapter with a monochrome or
composite monitor.
After you install Quattro Pro, to start the program:
o Type Q and press ENTER.
2. How to contact Technical Support
-----------------------------------
If you need help with Quattro Pro, please read this file and the
manuals.
If you still have a question and need assistance, help is available
from the following sources:
1. Type GO BORAPP on the CompuServe bulletin board system for
access to the BORLAND forums with their libraries of technical
information and answers to common questions.
2. Check with your local software dealer or users' group.
3. Call the BORLAND Technical Support Department at
(408) 438-5300. Please have the following information ready
before calling:
o Product name and serial number on your original distribution
disk. Please have your serial number ready, or we will be
unable to process your call.
o Computer brand and model, and the brands and model numbers of
any additional hardware.
o Operating system and version number (you can determine the
version number by typing VER at the DOS prompt).
o Contents of your AUTOEXEC.BAT file.
o Contents of your CONFIG.SYS file.
4. Write to:
BORLAND INTERNATIONAL, INC.
QUATTRO PRO Technical Support
1800 Green Hills Road
P.O. Box 660001
Scotts Valley, CA 95067-0001
Please include the serial number of your software, or we will be
unable to process your letter.
5. TechFax is a 24-hour automated service that sends free
technical information to your fax machine. You can use
your touch-tone phone to request up to three documents
per call. Call (800) 822-4269.
6. For technical assistance outside the USA, check the product
packaging for the name, address, and phone number of the
distributor nearest you.
3. Upgrading from Quattro Pro 3
-------------------------------
To upgrade to Quattro Pro 4 from an earlier version of Quattro Pro,
follow the instructions in Chapter 2 of "Getting Started."
If you previously used BSINST to install additional Bitstream fonts,
you must reinstall them after installing Quattro Pro 4. If you
have the newer type of Bitstream fonts (.SPD files), you must
use SPDINST to install them.
If you previously installed BORLAND's ProShow ValuePack, you must re-
install it after installing Quattro Pro 4.
If you have any read-only files in the Quattro Pro directory,
make them read-write before you run INSTALL. If INSTALL encounters
any read-only files, installation can't be successfully completed.
If you have custom menu trees from earlier versions, save them
to a different directory before you run INSTALL. Copy them
back to the Quattro Pro directory afterwards, then run NEWMU to
translate them to version 4 menu files. This retains all
previous menu structures.
Upgrading network installations
-------------------------------
When upgrading a network installation of Quattro Pro 3
to version 4, the menu and resource files stored in each user's
private directory must be updated. These include any .MU, .MP,
or .RF files. Replace the .RF files with the updated versions
and create new .MP files using MPMAKE as described in the
"User's Guide."
4. Bitstream fonts
------------------
Quattro Pro uses Bitstream's typefaces and enabling software,
producing high-quality bitmap fonts. When you look closely at printed
output from Quattro Pro, you may occasionally notice extra white space
between characters. This is not a problem with your fonts. This extra
white space is commonly reduced using a composition function called
kerning. Quattro Pro 4 does not offer kerning.
You can access Bitstream fonts in two places:
/Style|FontTable|Edit Fonts|Typeface
/Style|Fonts|Typeface
5. WYSIWYG mode
---------------
There are new default spreadsheet colors in version 4. These colors
appear in text display mode only, not in WYSIWYG mode.
If you want to use the version 3 text-mode colors,
choose /Options|Colors|Palettes|Version 3 Color.
When using proportional fonts in WYSIWYG mode, the following commands
may produce inappropriate results: /Style|Column Width; /Style|Block
Size|Set Width, Reset Width, and Auto Width; /Tool|Reformat, and
Parse. For best results, change to a text display mode before using
these commands.
6. Problems using a mouse
-------------------------
Display problems using Quattro Pro and Microsoft mouse driver version
7.04 disappear after CONFIG.SYS is changed to "device=mouse.sys /Y".
If the mouse pointer doesn't appear on screen, you may need to update
your mouse driver. See "Extended text display mode" in Chapter 1 of
the "User's Guide."
7. Running under Windows
------------------------
If you want to run Quattro Pro in a small window (instead of full-
screen), either delete the file EGASPL.PCX, rename it, or move it to
another directory. Within Quattro Pro, set the display mode to
one of the text modes. This way, Quattro Pro won't start up in
graphics mode.
8. Sound files
--------------
You may not be able to play sound files when running under Microsoft
Windows in 386/Enhanced mode, or while running under Quarterdeck
DESQView. When using the above configurations, save your spreadsheets
before experimenting with sound files. See Chapter 13 of the "User's
Guide" for instructions on using sound files.
If you would like to order additional sound effects, see the coupon
from RealSound that is included in your Quattro Pro package.
9. Slide transitions
---------------------
Some video adapters don't support all slide transitions. If you find
that one transition doesn't work with your video adapter, try
another.
10. Using Expanded memory
-------------------------
Quattro Pro can use up to 8MB of expanded memory.
To test whether your EMS hardware and software are working correctly,
run EMSTEST.COM from DOS and follow instructions on the screen. If
errors are detected, contact your local hardware dealer.
11. Printing
------------
Font 1 (Normal font) controls both vertical and horizontal spacing.
The vertical height of a row is calculated as follows:
* A manual row-height setting overrules the default row height.
* If the height of the row has not been manually set, the
height is determined by either the largest font in that row
or the height of Font 1, whichever is largest.
If the selector is within an inserted graph block, /Print|Graph
Print|Go will always print the inserted graph. To print a
different graph, position the selector outside the inserted graph
and use /Print|Graph Print|Name to select a different graph.
In text mode, when printing to a Color PostScript printer,
black shading is controlled by the foreground color of /Options|
Color|Spreadsheet|Shading. For black shading, choose foreground
color of black and background color of any other color.
In WYSIWYG mode, when printing to a color or black & white
PostScript printer, black shading may appear gray. Use /Options|
Colors|Spreadsheet|WYSIWYG Colors|Shaded Cells to choose a color
other than gray.
12. Links in a 1-2-3 version 2.2 file
-------------------------------------
The maximum number of different spreadsheets that a Quattro Pro
spreadsheet can link to is 62. If a 2.2 file has links to more
than 62 files, Quattro Pro stops reading data after the 62nd
link. Data beyond that point will not be loaded.
To load a 2.2 spreadsheet with more than 62 links, convert
the links into their values first, or relocate the important
links into a link library and keep the links to 62 or less.
13. Importing a .WK1 file
-------------------------
If the .WK1 file you're importing has Allways or WYSIWYG/Impress
formatting, Quattro Pro asks if you want to import it. If you
answer yes, the file is imported with a .WQ1 file extension.
14. Allways formatting
----------------------
Allways formatting is translated when importing a 1-2-3 version 2.2
file.
15. Cell references in a 1-2-3 version 3x file
----------------------------------------------
If a .WK3 file has multiple spreadsheets, 3-D cell references
are translated with @@ . For example, the formula
+D:A1*100 in BUDGETS.WK3 converts to @@("[BUDGETS.W0D]A1")*100.
16. Importing LICS and LMBCS
----------------------------
Choose /Options|International|LICS/LMBCS Conversion|Yes before
importing a 1-2-3 file that contains international characters.
17. Sample .QLL file
--------------------
Quattro Pro includes a file called SAMPLE.QLL, which contains several
add-in @functions. You can load this file with the /Tools|Library|Load
command. Once this file is loaded, the following additional @functions
are available:
ADD-IN @FUNCTION DESCRIPTION
================================================================
sinh(x) (exp(x) - exp(-x))/2
cosh(x) (exp(x) + exp(-x))/2
tanh(x) sinh(x)/cosh(x)
hypot(x,y) sqrt(x^2+y^2)
add_months(x,y) date obtained by adding y months to date x.
It handles the end of the month and year
as follows:
30-Nov-91 + 2 mon = 30-Jan-92
30-Nov-91 + 3 mon = 29-Feb-92
last_day(x) returns the last day of month of the serial
date number x (the time of day is dropped
from the serial number)
Use the following syntax with these @functions:
@LIBRARY.function (for example, @SAMPLE.sinh(x)).
18. Selecting blocks in macros
------------------------------
In macros, use {/ Macro;RetainBlock} to retain selected blocks as
Quattro Pro 4 does; use {/ Macro;NoRetainBlock} to
do block selection as Quattro Pro 3x did. Unless you
use {/ Macro;RetainBlock}, blocks are retained like
Quattro Pro 3x in macro execution.
19. Documentation corrections
-----------------------------
Here are some minor corrections to the manuals:
o The /Print|Layout|Percent Scaling command is now called
% Scaling.
o Step 3 on page 674 of the "User's Guide" should include:
Type: SPDINST and press Enter
o The correct menu-equivalent macro command for the Max Bubble Size
option in the /Graph|Customize Series dialog box for bubble
graphs in the "@Functions and Macros" manual (pages 201 and 226)
is {/ Bubble;Size}.
o There is a menu-equivalent macro command {/ Protection;Formstatus}
to find the status of formula protection.
20. Solve For improvements
--------------------------
Due to an improved solver engine, the Solve For command
might give slightly different answers than in previous versions
of Quattro Pro.
Solve For is now more sensitive to the starting values
supplied in nonlinear problems and might display the message
"No feasible solution can be found." Solve For tries solving
the problem, but first warns you that the result may not be
optimal because of your starting variable value. Since the
results are probably close, choose Go again, or use a different
starting value and try again.
21. Optimizer tip
-----------------
For best performance, we suggest you use Optimizer in text
display mode.
22. Dual values in Optimizer
----------------------------
If dual values in the answer report are close to zero, choose
Go again a few times to refine them. The solution will stay the
same, but dual values will converge.
23. Who should use Overstrike Print
-----------------------------------
/Options|International|Overstrike Print remaps accented characters
according to the French ISO character set. It is intended primarily
for French Canadian users of the U.S. English version of Quattro Pro.
You might not get the expected overstrike characters on a U.S. 7-bit
printer.
24. Printing from Audit
-----------------------
When you choose /Tools|Audit|Destination|Print, the following print
settings are used from the Print Layout dialog box:
o Break Pages
o % Scaling
o Margins
o Orientation (but Banner prints as Landscape)
You might want to set Break Pages to No when printing Label
References, Blank References, ERR, or External Link audits.
25. Pre-formatting cells
------------------------
If you pre-format a group of cells with a custom date format,
then press Ctrl-D to enter a date, the custom format is overwritten
with the default date format. Try entering all the dates first, then
applying the custom date format.
26. Format code for a number in scientific notation
---------------------------------------------------
To create format code for scientific notation, follow this example:
Cell contents Format code Display as
------------- ----------- ----------
123456 N0.00e+0 123e+5
27. Network users
-----------------
Quattro Pro lets you log in to any NetWare file server you have
rights to. However, you can't log in to the same server as two
different users from one station. If you try, you see the message
"Already logged in to server as a different user."
If you're performing a network task within Quattro Pro, such as
running a print-queue monitor, and the network goes down, you
might need to reboot after exiting Quattro Pro.
28. How to customize an overriding graph type
---------------------------------------------
To customize the overriding graph type series, set
/Graph|Graph Type to the overriding type. In the dialog
box, select the overriding series, then set the options
you want. Finally, set Graph Type back to the overall type.
For example, if the graph is a bar graph and the second series is
set to Override Type|Line, choose /Graph|Graph Type|Line, then
choose Customize Series. Choose 2nd Series, then change the
options for a line. Choose Quit, then set Graph Type back to Bar.
29. The Borland Print Spooler
-----------------------------
If you use DOS 5.0 when installing BPS.COM, don't use LOADHI BPS.COM.
If you're printing to LPT3, LPT4, PRN, or EPT with background
printing enabled, the device will be remapped to LPT1.
If you load BPS.COM, then load a TSR program (such as a Novell
NetWare driver), you should unload the TSR program before
unloading BPS.COM to avoid problems.
30. Exporting to a Harvard Graphics file
----------------------------------------
Elements created with Quattro Pro's Annotator are lost if
you export to a Harvard Graphics file.
31. Installing different character sets
---------------------------------------
Contrary to the instructions in Appendix K of the User's
Guide, you must reinstall Quattro Pro 4 to install a different
character set.
32. Enhanced fonts
------------------
If you customize fonts in a Quattro Pro 4 file, the fonts will
change if you load the file in an earlier version of Quattro Pro.
33. Clearing a custom style
---------------------------
Clearing a custom style with /Style|Define Style|Erase returns
General numeric format to the block.
I. Additional Notes for GrandView LT Users
A. GrandView 2.0:
1. GrandView LT is a specially designed version of GrandView 2.0,
Symantec's full-featured outliner. For more information on
GrandView 2.0 and a special upgrade offer, see Appendix B of the
GrandView LT user guide.
B. Printing:
1. GrandView LT was designed as a companion product for Freelance
Graphics, and therefore includes only minimal printing
capabilities. When using GrandView LT, you are internally
connected to the program's TTY driver which provides standard,
unformatted courier output to dot matrix and laser printers
(Note: GV LT will not print to Postscript printers, however you
can export your outline to most word processors through the ASCII
file format and print your file from your word processor).
C. Freelance Graphics Customize Dialog
1. Text chart margins will not accept fractional percentages
(example: 2.5% is not an acceptable value for this field).
2. When saving a new Freelance Graphics text chart style, be sure NOT
to give it an existing chart style name, or it will overwrite the
existing style without warning.
D. Setting Colors in GrandView LT
1. GrandView LT, just like the full version of GrandView, lets you
customize the color of any of your screen elements through the
Customize Color dialog on the Color submenu (under the Setup Menu).
2. The following elements appear in the Customize Colors dialog, but
are not functional in GrandView LT. They relate to commands
included in GrandView 2.0. Because they are inactive in this
special version, choosing colors for these elements will have no
effect on your outlines:
a) Underline
b) Boldface
c) Italics
d) Superscript
e) Subscript
f) Format Tags
g) Text in Columns
h) Cursor in Columns
i) Marked labeling
j) Highlight in Calendar
E. Command Line Parameters
1. Both GrandView LT and Freelance Graphics have certain command line
parameters that can be used to affect how the programs operate. The
Freelance Graphics large and small options work when using
GrandView LT. Just type GVFL L or GVFL S.
2. GrandView LT lets you use the command line parameter, /RD to
specify the use of hard disk for swapping instead of using EMS
memory.
F. IBM PS/2 Mouse Driver
1. Version 3.0 or lower of the IBM PS/2 mouse drivers are not
supported when using GrandView LT.
G. Running GrandView LT in Windows 3.0
1. When running GrandView LT in a window, Windows 3.0 controls the
mouse events. If you click the mouse inside the windowed
application, you are selecting a region of that window that can be
copied to the clipboard.
2. The Alt-Enter combination key creates a sub-headline in GrandView
LT, but when running Windows 3.0 Alt-Enter will toggle from full
screen mode to window mode and vice versa. However, if you are
running Windows 3.0 in enhanced mode you can reserve this key for
GrandView LT to use. To reserve this combination key for GrandView
LT, set the Alt-Enter key switch ON in the Reserve Shortcut Keys in
the Advanced options of your PIF file.
3. If you are using the EMM386.sys driver or any memory manager to
simulate expanded memory and you want GrandView LT to make use of
expanded memory, make sure you set enough memory for this to take
effect. To calculate how much expanded memory GrandView LT will use
for swapping during a particular Freelance Graphics session, add
22K to the amount of free memory (i.e. conventional memory in your
system before loading GrandView LT or Freelance Graphics). For
example, if you have 490K of free memory, GrandView LT will require
512K for swapping.
H. Saving Text Charts when using a RAM Drive.
1. When creating your Freelance Graphics text charts from a GrandView
LT outline with a RAM drive, it is advised that you specify a
target drive other than the RAM Drive for saving your text charts.
I. EGA (Enhanced Graphics Adapter) users.
1. If you are using an EGA monitor with the Quadram Quad EGA graphics
adapter card, you may see color changes when switching from
GrandView LT to the Charts and Drawings page in Freelance
Graphics. To restore the correct colors, simply switch to any form
(i.e. the Print Options form, Help, Chart) and then return to the
Charts and Drawings page.
J. GRAPHICS.COM
1. GVLT will not work if the GRAPHICS.COM file is in your
autoexec.bat file. Please remove this file from your autoexec.bat
file before running GVLT.
K. IBM 3270
1. GrandView will not load on an IBM 3270 PC.
L. Documentation Error for Gathering Command.
1. In page 104 of the GrandView LT User's Guide, in the "Selecting,
Marking, and Gathering" section, there are references to the
gather command, but this command is not functional in GrandView
LT.
SmartPics for Windows -- README.TXT
This document contains important information which is not included in the
SmartPics for Windows printed documentation. It provides information on:
o Using the SmartPics SmartIcon in other Lotus products
o Setting access privileges to the SmartPics directories on different
networks
o Using SmartPics on a 3COM 3+Share network
o Using SmartPics as an OLE server
o Using SmartPics with other applications
** Using the SmartPics SmartIcon in Other Lotus Products **
You can have quick access to SmartPics from both Ami Pro and Lotus
1-2-3 for Windows using the SmartPics SmartIcon. Follow the procedures
below to install the SmartPics SmartIcon in each of these products:
- Installing the SmartPics SmartIcon in Ami Pro:
1. Copy SMARTPIC.BMP to your Ami Pro directory
(e.g., copy c:\smartpic\smartpic.bmp c:\amipro).
2. Copy SMARTPIC.SMM to your Ami Pro macros directory
(e.g., copy c:\smartpic\smartpic.smm c:\amipro\macros).
3. From the Ami Pro menu bar, choose Tools SmartIcons.
4. In the SmartIcons dialog box, click the Customize button.
5. In the Customize SmartIcons dialog box, scroll through the Tools
Custom Icons window until the SmartPics light bulb icon appears.
6. Drag the SmartPics icon into the Current Palette window.
7. Click Assign Macro.
8. In the Assign Macro dialog box, click Next Icon until the SmartPics
light bulb appears in the Selected Icon window, then select
SMARTPIC.SMM in the Macros list box.
9. Click Save, and then click OK in each dialog box until you return
to the main Ami Pro screen. The SmartPics SmartIcon is now
accessible.
For more information on using macros in Ami Pro, refer to your
Ami Pro documentation.
NOTE: If you did not place SmartPics for Windows in c:\smartpic,
you must also edit the SmartPics macro file to show the proper
path:
1. From the Ami Pro menu bar, choose Tools Macro Edit.
2. In the Edit Macro dialog box, choose SMARTPIC.SMM and click OK.
3. Change the statement:
"defdir="c:\smartpic"
to reflect the path where you installed SmartPics.
4. Double-click the control menu box in the top left corner of the
editing window to close the window. Ami Pro asks if you want to
save the changes to the macro. Click Yes.
- Installing the SmartPics SmartIcon in 1-2-3 for Windows:
1. Copy SMARTPIC.BMP and SMARTPIC.MAC to your 123\sheetico directory
(e.g., copy c:\smartpic\smartpic.bmp c:\123\sheetico).
2. From the 1-2-3 menu bar, choose Tools SmartIcons.
3. In the Tools SmartIcons dialog box, click the Customize button.
4. In the Tools SmartIcons Customize dialog box, scroll through the
Custom Icons window until the SmartPics light bulb icon appears.
5. Select the SmartPics icon and click Assign Macro.
6. In the Tools SmartIcons Customize Assign Macro dialog box, the
macro SMARTPIC.MAC will appear.
NOTE: If you installed SmartPics for Windows in a directory other
than c:\smartpic, edit the macro to show the alternative directory.
7. Click OK.
8. In the Tools SmartIcons Customize dialog box, click Add.
9. Click OK to close each dialog box until you return to the main
1-2-3 screen.
For more information on using macros in 1-2-3, refer to your 1-2-3
documentation.
NOTE: The SmartPics program directory contains three bitmaps for the
SmartPics SmartIcon, one for each monitor resolution.
o SMARTPIC.VGA (for VGA monitors)
o SMARTPIC.EGA (for EGA monitors)
o SMARTPIC.851 (for 8514 monitors)
The program directory also contains a bitmap called SMARTPIC.BMP. This
bitmap controls how the SmartPics SmartIcon displays. When you install
SmartPics, the install program tries to determine the type of monitor
you have and automatically copies the appropriate bitmap to
SMARTPIC.BMP.
If you change the type of monitor you have after you install SmartPics,
you should copy the appropriate SmartIcon bitmap to SMARTPIC.BMP. This
adjusts the display of the SmartPics SmartIcon for your monitor. For
example, if you had a VGA monitor when you installed SmartPics, but now
have an 8514 monitor, you should copy SMARTPIC.851 to SMARTPIC.BMP.
** Setting Access Privileges to the SmartPics Directories on Different
Networks **
FOR NETWORK ADMINISTRATORS: SmartPics for Windows is designed to run
on several different networks. Each network operating system uses
different commands and terminology, and may even offer different or
unique functionality.
Depending on the network you are using, you may have to assign users
access privileges to the SmartPics program and network directories
specific to the network.
For example, for Novell NetWare 386 version 3.11, you should assign
users R and F (Read and File-scan) privileges to the SmartPics program
directory and C, E, F, M, R, and W (Create, Erase, File-scan, Modify,
Read, and Write) privileges to the network subdirectory. For Banyan
Vines version 4.1, you should assign users R (Read) access to the
program directory and M (Modify) access to the network subdirectory.
See your network documentation for information on how to assign these
privileges.
In addition, some networks may require that node users have Search
access privileges to the entire path up to the SmartPics program
directory, including the root directory. For example, if SmartPics
resides on g:\apps\windows\smartpic, users need Search access
privileges to g:\, g:\apps, and g:\apps\windows.
If node users on these networks do not have Search access privileges
to these directories, the Lotus SmartPics browser will be unable
to find the correct path for the SmartPics symbols in the Directory
dialog box.
** Using SmartPics on a 3COM 3+Share Network **
FOR NETWORK ADMINISTRATORS: If you are using a 3COM 3+Share network,
when you create directories, users are assigned read-only access
privileges to these directories by default. For SmartPics, users need
read-write-delete-create access privileges to the SmartPics network
subdirectory.
To gain these additional rights to the SmartPics network subdirectory,
you must first make both the SmartPics program and network directories
shareable. This gives users read-write access to these directories.
See your 3COM 3+Share network documentation for more information.
Next, at the DOS prompt for the SmartPics program directory type:
attrib *.* +r
and press ENTER.
This gives users read-write access rights to the SmartPics program
directory.
As network administrator, you will need to remove the read-only
attributes from the SMARTPIC.NET file in the SmartPics program directory
so that you can update node licensing information.
To do this, at the DOS prompt for the SmartPics program directory type:
attrib smartpic.net -r
and press ENTER.
All users now have all access privileges to this file. When you finish
updating the node licensing information, make sure that you reset the
read-only attribute for this file.
In addition, if you are running the server edition of Windows on this
network, you may need to copy OLECLI.DLL, OLESVR.DLL, and SHELL.DLL
from your SmartPics server directory to the Windows server directory.
** Using SmartPics As an OLE Server **
SmartPics can run in either of two modes. When you access SmartPics
from the Windows Program Manager, SmartPics runs in normal mode and
runs as a freestanding Windows application. In this mode, SmartPics
does not copy images to the Windows Clipboard in the following formats:
o native
o owner link
o object link
When you access SmartPics from within applications that support Object
Linking and Embedding (OLE), SmartPics runs as a mini-OLE server. In
this mode, SmartPics does not support linking.
** Using SmartPics with Other Applications **
You can use SmartPics images in a wide variety of applications. When
you copy a SmartPics image to paste into another application, by
default, SmartPics copies the image in the Windows metafile format (WMF).
This format produces the best results.
For applications that do not support the metafile format, SmartPics
offers two additional formats: Device Independent Bitmap (DIB) and
Bitmap (BMP). You can choose a format in the SmartPics Options dialog
box.
When using SmartPics images in other applications, keep in mind the
following:
- If you try to paste a SmartPics image into an application and the
paste function is not available, that application may not support
the format that you used to copy the SmartPics image (metafile,
Device Independent Bitmap, or bitmap).
In the SmartPics Options dialog box, choose another format and copy
the image again. Then try to paste it into the other application.
- Sometimes, when you paste a SmartPics image into an application the
image may not appear optimally, for example, it may appear grainy
or speckled.
In the SmartPics Options dialog box, choose the Windows metafile
format to obtain optimal results.
- Sometimes, when you copy a SmartPics image using the Windows
metafile format (the default) and paste it into some applications, for
example, Word Perfect for Windows 5.1, images with white flesh tones
appear gray.
In the SmartPics Options dialog box, choose the Black line art
symbols option for the version of the symbols you want to use.
Adobe Type Manager (R) 1.15 Release Notes Windows Version April 15, 1991 Adobe Type Manager is a registered trademark of Adobe Systems Incorporated. Copyright 1983-1991 Adobe Systems Incorporated. All Rights Reserved. Patents Pending. ------------------------------------------------------------ APPLICATION-SPECIFIC NOTES >> Ami Professional 1.2 > Twelve-point Tms Rmn text may not enlarge in Ami's Enlarged view. This also occurs without ATM. Use Times instead of Tms Rmn. > If you use Ami's Pair Kerning option, wait until you are ready to print before activating it, rather than leaving it on all the time. >> Corel Draw 1.21 & 2.0 These versions of Corel Draw do not support ATM. >> PageMaker 3.01 & 4.0 > For the best results with ATM, set the Vector text above and Stretch text above limits in PageMaker's Preferences dialog box to 600 pixels (the maximum) for PageMaker 3.01 and 10,000 pixels for version 4.0. Earlier versions had a maximum of 127 pixels. > Underline and strikeout lines may appear broken when automatic kerning and/or justification is in effect, due to the way PageMaker handles automatic kerning. Turning paired kerning off will correct this problem. >> PowerPoint 2.0 For the best results at small point sizes on screen, remove the "Small Fonts" font using the Fonts option in the Windows Control Panel. >> Toolbook 1.0 Text may appear jagged when printed from Toolbook. This is because Toolbook does its own scaling of the screen image for printing, rather than using Windows' (or ATM's) font facilities. >> Ventura Publisher Windows Edition v3.0 > Backspacing at the end of a line sometimes causes the line to move down the screen one line per backspace. This also occurs without ATM. > In Reduced View, the fonts Helvetica and Times will not display correctly. >> Word for Windows 1.1 > The typeface used in the ruler and in the status bar may not be Helvetica. This is normal -- Word uses the first variable pitch sans-serif font available in the [Fonts] section of your ATM.INI file. > The bullet character displays and prints as a lowercase "o". This is a feature of Word. >> Excel 3.0 > When printing to a PCL printer such as the LaserJet Series II, make sure that the print resolution in the printer setup menu is set to 300 dpi. > If you are using rotated text in graphs, you must remove the aliases for the Roman and Modern fonts. See "Windows Vector fonts" below. ----------------------------------------------------------- GENERAL HINTS AND TIPS >> "Times" vs. "Tms Rmn" Both Times and Tms Rmn appear in your applications' font menus when ATM is on. While ATM automatically substitutes Times whenever it sees Tms Rmn (for backward compatibility with existing documents), itis more reliable to select Times instead. The same is true for Helvetica vs. Helv. >> Maximum number of fonts ATM 1.15 can install a maximum of 1500 fonts. However, Windows apparently limits the number of PostScript soft font entries in your WIN.INI file to approximately 175. If you get spurious printer error messages when starting your application or switching to a PostScript printer, you may have reached this limit. Turn off ATM and restart Windows. If the condition still persists, you must manually remove these entries from your WIN.INI file. >> Windows vector fonts ATM will substitute its scalable Times and Helvetica for Windows' Roman and Modern, respectively, in order to eliminate the "stick- figure" appearance of these fonts. If you don't want ATM to make this substitution, delete the following two lines from the [Aliases] section of your ATM.INI file: Roman=Times Modern=Helvetica >> PostScript printer font downloading The Add font option in the ATM Control Panel adds the selected fonts to every PostScript printer in WIN.INI as manually downloaded fonts. This configuration minimizes printing time since fonts will not be downloaded by Windows every time there is a font change in your document; however, the desired fonts must be resident in the printer (either in memory or on the printer's hard disk) before printing. You can reconfigure a manually downloaded font as an automatically downloaded font by modifying its entry in the PostScript section of WIN.INI. See the documentation provided with your font package for more information. >> Re-installing or installing a new version of ATM If you already have a version of ATM installed on your system, turn it off using the ATM Control Panel and restart Windows before running the ATM Installer. ------------------------------------------------------------ TROUBLESHOOTING Problem: ATM displays the message "ATM fonts and PostScript printer fonts don't match on xxx." Solution: "xxx" is the name of the first font that does not match. This message appears if your PostScript printer is not "active" or if you have changed printer ports since installing fonts through the ATM Control Panel. To reactivate your printer, you must use the Printers option in the Windows Control Panel; selecting the printer from your application's Printer Setup menu alone is not enough. If you have changed printer ports, you must add the fonts again through the ATM Control Panel. Problem: Justified text sometimes extends beyond the right margin on screen. Solution: Turn off the "Use pre-built or resident bitmap fonts" option in the ATM Control Panel. Problem: Italic or script fonts are sometimes clipped at the end of a line or at the current cursor position. Solution: This is a limitation of Windows and affects only screen display of text. The text will print correctly with ATM. Problem: Some colors of text print incorrectly on an HP PaintJet. Solution: Version 1.0 of the HP PaintJet driver and version 1.0 of Zenographics' SuperPrint do not correctly support color printing with ATM. Version 1.1 of SuperPrint and version 1.01 of the HP driver correct this problem. Problem: Ventura Publisher v3.0 displays a "Divide by zero" error message. Solution: This is due to the way Ventura Publisher manages font information. Exit Ventura Publisher, remove some fonts using the ATM Control Panel and restart Windows. Contact Ventura for the "11/90 patch" disk at (800) 822-8221. Problem: Selecting text in Ami Professional 1.2 seems sluggish. Solution: Turn off the Pair Kerning option in Ami's Defaults menu until you are ready to print. The sluggishness also occurs without ATM when using printers that support automatic kerning (such as PostScript printers). The sluggishness is due to Ami's extra overhead in performing its kerning calculations. Since ATM provides automatic kerning capabilities for all Windows-supported printers, this suggestion also applies to non-PostScript printers. Problem: Courier text is clipped at sizes smaller than 9 point on screen and on printed output. Solution: In order to avoid problems with applications that do not handle Courier correctly, ATM must return a fixed-size screen bitmapped font for small sizes. You can change this by deleting the following line from the [Aliases] section of your ATM.INI file: Courier=Courier ATM will then provide the exact (unclipped) size of Courier requested by your applications. Note that some applications don't expect to receive the size they requested. For example, the numbers in the ruler of AmiPro 1.2 will be displayed in 1 point type.
1-2-3 Release 4 for Windows Product Updates (README.TXT)
**CONTENTS**
1. Install
Information for Upgraders
Distribution Install
Installing on Computers with CD-ROM Drives
2. Windows and Available Memory
3. Charting Information for Upgraders
4. Printing Performance Information
Printer Drivers and Devices
Print Resolution
5. DataLens and ODBC Drivers
ODBC Drivers
IBM Database Manager
Environment Variables
LOTUS.BCF File
6. Version Manager
7. Solver
8. Command-Line Parameters
9. Corrections to the Documentation
User's Guide
What's New
DataLens Drivers for 1-2-3
Macros Help
10. Font Usage
Font Mapping
Font Performance Tips
Installing and Removing ATM
**1. INSTALL**
INFORMATION FOR UPGRADERS
If you install 1-2-3 Release 4 in a directory that contains a previous
release of 1-2-3 for Windows, you should have 2MB to 3MB of free hard-disk
space.
If your Windows directory is on a different drive from your 1-2-3 directory,
the drive that contains your Windows directory should have 1.5MB to 2MB of
free hard-disk space.
DISTRIBUTION INSTALL
To streamline the installation of 1-2-3 on many stand-alone computers, copy
the 1-2-3 Release 4 files to a network server and then let licensed users
install 1-2-3 on their hard disks from the server.
Follow these instructions to copy 1-2-3 to the server:
1. Follow the instructions on the label of Disk 1 to start Install.
2. Enter your name and company name in the Recording Your Name and
Company Name dialog box, and then choose OK.
Note: Each user who installs from the server must enter his or her
name during Install, but the company name you enter now remains fixed.
3. Choose OK to confirm the names.
4. Choose Exit Install to end the Install program.
5. End Microsoft Windows.
6. At the operating system prompt, type a:crsby and press ENTER.
If Disk 1 is not in diskette drive A:, substitute the correct
letter.
CRSBY.BAT copies the compressed 1-2-3 files to the server, prompting you
to change disks until all the files are copied.
Users can now follow these instructions to install 1-2-3 Release 4 on their
hard disks.
1. In the Windows Program Manager, choose File Run.
2. Type [x]:\path\install in the Command Line text box.
[x]:\path is the drive letter and path for the server directory that
contains the 1-2-3 files. For example, type t:\123r4w\install to start
Install from a directory named \123R4W on drive T:.
3. Choose OK.
The Install program displays a series of dialog boxes that prompt users
for information about what to install and how to install it.
INSTALLING ON COMPUTERS WITH CD-ROM DRIVES
If you are installing 1-2-3 on a computer that has a CD-ROM drive, make
sure the drive contains a CD-ROM and is closed before you start Install.
**2. WINDOWS AND AVAILABLE MEMORY**
Note: Windows 3.1 requires more memory than Windows 3.0, so you may need to
free additional memory before you use 1-2-3 with Windows 3.1.
Before you start 1-2-3, find out how much memory is available by opening
Program Manager and choosing Help About Program Manager.
If less than 1800K of memory is free, you will not be able to start 1-2-3
Release 4. Close open applications and remove memory-resident programs
to make more memory available. Then check the amount of free memory again.
If slightly more than 1800K of memory is free, you can start 1-2-3, but
you may encounter Memory Full messages while you work.
The following suggestions can help you increase the amount of available
memory.
* For maximum memory savings, remove SMARTdrive. (If you do not want to
remove SMARTdrive, see the next bullet to reduce the SMARTdrive cache
size.)
To remove SMARTdrive in Windows 3.0, remove the
DEVICE=[x]:\WINDOWS\SMARTDRV.SYS statement from CONFIG.SYS.
To remove SMARTdrive in Windows 3.1, remove the
[x]:\WINDOWS\SMARTDRV.EXE statement from AUTOEXEC.BAT.
You can either delete these statements or type REM in front of them.
For example, REM [x]:\WINDOWS\SMARTDRV.EXE
* If you do not want to remove SMARTdrive, you can save memory by reducing
the SMARTdrive cache to 256K.
In Windows 3.0, edit the SMARTdrive statement in CONFIG.SYS
so it reads DEVICE=[x]:\WINDOWS\SMARTDRV.SYS 1024 256.
In Windows 3.1, edit the SMARTdrive statement in AUTOEXEC.BAT so it reads
[x]:\WINDOWS\SMARTDRV.EXE 1024 256.
* 386 users only: Increase the Windows swap file size to at least 1MB.
To learn how to change the swap file size, see the Microsoft Windows
documentation.
* Windows 3.1 users only: Windows 3.1 comes with a scalable font manager,
so you can turn off ATM to maximize memory savings. To turn off ATM,
double-click the ATM Control Panel icon. Under ATM, select Off.
Select Exit. Restart Windows.
Tip: If 1-2-3 displays the message "Out of memory" or "Not enough Windows
resources to complete the operation," and you cannot save your files with
File Save, use the keyboard shortcut Ctrl+S.
**3. CHARTING INFORMATION FOR UPGRADERS**
To work with named charts that you created in a previous release of 1-2-3
for Windows, but did not add to the worksheet, open the .WK3 file that
contains the charts and choose Edit Go To. Select Chart in the "Type of
item" drop-down box, and then select the named chart in the list box.
1-2-3 adds the chart to the center of the worksheet area displayed on the
screen. You can move the chart anywhere in the worksheet.
**4. PRINTING PERFORMANCE INFORMATION**
PRINTER DRIVERS AND DEVICES
Printer manufacturers periodically update printer drivers. In some cases,
drivers newer than those that shipped with Windows 3.1 are available.
To find out if a newer driver is available for your printer, check bulletin
boards such as CompuServe, or contact your printer manufacturer.
The following table lists some popular printers and newer drivers that
are currently available.
PRINTER NEW DRIVER
======= ==========
HP DeskJet Family Version 3 or higher
HP LaserJet III Versions 2 and 2.1 (newer than 31.3.89)
HP LaserJet IV Version 31.V1.18 or higher
IBM 4019/4029 Version 3.08 or higher
Postscript Versions 3.5 and 3.53
To find out the version number of your printer driver, do the following:
1. Open the Windows Control Panel and select Printers.
Windows displays a list of printers installed on your system.
2. Highlight a printer in the list.
4. Choose Setup.
The Setup dialog box for your printer appears.
5. Choose About to see information about your printer, including the
version number of the driver.
PRINT RESOLUTION
1-2-3 Release 4 is optimized for printing at 300 dots-per-inch (dpi).
Tip: If you want to print at 600 dpi, and your print job contains
many different fonts, and you encounter problems printing, open
Printers in the Windows Control Panel, and select the "Print True Type
as Graphics" check box in your printer's Setup Options or Setup Options
Advanced dialog box.
**5. DATALENS AND ODBC DRIVERS**
If 1-2-3 displays the message "Invalid field name" when you query against
worksheets on disk, choose Set database table before you use any other
Query command.
ODBC DRIVERS
1-2-3 Release 4 can be configured to use drivers that meet the Microsoft
Open Database Connectivity (ODBC) specification. The dBASE DataLens driver
that comes with 1-2-3 Release 4 uses an ODBC engine.
Note: Most ODBC drivers have not been certified with 1-2-3. Lotus does not
provide technical support for these drivers.
If you are using the DataLens dBASE driver or any other ODBC driver with
1-2-3, start SHARE.EXE before you start Windows. To start SHARE.EXE before
every Windows session, add the following line to your AUTOEXEC.BAT file:
C:\DOS\SHARE
See your DOS documentation for information about SHARE.EXE.
You can configure 1-2-3 to use either all ODBC drivers or one specific
driver. To provide access to all ODBC sources, add the following line to
your LOTUS.BCF file:
DN="ODBC" DL="DLODBC" DD="All ODBC sources";
You can add support for a specific ODBC driver by including a DC parameter
to the ODBC record in LOTUS.BCF. If an entry with the string DL="DLODBC",
as shown above, also includes a string of the form DC="driver=xxx" then
1-2-3 will make available only those sources that use "xxx" as a driver.
For example:
DN="SQL Database via ODBC" DL="DLODBC" DC="driver=sql.dll" AC=UI,PW;
You can configure 1-2-3 to prompt for a user ID and password for a data
source by adding the following line to the LOTUS.BCF:
DB="source name" DN="ODBC" AC=UI,PW;
For more information on editing your LOTUS.BCF file, see DataLens Drivers
for 1-2-3.
When the 1-2-3 user picks the DataLens driver for dBASE files, the list of
available databases includes the following:
* The current directory
* All data sources in ODBC.INI that have "driver=qodbf.dll"
In addition, you can also add a new database name to ODBC.INI and type in
the new path.
Data source names for dBASE must be paths when using DLODBC.
When you use a macro to send updates to ODBC-dBASE IV tables, you must
follow the {SEND-SQL} command with a {COMMIT} command.
IBM DATABASE MANAGER
For Database Manager access to an OS/2 2.0 server, you need the Local Area
Network Support Program Version 1.3.
ENVIRONMENT VARIABLES
Unlike some other releases of 1-2-3, 1-2-3 Release 4 does not use the
"LOTUSBCF" environment variable, but reads only records listed in the
LOTUS.BCF file located in \LOTUSAPPS\DATALENS.
**6. VERSION MANAGER**
If you are using Version Manager with Lotus Notes Release 3, start SHARE.EXE
before you start Windows. To start SHARE.EXE before every Windows session,
add the following line to your AUTOEXEC.BAT file:
C:\DOS\SHARE
See your DOS documentation for information about SHARE.EXE.
When you use shared files, Lotus Notes may display certain messages in a
special untitled error window during your 1-2-3 session. Attempting to
close this window ends communication with the Notes server for the rest
of the 1-2-3 session.
If 1-2-3 displays the message "Error Initializing Lotus Notes" when you
try to open a shared file (.NS4), check the following:
* If the LotusMail section in your WIN.INI file specifies Notes, make sure
it includes the correct Notes program path. For example:
[LotusMail]
Application=Notes
Program=x:\notes\notes.exe
* If the LotusApplications section of your LOTUS.INI file specifies Notes,
make sure it includes the correct Notes program path. For example:
[LotusApplications]
Notes=x:\notes\notes.exe
* Make sure SHARE.EXE was started before you started Windows.
If you delete all versions from a range in a shared file (.NS4), you will
be unable to create any more versions in that range. Do not delete all
versions from a range unless you are sure you no longer want to share it.
**7. SOLVER**
Solver uses relationships among formula cells in 1-2-3 to arrive at its
answers. Since DDE links get their data from sources outside 1-2-3, you
should not use @DDELINK formulas in cells that you use as adjustable or
constraint cells for Solver.
**8. COMMAND-LINE PARAMETERS**
To specify command-line parameters for 1-2-3 Release 4
1. Highlight the 1-2-3 Release 4 icon.
2. Choose File Properties from the Windows Program Manager.
3. In the Command Line text box, append a command-line parameter to
123W.EXE. (For example, C:\123R4W\PROGRAMS\123W.EXE -s)
You can specify the following command-line parameters:
filename
Lets you specify a file to load whenever you start 1-2-3.
-s
Makes 1-2-3 Release 4 use the software floating point driver instead
of a math coprocessor. Use this parameter if you have a defective math
coprocessor in your computer or if your computer tells 1-2-3 you have a
math coprocessor when you do not. Under these circumstances, all your
formulas may evaluate to 0, ERR, or *** (asterisks).
-i [filename.ini]
Lets you specify an initialization file other than 123R4.INI. For example,
C:\123R4W\PROGRAMS\123W.EXE -iC:\123R4W\MYINI.INI specifies the
initialization file C:\123R4W\MYINI.INI.
Note: If you use 1-2-3 Release 4 with Lotus Notes Document Inset
Protocol (DIP), you must have 123R4.INI in your Windows directory.
**9. CORRECTIONS TO THE DOCUMENTATION**
USER'S GUIDE
Page 89: The second sentence of the Note should read: To delete a named
range that contains versions, you must first delete the versions.
Page 125: The last sentence in the second paragraph under "Changing
column width" should read: Use Style Column Width to change the column to
a specific width, reset to the default width, or set the width to fit the
largest entry in the current selection.
Page 126: The second bullet under step 3 of "To change columns to a
specified width" should read: "Fit widest entry" adjusts the columns to
the width of the widest entries in the current selection.
WHAT'S NEW
Pages 88: Add the following to the Transcript Commands section:
Record Relative Records range selections as offsets of the current cell.
Record Absolute Records range selections as cell addresses.
Appendix D: @USER is not supported by 1-2-3 Release 4. Use
@INFO("setup-user-name"} instead.
Appendix E: Add the macro command {SELECT-RANGE-RELATIVE}. Remove the
macro commands {PARSE-CREATE} and {PARSE-RESET}.
DATALENS DRIVERS FOR 1-2-3
Pages 5 and 6: Wherever the variable [range-name] appears, substitute
the variable [table-name].
MACROS HELP
{LINK-CREATE} topic: Remove the last sentence from the description of
the app-name argument.
**10. FONT USAGE**
FONT MAPPING
1-2-3 Release 4 can map requests for Adobe Type Manager (ATM) fonts to
TrueType fonts, or requests for TrueType fonts to ATM fonts.
Font mapping is controlled by the TT_MAP statement in the [TTMAPPING]
section of your 123R4.INI file. When you start 1-2-3 for the first time,
1-2-3 automatically sets TT_MAP according to your configuration.
Note: When you open a file created with 1-2-3 for DOS, Wysiwyg fonts are
mapped to Windows fonts using the settings in the [FONTMAPPING] section
of your 123R4.INI file.
FONT PERFORMANCE TIPS
Use ATM fonts, such as Arial MT, when rotating text blocks in 1-2-3.
For information about rotating text blocks, search on "Rotating drawn
objects" in Help.
Use TrueType fonts to increase printing speed with a Hewlett-Packard
LaserJet IV, because Arial and Times New Roman are internal fonts for
this printer.
INSTALLING AND REMOVING ATM
If you installed 1-2-3 on a network node, you can install ATM from the
server if your network administrator transferred ATM to the server. To
install ATM:
1. Open the Windows Program Manager.
2. Choose File Run.
3. Type x:\path\ATM\install in the Command Line text box.
x:\path is the driver letter and path for the 1-2-3 directory on your
server. For example, type t:\123r4w\atm\install to install ATM from a
1-2-3 directory named \123R4W on drive T:.
4. Choose OK.
If you run Windows from a network server, you will be able to install ATM
only if you have write access to the WINDOWS\SYSTEM directory while you are
installing. See your network administrator to get write access to this
directory.
After you install ATM, other Windows applications may look slightly
different onscreen because ATM substitutes its scalable fonts for certain
Windows bitmap fonts. The point size at which ATM makes this substitution
is controlled by the SynonymPSBegin= statement in ATM.INI.
SynonymPSBegin= is initially set to 9; this means ATM substitutes its
fonts for Windows fonts larger than 9 points. If you change this statement
to SynonymPSBegin=13, ATM substitutes its fonts for Windows fonts larger
than 13 points. Other Windows applications that use 10 and 12 point fonts
will continue to look the same as they did before you installed ATM.
If you experience difficulties with ATM soft fonts, you can remove ATM
from your hard disk and re-install it.
Before you remove ATM from your hard disk, do the following:
1. If you installed additional fonts, copy those fonts to a temporary
directory.
2. Remove all Windows soft fonts from your WIN.INI file. Soft fonts are
listed with the installed printers. In the example below, an * (asterisk)
marks each line to remove.
[PostScript,LPT2]
device=14
color=2
feed1=1
*softfonts=11
*softfont1=c:\psfonts\pfm\_a______.pfm,c:\psfonts\_a______.pfb
*softfont2=c:\psfonts\pfm\bdbc____.pfm,c:\psfonts\bdbc____.pfb
To remove ATM from your system, do the following:
1. End Microsoft Windows.
2. Change the following lines of your SYSTEM.INI file, which is located in
your Windows directory:
* Change system.drv=atmsys.drv to system.drv=system.drv
* Delete the line atm.system.drv=system.drv
Note: These lines may be different on some systems (for example, the
Hewlett-Packard Vectra); however, the result should be a single line
that reads system.drv=system.drv.
3. Delete the following files:
* Delete ATM16.DLL and ATM32.DLL from the \SYSTEM subdirectory of your
Windows directory.
* Delete ATM.INI and ATMCNTRL.EXE from your Windows directory.
* Delete any .PFM, .PFB, .SFP, and .SFL files from the directories in
which you installed fonts.
4. To re-install ATM, start Windows and insert the ATM disk in drive A:.
Open the Windows Program Manager. Choose File Run. Type a:install in
the Command Line text box and then Choose OK.
IMPROV FOR WINDOWS, RELEASE 2.0 - RELEASE NOTES
This document contains notes about Improv Release 2.0. The notes
describe problems you might encounter and provide information
not available in the Improv Handbook, Improv in Action, and the
Help systems. To print this document, choose File Print.
INSTALL
If your system is running the DOS SHARE utility when you install
Improv, then the Improv Install program will be unable to delete
a temporary file named INSTMAIN.EXE, which is located in the
subdirectory named LOTUSTMP, which is located in your Windows
directory. After you complete the Install program, manually delete
the file INSTMAIN.EXE and then remove the LOTUSTMP directory.
IMPROV GUIDED TOUR
1. For optimal viewing of the Guided Tour, before you launch Improv
for the first time, turn off any screen saver program and switch
to the Windows 3.1 VGA display driver.
2. Improv attempts to load the Guided Tour the first time that you
launch the program. If you delete the Guided Tour before launching
Improv for the first time, be sure to change the following line in the
IMPROV.INI file, which is located in your Windows directory:
Change FirstTime=YES to FirstTime=NO. Changing this line prevents
Improv from trying to launch the tour.
SAMPLE SCRIPTS
The following sample library scripts are provided in the Scripts
directory. To find out more about how these scripts work, open
the .LSS files and read the descriptive comments in the scripts.
The scripts marked with an asterisk (*) are attached to
SmartIcons.
*COLORCEL.LSS - Allows you to assign colors to cells, based on
their values. There is an option to color "All Cells on Recalc."
When the option is checked, each time the worksheet
recalculates, the script checks every cell value. To turn this
option off, run the script again, and uncheck the option.
*LOADTMPL.LSS - Allows you to view a dialog box that lets you
choose from a list of worksheet templates to open.
*ADDINS20.LSS - Registers the add-in @functions for use in
formulas.
SEARCH.LSS - Allows you to search for and/or replace cell values
or text of formulas.
SCRPUTIL.LSS - Includes a set of utilities for writing Improv
applications in LotusScript.
DEFAULT PATHS
When specifying default paths in the Default Paths dialog box
(Tools\User Setup\Paths), do not enter a trailing backslash at
the end of a subdirectory path. For example, enter
C:\IMPROV\MYFILES, not C:\IMPROV\MYFILES\. All root directories
must end with a backslash. For example, enter D:\.
PRINTING
1. Multi-line text in a model may appear truncated when you
print to an HP LaserJet III. To correct this, check Send
TrueType as Graphics in the Options panel of the Print Setup
dialog box and then print the model.
2. Settings on the Print Setup dialog box--for example, paper
size--are not saved with the Improv model. If you open an
existing model and notice, for example, that the layout of a
presentation has changed, check the paper size specified in the
Print Setup dialog box.
3. If you set worksheet grid line styles to double lines, the
space between the lines may not appear in a print preview.
However, the lines will print correctly.
LOTUS CHART
1. If you get the message "Cannot create a chart" when you open
a file containing charts, do not save the file or you will lose the
charts previously contained in the file. Instead, when you get the
message, click the Explain button to get more information about resolving
the problem. Then close the file without saving it.
2. The only information that is linked between the worksheet and
a chart is the data that you plot. The legend names and
X-axis names are not linked. Therefore, if you edit an item name, the
chart does not update to reflect the new name.
3. To cut and paste data and keep a chart of that data updated, cut
and paste the cells only. If you cut and paste items, the chart
does not update.
4. The High-Low-Close-Open (HLCO) chart layouts that have bars at the
bottom and lines at the top will not display correctly unless
the chart has five or six data series.
5. The High-Low-Close-Open (HLCO) chart layouts that have no bars at
the bottom or lines at the top will not display correctly unless
the chart has four or fewer data series.
6. If you enter a maximum value for the chart scale, the chart
may not display it if there is not enough room. To correct this,
enlarge the chart vertically, change the major ticks value, or change
the minimum value.
7. You cannot format the series labels in a pie chart. The series
labels for other chart types take their format from the Y-axis
label format.
8. In a 3D chart, the X-axis tick labels may overlap or appear
truncated. To correct this, enlarge the plot of the chart or assign
a font in a smaller point size to the X-axis.
9. Assigning some fonts to the Y-axis title in a chart results
in horizontal text rather than vertical text appearing in the print
preview; however, the printout appears correctly. These fonts include
FixedSys, Helvetica Narrow, MS Sans Serif, MS Serif, Palatino,
System, and ZapfChancery.
FONTS
1. To assign a font size that is not listed in the InfoBox or on the
status bar, you must use LotusScript--for example, use the command
SetIntProperty(0, TextSize, 72) to specify a 72-point font. In
header/footer text, enter a format code to specify the desired font
--for example, {F 72}.
2. Improv does not support SuperText and SuperPrint (Releases 1.1, 1.2,
2.0, 2.1) from Zenographics.
TEXT EXPORT
If you export an unsaved file to a text file, there is no limit
to the size of the file you can export. If you export a saved file
to a text file, you can export a maximum of 8192 rows and 256 columns.
FILE IMPORT
1. Remove password protection from a file before you import
the file into Improv.
2. Remove embedded charts and graphic objects from an Excel 4.0 file
before you import the file into Improv.
3. When you import a 1-2-3 or Excel file that contains many formulas,
the import may take a long time. To import the worksheet faster,
don't import the formulas. To do this, uncheck Import Formulas in
the Worksheet Import dialog box.
4. When you import a 1-2-3 or Excel file, most functions will be
translated into their Improv equivalents; however, you may need to
recreate some manually after you import the file. For more information,
see Appendix B of the Improv Handbook, which lists 1-2-3 and Excel
functions and their Improv equivalents.
5. Improv can import Excel 4.0 files. If you upgraded from Excel 3.0 to
Excel 4.0, you must save Excel 3.0 files as Excel 4.0 files before
you import them into Improv.
DDE LINKS
A DDE link may break without warning if Improv is the server
and you rename, group, or ungroup items that are included in a linked
selection. If the link breaks, delete the link formula and recreate the
link.
COLLATE OPTIONS
In the International dialog box (Tools/UserSetup/International), the
ASCII option actually displays the ANSI character set.
LOTUSSCRIPT
1. Be aware of the following issues with scripts that use the CloseModel
or CloseIWindow functions to close models:
a) If you have a library script that closes the model it is attached to,
do not attach it to a model. Instead, use a model script for this
purpose. b) Do not debug a library or model script that uses
the CloseModel function to close the file that contains the
script.
2. Within a script, reading files from a floppy device that is not
ready and then choosing the Cancel option from a "Drive not ready"
message will cause Improv and Windows to crash. To work around this
problem, scripts should first include another file operation that
checks the drive to make sure that it is ready. For example,
include the dir$ function in the script, along with a way to exit the
script if the dir$ fails. Then if the drive is not ready, choosing
Cancel will succeed, but the dir$ will fail and the script will stop.
If the drive is ready, the script can continue with the file operation
that you originally wanted to perform.
3. If you do not use U.S. as your International country setting,
you should note the following. Using "\$" within the second argument
to the format$ function will cause the "$" to appear at the beginning
of the resulting text--for example, print format$(1234.56,"#,###.##\$")
will print $1,234.56. If you want the "$" trailing the text, use
print format$(1234.56,"#,###.##")+"$" which will print 1,234.56$.
4. In scripts, use the float data type to store Improv cell values.
Use the SetLongDoubleCellValue and GetLongDoubleCellValue functions
to set and get Improv cell data.
5. GetBrowserNote doesn't work when the selection is a model script.
6. GetSelection doesn't work when the selection is a library script.
7. Do not assign the same name to two scripts in the same script
library file. This includes scripts with the same names and different
capitalization. For example, do not name two scripts SCRIPT1 and
script1.
8. After deleting or renaming a script name in the Script Name box
of the script library window, you must press Enter.
9. Do not debug a script (Tools/Run Script/Debug) containing the command
CreateChart or CmdExec(xcmd_CreateChart). Instead, insert a STOP statement
in the script after these commands. Then to debug the script, run the
script. The STOP statement will invoke the Debug window, and
you will be able to debug the script from that point.
10. In Script Help, the description of the parameters for the
GetStringProperty is incorrect. Use the parameter IT_CONTEXT1 to find
the view/presentation/script name; use the parameter IT_CONTEXT2 to find
the worksheet name.
SCRIPT RECORDING AND PLAYBACK
1. Recorded scripts may have references to the specific model that
was operated on. To use the script on a different view, worksheet,
or model or to make the script more general, edit the lines before
running the recorded script.
2. You cannot generalize a script that records changes to
settings of graphic objects in Presentations because the names
of the objects are generated by Improv.
3. The option to replace data with calculated values when adding
a formula does not get recorded. When you run the script, the
formula will be created, but the data values will not be
replaced. To work around this problem, record clearing the cell
values first and then create the formula.
4. When recording moving between views, opening the Browser will
always be recorded. To move between views without opening the
Browser, change the SetSelectionByName function call in the
recorded script to CreateSelHandle, use the OpenIWindow command
on the selection, and remove the script text that opens the
Browser.
5. When editing text, operations such as Cut, Copy, and Paste are
not recorded. All that is recorded is the resulting edited text.
LOTUS DIALOG EDITOR
Do not use hard carriage returns when entering text for buttons
or text boxes. Instead, resize the control to allow the text to wrap.
C API
The Scripts directory contains an import library file
(LIBPL.LIB) and a header file (CAPI_PUB.H) for C API users. To
call into the Improv C API interface, create a Windows .DLL file
that includes the CAPI_PUB.H (Improv C API prototypes) and
links with LIBPL.LIB (Improv C API import library).
IMPROV FOR WINDOWS, RELEASE 2.1 - RELEASE NOTES
This document contains notes about Improv(R) Release 2.1.
The notes describe problems you might encounter and
provide information not available in the Improv Handbook,
Improv in Action, and the Help systems. To print this
document, choose File Print.
NEW FEATURES
WK4 Import/Export-- Improv can now import and export
1-2-3(R) files in WK4 format. For more complete information
search in Help under "Importing."
Working Together Icons-- Improv now has a set of SmartIcons
that allow you to launch other Lotus applications from
within Improv. For more complete information search in
Help under "Customizing SmartIcons" for "Using the Working
Together SmartIcons Set."
Notes Data Exchange-- Improv can now exchange data with
Lotus Notes(R). Improv supports text, numbers, and date/time
numbers in editable Notes fields. For more complete information
search in Help under "Data exchange."
INSTALL
1. If your system is running the DOS SHARE utility when
you install Improv, then the Improv Install program will
be unable to delete a temporary file named INSTMAIN.EXE,
which is located in the subdirectory named LOTUSTMP,
which is located in your Windows directory. After you
complete the Install program, manually delete the file
INSTMAIN.EXE and then remove the LOTUSTMP directory.
2. For Server installations, after setting up the \Lotshare
directory, create a subdirectory named \Improv.v20. This
directory will contain the license files. The full path
will be \Lotshare\Improv.v20.
IMPROV GUIDED TOUR
1. For optimal viewing of the Guided Tour, before you
launch Improv for the first time, turn off any screen
saver program and switch to the Windows 3.1 VGA display
driver.
2. Improv attempts to load the Guided Tour the first time
that you launch the program. If you delete the Guided Tour
before launching Improv for the first time, be sure to
change the following line in the IMPROV.INI file, which is
located in your Windows directory: Change FirstTime=YES to
FirstTime=NO. Changing this line prevents Improv from
trying to launch the tour.
SAMPLE SCRIPTS
The following sample library scripts are provided in the
Scripts directory. To find out more about how these
scripts work, open the .LSS files and read the descriptive
comments in the scripts. The scripts marked with an asterisk
(*) are attached to SmartIcons.
*COLORCEL.LSS - Allows you to assign colors to cells, based
on their values. There is an option to color "All Cells on
Recalc." When the option is checked, each time the worksheet
recalculates, the script checks every cell value. To turn
this option off, run the script again, and uncheck the
option.
*LOADTMPL.LSS - Allows you to view a dialog box that lets
you choose from a list of worksheet templates to open.
*ADDINS20.LSS - Registers the add-in @functions for use in
formulas.
SEARCH.LSS - Allows you to search for and/or replace cell
values or text of formulas.
SCRPUTIL.LSS - Includes a set of utilities for writing
Improv applications in LotusScript.
DEFAULT PATHS
When specifying default paths in the Default Paths dialog
box (Tools\User Setup\Paths), do not enter a trailing
backslash at the end of a subdirectory path. For example,
enter C:\IMPROV\MYFILES, not C:\IMPROV\MYFILES\. All root
directories must end with a backslash. For example, enter
D:\.
PRINTING
1. Multi-line text in a model may appear truncated when
you print to an HP LaserJet III. To correct this, check
Send TrueType as Graphics in the Options panel of the
Print Setup dialog box and then print the model.
2. Settings on the Print Setup dialog box--for example,
paper size--are not saved with the Improv model. If you
open an existing model and notice, for example, that the
layout of a presentation has changed, check the paper size
specified in the Print Setup dialog box.
3. If you set worksheet grid line styles to double lines,
the space between the lines may not appear in a print
preview. However, the lines will print correctly.
LOTUS CHART(TM)
1. If you get the message "Cannot create a chart" when
you open a file containing charts, do not save the file
or you will lose the charts previously contained in the
file. Instead, when you get the message, click the Explain
button to get more information about resolving the problem.
Then close the file without saving it.
2. The only information that is linked between the
worksheet and a chart is the data that you plot. The
legend names and X-axis names are not linked. Therefore,
if you edit an item name, the chart does not update to
reflect the new name.
3. To cut and paste data and keep a chart of that data
updated, cut and paste the cells only. If you cut and paste
items, the chart does not update.
4. The High-Low-Close-Open (HLCO) chart layouts that have
bars at the bottom and lines at the top will not display
correctly unless the chart has five or six data series.
5. The High-Low-Close-Open (HLCO) chart layouts that have
no bars at the bottom or lines at the top will not display
correctly unless the chart has four or fewer data series.
6. If you enter a maximum value for the chart scale, the
chart may not display it if there is not enough room.
To correct this, enlarge the chart vertically, change the
major ticks value, or change the minimum value.
7. You cannot format the series labels in a pie chart.
The series labels for other chart types take their format
from the Y-axis label format.
8. In a 3D chart, the X-axis tick labels may overlap or
appear truncated. To correct this, enlarge the plot of the
chart or assign a font in a smaller point size to the X-axis.
9. Assigning some fonts to the Y-axis title in a chart
results in horizontal text rather than vertical text
appearing in the print preview; however, the printout
appears correctly. These fonts include FixedSys, Helvetica
Narrow, MS Sans Serif, MS Serif, Palatino, System, and
ZapfChancery.
FONTS
1. To assign a font size that is not listed in the InfoBox
or on the status bar, you must use LotusScript--for example,
use the command SetIntProperty(0, TextSize, 72) to specify
a 72-point font. In header/footer text, enter a format code
to specify the desired font --for example, {F 72}.
2. Improv does not support SuperText and SuperPrint
(Releases 1.1, 1.2, 2.0, 2.1) from Zenographics.
TEXT EXPORT
If you export an unsaved file to a text file, there is no
limit to the size of the file you can export. If you export
a saved file to a text file, you can export a maximum of
8192 rows and 256 columns.
FILE IMPORT
1. Remove password protection from a file before you
import the file into Improv.
2. Remove embedded charts and graphic objects from a
Microsoft(R) Excel 4.0 file before you import the file
into Improv.
3. When you import a 1-2-3 or Excel file that contains
many formulas, the import may take a long time. To import
the worksheet faster, don't import the formulas. To do
this, uncheck Import Formulas in the Worksheet Import
dialog box.
4. When you import a 1-2-3 or Excel file, most functions
will be translated into their Improv equivalents; however,
you may need to recreate some manually after you import
the file. For more information, see Appendix B of the
Improv Handbook, which lists 1-2-3 and Excel functions and
their Improv equivalents.
5. Improv can import Excel 4.0 files. If you upgraded from
Excel 3.0 to Excel 4.0, you must save Excel 3.0 files as
Excel 4.0 files before you import them into Improv.
DDE LINKS
A DDE link may break without warning if Improv is the
server and you rename, group, or ungroup items that are
included in a linked selection. If the link breaks,
delete the link formula and recreate the link.
COLLATE OPTIONS
In the International dialog box (Tools/UserSetup/International),
the ASCII option actually displays the ANSI character set.
LOTUSSCRIPT
1. Be aware of the following issues with scripts that use
the CloseModel or CloseIWindow functions to close models:
a) If you have a library script that closes the model it is
attached to, do not attach it to a model. Instead, use a
model script for this purpose.
b) Do not debug a library or model script that uses
the CloseModel function to close the file that contains
the script.
2. Within a script, reading files from a floppy device
that is not ready and then choosing the Cancel option from
a "Drive not ready" message will cause Improv and Windows
to crash. To work around this problem, scripts should first
include another file operation that checks the drive to make
sure that it is ready. For example, include the dir$
function in the script, along with a way to exit the script
if the dir$ fails. Then if the drive is not ready, choosing
Cancel will succeed, but the dir$ will fail and the script
will stop. If the drive is ready, the script can continue
with the file operation that you originally wanted to perform.
3. If you do not use U.S. as your International country
setting, you should note the following. Using "\$" within
the second argument to the format$ function will cause the
"$" to appear at the beginning of the resulting text--for
example, print format$(1234.56,"#,###.##\$") will print
$1,234.56. If you want the "$" trailing the text, use print
format$(1234.56,"#,###.##")+"$" which will print 1,234.56$.
4. In scripts, use the float data type to store Improv cell
values. Use the SetLongDoubleCellValue and
GetLongDoubleCellValue functions in place of SetCellValue
and GetCellValue to set and get Improv cell data. This will
avoid rounding errors due to the conversion of 8 byte data
to 10 byte data.
5. GetBrowserNote doesn't work when the selection is a model
script.
6. GetSelection doesn't work when the selection is a library
script.
7. Do not assign the same name to two scripts in the same
script library file. This includes scripts with the same
names and different capitalization. For example, do not name
two scripts SCRIPT1 and script1.
8. After deleting or renaming a script name in the Script
Name box of the script library window, you must press Enter.
9. Do not debug a script (Tools/Run Script/Debug) containing
the command CreateChart or CmdExec(xcmd_CreateChart). Instead,
insert a STOP statement in the script after these commands.
Then to debug the script, run the script. The STOP statement
will invoke the Debug window, and you will be able to debug
the script from that point.
10. In Script Help, the description of the parameters for the
GetStringProperty is incorrect. Use the parameter IT_CONTEXT1
to find the view/presentation/script name; use the parameter
IT_CONTEXT2 to find the worksheet name.
SCRIPT RECORDING AND PLAYBACK
1. Recorded scripts may have references to the specific
model that was operated on. To use the script on a different
view, worksheet, or model or to make the script more general,
edit the lines before running the recorded script.
2. You cannot generalize a script that records changes to
settings of graphic objects in Presentations because the
names of the objects are generated by Improv.
3. The option to replace data with calculated values when
adding a formula does not get recorded. When you run the
script, the formula will be created, but the data values
will not be replaced. To work around this problem, record
clearing the cell values first and then create the formula.
4. When recording moving between views, opening the Browser
will always be recorded. To move between views without
opening the Browser, change the SetSelectionByName function
call in the recorded script to CreateSelHandle, use the
OpenIWindow command on the selection, and remove the script
text that opens the Browser.
5. When editing text, operations such as Cut, Copy, and
Paste are not recorded. All that is recorded is the
resulting edited text.
LOTUS DIALOG EDITOR
Do not use hard carriage returns when entering text for
buttons or text boxes. Instead, resize the control to allow
the text to wrap.
C API
The Scripts directory contains an import library file
(LIBPL.LIB) and a header file (CAPI_PUB.H) for C API users.
To call into the Improv C API interface, create a Windows
.DLL file that includes the CAPI_PUB.H (Improv C API
prototypes) and links with LIBPL.LIB (Improv C API import
library).
1-2-3 Release 4 for Windows Product Updates (README.TXT)
**CONTENTS**
1. Install
Information for Upgraders
Distribution Install
Installing on Computers with CD-ROM Drives
2. Windows and Available Memory
3. Charting Information for Upgraders
4. Printing Performance Information
Printer Drivers and Devices
Print Resolution
5. DataLens and ODBC Drivers
ODBC Drivers
IBM Database Manager
Environment Variables
LOTUS.BCF File
6. Version Manager
7. Solver
8. Command-Line Parameters
9. Corrections to the Documentation
User's Guide
What's New
DataLens Drivers for 1-2-3
Macros Help
10. Font Usage
Font Mapping
Font Performance Tips
Installing and Removing ATM
**1. INSTALL**
INFORMATION FOR UPGRADERS
If you install 1-2-3 Release 4 in a directory that contains a previous
release of 1-2-3 for Windows, you should have 2MB to 3MB of free hard-disk
space.
If your Windows directory is on a different drive from your 1-2-3 directory,
the drive that contains your Windows directory should have 1.5MB to 2MB of
free hard-disk space.
DISTRIBUTION INSTALL
To streamline the installation of 1-2-3 on many stand-alone computers, copy
the 1-2-3 Release 4 files to a network server and then let licensed users
install 1-2-3 on their hard disks from the server.
Follow these instructions to copy 1-2-3 to the server:
1. Follow the instructions on the label of Disk 1 to start Install.
2. Enter your name and company name in the Recording Your Name and
Company Name dialog box, and then choose OK.
Note: Each user who installs from the server must enter his or her
name during Install, but the company name you enter now remains fixed.
3. Choose OK to confirm the names.
4. Choose Exit Install to end the Install program.
5. End Microsoft Windows.
6. At the operating system prompt, type a:crsby and press ENTER.
If Disk 1 is not in diskette drive A:, substitute the correct
letter.
CRSBY.BAT copies the compressed 1-2-3 files to the server, prompting you
to change disks until all the files are copied.
Users can now follow these instructions to install 1-2-3 Release 4 on their
hard disks.
1. In the Windows Program Manager, choose File Run.
2. Type [x]:\path\install in the Command Line text box.
[x]:\path is the drive letter and path for the server directory that
contains the 1-2-3 files. For example, type t:\123r4w\install to start
Install from a directory named \123R4W on drive T:.
3. Choose OK.
The Install program displays a series of dialog boxes that prompt users
for information about what to install and how to install it.
INSTALLING ON COMPUTERS WITH CD-ROM DRIVES
If you are installing 1-2-3 on a computer that has a CD-ROM drive, make
sure the drive contains a CD-ROM and is closed before you start Install.
**2. WINDOWS AND AVAILABLE MEMORY**
Note: Windows 3.1 requires more memory than Windows 3.0, so you may need to
free additional memory before you use 1-2-3 with Windows 3.1.
Before you start 1-2-3, find out how much memory is available by opening
Program Manager and choosing Help About Program Manager.
If less than 1800K of memory is free, you will not be able to start 1-2-3
Release 4. Close open applications and remove memory-resident programs
to make more memory available. Then check the amount of free memory again.
If slightly more than 1800K of memory is free, you can start 1-2-3, but
you may encounter Memory Full messages while you work.
The following suggestions can help you increase the amount of available
memory.
* For maximum memory savings, remove SMARTdrive. (If you do not want to
remove SMARTdrive, see the next bullet to reduce the SMARTdrive cache
size.)
To remove SMARTdrive in Windows 3.0, remove the
DEVICE=[x]:\WINDOWS\SMARTDRV.SYS statement from CONFIG.SYS.
To remove SMARTdrive in Windows 3.1, remove the
[x]:\WINDOWS\SMARTDRV.EXE statement from AUTOEXEC.BAT.
You can either delete these statements or type REM in front of them.
For example, REM [x]:\WINDOWS\SMARTDRV.EXE
* If you do not want to remove SMARTdrive, you can save memory by reducing
the SMARTdrive cache to 256K.
In Windows 3.0, edit the SMARTdrive statement in CONFIG.SYS
so it reads DEVICE=[x]:\WINDOWS\SMARTDRV.SYS 1024 256.
In Windows 3.1, edit the SMARTdrive statement in AUTOEXEC.BAT so it reads
[x]:\WINDOWS\SMARTDRV.EXE 1024 256.
* 386 users only: Increase the Windows swap file size to at least 1MB.
To learn how to change the swap file size, see the Microsoft Windows
documentation.
* Windows 3.1 users only: Windows 3.1 comes with a scalable font manager,
so you can turn off ATM to maximize memory savings. To turn off ATM,
double-click the ATM Control Panel icon. Under ATM, select Off.
Select Exit. Restart Windows.
Tip: If 1-2-3 displays the message "Out of memory" or "Not enough Windows
resources to complete the operation," and you cannot save your files with
File Save, use the keyboard shortcut Ctrl+S.
**3. CHARTING INFORMATION FOR UPGRADERS**
To work with named charts that you created in a previous release of 1-2-3
for Windows, but did not add to the worksheet, open the .WK3 file that
contains the charts and choose Edit Go To. Select Chart in the "Type of
item" drop-down box, and then select the named chart in the list box.
1-2-3 adds the chart to the center of the worksheet area displayed on the
screen. You can move the chart anywhere in the worksheet.
**4. PRINTING PERFORMANCE INFORMATION**
PRINTER DRIVERS AND DEVICES
Printer manufacturers periodically update printer drivers. In some cases,
drivers newer than those that shipped with Windows 3.1 are available.
To find out if a newer driver is available for your printer, check bulletin
boards such as CompuServe, or contact your printer manufacturer.
The following table lists some popular printers and newer drivers that
are currently available.
PRINTER NEW DRIVER
======= ==========
HP DeskJet Family Version 3 or higher
HP LaserJet III Versions 2 and 2.1 (newer than 31.3.89)
HP LaserJet IV Version 31.V1.18 or higher
IBM 4019/4029 Version 3.08 or higher
Postscript Versions 3.5 and 3.53
To find out the version number of your printer driver, do the following:
1. Open the Windows Control Panel and select Printers.
Windows displays a list of printers installed on your system.
2. Highlight a printer in the list.
4. Choose Setup.
The Setup dialog box for your printer appears.
5. Choose About to see information about your printer, including the
version number of the driver.
PRINT RESOLUTION
1-2-3 Release 4 is optimized for printing at 300 dots-per-inch (dpi).
Tip: If you want to print at 600 dpi, and your print job contains
many different fonts, and you encounter problems printing, open
Printers in the Windows Control Panel, and select the "Print True Type
as Graphics" check box in your printer's Setup Options or Setup Options
Advanced dialog box.
**5. DATALENS AND ODBC DRIVERS**
If 1-2-3 displays the message "Invalid field name" when you query against
worksheets on disk, choose Set database table before you use any other
Query command.
ODBC DRIVERS
1-2-3 Release 4 can be configured to use drivers that meet the Microsoft
Open Database Connectivity (ODBC) specification. The dBASE DataLens driver
that comes with 1-2-3 Release 4 uses an ODBC engine.
Note: Most ODBC drivers have not been certified with 1-2-3. Lotus does not
provide technical support for these drivers.
If you are using the DataLens dBASE driver or any other ODBC driver with
1-2-3, start SHARE.EXE before you start Windows. To start SHARE.EXE before
every Windows session, add the following line to your AUTOEXEC.BAT file:
C:\DOS\SHARE
See your DOS documentation for information about SHARE.EXE.
You can configure 1-2-3 to use either all ODBC drivers or one specific
driver. To provide access to all ODBC sources, add the following line to
your LOTUS.BCF file:
DN="ODBC" DL="DLODBC" DD="All ODBC sources";
You can add support for a specific ODBC driver by including a DC parameter
to the ODBC record in LOTUS.BCF. If an entry with the string DL="DLODBC",
as shown above, also includes a string of the form DC="driver=xxx" then
1-2-3 will make available only those sources that use "xxx" as a driver.
For example:
DN="SQL Database via ODBC" DL="DLODBC" DC="driver=sql.dll" AC=UI,PW;
You can configure 1-2-3 to prompt for a user ID and password for a data
source by adding the following line to the LOTUS.BCF:
DB="source name" DN="ODBC" AC=UI,PW;
For more information on editing your LOTUS.BCF file, see DataLens Drivers
for 1-2-3.
When the 1-2-3 user picks the DataLens driver for dBASE files, the list of
available databases includes the following:
* The current directory
* All data sources in ODBC.INI that have "driver=qodbf.dll"
In addition, you can also add a new database name to ODBC.INI and type in
the new path.
Data source names for dBASE must be paths when using DLODBC.
When you use a macro to send updates to ODBC-dBASE IV tables, you must
follow the {SEND-SQL} command with a {COMMIT} command.
IBM DATABASE MANAGER
For Database Manager access to an OS/2 2.0 server, you need the Local Area
Network Support Program Version 1.3.
ENVIRONMENT VARIABLES
Unlike some other releases of 1-2-3, 1-2-3 Release 4 does not use the
"LOTUSBCF" environment variable, but reads only records listed in the
LOTUS.BCF file located in \LOTUSAPPS\DATALENS.
**6. VERSION MANAGER**
If you are using Version Manager with Lotus Notes Release 3, start SHARE.EXE
before you start Windows. To start SHARE.EXE before every Windows session,
add the following line to your AUTOEXEC.BAT file:
C:\DOS\SHARE
See your DOS documentation for information about SHARE.EXE.
When you use shared files, Lotus Notes may display certain messages in a
special untitled error window during your 1-2-3 session. Attempting to
close this window ends communication with the Notes server for the rest
of the 1-2-3 session.
If 1-2-3 displays the message "Error Initializing Lotus Notes" when you
try to open a shared file (.NS4), check the following:
* If the LotusMail section in your WIN.INI file specifies Notes, make sure
it includes the correct Notes program path. For example:
[LotusMail]
Application=Notes
Program=x:\notes\notes.exe
* If the LotusApplications section of your LOTUS.INI file specifies Notes,
make sure it includes the correct Notes program path. For example:
[LotusApplications]
Notes=x:\notes\notes.exe
* Make sure SHARE.EXE was started before you started Windows.
If you delete all versions from a range in a shared file (.NS4), you will
be unable to create any more versions in that range. Do not delete all
versions from a range unless you are sure you no longer want to share it.
**7. SOLVER**
Solver uses relationships among formula cells in 1-2-3 to arrive at its
answers. Since DDE links get their data from sources outside 1-2-3, you
should not use @DDELINK formulas in cells that you use as adjustable or
constraint cells for Solver.
**8. COMMAND-LINE PARAMETERS**
To specify command-line parameters for 1-2-3 Release 4
1. Highlight the 1-2-3 Release 4 icon.
2. Choose File Properties from the Windows Program Manager.
3. In the Command Line text box, append a command-line parameter to
123W.EXE. (For example, C:\123R4W\PROGRAMS\123W.EXE -s)
You can specify the following command-line parameters:
filename
Lets you specify a file to load whenever you start 1-2-3.
-s
Makes 1-2-3 Release 4 use the software floating point driver instead
of a math coprocessor. Use this parameter if you have a defective math
coprocessor in your computer or if your computer tells 1-2-3 you have a
math coprocessor when you do not. Under these circumstances, all your
formulas may evaluate to 0, ERR, or *** (asterisks).
-i [filename.ini]
Lets you specify an initialization file other than 123R4.INI. For example,
C:\123R4W\PROGRAMS\123W.EXE -iC:\123R4W\MYINI.INI specifies the
initialization file C:\123R4W\MYINI.INI.
Note: If you use 1-2-3 Release 4 with Lotus Notes Document Inset
Protocol (DIP), you must have 123R4.INI in your Windows directory.
**9. CORRECTIONS TO THE DOCUMENTATION**
USER'S GUIDE
Page 89: The second sentence of the Note should read: To delete a named
range that contains versions, you must first delete the versions.
Page 125: The last sentence in the second paragraph under "Changing
column width" should read: Use Style Column Width to change the column to
a specific width, reset to the default width, or set the width to fit the
largest entry in the current selection.
Page 126: The second bullet under step 3 of "To change columns to a
specified width" should read: "Fit widest entry" adjusts the columns to
the width of the widest entries in the current selection.
WHAT'S NEW
Pages 88: Add the following to the Transcript Commands section:
Record Relative Records range selections as offsets of the current cell.
Record Absolute Records range selections as cell addresses.
Appendix D: @USER is not supported by 1-2-3 Release 4. Use
@INFO("setup-user-name"} instead.
Appendix E: Add the macro command {SELECT-RANGE-RELATIVE}. Remove the
macro commands {PARSE-CREATE} and {PARSE-RESET}.
DATALENS DRIVERS FOR 1-2-3
Pages 5 and 6: Wherever the variable [range-name] appears, substitute
the variable [table-name].
MACROS HELP
{LINK-CREATE} topic: Remove the last sentence from the description of
the app-name argument.
**10. FONT USAGE**
FONT MAPPING
1-2-3 Release 4 can map requests for Adobe Type Manager (ATM) fonts to
TrueType fonts, or requests for TrueType fonts to ATM fonts.
Font mapping is controlled by the TT_MAP statement in the [TTMAPPING]
section of your 123R4.INI file. When you start 1-2-3 for the first time,
1-2-3 automatically sets TT_MAP according to your configuration.
Note: When you open a file created with 1-2-3 for DOS, Wysiwyg fonts are
mapped to Windows fonts using the settings in the [FONTMAPPING] section
of your 123R4.INI file.
FONT PERFORMANCE TIPS
Use ATM fonts, such as Arial MT, when rotating text blocks in 1-2-3.
For information about rotating text blocks, search on "Rotating drawn
objects" in Help.
Use TrueType fonts to increase printing speed with a Hewlett-Packard
LaserJet IV, because Arial and Times New Roman are internal fonts for
this printer.
INSTALLING AND REMOVING ATM
If you installed 1-2-3 on a network node, you can install ATM from the
server if your network administrator transferred ATM to the server. To
install ATM:
1. Open the Windows Program Manager.
2. Choose File Run.
3. Type x:\path\ATM\install in the Command Line text box.
x:\path is the driver letter and path for the 1-2-3 directory on your
server. For example, type t:\123r4w\atm\install to install ATM from a
1-2-3 directory named \123R4W on drive T:.
4. Choose OK.
If you run Windows from a network server, you will be able to install ATM
only if you have write access to the WINDOWS\SYSTEM directory while you are
installing. See your network administrator to get write access to this
directory.
After you install ATM, other Windows applications may look slightly
different onscreen because ATM substitutes its scalable fonts for certain
Windows bitmap fonts. The point size at which ATM makes this substitution
is controlled by the SynonymPSBegin= statement in ATM.INI.
SynonymPSBegin= is initially set to 9; this means ATM substitutes its
fonts for Windows fonts larger than 9 points. If you change this statement
to SynonymPSBegin=13, ATM substitutes its fonts for Windows fonts larger
than 13 points. Other Windows applications that use 10 and 12 point fonts
will continue to look the same as they did before you installed ATM.
If you experience difficulties with ATM soft fonts, you can remove ATM
from your hard disk and re-install it.
Before you remove ATM from your hard disk, do the following:
1. If you installed additional fonts, copy those fonts to a temporary
directory.
2. Remove all Windows soft fonts from your WIN.INI file. Soft fonts are
listed with the installed printers. In the example below, an * (asterisk)
marks each line to remove.
[PostScript,LPT2]
device=14
color=2
feed1=1
*softfonts=11
*softfont1=c:\psfonts\pfm\_a______.pfm,c:\psfonts\_a______.pfb
*softfont2=c:\psfonts\pfm\bdbc____.pfm,c:\psfonts\bdbc____.pfb
To remove ATM from your system, do the following:
1. End Microsoft Windows.
2. Change the following lines of your SYSTEM.INI file, which is located in
your Windows directory:
* Change system.drv=atmsys.drv to system.drv=system.drv
* Delete the line atm.system.drv=system.drv
Note: These lines may be different on some systems (for example, the
Hewlett-Packard Vectra); however, the result should be a single line
that reads system.drv=system.drv.
3. Delete the following files:
* Delete ATM16.DLL and ATM32.DLL from the \SYSTEM subdirectory of your
Windows directory.
* Delete ATM.INI and ATMCNTRL.EXE from your Windows directory.
* Delete any .PFM, .PFB, .SFP, and .SFL files from the directories in
which you installed fonts.
4. To re-install ATM, start Windows and insert the ATM disk in drive A:.
Open the Windows Program Manager. Choose File Run. Type a:install in
the Command Line text box and then Choose OK.
OFFICE 安装说明 1.将盘COPY到硬盘, 及相应子目录上. 2.如果已装入XENIX则执行P37加载打印驱动程序, 并在子目录下执行op37.bat文件. 3.如果未装入XENIX则执行p3070加载打印驱动程序, 并在子目录下执行op3070.bat文件. 4.执行OP.COM加载OFFICE程序 5.软件使用与前版本相同,使用607k clib24字库. 6.如有个别问题,请与浙江粮食局计划处 斯掌龙 或商业部信息中心 王耀,秦绪曾 联系.
WELCOME TO PARADOX 3.5
----------------------
This file contains important information that is not contained in the
documentation for Paradox 3.5. All information in this file supersedes
information in the Paradox 3.5 documentation.
TABLE OF CONTENTS
-----------------
1. Resolving Hardware and Software Compatibility Issues
2. Notes on Interactive Paradox
3. Notes on PAL
4. Starting and Running Paradox in Special Configurations
5. Notes on the Custom Configuration Program
6. Notes on the Personal Programmer
7. Files on the Disks
1. RESOLVING HARDWARE AND SOFTWARE COMPATIBILITY ISSUES
-------------------------------------------------------
Hardware/Software Compatibility:
Paradox is designed to follow memory management standards where they
exist, to make the best possible use of your computer, and to allow you
maximum flexibility to tune the program the way you want. When Paradox
loads, it tries to detect any EMS emulation, RAM disks, and caches you
have, and configures itself to run optimally in that environment. Some-
times you will want or need to modify the default configuration. You can
override Paradox's installation defaults with the Custom Configuration
Program (CCP) or with command-line options. See Chapter 14 of the
"Paradox User's Guide" for details.
Unfortunately, standards have been slow to evolve for memory
management. Paradox conforms to the major standards that do exist: the
VDISK standard for RAM disks, the VCPI standard for EMS emulation, and the
XMS standard for extended memory. If you use software that conforms to
some other standard, you may have to make adjustments to run Paradox.
Please check the list that follows for known compatibility problems.
Some specific compatibility problems are:
- If you're running your machine in fast or "turbo" mode, it may be
running faster than the hardware was designed to run. This may
cause it to drop instructions occasionally at its fastest speed.
While some of your software may run just fine in turbo mode,
Paradox sometimes makes heavier demands on the hardware than
other software packages. If you experience difficulty, try
running Paradox in slower or "safe" mode. (This is not to say
that all machines offering a choice of speeds are suspect; Paradox
will not have trouble on any machine's highest speed as long as
all the machine's components are designed to run at that speed.)
Machines that may experience this problem include 6Mhz IBM ATs
that have been sped up to 8Mhz or faster, the WYSEpc 286 in its
12.5Mhz mode, and the Rose Hill 286 at its faster speed.
- The Tall Tree JRAM EMS card is not supported by Paradox.
- A 286 machine with an old BIOS might not be able to run in
protected mode.
- A disk cache called VCache is known to be incompatible with
Paradox. Do not run VCache with Paradox.
- Some EMS emulators can run without allocating an EMS page frame.
This lets you use their many extra features, particularly the
ability to relocate drivers above 640K, even if you don't want to
use EMS. QEMM's FRAME=NONE option has this effect, as does
386Max's NOFRAME option. If you use your EMS emulator this way,
you must run Paradox in real mode (this is the mode it will run
in by default). Attempting to force Paradox into protected mode
in this situation might hang your machine.
- If you use a version of PC LAN that includes a cache and you locate
the cache in the network server's extended memory, you cannot run
Paradox on the server - there isn't enough memory below 640K left
for Paradox to run in real mode, and the PC LAN cache does not
allow any other program to use extended memory.
- The AST REX.SYS driver, which converts EEMS expanded memory back to
extended memory, is not compatible with Paradox 3.5. To obtain
extended memory with an EEMS board, don't let the REMM.SYS expanded
memory driver use some or all of the memory on the board. (In some
cases, you will have to set switches on the board to accomplish
this.)
- Under DOS 2.x, Paradox 3.5 runs only in real mode, not in protected
mode.
Testing Your CPU and EMS:
If you experience intermittent failures, they may be due to a
processor that's running too fast or memory that is defective or runs too
slowly. Paradox 3.5 includes two small programs to test for problems of
this sort. Although they cannot detect all machine problems, they do test
machine components that Paradox 3.5 stresses; as a result, they
often help pinpoint problem areas. The programs are CPUTEST.EXE and
EMSTEST.COM. Both are installed in your Paradox 3.5 program directory
automatically. If you have any reason to suspect that your hardware may
not be able to keep up with Paradox, you should run both programs (run only
CPUTEST if you don't have expanded memory). Even if your computer is
running flawlessly, feel free to try them out. CPUTEST runs just a few
seconds, and EMSTEST just a few minutes.
To run CPUTEST, just move to your Paradox directory (usually \PDOX35)
and type
CPUTEST
You should see the message "This CPU Tests OK." A message like "2
instructions skipped" probably indicates that your computer's processor is
running too fast.
To run EMSTEST, move to your Paradox directory, type
EMSTEST
and press keys as instructed. The test will verify that your Expanded
Memory Specification (EMS) hardware and software are working correctly.
You should see descriptions of a number of tests, each followed by the
status "OK." Any other status message indicates a probable EMS failure.
2. NOTES ON INTERACTIVE PARADOX
-------------------------------
Incremental Menu Selection:
In Paradox 3.0, you can type a letter when choosing from a menu to
narrow your selection down to choices starting with that letter, then make
your final selection using the arrow keys. In Paradox 3.5, you can type a
second letter to narrow your choices down further, then a third letter, and
so on. As you type each letter, it will be colored differently in the
current menu item. Whenever there is only one choice that matches the
letters typed, it will be selected immediately, just as is done in Paradox
3.0 when the first letter of a choice is unique. You can still use the
arrow keys to select, as before; as soon as you do, the incremental
selection in process is abandoned, so you must start from the beginning of
the desired choice to select it using incremental type in.
Incremental menu selection works wherever you select from a menu: in
Paradox's own menus; in application menus created by SHOWMENU; in lists of
tables, scripts, forms, and other objects; and in lists produced by
SHOWARRAY, SHOWTABLES, and SHOWFILES. In interactive use, the new
incremental selection capability is completely compatible with existing
menu interaction. Scripts that use InstantRecord, SHOWMENU, or braced menu
selections will also be compatible with Paradox 3.5. Scripts that use
KEYPRESS and TYPE IN to select from menus might behave differently:
keystrokes that did not cause a menu item to be selected now can, depending
on the contents of the menu list.
Tools|Copy|JustFamily:
Previous versions of Tools|Copy|JustFamily could copy corrupt or
out-of-date family members from the source to the target table. Although
this was clearly the wrong action for corrupt family members, it did allow
you to "re-attach" a correct but out-of-date object to its table.
Copy|JustFamily now checks that each object is a valid member of the source
table's family before copying it. As a result, you will no longer be able
to use it to attach out-of-date family members to their tables.
Tools|Info|Lock:
The LIST table that Tools|Info|Lock produces now gives more infor-
mation when there is a form-lock on a multi-table form. When a table is
form-locked, Paradox displays "Form Lock" in the lock type field, followed
by the type of lock that pre-Paradox 3.0 users will see. (These earlier
versions of Paradox cannot use a form-locked table because they don't
support multi-table forms.) For example, if you are coediting a multi-
table form, the type field will show "Form Lock-WL", where WL stands for
Write Lock. The other abbreviations are PFL (Prevent Full Lock) and PWL
(Prevent Write Lock). Paradox no longer adds a second record saying "Write
Lock" in the LIST table.
Undo:
In a multi-table form, Undo works differently than in Paradox 3.0 in
one minor case: After a form toggle, it now takes two Undo operations to
back up as far as one Undo did previously.
Number Rounding Issues:
Paradox 3.5 uses the Turbo C math library, which provides greater
precision than the one used in Paradox 3.0. This will cause some numeric
and dollar values that were entered using an earlier version of Paradox to
be rounded differently in Paradox 3.5. Data entered in Paradox 3.5 will
not exhibit this problem. (Because of the way Paradox represents numbers,
there will always be occasional round-off errors when manipulating numbers
with many decimal digits of precision. Unfortunately, other methods of
representing numbers also have disadvantages.)
Because data entered in Paradox 3.5 works fine, the solution is to
export the existing Paradox file to an ASCII file, then import the data
back into Paradox 3.5. You can put your data back into the same table it
started in, leaving the table's family unaltered. The steps to follow are:
1. Make a backup of the table to be processed (if you don't have one)
in case any problems arise.
2. Export the table to ASCII format. If your table is named CUSTOMER
and you want to call the temporary ASCII file TEMP_30, use:
Tools|ExportImport|Export|Ascii|Delimited
and enter CUSTOMER as the table name and TEMP_30 as the exported
file's name.
3. Empty the CUSTOMER table, using Tools|More|Empty.
4. Import your data back into CUSTOMER, using the AppendDelimited
command (not the Delimited command):
Tools|ExportImport|Import|Ascii|AppendDelimited
Type in TEMP_30 when you are prompted for a file name and CUSTOMER
when you are prompted for a table name.
Norwegian/Danish Sort Order:
Minor corrections have been made to the NORDAN.SOR sort file. The
table in Chapter 14 of the "Paradox User's Guide" labeled "Swedish/Finnish
and Norwegian/Danish Sort Order" is accurate only for the SWEDFIN.SOR sort
order. The order of alphabetic characters according to NORDAN.SOR is shown
below. (Note that ASCII characters 155 and 157 appear as slashed "O"s if
you have the Norwegian/Danish video ROM.)
ASCII ASCII ASCII ASCII
Char Code Char Code Char Code Char Code
----------- ----------- ----------- -----------
a 97 i 105 Q 81 ä 132
á 160 ï 139 r 114 Æ 146
à 133 í 161 R 82 Ä 142
â 131 ì 141 s 115 ¢ 155
A 65 î 140 S 83 ö 148
b 98 I 73 t 116 ¥ 157
B 66 j 106 T 84 Ö 153
c 99 J 74 u 117 å 134
ç 135 k 107 ú 163 Å 143
C 67 K 75 ù 151 α 224
Ç 128 l 108 û 150 ß 225
d 100 L 76 U 85 Γ 226
D 68 m 109 v 118 π 227
e 101 M 77 V 86 Σ 228
ë 137 n 110 w 119 σ 229
é 130 ñ 164 W 87 µ 230
è 138 N 78 x 120 τ 231
ê 136 Ñ 165 X 88 Φ 232
E 69 o 111 y 121 Θ 233
É 144 ó 162 ü 129 Ω 234
f 102 ò 149 ÿ 152 δ 235
F 70 ô 147 Y 89 ∞ 236
g 103 O 79 Ü 154 φ 237
G 71 p 112 z 122 ε 238
h 104 P 80 Z 90 ∩ 239
H 72 q 113 æ 145 ≡ 240
Compatibility with Paradox 3.0:
Paradox 3.5 is compatible with previous versions of Paradox. However,
if you will be running existing applications under Paradox 3.5 or want your
Paradox 3.5 development to coexist with previous versions, there are a few
points you should consider:
- Although tables from previous versions of Paradox are completely
compatible with Paradox 3.5, tables created in Paradox 3.5 exhibit
better performance in almost all cases. For best performance in
Paradox 3.5, you should restructure existing tables in Paradox 3.5.
To do this, choose Modify|Restructure, then press Do-It (without
making any changes to the table's structure). However, if some
users will continue to use these tables with earlier versions of
Paradox, be aware that these restructured tables will require more
memory when placed on the workspace - up to 2K more for each table
and for each index on the table. (Paradox 3.5 doesn't use more
memory per image on the workspace for tables built with the
new structure; only earlier versions of Paradox do.)
- As explained in the "Upgrade Guide," Paradox 3.5 uses a new format
for procedure library files. Paradox 3.5 can read existing
libraries, but previous versions cannot read Paradox 3.5 libraries.
In addition, although Paradox 3.5 can read procedures from a
Paradox 3.0 library, you cannot write such procedures directly from
memory into a Paradox 3.5 library. You must play a script
containing the procedures in source code form, then use WRITELIB
to write them to the new library.
- You might notice that previous Paradox versions can often use forms
and reports that contain functions and variables in calculated
fields. However, there are some functions (DOW, for example) that
Paradox versions before 3.5 will not accept in calculated fields.
In addition, these Paradox versions cannot modify Paradox 3.5 forms
and reports that use functions or variables. If you attempt either
operation, you will see a message like "Invalid calculation..." or
"Invalid fields removed from form...". Select Cancel from the menu
to back out of Forms|Change or Report|Change mode, then use Paradox
3.5 to modify the form or report; otherwise, you will lose all the
calculated expressions that the earlier version of Paradox doesn't
understand.
- A few messages have been changed. Although most of the changes
just correct spelling and punctuation errors, applications that
test for the exact text of a message will not recognize the new
messages. Applications should avoid testing messages whenever
possible.
- Minor changes have been made to the Tools|ExportImport menus to
include Quattro PRO import and export. There are other menu
changes, but they do not introduce compatibility issues; for
example, Paradox 3.5 accepts "QuerySpeedup" and "QuerySpeed"
interchangeably.
Printing Graphs:
Paradox (by default) does not do a page-eject after printing a graph.
This allows you to place more than one graph on a page. On a PostScript
printer or other laser printer, it may seem that your graph was not sent to
the printer properly, since there is often no sign of activity until a page
is ejected. To override the default temporarily, enter the Graph subsystem
(using Image|Graph|Modify), then choose Overall|PrinterLayout and set
"Break Page" to "Y". To override it permanently, play Custom and go
through the same steps.
3. NOTES ON PAL
---------------
RUN ([Ctrl][O]) and RUN BIG ([Alt][O]):
Paradox 3.5 uses Borland's VROOMM memory management, which loads
modules of program code into memory dynamically as they are needed. As a
result, the amount of memory available when you execute PAL's RUN or RUN
BIG command (or their keyboard equivalents, [Ctrl][O] and [Alt][O]) will
vary more in the course of a session than it did in Paradox 3.0. Exactly
how much memory is available depends on many factors, but neither RUN nor
RUN BIG will always give you as much memory as Paradox 3.0 did.
In both real and protected mode, RUN always gives 140K or more; if it
can't free up that much, Paradox automatically converts the RUN to a RUN
BIG. In real mode, RUN BIG can usually free up all but about 25K of the
memory available when you started Paradox. In protected mode, it can
usually free up all but about 75K of the memory available at Paradox
startup.
For most users, RUN and RUN BIG will work just as before. If you are
using RUN BIG to run a memory-intensive program from within Paradox, check
that the operation will still work in your configuration.
PRINT FILE:
PAL's PRINT FILE command is much faster now because Paradox keeps the
file open as long as possible and buffers the output. If you previously
optimized PRINT FILE by concatenating output into long strings, you'll find
that this is no longer necessary. Paradox knows to write the buffer and
close the file almost any time it could be necessary: when you exit
Paradox, execute a RUN command, print to another file, use the FILESIZE
function to test the size of the file just written, play the script just
written, etc. If you want to close the file before Paradox does so
automatically - if you use it as a semaphore to other network users, for
example - use something like
DUMMY = ISFILE("filename.txt")
(where "filename.txt" is the name of your file) to force it to be closed.
RECORDSTATUS Function:
In several cases, RECORDSTATUS may return a result that is not what
you expect. It's helpful to be aware of these cases and know why
RECORDSTATUS reports what it does:
- Using RESYNCKEY to show Many-one and Many-many details matching the
current record has the effect of posting your changes (though the
record remains locked.) As a result, RECORDSTATUS ("Modified")
returns False.
- RECORDSTATUS ("KeyViol") returns False if you've inserted a
duplicate record but haven't yet tried to post it, since Paradox
doesn't detect the key violation until then.
- RECORDSTATUS ("KeyViol") also returns false if you enter a
duplicate key in a multi-table form in CoEdit and try to post it.
This looks like a key violation, but really isn't from Paradox's
point of view: you don't have the existing record that the new
one conflicts with locked, you can't use [Alt][K] to toggle
between the two, and [Alt][L] won't force posting of the new record.
Error Procedures and Error Codes:
The complete list of error codes and their causes is given below. If
you have a Paradox 3.5 manual set, you'll also find this table in your "PAL
User's Guide." There are two other small points about error procedures and
error codes to note:
- If you attempt to modify a table that is write-protected, Paradox
sets errorcode to 22, not to 35 as in previous versions.
- When an error procedure is called because a low memory warning is
issued, Paradox always retries the current statement on return from
the error procedure, even if the return value from the procedure
specifies that it should be skipped. This makes it easier to run
existing applications under Paradox 3.5.
PARADOX ERROR CODES
Code Meaning
---- -------------------------------------
0 No error (for example, record was not
changed or key was found)
File or directory errors
1 Drive not ready
2 Directory not found
3* Table in use by another user
4* Full lock placed on table by another user
5 File not found
6 File corrupted
7 Index file corrupted
8 Object version mismatch
9* Record locked by another user
10 Directory in use by another user
11* Directory is private directory of another user
12 No access to directory at operating system level
13 Index inconsistent with sort order
14 Multiuser access denied
15 PARADOX.NET file conflict
General script errors
20 Invalid context for operation
21 Insufficient password rights
22 Table is write-protected
23 Invalid field value
24 Obsolete procedure library
25 Insufficient image rights
26** Invalid PAL context
27 Operation not completed
28 Too many nested closed procedures
29 Table is remote (on an SQL server)
Argument errors
30 Data type mismatch
31 Argument out of range
32 Wrong number of arguments
33 Invalid argument
34 Variable or procedure not assigned
35 Invalid menu command
Resource errors
40** Not enough memory to complete operation
41 Not enough disk space to complete operation
42** Not enough stack space to complete operation
43 Printer not ready
44 Low memory warning
Record-oriented operation errors
50** Record was deleted by another user
51** Record was changed by another user
52** Record was inserted by another user
53** Record with that key already exists
54** Record or table was not locked
55** Record is already locked by you
56** Lookup key not found
Multi-table operation errors
60 Referential integrity check
61 Invalid multi-table form
62** Form locked
63 Link locked
* For this code, ERRORUSER() returns the name of the user who locked
the resource
** This code does not invoke a designated error procedure
4. STARTING AND RUNNING PARADOX IN SPECIAL CONFIGURATIONS
---------------------------------------------------------
Running Paradox 3.5 under Windows 3.0:
You can run Paradox 3.5 and the Paradox Personal Programmer (PProg)
under Windows 3.0. If you plan to do this, you need to do four things, in
this order:
1. Copy the .PIF and .GRP files from the \WINDOWS subdirectory on your
Paradox Installation\Sample Tables disk into your Windows directory
(usually C:\WINDOWS). The PARADOX.PIF and PPROG.PIF files allow
Paradox and the Personal Programmer to run optimally under Windows.
If you choose to modify them or define your own .PIF files, you
should always include the -win command-line option. PARADOX.GRP
gives Windows a program manager icon for Paradox 3.5 that contains
icons for Paradox 3.5 and the Paradox Personal Programmer.
2. Make sure your Paradox system directory is in your DOS PATH
statement, so Windows can find the files. For information on the
PATH statement, see your DOS manual.
3. Run the DOS SHARE program. Type SHARE at any DOS prompt to do
this, or add a SHARE statement to your AUTOEXEC.BAT file. SHARE
must be resident to run Paradox 3.5 under Windows.
4. Set up a program group in Windows to put a Paradox icon on the
Windows Program Manager screen. To create this program group,
a. Choose File from the Windows Program Manager.
b. Choose New, then choose Program Group.
c. Fill in a description of the group to appear under the icon (for
example, PARADOX 3.5).
d. Fill in the full path name of the group file (for example,
C:\WINDOWS\PARADOX.GRP).
e. Click OK. Two new icons appear in your Paradox 3.5 window: one
for Paradox 3.5 and one for the Paradox Personal Programmer.
Windows is now set up to run either Paradox 3.5 or the Personal Programmer
whenever you want. Double-click on the appropriate icon to invoke the
program.
Paradox 3.5 runs in a bordered window when Windows is running in 386
Enhanced Mode. (You enter this mode by starting Windows with the command
WIN /3). If you are running Windows on an 8088 or 80286 computer, or on a
386 in real or standard mode, Paradox and the Personal Programmer run in
full-screen mode and appear as they do when run outside Windows. In this
full-screen mode, press [ALT][ESC] to switch from Paradox to another
Windows application. The Paradox (or PProg) icon appears at the lower
left corner of the Program Manager window; double-click on it to return
to Paradox (or PProg).
After you press a mouse button in a window, its title bar says Select.
This means that Windows has taken over control of the keyboard and mouse so
you can cut or paste, operations Paradox does not support. Press [ESC]
to return control to Paradox.
To close files properly and prevent data loss, always exit Paradox
using the keyboard (press [F10] and choose Exit|Yes), not the mouse. If you
try to exit Windows with Paradox still running, a warning appears and you
are given a chance to exit Paradox properly; Windows will not let you exit
without closing applications.
Running Paradox 3.5 under DESQview:
You can run Paradox 3.5 under DESQview in either real or protected mode
on a 286 or higher machine. Here's how to configure DESQview to run
Paradox 3.5:
1. Install Paradox 3.5 according to the installation instructions in
the "Introduction to Paradox" manual or the "Upgrade Guide."
2. From the DESQview Main menu, choose Open Window.
3. If you are upgrading from Paradox 3.0 to 3.5, select Paradox3 from
the file list, then choose Change a Program. If you are installing
Paradox for the first time, you'll first have to use Add a Program
to add the program name to this list.
4. Press [F1] to see the Standard Options screen. Type the program
name, any batch file name you use to invoke it, the full path
name (including file name), and any command-line parameters you
use. Set Memory Size (in K) to 440. Set the Standard Options
switches as follows:
Writes Text To Screen [N]*
Displays Graphics Info [Y]
Virtualize Text/Graphics [N]**
Uses Serial Ports [N]
Requires Floppy [N]
5. Press [F1] again for the Advanced Options screen. Set the following
parameters:
System memory 0
Max Program Size (in K) 640
Script Buffer Size 1000
Max Expanded Memory 1024***
Set the switches as follows:
Close On Exit [ ](leave blank)
Allow Close Window Command [N]
Uses Math Coprocessor [Y]
Share CPU When Foreground [Y]
Can Be Swapped Out [ ](leave blank)
Use Its Own Colors [Y]
Run In Background [ ](leave blank)
Keyboard Conflict [0]
Share EGA When Foreground [Y]
Protection Level [0]
* On a 286 machine, set this switch to Yes.
** On a 286 machine or on a 386 or higher machine running in
protected mode, set this switch to Yes.
*** Max Expanded Memory can be set higher.
6. Exit Change a Program or Add a Program and start Paradox in the
usual way under DESQview.
Use the same procedure to configure DESQview to run the Paradox Personal
Programmer.
If you plan to run multiple Paradox sessions under DESQview, you
should make the Paradox program files read-only. You'll also need one
Paradox serial number for each session.
Multiple Paradox Sessions:
When you run Paradox on a network, the network operating system ensures
that you can share program and data files with other users whenever sharing
is appropriate. On a standalone machine, DOS's SHARE command and Paradox's
-share command-line option have the same effect. Without them, DOS assumes
that no file sharing is required. Applications that might share files on a
standalone computer include
- Windows
- DESQview
- Add-in programs for Paradox, such as Kallista's KMemo
- In-house applications that use the RUN command to execute Paradox
Engine programs. These programs in turn might perform special
processing on the applications' tables.
If you will be sharing files on a standalone machine, you should use
the -share command-line option. The -share option now requires that DOS
SHARE be loaded (and this in turn means that you will need to use DOS 3.0 or
higher). Using -share causes Paradox to write a PARADOX.NET file in the
root directory on your hard disk and to put an entry in it for each session
or program that runs Paradox. This guarantees that file sharing works
correctly.
Software EMS Drivers:
This note is an addition to the notes about XMS-compliant EMS drivers
in the "Upgrade Guide" and the "Paradox User's Guide."
If your system has extended memory that an XMS-compliant EMS driver is
converting to expanded memory, Paradox handles this memory at startup in
the following ways:
In real mode with neither the -extk or -emk command-line options set,
Paradox asks the driver for all the available extended memory, then uses
that memory as a swap device. To keep Paradox from using all the expanded
memory in this way, use the -extk command-line option. For example, if you
normally have 4MB of extended memory being converted to expanded memory,
and you want Paradox to take only 1MB of that memory, type
paradox -real -extk 1024
(You usually need to include the -real option, since Paradox attempts to
run in protected mode by default.) The rest of the memory remains as
expanded memory, which Paradox also uses as a swap device. To save some of
that expanded memory for another (concurrent) program, you must also set an
-emk option. For instance, if you have 4MB, and you want to have Paradox
use 1MB as extended, 1MB as expanded, and leave 2MB of expanded for another
program, type
paradox -extk 1024 -emk 1024
When you start Paradox in protected mode, the options are evaluated
differently. In protected mode, Paradox takes all the XMS-compliant EMS
memory as extended memory before it evaluates the -ext or -emk options. If
the EMS driver is set up in your CONFIG.SYS file so that only some of the
extended memory is available to the EMS driver, Paradox uses only that
memory configured as expanded, but changes it to extended. Paradox does
not use the non-EMS configured extended memory at all. For instance, if you
have 1MB left as extended and 3MB configured as expanded, Paradox takes 3MB
and uses it as extended.
Novell NetWare 386:
NetWare 386 allows you to define a virtual root. This means that it
allows you to map a drive letter to a subdirectory in such a way that the
user of that mapping can only access the mapped subdirectory and its child
directories. (Ordinarily, NetWare mappings are just shortcuts; you can
still use the DOS CHDIR command to access any directory on the volume.)
Virtual roots are created with the 'MAP ROOT' command.
Since virtual roots allow different users to access different
subdirectories of a volume with the same network drive path, Paradox might
not enforce locking correctly if two users specify paths to the PARADOX.NET
file which do not indicate the same subdirectory on the server. For
example, if one user maps S: using the command
MAP ROOT S: server\sys:pdoxdata
and another user maps S: using
MAP S: server\sys:pdoxdata
then the \PDOXDATA directory will be S:\ for the first user and
S:\pdoxdata for the second user. Similarly, if one user maps S: using
MAP ROOT S: server\sys:pdoxdata
and another maps S: using
MAP ROOT S: server\sys:pdox
then S:\ for the first user will be different than S:\ for the second user.
Both of these situations can lead to severe data corruption.
Be sure to observe the warning in the Network Administrator's Guide
that "All Paradox users must have the directory containing the PARADOX.NET
file mapped to the same logical drive and directory." Suppose your
PARADOX.NET file is in server\sys:pdoxdata and you use your system login
script to map S: to server\sys:pdoxdata as a virtual root. Then you should
specify when you install Paradox that PARADOX.NET is in S:\. Once
you've done this, it is essential that no one override the mapping of S:.
In this way, all active users share the PARADOX.NET file, each recognizes
the others as active users, and all respect the others' lock files.
5. NOTES ON THE CUSTOM CONFIGURATION PROGRAM
--------------------------------------------
Configuration Issues:
When discussing Custom's new handling of color settings, the "Upgrade
Guide" says that when you're in Video|Colors, you will recognize your
existing color settings by their names. Ordinarily, this won't be true;
when you run Custom with Paradox 3.5, you will start with the default
configuration file. Even users of earlier Paradox versions who have
chosen to override only a few of Paradox's defaults are better off
redefining their configurations from scratch. But if your existing
configuration file is highly customized - if you've modified the default
report or graph specification, or selected several graph printers, or added
report setup strings or color settings - you may want to retain your
existing configuration. To do so, copy your PARADOX3.CFG file (or another
.CFG file from a previous version of Paradox) to PARADOX.CFG and move it to
your Paradox 3.5 directory. (You may want to save a copy of the current
PARADOX.CFG first.) You can now use Paradox 3.5's Custom program to
further customize your configuration.
B&W Monitors:
On monochrome and B&W monitors, Paradox uses only the built-in color
setting. (A B&W monitor is a monochrome monitor attached to a color video
card.) If you want to modify the color setting on a B&W monitor, you must
set your monitor type to "Color" (using the Video|Monitor command);
otherwise, Paradox ignores the changes you make to the color setting. The
effect, of course, will be to change the shades of gray or orange that your
monitor uses to show different elements of the Paradox display.
Graph Printers:
The list of graph printers you can choose from in Custom's
Graphs|Printers command has been updated and expanded, and a few older
printers have been removed from the list. If you want to use a printer
that was available in Paradox 3.0 but is not available in Paradox 3.5,
here's how:
- If you haven't already done so, run Paradox 3.0 and Paradox 3.0's
version of Custom to select the printer.
- Rename your PARADOX3.CFG file to PARADOX.CFG and move it to your
Paradox 3.5 directory. (You may want to save a copy of the current
PARADOX.CFG first.)
- Run Paradox 3.5 as usual. The printer defined in Paradox 3.0 will
be available.
Directories and Paths:
Previous versions of Paradox installed Custom in the program directory
by default, but did not require that it be there. With Paradox 3.5, you
must store Custom in the system directory or in a directory on your path in
order to use the Tune|ProtectedMode|MachineInfo and Configure options.
This ensures that Paradox can find the machine configuration information
that Custom writes out. If the Paradox system directory on your
network is normally read-only, you will need to log on as the network
administrator to write to it. For more information, see the "Upgrade
Guide."
The MachineInfo Report:
Custom's MachineInfo report displays basic information about your
machine configuration. Because computers vary widely, the report is
sometimes incomplete or slightly inaccurate. For example, not every BIOS
contains an ID at the "standard" address, but MachineInfo can't determine
what's a valid ID string and what isn't. Don't be alarmed if you see random
characters, or even a message like "fatal error" in the "BIOS ID String"
field. It's just extraneous text that MachineInfo mistook for the BIOS ID.
6. NOTES ON THE PERSONAL PROGRAMMER
-----------------------------------
There have been some minor changes to the Personal Programmer. Other
than the changes noted below, all parts of the program operate just as
they did in Paradox 3.0.
1. Paradox 3.5 uses a slightly modified way of reading
and writing libraries. Although Paradox 3.5 will read the
old libraries in exactly the same way as it did before,
the Personal Programmer can not directly modify libraries
in the old format. If you are modifying an application
that was originally created in 3.0, you will see a new
menu the first time you modify the application in 3.5. It
will appear immediately after you enter the name of the
application, and will offer you the option of updating
your libraries to 3.5 format.
If you choose Cancel, you will return to the Personal
Programmer Main menu. If you choose Update, the Personal
Programmer will rebuild your libraries in the new 3.5
format. Be aware that if you update the libraries, the
application will not be usable in Paradox 3.0. If you need
to modify an application that will be used with both 3.5
and 3.0, you should modify the application using only
Personal Programmer 3.0.
2. The Personal Programmer was not designed to be used on a
network and will not generate a multiuser application. In
Paradox 3.0, the large amount of memory needed to create
an application made it very difficult to execute the
Personal Programmer with the network software loaded.
Now that the Personal Programmer can access Extended RAM,
it would have been possible to run while the network
drivers are loaded. However, running the Personal
Programmer on a network drive with other users working
interactively could result in the failure of the program
and a loss of work. To prevent this loss of data, the
Personal Programmer has been modified to prevent the use
of a network drive.
3. The Personal Programmer allows you to set validation checks on
fields, requiring that they be filled with valid data.
There is one case where a combination of validity checks
will cause a problem. If you use the "TableLookup/HelpAndFill"
and the "RequiredField" options together, users may get
"stuck" in the field. In this case, pressing F1 to bring
up the Lookup will result in the message "A value must be
provided in this field." The user doesn't know what a
valid value is, and can't check to find out. This
combination should be avoided.
7. FILES ON THE DISKS
---------------------
This is the configuration for 5.25" disks. Each 3.5" disk except
Personal Programmer Disk 3 contains the directories and files from two
5.25" disks, as indicated by its disk label.
DISK 1: INSTALLATION/SAMPLE TABLES DISK
----------------------------------------
INSTALL EXE - Paradox installation program
README COM - Program to display README file
INSTALL CFG - Installation parameters
UNZIP EXE - Program to "unzip" compressed files
ASCII SOR - ASCII sort order
INTL SOR - International sort order
NORDAN SOR - Norwegian/Danish sort order
SWEDFIN SOR - Swedish/Finnish sort order
SYS ZIP - Zip file containing:
NUPDATE EXE - Program to update serial numbers, net type
PARADOXK EXE - Protected mode driver program
PARADOX CFG - Default Paradox configuration settings
PARADOX SOM - Paradox program file
In \UTIL:
UTIL ZIP - Zip file containing:
FLIMPORT EXE - Fixed-length Import utility program
FLIMPORT DOC - Documentation for Fixed-length Import program
VOUCH EXE - Checksum utility program
In \SAMPAPP:
SAMPAPP ZIP - Zip file containing sample application:
BOARD SC - Script to display Price table
DOFEED SC - Script to generate stock Price changes
FEED SC - Script to call procedures in DOFEED.SC
GRAPHS SC - Script to display graphs
HOLDINGS SC - Script to display holdings
MKLIB SC - Script to build procedure library
PORTFOL SC - Script to display portfolios
STOCKS SC - Main menu script
TICKER SC - Script to display "ticker tape"
HOLDING DB - Holdings table
HOLDING PX - Holdings table - primary index
PRICE DB - Stock Price table
PRICE PX - Stock Price table - primary index
PRICE SET - Stock Price table - settings file
GRAPH1 G - Sample application Bar & Marker graph spec
GRAPH2 G - Sample application 3-D Bar graph spec
GRAPH3 G - Stacked Bar graph spec
GRAPH4 G - Sample application Pie chart spec
In \TABLES:
TABLES ZIP - Zip file containing sample files:
DEBUGTST SC - Sample PAL code (with intentional errors)
PIES SC - Recorded script to create sample graphs
RECAP SC - Script to do work done manually during tutorial
BOOKORD DB - Sample Book orders table
BOOKORD F1 - Sample Book orders table - form 1
BOOKORD PX - Sample Book orders table - primary index
CUSTOMER DB - Sample Customer table
CUSTOMER F1 - Sample Customer table - form 1
CUSTOMER F2 - Sample Customer table - form 2
CUSTOMER F3 - Sample Customer table - form 3
CUSTOMER PX - Sample Customer table - primary index
CUSTOMER R1 - Sample Customer table - report 1
CUSTOMER R2 - Sample Customer table - report 2
CUSTOMER SET - Sample Customer table - image settings
DISTRICT WQ1 - Sample Quattro PRO worksheet
EMPLOYEE DB - Sample Employee table
EMPLOYEE F1 - Sample Employee table - form 1
EMPLOYEE PX - Sample Employee table - primary index
EMPLOYEE SET - Sample Employee table - image settings
HOMEGRP DB - Sample Home group table
MAIL DB - Sample Mail table
MAIL PX - Sample Mail table - primary index
MAIL R1 - Sample Mail table - report 1
MASTERBK DB - Sample Master book table
NEWRECS DB - Sample New records table
PRODUCTS DB - Sample Products table
PRODUCTS SET - Sample Products table - image settings
PROMO DB - Sample Promotion table
PROMO PX - Sample Promotion table - primary index
REPPERF DB - Sample Repperf table
REPPERF PX - Sample Repperf table - primary index
SALES DB - Sample Sales table
SALES SET - Sample Sales table - image settings
SUBGROUP DB - Sample Subgroup table
VOLS DB - Sample Volumes table
VOLS PX - Sample Volumes table - primary index
XCHANGE DB - Sample Xchange table
In \WINDOWS:
PARADOX PIF - Windows 3.0 PIF file for Paradox
PPROG PIF - Windows 3.0 PIF file for PProg
PDOXRUN PIF - Windows 3.0 PIF file for Runtime
PARADOX GRP - Windows 3.0 group file for Paradox
README - This file
DISK 2: SYSTEM DISK 1
----------------------
in \SYSTEM1:
PDOX1 ZI1 - First part of main Paradox executable file
DISK 3: SYSTEM DISK 2
----------------------
in \SYSTEM2:
PDOX1 ZI2 - Second part of main Paradox executable file
PDOX2 ZI1 - First part of zip file for other Paradox files
DISK 4: SYSTEM DISK 3
----------------------
in \SYSTEM3:
PDOX2 ZI2 - Second part of zip file for other Paradox files
DISK 5: CUSTOM CONFIGURATION DISK
----------------------------------
In \CUSTOM:
CUSTOM ZIP - Zip file containing:
CUSTOM SC - Custom Configuration - main script
COLORS LIB - Custom Configuration - color procedures library
CUSTOM LIB - Custom Configuration - main procedure library
CUSTOM OV1 - Custom Configuration - Tune menu command
DISK 6: DATA ENTRY TOOLKIT DISK
--------------------------------
In \TOOLKIT:
TOOLKIT ZIP - Zip file containing Data Entry Toolkit:
BORROW0 SC - Borrow script for CUSTDPA.SC
BORROW1 SC - Borrow script for MINIDPA.SC
BORROW2 SC - Borrow script for INVDPA.SC
BORROW3 SC - Borrow script for ORDRDPA.SC
CUSTDEMO SC - Custom procedures for Cust table, DoWait demo
CUSTDPA SC - DoWait Procedure Assignment set for Cust
DEMO SC - Starts the DoWait demonstration
DOW8DEMO SC - Builds DOW8DEMO.LIB for DoWait demo
EDITMENU SC - Source code for EditMenu procedure
ENFORME SC - Main Enforme form editor script
FORMBRDR SC - Enforme border drawing routines
FORMGOTO SC - Enforme workspace positioning routines
FORMHELP SC - Enforme help screen
FORMHOPS SC - Enforme workspace movement routines
FORMMAIN SC - Enforme main getkey procedure
FORMMAKE SC - Script to create Enforme procedure library
FORMSLCT SC - Enforme form selection routines
GETFILE SC - Source code for GetFile procedure
GETPASS SC - Source code for GetPassword procedure
HELPDEMO SC - Inactivity proc, help for DoWait demonstration
INVDEMO SC - Custom procedures for Invoice, DoWait demo
INVDPA SC - DoWait Procedure Assignment set for Invoice
KERNEL SC - Source code for DoWait procedures
KEYCODES SC - Source code for SetKeycodes procedure
LOOKSLCT SC - Source code for LookupSelect procedure
LOOKWAIT SC - Source code for LookupWait procedure
MINIDEMO SC - Source code for sample SetUpDoWait session
MINIDPA SC - DoWait Procedure Assignment set for Cust
ORDRDEMO SC - Custom procedures for Orders table, DoWait demo
ORDRDPA SC - DoWait Procedure Assignment set for Orders
POPUP SC - Source code for Popup procedures
POPUP2 SC - Source code for Popup2 procedures
RECURSW8 SC - Source code for RecurseWait procedure
RELEASW8 SC - Source code for ReleaseWait procedure
RFRSHCNV SC - Source code for RefreshCanvas procedure
TKDEBUG SC - Source code for TKDebug procedure
TKMENU SC - TKMenu main script
TKUPDATE SC - Script to update Paradox 2.0 spec files
TKUPDATE LIB - TKUpdate procedure library
TOOLKIT2 LIB - TKMenu procedure library
CARRIERS DB - DoWait demo Carrier service table
CARRIERS F - DoWait demo Carrier service table - form 1
CUST DB - DoWait demo Customer table
CUST F - DoWait demo Customer table - form F
CUST F1 - DoWait demo Customer table - form 1
CUST PX - DoWait demo Customer table - primary index
CUST VAL - DoWait demo Customer table - validity checks
INVOICE DB - DoWait demo Invoice table
INVOICE F - DoWait demo Invoice table - form F
INVOICE PX - DoWait demo Invoice table - primary index
INVOICE VAL - DoWait demo Invoice table - validity checks
ORDERS DB - DoWait demo Orders table
ORDERS F - DoWait demo Orders table - form F
ORDERS PX - DoWait demo Orders table - primary index
ORDERS VAL - DoWait demo Orders table - validity checks
PAYMENT DB - DoWait demo Payment table
STOCK DB - DoWait demo Stock table
STOCK PX - DoWait demo Stock table - primary index
TKFIELDS DB - TKMenu field-level proc data table
TKFIELDS F - TKMenu field-level proc data table - form F
TKFLDLVL DB - TKMenu field-level procedures - table
TKFLDLVL F - TKMenu field-level procedures - form F
TKFLDLVL PX - TKMenu field-level procedures - primary index
TKFLDLVL R - TKMenu field-level procedures - report R
TKFLDLVL SET - TKMenu field-level procedures - image settings
TKFLDLVL VAL - TKMenu field-level procedures - validity checks
TKKEYLVL DB - TKMenu key-level procedures - table
TKKEYLVL PX - TKMenu key-level procedures - primary index
TKKEYLVL R - TKMenu key-level procedures - report R
TKKEYLVL VAL - TKMenu key-level procedures - validity checks
TKPRCMAP DB - TOOLKIT.LIB procedure mapping - table
TKPRCMAP PX - TOOLKIT.LIB procedure mapping - primary index
TKPROCS DB - TOOLKIT.LIB procedure list - table
TKPROCS PX - TOOLKIT.LIB procedure list - primary index
TKPROCS VAL - TOOLKIT.LIB procedure list - validity checks
TKTBLLVL DB - TKMenu table-level procedures - table
TKTBLLVL R - TKMenu table-level procedures - report R
TKTBLLVL VAL - TKMenu table-level procedures - validity checks
In \PROTECT:
PROTECT ZIP - Zip file containing:
PROTECT SC - Protection Generator - main script
PROTECT LIB - Protection Generator - procedure library
DISK 7: PERSONAL PROGRAMMER DISK 1
-----------------------------------
in \PPROG1:
PPROG SOM - Personal Programmer program file
PPROG1 ZI1 - First part of main PProg executable file
In \VIDEO:
VIDEO ZIP - Zip file containing Video demo application:
VIDENT SC - Data entry script
CUSTOMER DB - Customer table
CUSTOMER F1 - Customer table - form 1
CUSTOMER PX - Customer table - primary index
FILMCAT DB - Film category table
FILMCAT PX - Film category table - primary index
FILMS DB - Films table
FILMS F - Films table - standard form
FILMS PX - Films table - primary index
ORDERS DB - Orders table
ORDERS F1 - Orders table - form 1
ORDERS F2 - Orders table - form 2
ORDERS PX - Orders table - primary index
ORDERS VAL - Orders table - validity checks
ORDTEMP DB - Film checkout table
ORDTEMP F1 - Film checkout table - form 1
ORDTEMP VAL - Film checkout table - validity checks
OVERMAP DB - Overdue films - map table
OVERSRC DB - Overdue films - source table
OVERSRC R2 - Overdue films - source table report 2
DISK 8: PERSONAL PROGRAMMER DISK 2
-----------------------------------
in \PPROG2:
PPROG1 ZI2 - Second part of main PProg executable file
PPROG2 ZI1 - First part of zip file for other PProg files
DISK 9: PERSONAL PROGRAMMER DISK 3
-----------------------------------
in \PPROG3:
PPROG2 ZI2 - Second part of zip file for other PProg files
WELCOME TO PARADOX 3.5
----------------------
This file contains important information that is not contained in the
documentation for Paradox 3.5. All information in this file supersedes
information in the Paradox 3.5 documentation.
TABLE OF CONTENTS
-----------------
1. Resolving Hardware and Software Compatibility Issues
2. Notes on Interactive Paradox
3. Notes on PAL
4. Starting and Running Paradox in Special Configurations
5. Notes on the Custom Configuration Program
6. Notes on the Personal Programmer
7. Files on the Disks
1. RESOLVING HARDWARE AND SOFTWARE COMPATIBILITY ISSUES
-------------------------------------------------------
Hardware/Software Compatibility:
Paradox is designed to follow memory management standards where they
exist, to make the best possible use of your computer, and to allow you
maximum flexibility to tune the program the way you want. When Paradox
loads, it tries to detect any EMS emulation, RAM disks, and caches you
have, and configures itself to run optimally in that environment. Some-
times you will want or need to modify the default configuration. You can
override Paradox's installation defaults with the Custom Configuration
Program (CCP) or with command-line options. See Chapter 14 of the
"Paradox User's Guide" for details.
Unfortunately, standards have been slow to evolve for memory
management. Paradox conforms to the major standards that do exist: the
VDISK standard for RAM disks, the VCPI standard for EMS emulation, and the
XMS standard for extended memory. If you use software that conforms to
some other standard, you may have to make adjustments to run Paradox.
Please check the list that follows for known compatibility problems.
Some specific compatibility problems are:
- If you're running your machine in fast or "turbo" mode, it may be
running faster than the hardware was designed to run. This may
cause it to drop instructions occasionally at its fastest speed.
While some of your software may run just fine in turbo mode,
Paradox sometimes makes heavier demands on the hardware than
other software packages. If you experience difficulty, try
running Paradox in slower or "safe" mode. (This is not to say
that all machines offering a choice of speeds are suspect; Paradox
will not have trouble on any machine's highest speed as long as
all the machine's components are designed to run at that speed.)
Machines that may experience this problem include 6Mhz IBM ATs
that have been sped up to 8Mhz or faster, the WYSEpc 286 in its
12.5Mhz mode, and the Rose Hill 286 at its faster speed.
- The Tall Tree JRAM EMS card is not supported by Paradox.
- A 286 machine with an old BIOS might not be able to run in
protected mode.
- A disk cache called VCache is known to be incompatible with
Paradox. Do not run VCache with Paradox.
- Some EMS emulators can run without allocating an EMS page frame.
This lets you use their many extra features, particularly the
ability to relocate drivers above 640K, even if you don't want to
use EMS. QEMM's FRAME=NONE option has this effect, as does
386Max's NOFRAME option. If you use your EMS emulator this way,
you must run Paradox in real mode (this is the mode it will run
in by default). Attempting to force Paradox into protected mode
in this situation might hang your machine.
- If you use a version of PC LAN that includes a cache and you locate
the cache in the network server's extended memory, you cannot run
Paradox on the server - there isn't enough memory below 640K left
for Paradox to run in real mode, and the PC LAN cache does not
allow any other program to use extended memory.
- The AST REX.SYS driver, which converts EEMS expanded memory back to
extended memory, is not compatible with Paradox 3.5. To obtain
extended memory with an EEMS board, don't let the REMM.SYS expanded
memory driver use some or all of the memory on the board. (In some
cases, you will have to set switches on the board to accomplish
this.)
- Under DOS 2.x, Paradox 3.5 runs only in real mode, not in protected
mode.
Testing Your CPU and EMS:
If you experience intermittent failures, they may be due to a
processor that's running too fast or memory that is defective or runs too
slowly. Paradox 3.5 includes two small programs to test for problems of
this sort. Although they cannot detect all machine problems, they do test
machine components that Paradox 3.5 stresses; as a result, they
often help pinpoint problem areas. The programs are CPUTEST.EXE and
EMSTEST.COM. Both are installed in your Paradox 3.5 program directory
automatically. If you have any reason to suspect that your hardware may
not be able to keep up with Paradox, you should run both programs (run only
CPUTEST if you don't have expanded memory). Even if your computer is
running flawlessly, feel free to try them out. CPUTEST runs just a few
seconds, and EMSTEST just a few minutes.
To run CPUTEST, just move to your Paradox directory (usually \PDOX35)
and type
CPUTEST
You should see the message "This CPU Tests OK." A message like "2
instructions skipped" probably indicates that your computer's processor is
running too fast.
To run EMSTEST, move to your Paradox directory, type
EMSTEST
and press keys as instructed. The test will verify that your Expanded
Memory Specification (EMS) hardware and software are working correctly.
You should see descriptions of a number of tests, each followed by the
status "OK." Any other status message indicates a probable EMS failure.
2. NOTES ON INTERACTIVE PARADOX
-------------------------------
Incremental Menu Selection:
In Paradox 3.0, you can type a letter when choosing from a menu to
narrow your selection down to choices starting with that letter, then make
your final selection using the arrow keys. In Paradox 3.5, you can type a
second letter to narrow your choices down further, then a third letter, and
so on. As you type each letter, it will be colored differently in the
current menu item. Whenever there is only one choice that matches the
letters typed, it will be selected immediately, just as is done in Paradox
3.0 when the first letter of a choice is unique. You can still use the
arrow keys to select, as before; as soon as you do, the incremental
selection in process is abandoned, so you must start from the beginning of
the desired choice to select it using incremental type in.
Incremental menu selection works wherever you select from a menu: in
Paradox's own menus; in application menus created by SHOWMENU; in lists of
tables, scripts, forms, and other objects; and in lists produced by
SHOWARRAY, SHOWTABLES, and SHOWFILES. In interactive use, the new
incremental selection capability is completely compatible with existing
menu interaction. Scripts that use InstantRecord, SHOWMENU, or braced menu
selections will also be compatible with Paradox 3.5. Scripts that use
KEYPRESS and TYPE IN to select from menus might behave differently:
keystrokes that did not cause a menu item to be selected now can, depending
on the contents of the menu list.
Tools|Copy|JustFamily:
Previous versions of Tools|Copy|JustFamily could copy corrupt or
out-of-date family members from the source to the target table. Although
this was clearly the wrong action for corrupt family members, it did allow
you to "re-attach" a correct but out-of-date object to its table.
Copy|JustFamily now checks that each object is a valid member of the source
table's family before copying it. As a result, you will no longer be able
to use it to attach out-of-date family members to their tables.
Tools|Info|Lock:
The LIST table that Tools|Info|Lock produces now gives more infor-
mation when there is a form-lock on a multi-table form. When a table is
form-locked, Paradox displays "Form Lock" in the lock type field, followed
by the type of lock that pre-Paradox 3.0 users will see. (These earlier
versions of Paradox cannot use a form-locked table because they don't
support multi-table forms.) For example, if you are coediting a multi-
table form, the type field will show "Form Lock-WL", where WL stands for
Write Lock. The other abbreviations are PFL (Prevent Full Lock) and PWL
(Prevent Write Lock). Paradox no longer adds a second record saying "Write
Lock" in the LIST table.
Undo:
In a multi-table form, Undo works differently than in Paradox 3.0 in
one minor case: After a form toggle, it now takes two Undo operations to
back up as far as one Undo did previously.
Number Rounding Issues:
Paradox 3.5 uses the Turbo C math library, which provides greater
precision than the one used in Paradox 3.0. This will cause some numeric
and dollar values that were entered using an earlier version of Paradox to
be rounded differently in Paradox 3.5. Data entered in Paradox 3.5 will
not exhibit this problem. (Because of the way Paradox represents numbers,
there will always be occasional round-off errors when manipulating numbers
with many decimal digits of precision. Unfortunately, other methods of
representing numbers also have disadvantages.)
Because data entered in Paradox 3.5 works fine, the solution is to
export the existing Paradox file to an ASCII file, then import the data
back into Paradox 3.5. You can put your data back into the same table it
started in, leaving the table's family unaltered. The steps to follow are:
1. Make a backup of the table to be processed (if you don't have one)
in case any problems arise.
2. Export the table to ASCII format. If your table is named CUSTOMER
and you want to call the temporary ASCII file TEMP_30, use:
Tools|ExportImport|Export|Ascii|Delimited
and enter CUSTOMER as the table name and TEMP_30 as the exported
file's name.
3. Empty the CUSTOMER table, using Tools|More|Empty.
4. Import your data back into CUSTOMER, using the AppendDelimited
command (not the Delimited command):
Tools|ExportImport|Import|Ascii|AppendDelimited
Type in TEMP_30 when you are prompted for a file name and CUSTOMER
when you are prompted for a table name.
Norwegian/Danish Sort Order:
Minor corrections have been made to the NORDAN.SOR sort file. The
table in Chapter 14 of the "Paradox User's Guide" labeled "Swedish/Finnish
and Norwegian/Danish Sort Order" is accurate only for the SWEDFIN.SOR sort
order. The order of alphabetic characters according to NORDAN.SOR is shown
below. (Note that ASCII characters 155 and 157 appear as slashed "O"s if
you have the Norwegian/Danish video ROM.)
ASCII ASCII ASCII ASCII
Char Code Char Code Char Code Char Code
----------- ----------- ----------- -----------
a 97 i 105 Q 81 ä 132
á 160 ï 139 r 114 Æ 146
à 133 í 161 R 82 Ä 142
â 131 ì 141 s 115 ¢ 155
A 65 î 140 S 83 ö 148
b 98 I 73 t 116 ¥ 157
B 66 j 106 T 84 Ö 153
c 99 J 74 u 117 å 134
ç 135 k 107 ú 163 Å 143
C 67 K 75 ù 151 α 224
Ç 128 l 108 û 150 ß 225
d 100 L 76 U 85 Γ 226
D 68 m 109 v 118 π 227
e 101 M 77 V 86 Σ 228
ë 137 n 110 w 119 σ 229
é 130 ñ 164 W 87 µ 230
è 138 N 78 x 120 τ 231
ê 136 Ñ 165 X 88 Φ 232
E 69 o 111 y 121 Θ 233
É 144 ó 162 ü 129 Ω 234
f 102 ò 149 ÿ 152 δ 235
F 70 ô 147 Y 89 ∞ 236
g 103 O 79 Ü 154 φ 237
G 71 p 112 z 122 ε 238
h 104 P 80 Z 90 ∩ 239
H 72 q 113 æ 145 ≡ 240
Compatibility with Paradox 3.0:
Paradox 3.5 is compatible with previous versions of Paradox. However,
if you will be running existing applications under Paradox 3.5 or want your
Paradox 3.5 development to coexist with previous versions, there are a few
points you should consider:
- Although tables from previous versions of Paradox are completely
compatible with Paradox 3.5, tables created in Paradox 3.5 exhibit
better performance in almost all cases. For best performance in
Paradox 3.5, you should restructure existing tables in Paradox 3.5.
To do this, choose Modify|Restructure, then press Do-It (without
making any changes to the table's structure). However, if some
users will continue to use these tables with earlier versions of
Paradox, be aware that these restructured tables will require more
memory when placed on the workspace - up to 2K more for each table
and for each index on the table. (Paradox 3.5 doesn't use more
memory per image on the workspace for tables built with the
new structure; only earlier versions of Paradox do.)
- As explained in the "Upgrade Guide," Paradox 3.5 uses a new format
for procedure library files. Paradox 3.5 can read existing
libraries, but previous versions cannot read Paradox 3.5 libraries.
In addition, although Paradox 3.5 can read procedures from a
Paradox 3.0 library, you cannot write such procedures directly from
memory into a Paradox 3.5 library. You must play a script
containing the procedures in source code form, then use WRITELIB
to write them to the new library.
- You might notice that previous Paradox versions can often use forms
and reports that contain functions and variables in calculated
fields. However, there are some functions (DOW, for example) that
Paradox versions before 3.5 will not accept in calculated fields.
In addition, these Paradox versions cannot modify Paradox 3.5 forms
and reports that use functions or variables. If you attempt either
operation, you will see a message like "Invalid calculation..." or
"Invalid fields removed from form...". Select Cancel from the menu
to back out of Forms|Change or Report|Change mode, then use Paradox
3.5 to modify the form or report; otherwise, you will lose all the
calculated expressions that the earlier version of Paradox doesn't
understand.
- A few messages have been changed. Although most of the changes
just correct spelling and punctuation errors, applications that
test for the exact text of a message will not recognize the new
messages. Applications should avoid testing messages whenever
possible.
- Minor changes have been made to the Tools|ExportImport menus to
include Quattro PRO import and export. There are other menu
changes, but they do not introduce compatibility issues; for
example, Paradox 3.5 accepts "QuerySpeedup" and "QuerySpeed"
interchangeably.
Printing Graphs:
Paradox (by default) does not do a page-eject after printing a graph.
This allows you to place more than one graph on a page. On a PostScript
printer or other laser printer, it may seem that your graph was not sent to
the printer properly, since there is often no sign of activity until a page
is ejected. To override the default temporarily, enter the Graph subsystem
(using Image|Graph|Modify), then choose Overall|PrinterLayout and set
"Break Page" to "Y". To override it permanently, play Custom and go
through the same steps.
3. NOTES ON PAL
---------------
RUN ([Ctrl][O]) and RUN BIG ([Alt][O]):
Paradox 3.5 uses Borland's VROOMM memory management, which loads
modules of program code into memory dynamically as they are needed. As a
result, the amount of memory available when you execute PAL's RUN or RUN
BIG command (or their keyboard equivalents, [Ctrl][O] and [Alt][O]) will
vary more in the course of a session than it did in Paradox 3.0. Exactly
how much memory is available depends on many factors, but neither RUN nor
RUN BIG will always give you as much memory as Paradox 3.0 did.
In both real and protected mode, RUN always gives 140K or more; if it
can't free up that much, Paradox automatically converts the RUN to a RUN
BIG. In real mode, RUN BIG can usually free up all but about 25K of the
memory available when you started Paradox. In protected mode, it can
usually free up all but about 75K of the memory available at Paradox
startup.
For most users, RUN and RUN BIG will work just as before. If you are
using RUN BIG to run a memory-intensive program from within Paradox, check
that the operation will still work in your configuration.
PRINT FILE:
PAL's PRINT FILE command is much faster now because Paradox keeps the
file open as long as possible and buffers the output. If you previously
optimized PRINT FILE by concatenating output into long strings, you'll find
that this is no longer necessary. Paradox knows to write the buffer and
close the file almost any time it could be necessary: when you exit
Paradox, execute a RUN command, print to another file, use the FILESIZE
function to test the size of the file just written, play the script just
written, etc. If you want to close the file before Paradox does so
automatically - if you use it as a semaphore to other network users, for
example - use something like
DUMMY = ISFILE("filename.txt")
(where "filename.txt" is the name of your file) to force it to be closed.
RECORDSTATUS Function:
In several cases, RECORDSTATUS may return a result that is not what
you expect. It's helpful to be aware of these cases and know why
RECORDSTATUS reports what it does:
- Using RESYNCKEY to show Many-one and Many-many details matching the
current record has the effect of posting your changes (though the
record remains locked.) As a result, RECORDSTATUS ("Modified")
returns False.
- RECORDSTATUS ("KeyViol") returns False if you've inserted a
duplicate record but haven't yet tried to post it, since Paradox
doesn't detect the key violation until then.
- RECORDSTATUS ("KeyViol") also returns false if you enter a
duplicate key in a multi-table form in CoEdit and try to post it.
This looks like a key violation, but really isn't from Paradox's
point of view: you don't have the existing record that the new
one conflicts with locked, you can't use [Alt][K] to toggle
between the two, and [Alt][L] won't force posting of the new record.
Error Procedures and Error Codes:
The complete list of error codes and their causes is given below. If
you have a Paradox 3.5 manual set, you'll also find this table in your "PAL
User's Guide." There are two other small points about error procedures and
error codes to note:
- If you attempt to modify a table that is write-protected, Paradox
sets errorcode to 22, not to 35 as in previous versions.
- When an error procedure is called because a low memory warning is
issued, Paradox always retries the current statement on return from
the error procedure, even if the return value from the procedure
specifies that it should be skipped. This makes it easier to run
existing applications under Paradox 3.5.
PARADOX ERROR CODES
Code Meaning
---- -------------------------------------
0 No error (for example, record was not
changed or key was found)
File or directory errors
1 Drive not ready
2 Directory not found
3* Table in use by another user
4* Full lock placed on table by another user
5 File not found
6 File corrupted
7 Index file corrupted
8 Object version mismatch
9* Record locked by another user
10 Directory in use by another user
11* Directory is private directory of another user
12 No access to directory at operating system level
13 Index inconsistent with sort order
14 Multiuser access denied
15 PARADOX.NET file conflict
General script errors
20 Invalid context for operation
21 Insufficient password rights
22 Table is write-protected
23 Invalid field value
24 Obsolete procedure library
25 Insufficient image rights
26** Invalid PAL context
27 Operation not completed
28 Too many nested closed procedures
29 Table is remote (on an SQL server)
Argument errors
30 Data type mismatch
31 Argument out of range
32 Wrong number of arguments
33 Invalid argument
34 Variable or procedure not assigned
35 Invalid menu command
Resource errors
40** Not enough memory to complete operation
41 Not enough disk space to complete operation
42** Not enough stack space to complete operation
43 Printer not ready
44 Low memory warning
Record-oriented operation errors
50** Record was deleted by another user
51** Record was changed by another user
52** Record was inserted by another user
53** Record with that key already exists
54** Record or table was not locked
55** Record is already locked by you
56** Lookup key not found
Multi-table operation errors
60 Referential integrity check
61 Invalid multi-table form
62** Form locked
63 Link locked
* For this code, ERRORUSER() returns the name of the user who locked
the resource
** This code does not invoke a designated error procedure
4. STARTING AND RUNNING PARADOX IN SPECIAL CONFIGURATIONS
---------------------------------------------------------
Running Paradox 3.5 under Windows 3.0:
You can run Paradox 3.5 and the Paradox Personal Programmer (PProg)
under Windows 3.0. If you plan to do this, you need to do four things, in
this order:
1. Copy the .PIF and .GRP files from the \WINDOWS subdirectory on your
Paradox Installation\Sample Tables disk into your Windows directory
(usually C:\WINDOWS). The PARADOX.PIF and PPROG.PIF files allow
Paradox and the Personal Programmer to run optimally under Windows.
If you choose to modify them or define your own .PIF files, you
should always include the -win command-line option. PARADOX.GRP
gives Windows a program manager icon for Paradox 3.5 that contains
icons for Paradox 3.5 and the Paradox Personal Programmer.
2. Make sure your Paradox system directory is in your DOS PATH
statement, so Windows can find the files. For information on the
PATH statement, see your DOS manual.
3. Run the DOS SHARE program. Type SHARE at any DOS prompt to do
this, or add a SHARE statement to your AUTOEXEC.BAT file. SHARE
must be resident to run Paradox 3.5 under Windows.
4. Set up a program group in Windows to put a Paradox icon on the
Windows Program Manager screen. To create this program group,
a. Choose File from the Windows Program Manager.
b. Choose New, then choose Program Group.
c. Fill in a description of the group to appear under the icon (for
example, PARADOX 3.5).
d. Fill in the full path name of the group file (for example,
C:\WINDOWS\PARADOX.GRP).
e. Click OK. Two new icons appear in your Paradox 3.5 window: one
for Paradox 3.5 and one for the Paradox Personal Programmer.
Windows is now set up to run either Paradox 3.5 or the Personal Programmer
whenever you want. Double-click on the appropriate icon to invoke the
program.
Paradox 3.5 runs in a bordered window when Windows is running in 386
Enhanced Mode. (You enter this mode by starting Windows with the command
WIN /3). If you are running Windows on an 8088 or 80286 computer, or on a
386 in real or standard mode, Paradox and the Personal Programmer run in
full-screen mode and appear as they do when run outside Windows. In this
full-screen mode, press [ALT][ESC] to switch from Paradox to another
Windows application. The Paradox (or PProg) icon appears at the lower
left corner of the Program Manager window; double-click on it to return
to Paradox (or PProg).
After you press a mouse button in a window, its title bar says Select.
This means that Windows has taken over control of the keyboard and mouse so
you can cut or paste, operations Paradox does not support. Press [ESC]
to return control to Paradox.
To close files properly and prevent data loss, always exit Paradox
using the keyboard (press [F10] and choose Exit|Yes), not the mouse. If you
try to exit Windows with Paradox still running, a warning appears and you
are given a chance to exit Paradox properly; Windows will not let you exit
without closing applications.
Running Paradox 3.5 under DESQview:
You can run Paradox 3.5 under DESQview in either real or protected mode
on a 286 or higher machine. Here's how to configure DESQview to run
Paradox 3.5:
1. Install Paradox 3.5 according to the installation instructions in
the "Introduction to Paradox" manual or the "Upgrade Guide."
2. From the DESQview Main menu, choose Open Window.
3. If you are upgrading from Paradox 3.0 to 3.5, select Paradox3 from
the file list, then choose Change a Program. If you are installing
Paradox for the first time, you'll first have to use Add a Program
to add the program name to this list.
4. Press [F1] to see the Standard Options screen. Type the program
name, any batch file name you use to invoke it, the full path
name (including file name), and any command-line parameters you
use. Set Memory Size (in K) to 440. Set the Standard Options
switches as follows:
Writes Text To Screen [N]*
Displays Graphics Info [Y]
Virtualize Text/Graphics [N]**
Uses Serial Ports [N]
Requires Floppy [N]
5. Press [F1] again for the Advanced Options screen. Set the following
parameters:
System memory 0
Max Program Size (in K) 640
Script Buffer Size 1000
Max Expanded Memory 1024***
Set the switches as follows:
Close On Exit [ ](leave blank)
Allow Close Window Command [N]
Uses Math Coprocessor [Y]
Share CPU When Foreground [Y]
Can Be Swapped Out [ ](leave blank)
Use Its Own Colors [Y]
Run In Background [ ](leave blank)
Keyboard Conflict [0]
Share EGA When Foreground [Y]
Protection Level [0]
* On a 286 machine, set this switch to Yes.
** On a 286 machine or on a 386 or higher machine running in
protected mode, set this switch to Yes.
*** Max Expanded Memory can be set higher.
6. Exit Change a Program or Add a Program and start Paradox in the
usual way under DESQview.
Use the same procedure to configure DESQview to run the Paradox Personal
Programmer.
If you plan to run multiple Paradox sessions under DESQview, you
should make the Paradox program files read-only. You'll also need one
Paradox serial number for each session.
Multiple Paradox Sessions:
When you run Paradox on a network, the network operating system ensures
that you can share program and data files with other users whenever sharing
is appropriate. On a standalone machine, DOS's SHARE command and Paradox's
-share command-line option have the same effect. Without them, DOS assumes
that no file sharing is required. Applications that might share files on a
standalone computer include
- Windows
- DESQview
- Add-in programs for Paradox, such as Kallista's KMemo
- In-house applications that use the RUN command to execute Paradox
Engine programs. These programs in turn might perform special
processing on the applications' tables.
If you will be sharing files on a standalone machine, you should use
the -share command-line option. The -share option now requires that DOS
SHARE be loaded (and this in turn means that you will need to use DOS 3.0 or
higher). Using -share causes Paradox to write a PARADOX.NET file in the
root directory on your hard disk and to put an entry in it for each session
or program that runs Paradox. This guarantees that file sharing works
correctly.
Software EMS Drivers:
This note is an addition to the notes about XMS-compliant EMS drivers
in the "Upgrade Guide" and the "Paradox User's Guide."
If your system has extended memory that an XMS-compliant EMS driver is
converting to expanded memory, Paradox handles this memory at startup in
the following ways:
In real mode with neither the -extk or -emk command-line options set,
Paradox asks the driver for all the available extended memory, then uses
that memory as a swap device. To keep Paradox from using all the expanded
memory in this way, use the -extk command-line option. For example, if you
normally have 4MB of extended memory being converted to expanded memory,
and you want Paradox to take only 1MB of that memory, type
paradox -real -extk 1024
(You usually need to include the -real option, since Paradox attempts to
run in protected mode by default.) The rest of the memory remains as
expanded memory, which Paradox also uses as a swap device. To save some of
that expanded memory for another (concurrent) program, you must also set an
-emk option. For instance, if you have 4MB, and you want to have Paradox
use 1MB as extended, 1MB as expanded, and leave 2MB of expanded for another
program, type
paradox -extk 1024 -emk 1024
When you start Paradox in protected mode, the options are evaluated
differently. In protected mode, Paradox takes all the XMS-compliant EMS
memory as extended memory before it evaluates the -ext or -emk options. If
the EMS driver is set up in your CONFIG.SYS file so that only some of the
extended memory is available to the EMS driver, Paradox uses only that
memory configured as expanded, but changes it to extended. Paradox does
not use the non-EMS configured extended memory at all. For instance, if you
have 1MB left as extended and 3MB configured as expanded, Paradox takes 3MB
and uses it as extended.
Novell NetWare 386:
NetWare 386 allows you to define a virtual root. This means that it
allows you to map a drive letter to a subdirectory in such a way that the
user of that mapping can only access the mapped subdirectory and its child
directories. (Ordinarily, NetWare mappings are just shortcuts; you can
still use the DOS CHDIR command to access any directory on the volume.)
Virtual roots are created with the 'MAP ROOT' command.
Since virtual roots allow different users to access different
subdirectories of a volume with the same network drive path, Paradox might
not enforce locking correctly if two users specify paths to the PARADOX.NET
file which do not indicate the same subdirectory on the server. For
example, if one user maps S: using the command
MAP ROOT S: server\sys:pdoxdata
and another user maps S: using
MAP S: server\sys:pdoxdata
then the \PDOXDATA directory will be S:\ for the first user and
S:\pdoxdata for the second user. Similarly, if one user maps S: using
MAP ROOT S: server\sys:pdoxdata
and another maps S: using
MAP ROOT S: server\sys:pdox
then S:\ for the first user will be different than S:\ for the second user.
Both of these situations can lead to severe data corruption.
Be sure to observe the warning in the Network Administrator's Guide
that "All Paradox users must have the directory containing the PARADOX.NET
file mapped to the same logical drive and directory." Suppose your
PARADOX.NET file is in server\sys:pdoxdata and you use your system login
script to map S: to server\sys:pdoxdata as a virtual root. Then you should
specify when you install Paradox that PARADOX.NET is in S:\. Once
you've done this, it is essential that no one override the mapping of S:.
In this way, all active users share the PARADOX.NET file, each recognizes
the others as active users, and all respect the others' lock files.
5. NOTES ON THE CUSTOM CONFIGURATION PROGRAM
--------------------------------------------
Configuration Issues:
When discussing Custom's new handling of color settings, the "Upgrade
Guide" says that when you're in Video|Colors, you will recognize your
existing color settings by their names. Ordinarily, this won't be true;
when you run Custom with Paradox 3.5, you will start with the default
configuration file. Even users of earlier Paradox versions who have
chosen to override only a few of Paradox's defaults are better off
redefining their configurations from scratch. But if your existing
configuration file is highly customized - if you've modified the default
report or graph specification, or selected several graph printers, or added
report setup strings or color settings - you may want to retain your
existing configuration. To do so, copy your PARADOX3.CFG file (or another
.CFG file from a previous version of Paradox) to PARADOX.CFG and move it to
your Paradox 3.5 directory. (You may want to save a copy of the current
PARADOX.CFG first.) You can now use Paradox 3.5's Custom program to
further customize your configuration.
B&W Monitors:
On monochrome and B&W monitors, Paradox uses only the built-in color
setting. (A B&W monitor is a monochrome monitor attached to a color video
card.) If you want to modify the color setting on a B&W monitor, you must
set your monitor type to "Color" (using the Video|Monitor command);
otherwise, Paradox ignores the changes you make to the color setting. The
effect, of course, will be to change the shades of gray or orange that your
monitor uses to show different elements of the Paradox display.
Graph Printers:
The list of graph printers you can choose from in Custom's
Graphs|Printers command has been updated and expanded, and a few older
printers have been removed from the list. If you want to use a printer
that was available in Paradox 3.0 but is not available in Paradox 3.5,
here's how:
- If you haven't already done so, run Paradox 3.0 and Paradox 3.0's
version of Custom to select the printer.
- Rename your PARADOX3.CFG file to PARADOX.CFG and move it to your
Paradox 3.5 directory. (You may want to save a copy of the current
PARADOX.CFG first.)
- Run Paradox 3.5 as usual. The printer defined in Paradox 3.0 will
be available.
Directories and Paths:
Previous versions of Paradox installed Custom in the program directory
by default, but did not require that it be there. With Paradox 3.5, you
must store Custom in the system directory or in a directory on your path in
order to use the Tune|ProtectedMode|MachineInfo and Configure options.
This ensures that Paradox can find the machine configuration information
that Custom writes out. If the Paradox system directory on your
network is normally read-only, you will need to log on as the network
administrator to write to it. For more information, see the "Upgrade
Guide."
The MachineInfo Report:
Custom's MachineInfo report displays basic information about your
machine configuration. Because computers vary widely, the report is
sometimes incomplete or slightly inaccurate. For example, not every BIOS
contains an ID at the "standard" address, but MachineInfo can't determine
what's a valid ID string and what isn't. Don't be alarmed if you see random
characters, or even a message like "fatal error" in the "BIOS ID String"
field. It's just extraneous text that MachineInfo mistook for the BIOS ID.
6. NOTES ON THE PERSONAL PROGRAMMER
-----------------------------------
There have been some minor changes to the Personal Programmer. Other
than the changes noted below, all parts of the program operate just as
they did in Paradox 3.0.
1. Paradox 3.5 uses a slightly modified way of reading
and writing libraries. Although Paradox 3.5 will read the
old libraries in exactly the same way as it did before,
the Personal Programmer can not directly modify libraries
in the old format. If you are modifying an application
that was originally created in 3.0, you will see a new
menu the first time you modify the application in 3.5. It
will appear immediately after you enter the name of the
application, and will offer you the option of updating
your libraries to 3.5 format.
If you choose Cancel, you will return to the Personal
Programmer Main menu. If you choose Update, the Personal
Programmer will rebuild your libraries in the new 3.5
format. Be aware that if you update the libraries, the
application will not be usable in Paradox 3.0. If you need
to modify an application that will be used with both 3.5
and 3.0, you should modify the application using only
Personal Programmer 3.0.
2. The Personal Programmer was not designed to be used on a
network and will not generate a multiuser application. In
Paradox 3.0, the large amount of memory needed to create
an application made it very difficult to execute the
Personal Programmer with the network software loaded.
Now that the Personal Programmer can access Extended RAM,
it would have been possible to run while the network
drivers are loaded. However, running the Personal
Programmer on a network drive with other users working
interactively could result in the failure of the program
and a loss of work. To prevent this loss of data, the
Personal Programmer has been modified to prevent the use
of a network drive.
3. The Personal Programmer allows you to set validation checks on
fields, requiring that they be filled with valid data.
There is one case where a combination of validity checks
will cause a problem. If you use the "TableLookup/HelpAndFill"
and the "RequiredField" options together, users may get
"stuck" in the field. In this case, pressing F1 to bring
up the Lookup will result in the message "A value must be
provided in this field." The user doesn't know what a
valid value is, and can't check to find out. This
combination should be avoided.
7. FILES ON THE DISKS
---------------------
This is the configuration for 5.25" disks. Each 3.5" disk except
Personal Programmer Disk 3 contains the directories and files from two
5.25" disks, as indicated by its disk label.
DISK 1: INSTALLATION/SAMPLE TABLES DISK
----------------------------------------
INSTALL EXE - Paradox installation program
README COM - Program to display README file
INSTALL CFG - Installation parameters
UNZIP EXE - Program to "unzip" compressed files
ASCII SOR - ASCII sort order
INTL SOR - International sort order
NORDAN SOR - Norwegian/Danish sort order
SWEDFIN SOR - Swedish/Finnish sort order
SYS ZIP - Zip file containing:
NUPDATE EXE - Program to update serial numbers, net type
PARADOXK EXE - Protected mode driver program
PARADOX CFG - Default Paradox configuration settings
PARADOX SOM - Paradox program file
In \UTIL:
UTIL ZIP - Zip file containing:
FLIMPORT EXE - Fixed-length Import utility program
FLIMPORT DOC - Documentation for Fixed-length Import program
VOUCH EXE - Checksum utility program
In \SAMPAPP:
SAMPAPP ZIP - Zip file containing sample application:
BOARD SC - Script to display Price table
DOFEED SC - Script to generate stock Price changes
FEED SC - Script to call procedures in DOFEED.SC
GRAPHS SC - Script to display graphs
HOLDINGS SC - Script to display holdings
MKLIB SC - Script to build procedure library
PORTFOL SC - Script to display portfolios
STOCKS SC - Main menu script
TICKER SC - Script to display "ticker tape"
HOLDING DB - Holdings table
HOLDING PX - Holdings table - primary index
PRICE DB - Stock Price table
PRICE PX - Stock Price table - primary index
PRICE SET - Stock Price table - settings file
GRAPH1 G - Sample application Bar & Marker graph spec
GRAPH2 G - Sample application 3-D Bar graph spec
GRAPH3 G - Stacked Bar graph spec
GRAPH4 G - Sample application Pie chart spec
In \TABLES:
TABLES ZIP - Zip file containing sample files:
DEBUGTST SC - Sample PAL code (with intentional errors)
PIES SC - Recorded script to create sample graphs
RECAP SC - Script to do work done manually during tutorial
BOOKORD DB - Sample Book orders table
BOOKORD F1 - Sample Book orders table - form 1
BOOKORD PX - Sample Book orders table - primary index
CUSTOMER DB - Sample Customer table
CUSTOMER F1 - Sample Customer table - form 1
CUSTOMER F2 - Sample Customer table - form 2
CUSTOMER F3 - Sample Customer table - form 3
CUSTOMER PX - Sample Customer table - primary index
CUSTOMER R1 - Sample Customer table - report 1
CUSTOMER R2 - Sample Customer table - report 2
CUSTOMER SET - Sample Customer table - image settings
DISTRICT WQ1 - Sample Quattro PRO worksheet
EMPLOYEE DB - Sample Employee table
EMPLOYEE F1 - Sample Employee table - form 1
EMPLOYEE PX - Sample Employee table - primary index
EMPLOYEE SET - Sample Employee table - image settings
HOMEGRP DB - Sample Home group table
MAIL DB - Sample Mail table
MAIL PX - Sample Mail table - primary index
MAIL R1 - Sample Mail table - report 1
MASTERBK DB - Sample Master book table
NEWRECS DB - Sample New records table
PRODUCTS DB - Sample Products table
PRODUCTS SET - Sample Products table - image settings
PROMO DB - Sample Promotion table
PROMO PX - Sample Promotion table - primary index
REPPERF DB - Sample Repperf table
REPPERF PX - Sample Repperf table - primary index
SALES DB - Sample Sales table
SALES SET - Sample Sales table - image settings
SUBGROUP DB - Sample Subgroup table
VOLS DB - Sample Volumes table
VOLS PX - Sample Volumes table - primary index
XCHANGE DB - Sample Xchange table
In \WINDOWS:
PARADOX PIF - Windows 3.0 PIF file for Paradox
PPROG PIF - Windows 3.0 PIF file for PProg
PDOXRUN PIF - Windows 3.0 PIF file for Runtime
PARADOX GRP - Windows 3.0 group file for Paradox
README - This file
DISK 2: SYSTEM DISK 1
----------------------
in \SYSTEM1:
PDOX1 ZI1 - First part of main Paradox executable file
DISK 3: SYSTEM DISK 2
----------------------
in \SYSTEM2:
PDOX1 ZI2 - Second part of main Paradox executable file
PDOX2 ZI1 - First part of zip file for other Paradox files
DISK 4: SYSTEM DISK 3
----------------------
in \SYSTEM3:
PDOX2 ZI2 - Second part of zip file for other Paradox files
DISK 5: CUSTOM CONFIGURATION DISK
----------------------------------
In \CUSTOM:
CUSTOM ZIP - Zip file containing:
CUSTOM SC - Custom Configuration - main script
COLORS LIB - Custom Configuration - color procedures library
CUSTOM LIB - Custom Configuration - main procedure library
CUSTOM OV1 - Custom Configuration - Tune menu command
DISK 6: DATA ENTRY TOOLKIT DISK
--------------------------------
In \TOOLKIT:
TOOLKIT ZIP - Zip file containing Data Entry Toolkit:
BORROW0 SC - Borrow script for CUSTDPA.SC
BORROW1 SC - Borrow script for MINIDPA.SC
BORROW2 SC - Borrow script for INVDPA.SC
BORROW3 SC - Borrow script for ORDRDPA.SC
CUSTDEMO SC - Custom procedures for Cust table, DoWait demo
CUSTDPA SC - DoWait Procedure Assignment set for Cust
DEMO SC - Starts the DoWait demonstration
DOW8DEMO SC - Builds DOW8DEMO.LIB for DoWait demo
EDITMENU SC - Source code for EditMenu procedure
ENFORME SC - Main Enforme form editor script
FORMBRDR SC - Enforme border drawing routines
FORMGOTO SC - Enforme workspace positioning routines
FORMHELP SC - Enforme help screen
FORMHOPS SC - Enforme workspace movement routines
FORMMAIN SC - Enforme main getkey procedure
FORMMAKE SC - Script to create Enforme procedure library
FORMSLCT SC - Enforme form selection routines
GETFILE SC - Source code for GetFile procedure
GETPASS SC - Source code for GetPassword procedure
HELPDEMO SC - Inactivity proc, help for DoWait demonstration
INVDEMO SC - Custom procedures for Invoice, DoWait demo
INVDPA SC - DoWait Procedure Assignment set for Invoice
KERNEL SC - Source code for DoWait procedures
KEYCODES SC - Source code for SetKeycodes procedure
LOOKSLCT SC - Source code for LookupSelect procedure
LOOKWAIT SC - Source code for LookupWait procedure
MINIDEMO SC - Source code for sample SetUpDoWait session
MINIDPA SC - DoWait Procedure Assignment set for Cust
ORDRDEMO SC - Custom procedures for Orders table, DoWait demo
ORDRDPA SC - DoWait Procedure Assignment set for Orders
POPUP SC - Source code for Popup procedures
POPUP2 SC - Source code for Popup2 procedures
RECURSW8 SC - Source code for RecurseWait procedure
RELEASW8 SC - Source code for ReleaseWait procedure
RFRSHCNV SC - Source code for RefreshCanvas procedure
TKDEBUG SC - Source code for TKDebug procedure
TKMENU SC - TKMenu main script
TKUPDATE SC - Script to update Paradox 2.0 spec files
TKUPDATE LIB - TKUpdate procedure library
TOOLKIT2 LIB - TKMenu procedure library
CARRIERS DB - DoWait demo Carrier service table
CARRIERS F - DoWait demo Carrier service table - form 1
CUST DB - DoWait demo Customer table
CUST F - DoWait demo Customer table - form F
CUST F1 - DoWait demo Customer table - form 1
CUST PX - DoWait demo Customer table - primary index
CUST VAL - DoWait demo Customer table - validity checks
INVOICE DB - DoWait demo Invoice table
INVOICE F - DoWait demo Invoice table - form F
INVOICE PX - DoWait demo Invoice table - primary index
INVOICE VAL - DoWait demo Invoice table - validity checks
ORDERS DB - DoWait demo Orders table
ORDERS F - DoWait demo Orders table - form F
ORDERS PX - DoWait demo Orders table - primary index
ORDERS VAL - DoWait demo Orders table - validity checks
PAYMENT DB - DoWait demo Payment table
STOCK DB - DoWait demo Stock table
STOCK PX - DoWait demo Stock table - primary index
TKFIELDS DB - TKMenu field-level proc data table
TKFIELDS F - TKMenu field-level proc data table - form F
TKFLDLVL DB - TKMenu field-level procedures - table
TKFLDLVL F - TKMenu field-level procedures - form F
TKFLDLVL PX - TKMenu field-level procedures - primary index
TKFLDLVL R - TKMenu field-level procedures - report R
TKFLDLVL SET - TKMenu field-level procedures - image settings
TKFLDLVL VAL - TKMenu field-level procedures - validity checks
TKKEYLVL DB - TKMenu key-level procedures - table
TKKEYLVL PX - TKMenu key-level procedures - primary index
TKKEYLVL R - TKMenu key-level procedures - report R
TKKEYLVL VAL - TKMenu key-level procedures - validity checks
TKPRCMAP DB - TOOLKIT.LIB procedure mapping - table
TKPRCMAP PX - TOOLKIT.LIB procedure mapping - primary index
TKPROCS DB - TOOLKIT.LIB procedure list - table
TKPROCS PX - TOOLKIT.LIB procedure list - primary index
TKPROCS VAL - TOOLKIT.LIB procedure list - validity checks
TKTBLLVL DB - TKMenu table-level procedures - table
TKTBLLVL R - TKMenu table-level procedures - report R
TKTBLLVL VAL - TKMenu table-level procedures - validity checks
In \PROTECT:
PROTECT ZIP - Zip file containing:
PROTECT SC - Protection Generator - main script
PROTECT LIB - Protection Generator - procedure library
DISK 7: PERSONAL PROGRAMMER DISK 1
-----------------------------------
in \PPROG1:
PPROG SOM - Personal Programmer program file
PPROG1 ZI1 - First part of main PProg executable file
In \VIDEO:
VIDEO ZIP - Zip file containing Video demo application:
VIDENT SC - Data entry script
CUSTOMER DB - Customer table
CUSTOMER F1 - Customer table - form 1
CUSTOMER PX - Customer table - primary index
FILMCAT DB - Film category table
FILMCAT PX - Film category table - primary index
FILMS DB - Films table
FILMS F - Films table - standard form
FILMS PX - Films table - primary index
ORDERS DB - Orders table
ORDERS F1 - Orders table - form 1
ORDERS F2 - Orders table - form 2
ORDERS PX - Orders table - primary index
ORDERS VAL - Orders table - validity checks
ORDTEMP DB - Film checkout table
ORDTEMP F1 - Film checkout table - form 1
ORDTEMP VAL - Film checkout table - validity checks
OVERMAP DB - Overdue films - map table
OVERSRC DB - Overdue films - source table
OVERSRC R2 - Overdue films - source table report 2
DISK 8: PERSONAL PROGRAMMER DISK 2
-----------------------------------
in \PPROG2:
PPROG1 ZI2 - Second part of main PProg executable file
PPROG2 ZI1 - First part of zip file for other PProg files
DISK 9: PERSONAL PROGRAMMER DISK 3
-----------------------------------
in \PPROG3:
PPROG2 ZI2 - Second part of zip file for other PProg files
WELCOME TO PARADOX FOR WINDOWS
------------------------------
This file contains important, late-breaking information about Paradox,
including revisions to the documentation. For answers to commonly asked
questions about Paradox, see the HELPME.TXT file in the Paradox system
directory. Information in these files supersedes information in the
Paradox documentation.
TABLE OF CONTENTS
-----------------
1. Contacting Borland
2. TUTILITY Notes
3. Documentation Notes
1. CONTACTING BORLAND
---------------------
If you have any problems, please read this file, the HELPME.TXT file, and
the Paradox manuals first. If you still need assistance, see the "Getting
Started" manual for a complete description of the different services
Borland offers. For your convenience, the contact information is
summarized below.
TechFax
-------
U.S. and Canada 800-822-4269 (voice)
File Download BBS
-----------------
U.S. and Canada 408-439-9096
Australia 02-911-1024
Online Information Services
---------------------------
CompuServe GO BORLAND
BIX JOIN BORLAND
GEnie BORLAND
Paradox Automated Support
-------------------------
U.S. and Canada 800-524-8420 (24-hour voice response system)
Paradox Technical Advisor
-------------------------
U.S. only 900-555-1000 (voice)
Customer Service
----------------
U.S. 408-461-9000 (7 a.m. to 5 p.m. Pacific time)
Canada 416-229-6000
U.K. 0734 321150
Australia 02-911-1033
2. TUTILITY NOTES
-----------------
TUTILITY checks a Paradox table for damage and rebuilds it if
necessary. Paradox tables can be damaged by power failures, hardware
failures, bad network cards or connections, removing a floppy disk
that Paradox is accessing, or rebooting the system while Paradox is
active in memory. You should always make regular backups of your
important data.
To start TUTILITY, type TUTILITY at the DOS prompt, then press
[Enter]. If you installed Paradox in the PDOXWIN directory, you can
also start TUTILITY from its icon in the Paradox for Windows group.
If you installed to a different directory, you have to edit
TUTILITY.PIF before you can start TUTILITY from its icon.
Additional instructions and a description of program options are
provided in the TUTILITY.DOC file. Online help is also available when
you run the program. Command-line help is available by typing
TUTILITY -help.
3. DOCUMENTATION NOTES
----------------------
This section of the README file contains new information and revisions
to the Paradox manuals.
"Getting Started"
-----------------
- Your SHARE.EXE command (in either your AUTOEXEC.BAT or your
CONFIG.SYS) should include these optional parameters:
SHARE /F:4096 /L:400
The /F parameter allocates file space for the DOS storage area used
to record file-sharing information. The default value is 2048. The /L
parameter sets the number of files that can be locked at one time. The
default value is 20.
- The following command-line options have been added to Paradox:
-n Do not write changes to WIN.INI. When you exit Paradox, the names
of the working directory and the private directory are written to
WIN.INI. Use -n to prevent this. You can place -n in the FLAGS=
line of the [PDOXWIN] section of WIN.INI. If you do this and need to
save changes to WIN.INI, you can override the -n option by starting
Paradox with the -y option. For more information about starting
Paradox with command-line options, see Chapter 14 in "Getting
Started."
-y Do write changes to WIN.INI
-e Prevents Paradox from writing changes to PDOXWIN.INI and
PDOXWORK.INI. This option is useful for developers who require
specific settings in these files.
-f Lets Paradox writes changes to PDOXWIN.INI and PDOXWORK.INI. This
option overrides -e if is placed in the FLAGS= line in the [PDOXWIN]
section of WIN.INI.
-s Prevents users from resizing the Desktop. This option starts Paradox
without a resizable window border. It does not prevent the window
from being resized by ObjectPAL applications.
-t Lets users resize the Desktop. This option can be used to override -s
if it is placed in the FLAGS= line in the [PDOXWIN] section of
WIN.INI.
- When starting a second instance of Paradox from a second Paradox icon,
use the -n command-line option (which prohibits Paradox from saving
private and working directory settings in the WIN.INI file) and the
-p option (which lets you choose a different private directory).
- If you are accessing a table on a network, you must close the table
before you log off the network.
"User's Guide"
--------------
- When you export data to or import data from an ASCII file, your date,
numeric, and currency fields use the settings from your Windows Control
Panel.
- If a Windows file association already exists for a .DBF or .QBE file,
Paradox will overwrite it during installation.
- Under certain conditions in a multiuser environment, forms bound to
unkeyed (unindexed) tables may lose track of the current record during
a lengthy operation. You can avoid this situation entirely by using
keyed tables.
- You must supply the full path name (not an alias) for the Answer table
specified in the Properties|Answer Table|Options dialog.
"ObjectPAL Reference"
---------------------
- p. 227 isFromUI returns TRUE only for the first KeyEvent generated by a
keypress; for subsequent events or actions, isFromUI returns FALSE.
For example, when the user presses a key it generates a KeyEvent which
Paradox may translate into one or more events or actions; however,
isFromUI returns TRUE only for the first KeyEvent (the one generated
by the user).
- New method/procedure for the Form type: getFileName( ) String. As a
method, it returns the file name of the associated form. As a procedure
it returns the file name of the current form.
- New method for the TableView type: moveToRecord( tc TCursor ) Logical.
Makes a table view point to the current record of a TCursor.
- Keywords associated with specific types are described in Chapter 4,
"Object type reference." For example, CREATE, INDEX, and SORT act on
tables, so they're described in the Table section.
- The CREATE, INDEX, and SORT structures are not available from the
Methods dialog box or from the Language|Keywords menu. Refer to the
Table section of the "ObjectPAL Reference" for information about these
structures.
- Do not call a DynArray removeItem or empty method to modify a dynamic
array when iterating over it in a forEach loop.
- The following ObjectPAL methods and procedures are not documented
but are available in the Database type:
- setQueryRestartOptions (const qryRestartType SmallInt) Logical
Specifies the behavior of queries in a multiuser environment, where
qryRestartType is one of the following:
QueryLock SmallInt Acquires a write lock on the table
before executing a query.
QueryNoLock SmallInt Does not lock the table and ignores
changes to it during a query.
QueryRestart SmallInt Restarts a query if a change to the
table occurs during the query.
QueryDefault SmallInt Uses the query restart option specified
in the Properties|Restart Options
dialog box.
- getQueryRestartOptions () SmallInt
Returns the value established by setQueryRestartOptions.
"ObjectPAL Developer's Guide"
-----------------------------
- p. 193 The position coordinates for a dialog box are
calculated with respect to the screen; however, the
position coordinates for a form are calculated with
respect to the Paradox Desktop. The position coordinates
of dialog boxes are calculated with respect to the screen
because dialog boxes are not MDI children.
- Under certain conditions in a multiuser environment, unkeyed
(unindexed) tables may lose track of the current record during a
lengthy operation. If you're using a TCursor, you can call currRec to
make sure you're working with the current record. You can avoid this
situation entirely by using keyed tables.
- When you use ObjectPAL to place a primary index on an existing table
that is either on a network drive or accessed with local share on, you
must create a maintained index.
WELCOME TO PARADOX FOR WINDOWS 4.5
----------------------------------
This file contains important, late-breaking information
about Paradox, including revisions to the documentation.
This README is one of five online files included with
Paradox. You'll find additional information in these files:
File Contains
---- --------
UPGRADE.TXT New features of the interactive Paradox
product.
NEWPAL.DB A Paradox table containing new and enhanced
ObjectPAL methods, procedures, and
properties. This table also contains SQL-
specific ObjectPAL methods. See the "Using
NEWPAL.DB" section of UPGRADE.TXT for details
on working with this table.
HELPME.TXT Tips and techniques for working with Paradox.
SETTINGS.TXT An explanation of .INI file settings.
UPGRADE, HELPME, and README, are included as icons in your
Paradox for Windows 4.5 Windows group. To open SETTINGS, use
the text editor of your choice.
TABLE OF CONTENTS
-----------------
1. Installation Information
2. Documentation Errors
3. Deleting Optional Software
4. TUTILITY Notes
5. QuickStart Labels Upgrade
1. INSTALLATION INFORMATION
---------------------------
- If you install Paradox on a machine that has a VGA
driver, but is using a monochrome display, the check
boxes on the Installation dialog box do not paint
correctly. You can assume that all check boxes are
checked by default.
- If you install Paradox for Windows 4.5 as a part of the
Borland Office suite, you can disregard the CAUTION
statements on pages 2 and 33 of the Borland Office
Getting Started booklet.
- If, during the installation process, the Install program
attempts to overwrite a file that has the DOS Read-Only
attribute, Paradox returns you to the Installation dialog
box without completing the installation. You must remove
the Read-Only attribute before attempting to install
again.
2. DOCUMENTATION ERRORS
-----------------------
- The Paradox for Windows printed documentation does not
reflect new features and changes in Paradox. See the
UPGRADE.TXT and NEWPAL.DB files for details on new or
enhanced features.
"Getting Started"
-----------------
- You must run DOS SHARE if you want to use multiple
instances of Paradox or ODAPI clients (such as the
Workgroup Desktop or the Database Desktop included with
Quattro Pro for Windows.) If you do not run SHARE in this
situation, the second instance will not load.
The SHARE.EXE command (in either your AUTOEXEC.BAT or
your CONFIG.SYS) should include these optional
parameters:
SHARE /F:4096 /L:40
The /F parameter allocates file space for the DOS storage
area used to record file-sharing information. The default
value is 2048. The /L parameter sets the number of files
that can be locked at one time. The default value is 20.
"User's Guide"
--------------
- The field _Invariant Field ID in the STRUCT.DB table is
used internally by Paradox to identify fields for use in
associated design documents.
- When you export data to or import data from an ASCII
file, your date, numeric, and currency fields use the
settings from your Windows Control Panel.
- If a Windows file association already exists for a .DBF
or .QBE file, Paradox will overwrite it during
installation.
- Under certain conditions in a multiuser environment,
forms bound to unkeyed (unindexed) tables may lose track
of the current record during a lengthy operation. You can
avoid this situation entirely by using keyed tables.
- Page 57: The paragraph describing the write lock states
"Other users can place a read lock on a table that you
have a write lock on." It should state "Other users can
place an open lock on a table that you have a write lock
on."
- When designing a graph in the Report Design window, the
Data Type option is not available from the Define Graph
dialog box.
"ObjectPAL Reference"
---------------------
- AnyType:unAssign() does not return a value. The correct
syntax is unAssign().
3. DELETING OPTIONAL SOFTWARE
-----------------------------
After installing and becoming familiar with Paradox, you
might decide to delete some of the optional software
components (such as sample files). The following table shows
what files you can delete and where they are located. This
table assumes you accepted the default locations when you
installed Paradox.
To remove Delete Directories Delete Files
--------- ------------------ ------------
Sample files (used in C:\PDOXWIN\SAMPLE All
examples in "Getting
Started" and the "User's
Guide"
ObjectPAL sample files C:\PDOXWIN\EXAMPLES ADDRESS.*
CHECKS.*
CUST.*
LETTERS.*
PDXPAINT.*
RASTEROP.*
SLOTS.*
XXX.*
SQL Tools C:\PDOXWIN\EXAMPLES SQL*.*
The ObjectPAL sample C:\PDOXWIN\DIVEPLAN All
application
The Workgroup Desktop C:\OBEX All
engine (OBEX)
Stored Workgroup C:\OBEX\OBJSTORE All
Desktop files
Workgroup Desktop C:\PDOXWIN\ADDRESS All
address information
Workgroup Desktop C:\PDOXWIN\WORKGRP All
program files
4. TUTILITY NOTES
-----------------
TUTILITY checks a Paradox table for damage and rebuilds it
if necessary. Paradox tables can be damaged by power
failures, hardware failures, bad network cards or
connections, removing a floppy disk that Paradox is
accessing, or rebooting the system while Paradox is active
in memory. You should always make regular backups of your
important data.
To start TUTILITY, type TUTILITY at the DOS prompt, then
press [Enter]. If you installed Paradox in the PDOXWIN
directory, you can also start TUTILITY from its icon in the
Paradox for Windows group. If you installed to a different
directory, you have to edit TUTILITY.PIF before you can
start TUTILITY from its icon.
Additional instructions and a description of program options
are provided in the TUTILITY.DOC file. Online help is also
available when you run the program. Command-line help is
available by typing TUTILITY -help.
5. QUICKSTART LABELS UPGRADE
-----------------------------
If you purchased Borland's QuickStart Labels package, for
use with Paradox for Windows 1.0, please call Borland
Customer Support at (408) 461-9000 for an upgrade.
-----------------------END-------------------------
WELCOME TO BORLAND PARADOX ENGINE 3.0 & DATABASE FRAMEWORK
----------------------------------------------------------
This file contains important, late-breaking information about Paradox
Engine 3.0 & Database Framework. For tips on using the Engine or Database
Framework, see the HELPME.TXT file in the Paradox Engine directory.
Information in these files supersedes the Paradox Engine 3.0 & Database
Framework documentation.
For sample programs, see the PXENG30\C\EXAMPLES and PXENG30\PASCAL\EXAMPLES
directories.
TABLE OF CONTENTS
-----------------
1. Contacting Borland
2. Documentation Revisions
1. CONTACTING BORLAND
---------------------
If you have any problems, please read this file, the HELPME.TXT file, and
the Paradox Engine 3.0 & Database Framework manuals first. If you still need
assistance, see the Paradox Engine 3.0 "User's Guide" manual for a complete
description of the different services Borland offers. For your convenience,
the contact information is summarized below.
TechFax
-------
U.S. and Canada 800-822-4269 (voice)
File Download BBS
-----------------
U.S. and Canada 408-439-9096
Online information services
---------------------------
CompuServe GO BORLAND
BIX JOIN BORLAND
GEnie BORLAND
Technical Support
-----------------
U.S. and Canada (6 a.m. to 5 p.m. Pacific time):
C/C++ 408-461-9133
Pascal 408-461-9177
Technical Advisor
-----------------
U.S. and Canada (6 a.m. to 5 p.m. Pacific time):
C/C++ 900-555-1002
Pascal 900-786-6080
Customer Service
----------------
U.S. and Canada (6 a.m. to 5 p.m. Pacific time):
408-438-5300 (voice)
2. DOCUMENTATION REVISIONS
--------------------------
In the Database Framework "Reference" and "Quick Reference" manuals, the
getFieldDesc member function of the BDatabase class should be called
getDescVector.
为阅读方便，请在［编辑］菜单中选择‘自动换行’选项。 ****************************************** * Microsoft Excel 5.0 中文版使用注意事项 * ****************************************** ㈠ Microsoft Excel 5.0 中文版为适合中国国情所做的改进 ———————————————————————————— 一、货币符号 在 Microsoft Excel 5.0 中文版中，可采用符合国标GB2312的人民币符号（￥）作为广泛使用的货币符号。 1、使用全角人民币符号：在所提供的数值格式中有提供。如果用户需自己定义数值格式，请按 Microsoft Windows 中文版提供的输入方式进行。 2、使用半角人民币符号：在选用中文字体，如宋体等格式化文字时，会自动将其中半角的美元符号（$）显示成半角的人民币符号（￥）。 3、调整人民币符号的位置：在设置数字格式时，如果要调整人民币符号的位置，请在 Microsoft Windows 中文版的［控制面板］的［国别设定］中进行设置。 4、在使用公式时，半角的美元符号（$）表示的是绝对引用。如果我们将单元格中的文字用中文字体格式化，则单元格中公式内的 $ 会以人民币符号显示；但编辑栏中的 $ 显示仍然不变。在这种情况下，公式的任何功能均不会受影响，系统仍将其当做 $ 进行处理。 二、日期与时间 Microsoft Excel 5.0 中文版内部提供 6 种表示日期和时间的描述格式： yyyy"年"m"月" m"月"d"日" yyyy"年"m"月"d"日" h"时"mm"分" h"时"mm"分"ss"秒" 上午/下午h"时"mm"分" 上午/下午h"时"mm"分"ss"秒" 三、自动填充序列 Microsoft Excel 5.0 中文版根据中国的传统习惯，预先设有： 日，一，二，三，四，五，六 星期一，星期二，星期三，星期四，星期五，星期六 一月，二月，....，十二月 第一季度，第二季度，第三季度，第四季度 正月，二月，....，十二月 子，丑，寅，卯，....， 甲，乙，丙，丁，....， 注意：在输入自定义的序列时，序列中的每一项之间必须用半角的逗号（,）作为分隔符。 四、使用中文字体的建议 考虑到中文字的特点，我们建议用户使用 12 或 9 点的字作为标准字体。这样，用户可以得到最佳的显示效果。在［工具］［选项］中的［普通］对话框中可以设置。 五、中文排序 Microsoft Excel 5.0 中文版提供的中文排序功能，是以加载宏的形式提供的，用户需安装后方能使用。 中文排序的规则与英文排序相同。在此，我们提供按拼音和笔画两种排序方式。 注：按拼音排序并不只局限于第一级字库。 六、文字对齐方式 Microsoft Excel 5.0 中文版根据中文字的特点，新增加了“分散对齐”的对齐方式，它使单元格内的各字均匀分布到单元格所限定的范围中。另外，为此对齐方式还专门设一选项“增加缩格”，可在分布时在其头尾加上相应的空格，使其效果更加美观。 ㈡、Microsoft Excel 5.0 中文版的键位使用问题 ——————————————————————— 在 Microsoft Windows 3.1 中文版系统下运行 Microsoft Excel 5.0 中文版，必须考虑到键位的问题。Windows 3.1 中文版运用 Ctrl+Shift 和 Ctrl+Space 作为中文输入法的切换键；但是，在 Excel 5.0 中也同样需要这些键作为快捷键完成一些操作。一般情况下，Windows作为操作系统会抢占这些键位。为解决这种冲突，可将 Windows 的［控制面板］［输入方法］中的“使用左边键切换输入方法”选项关掉。这样，中文输入法的切换只使用右边键；而作为应用程序的 Excel 则使用左边键进行相应的操作。 ［结束］
Microsoft Excel 3.1 的特別資訊
CVGA 驅動程式
一個更新版的 video 驅動程式（CVGA.DRV）已被複製到 EXCEL 的
目錄中。如果您所使用的是 VGA 顯示器，請將此檔案複製到 Windows
下的 SYSTEM 目錄中以取代目前所存在的 CVGA.DRV 檔案。
目錄:
--------------------------------------
1. 新增功能部份簡介
2. Microsoft Excel 3.1 的檔案相容性
3. Microsoft Excel 3.1 與 WIN.INI
4. 啟動時自動載入文件
5. 指定替代的啟動目錄
6. 產生隨機亂數
7. 預設字型
---------------------------------------
1. 新增功能部份簡介
新增圖形樣式 (詳細資料,請參考Microsoft Excel使用手冊)
水平長條圖 三種
垂直長條圖 二種
折線圖 一種
雷達圖 五種
組合圖 一種
新增數字格式 (詳細資料,請參考Microsoft Excel使用手冊)
鍵入數值: 11/20/91
格式 顯示
-----------------------------------------------
dddd 星期三
e/m/d 80/11/20
e年m月d日 80年11月20日
yyyy年m月d日 1991年11月20日
h時mm 11時15分
h時mm分ss秒 11時15分35秒
上午/下午h時mm分 上午11時15分
上午/下午h時mm分ss秒 下午11時15分35秒
新增函數部份(詳細資料,請參考Microsoft Excel函數參考手冊)
ASC(text)
BIG5(text)
DOLLAR(number,decimals)/USDOLLAR(number,decimals)
FINDB(find_text,within_text,start_num)
REPLACEB(old_text,start_num,num_bytes,new_text)
SEARCHB(find_text,within_text,start_at_num)
MIDB(text,start_num,num_bytes)
LENB(text)
LEFTB(text,num_bytes)
RIGHTB(text,num_bytes)
ROUNDUP(number,num_digits)
ROUNDDOWN(number,num_digits)
DB(cost,salvage,life,period,month)
RANK(number,ref,order)
其他新增部份
新增便捷鍵:
按鍵組合 顯示
------------------------------------------
CTRL+SHIFT+$ NT$
CTRL+; 輸日當天日期
* 文字工具鈕提供正確的處理中文/英文字的直行排列功能,(您可任意
使用搜尋/替換,資料匯入剖析,文字編輯等功能).
* 中文字是以內碼(Big 5)順序做排序準則.
* 中文Lotus 2.2RT版資料轉換.
* PC Works資料轉換.
* 要使用[格式][段落重排]功能重排中文時,請先將在中文版程式庫內附的
FMTJUST.XLA ADD-IN 巨集指令安裝到 Excel 3.1 內.
(安裝方式請參考 Microsoft Excel 中文版程式庫手冊).
-----------------------------------------------------------------
2. Microsoft Excel 3.1 的檔案相容性
中文版的 Microsoft Excel 3.1 可讀取美國版的 Microsoft
Excel 3.0 的所有文件，但不應使用任何 Microsoft Excel 3.0 的
版本來開啟以Microsoft Excel 3.1 的格式所儲存的文件。若要用
美國版 Microsoft Excel 3.0 來開啟 Microsoft Excel 3.1 的文件，
則在儲存 Microsoft Excel 3.1 的文件時，使用「檔案」「另存
新檔」指令，並選取「US Excel」格式。
附註：以此格式儲存的文件，可能會遺失一些格式設定。
----------------------------------------------------------------
3. Microsoft Excel 3.1 與 WIN.INI
Microsoft Excel 3.1 使用與 WIN.INI 同目錄中的 EXCEL.INI 檔案，
來自訂啟動時所需的設定。
EXCEL.INI 是一文字檔，您可用任何文字處理程式進行編修，修改後
也必須用文字檔儲存，不可含任何格式設定。使用 Microsoft Excel
3.1 並不需要編修 EXCEL.INI。若做了編修，您必須重新啟動
Microsoft Excel，才能使所做的修改生效。
安裝 Microsoft Excel 3.1 時，安裝(SETUP)程式會自動在 WIN.INI
所在的目錄內建立 EXCEL.INI，安裝程式也會在您安裝 Microsoft
Excel 的磁碟機與目錄內，另建立一個 EXCEL.INI 檔案。
** 在安裝目錄內的 INI 檔案，僅供網路系統使用，所以不應被修改，
若要修改 INI 檔案，則修改在 Windows 目錄內的 INI 檔案。
---------------------------------------------------------------
4. 啟動時自動載入文件
您可用下列兩種方法，使 Microsoft Excel 在啟動時自動載入文件：
(1)修改 EXCEL.INI 中 OPEN= 的敘述句，在 EXCEL.INI 中加上
OPEN=filename，可使 Microsoft Excel 每次啟動時，自動
載入該檔案(任何 EXCEL 文件或文字檔)。
(2)將檔案置於 XLSTART 次目錄內。安裝 Microsoft Excel 時，
會自動建立次目錄 XLSTART。Microsoft Excel 啟動時自動載
入此目錄內的所有檔案。
--------------------------------------------------------------
5. 指定替代的啟動目錄
指定替代的啟動目錄，請執行 Add-in 巨集 ALTSTART.XLA。在安裝
Excel 時若選取「巨集程式庫檔案」選項，這個巨集會複製到您的硬
磁碟機中。安裝程式將所有的巨集程式庫檔案置於次目錄 LIBRARY
內，而 LIBRARY 則置於安裝 Microsoft Excel 3.1 時您所指定的次
目錄內。
-------------------------------------------------------------
6. 產生隨機亂數
若您要 Microsoft Excel 3.1 在同一執行期間，產生不同的隨機
亂數，則在 EXCEL.INI 中 [Microsoft Excel] 之下加上：
randomize=1
-----------------------------------------------------------
7. 預設字型
更改新工作表所使用的預設字型及大小，請在 EXCEL.INI 中
[Microsoft Excel] 加上 字型= 的敘述句，格式如下：
字型="字型名稱,字型大小"
例如： 字型=Helv,10
字型名稱必須與 Microsoft Excel 3.1 「格式」「字型」對話
方塊所列示的字型名稱完全相同。在 Microsoft Excel 3.1 中，
字型= 的敘述句設定了用於「一般」(NORMAL)樣式的預設字型，以
及用於欄名列號及「資訊」視窗文字的字型。
更多有關 Microsoft Excel 3.1 列印及網路的資訊，請參閱
PRINTER.TXT 或 NETWORK.TXT，這兩個檔案都在安裝目錄內。
RELEASE SHEET for CBTREE Version 2.30
Revised 11/01/87
This document describes the changes which you must make to your source code
in order to upgrade from version 1.3x to version 2.x. BACKUP ALL YOUR SOURCE
AND INDEX FILES BEFORE PROCEEDING!
1. btrinit() now allocates memory for btcommo.btkey. This means you should
not do this. The number of bytes allocated is btcommo.btkeylen + 1.
btcommo.btkeylen is defined by BTSETUP.EXE.
2. A new function btrterm(&btcommo) has been added to de-initialize your
B+tree. It currently releases memory allocated for btcommo.btkey and
btcommo.btrecnum. You should call this function instead of directly
freeing btcommo.btkey. This function will have increased functionality
in future releases. Therefore it is very important to start using the
btrinit()/btrterm() function pair.
3. btcommo.btrecnum used to be an array of MAXARRAY longs. It is now a
pointer to a dynamically allocated memory block which is allocated in
btrinit(). The number of bytes allocated is:
sizeof(long) * (btcommo.btmax + 1).
btcommo.btmax is defined in BTSETUP.EXE as the field Max Recs. The main
impact of this on your source is that all occurrences of MAXARRAY-1 should
be replaced with btcommo.btmax.
4. GETSEQ, GETALL and the new function GETKEYS often need to be called
several times in sequence before the entire index has been scanned. These
functions now maintain internal variables which remember the state of the
function between calls. This means:
o Improved performance,
o the original key no longer has to be re-loaded between calls
(although this will have no harmful effect),
o the functions *MUST* be called repeatedly until a less than full
block is returned (fewer than btcommo.btmax record numbers were
returned), or BTNOTFND was returned. If the calling sequence is to
be terminated before one of these conditions is met, the function
free_svkey(&btcommo) *MUST* be called. This is in order to reset the
internal variables. Not doing this may be dangerous to the health of
your B+trees.
Version 2.10:
5. The CBTREE NULL key value has been changed from three 7F's to a single 7F
in order to support key lengths of less than 3 characters. This means
that the first character of all keys must be between 0x01 and 0x7e
inclusive. This is typical for ASCII keys.
6. The source file 'btgiver.c' has been renamed to 'giveidxr.c'.
7. The external variable 'freespc' has been removed. The functions which
used 'freespc' have therefore been modified to receive 'freespc' as a
parameter. These include:
putfhdr(fd, freespc) and getfhdr(freespc, fd).
This is of importance only to those users who use these lower level
functions.
8. A macro btseek() has been added to cbtree.h. This is useful in seeking
to a record specified by btcommo.btloc. The usage of the macro is:
btseek(fd, btloc, reclen).
For example, after calling GETREC for a given key, you would call:
btseek(fd, btcommo.btloc, btcommo.btdatlen);
to seek to the desired record. btseek() takes care of the "record
location minus one" arithmetic for you. See getfpat.c for a simple
example on the use of btseek().
IMPORTANT NOTE: The btcommo.btloc return value may change in a future
release. We therefore recommend that you start using
btseek() so that this possible future change will
be transparent to your source code.
9. A new function bt_open() has been added to support the new file
protection mode paramters of the open() function. bt_open() also
maintains compatibility with older compilers. You should use bt_open()
instead of open() to open ALL your data and index files, especially
at places where a new file may be created. See btfio.h for more
information. See bld2keys.c for an example on how to use bt_open().
Version 2.11:
10. A new utility CHKBTREE.C has been added and performs integrity checks on
the specified B+tree index file.
11. Bug fix for GETALL and GETKEYS: if the final call to a series of GETALL
operations happened to exactly fill the btcommo.btrecnum block, then
the NEXT call to GETALL/GETKEYS would not return BTNOTFND, as it should
have. Now it does.
12. A buffer-full check in getidxr() allowed 4 bytes too many to be read into
the buffer. This has now been fixed.
13. Reminder: the cbtree() error messages are stored in the file
"ckerror.msg." If you would like verbose error messages to be displayed,
instead of just numerical codes, keep a copy of this file in the current
directory. Error messages will also get written to the file "error.fil"
when they occur.
Version 2.20:
14. Version 2.20 allows multiple B+trees to be stored in a single index file.
In order to support this enhancement, several changes have been made to
the CBTREE library functions as well as the support utilities:
o BTSETUP.EXE has a new field for the Index File Name. The default
name will be your B+tree Name plus the extention ".idx". The TBA
field should be left zero for now. If you desire multiple
B+trees to reside in the same Index File, then you should specify
the SAME Index File Name for ALL the B+trees that are to be
contained in it. BTSETUP.EXE now has a Delete function to allow
you to delete a particular B+tree entry.
o BTPARMS.BTR has an expanded structure. BTSETUP.EXE should be run
for each of your B+trees to update the BTPARMS.BTR file. Each of
your B+tree entries should be "edited," then the resulting new
settings should be saved. This is to make your parameter file
compatible with the changes made to support multiple B+trees in a
single index file.
o btrinit() has been enhanced to use the new information in the
BTPARMS.BTR file. In particular, btrinit() now initializes the
new btcommo structure member "idxname" with the Index File Name
which you speicified in BTSETUP.EXE. We urge to refer to
your index file names through btcommo.idxname, as when you
bt_open() your index files.
o If creatbtr() is called, it should be called IMMEDIATELY
following the corresponding call to btrinit(), and BEFORE any
subsequent calls to btrinit(). This is extremely important when
multiple B+trees are contained in a single index file.
o creatbtr() now only takes a single parameter (the address of the
btcommo structure), since the second parameter (the Index file
Name) is now included in the btcommo structure.
creatbtr() has been substantially modified for use with multiple
B+trees in a single index file. Previously, creatbtr() would
always truncate an existing index file and initialize it with a
single empty root node. Since there may be mutiple B+trees in an
index file, creatbtr() CANNOT now truncate the file without
destroying the other B+trees as well. If more than one B+tree
already exists in a given index file, creatbtr() will now delete
ONLY those nodes belonging to that B+tree. This process can take
several moments and it is therefore recommended that you develop
an application (if possible) using separate index files for each
B+tree. After development you can easily place all your B+trees
in a single index file. See Bld2keys.c which supports both
methods.
Version 2.21:
15. The portable file opening function bt_open() now supports the O_CREAT
mode flag. Normally O_NEW is used to specify a new/empty file.
O_CREAT will leave an existing file untouched.
16. All modules which use bt_open() should include the CBTREE file I/O
header "btfio.h".
17. The error reporting function ckerror() now uses low-level file
descriptors to write to ERROR.FIL. This means that the CBTREE Library
proper now has NO EXPLICIT references to FILE streams. The library
still has implicit references 'stdout' via calls to printf(), etc., but
these can easily be removed without effecting the functionality of the
library.
18. Support added for Ecosoft C compiler and Amiga Manx compiler. Special
thanks to David E. Holt for his work in porting to the Amiga Manx
compiler.
Version 2.30:
19. This version adds support for variable length records. The support
functions are in the file btvarlen.c. With a few exceptions, variable
length records opereate the same way as fixed-length records. The
support programs have all been modified (as applicable) to use a sample
variable length data file. Simply invoke the program with the "-v"
option and it will use the variable length database. In particular:
o BLD2KEYS -v -- build a working database w/ two keys
o USERBTR -v -- interactive demonstration
o BLDBTREE -v -- rebuilds the primary B+tree
o CBTRSEQ -v -- goes "inside" the B+tree for sequential keys
o TIMECB5 -v -- sample CBTREE operation timing suite
20. To invoke variable-length records, specify a Data Record Length of 0
(zero) in BTSETUP.EXE. Make sure ALL indexes for a given data file
agree!
21. Bld2keys.c is now especially well commented and is a good starting point
for looking into variable length records.
22. A new function initdat(fd, &btcommo) has been added to the library which
will automatically initialize your data file header record. It will
work properly for both fixed- and variable-length records.
23. Before calling INSERT, btcommo.btdtalen must be set to the length of
your (variable-length) record. This is only required for the INSERT
operation, and when using variable-length records.
24. The macro btseekv(fd, recloc, recsiz) has been added to cbtree.h for use
with variable length records. It is designed to be compatible with
btseek().
25. The functions in getfpatv.c and putfpatv.c (c.f. getfpat.c and
putfpat.c) demonstrate getting and putting variable-length records.
26. Two varaible length record functions will be directly needed by your
application:
o btsizvar(fd, recloc), and
o btnxtvar(fd, recloc).
btsizvar() will return the size of the record at the specified record
location. You will need to call this function before reading your
record so you know how much to read.
btnxtvar() will return the location of the next record after the given
one. If the 'recloc' is 1L (an "illegal" record location), it will
return the location of the FIRST record. This function can be used for
scanning your data base or re-indexing. See bldbtree.c for an example.
27. The program MKCBTREE.EXE has been renamed to MAKBTREE.EXE.
28. The program CKBTREE.EXE has been renamed to CHKBTREE.EXE.
29. The program DELBTREE.EXE has been provided to delete a B+tree from an
index file. If the index file has more than one B+tree, it will delete
only those nodes belonging to the one specified.
SUMMARY:
1. Take out memory allocation calls for btcommo.btkey.
2. Replace calls to free btcommo.btkey with btrterm(&btcommo).
3. Replace occurrences of MAXARRAY-1 with btcommo.btmax.
4. GETSEQ, GETALL and GETKEYS must be called repeatedly until fewer than
btcommo.btmax records are returned. Otherwise free_svkey(&btcommo) must
be called.
5. Declare local version of 'freespc' (where used) and pass as parameter to
getfhdr() and putfhdr().
6. Replace all lseek( fd, (btloc-1) * reclen, 0 ) calls with
btseek(fd, btloc, reclen) invocations.
7. Use bt_open() instead of open(), and include "btfio.h".
8. Keep the error message file "ckerror.msg" in the current directory for
verbose error messages.
9. Run BTSETUP and enter the "edit" mode for EACH of your B+trees. Enter
the proper name for the Index File corresponding to each of your B+trees.
Then [S]ave the new settings. The file BTPARMS.BTR will be updated.
10. Include "btfio.h" in those modules that use bt_open().
11. All calls to creatbtr() (if any) should be placed immediately after the
corresponding call to btrinit() and before any further calls to
btrinit(). This is REQUIRED if you are placing multiple B+trees in a
single index file.
12. Use the function initdat(fd, &btcommo) to initialize your data file
header record.
13. Use btsizvar() to get the size of your variable length data record.
Then use btseekv() to seek to it. Then read it. HINT: since the
record size is embedded in the data file, use btsizvar() only just
before reading the data record. This will reduce overall access time.
NOTE: Run BTSETUP.EXE and specify the value you had for MAXARRAY-1 as
Max Recs. See Appendix B in the manual: you may have to re-index if
Cells Per Index Block is changed by BTSETUP.EXE.