home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Pier Shareware 6
/
The_Pier_Shareware_Number_6_(The_Pier_Exchange)_(1995).iso
/
035
/
ls30hpfs.zip
/
HFSH.MSG
(
.txt
)
< prev
next >
Wrap
OS/2 Message File
|
1994-07-11
|
30KB
|
474 lines
MKMSGF
x!{!~!
&V(/)
*H+K+
<N@Q@T@W@Z@]@`@c@f@i@l@o@r@u@x@{@~@
@KA9B
HZJIK:MMN&Q
U"U%U(U+U.U1U4U7U:U=U@UCUFUIULUOURUUUXU[U^UaUdUgUjUmUpUsUvUyU|U
\{^.a3aLb
c\e_ebeeehekeneqeteweze}e
f"f%f(f+f.f1f4f7f:f=f@fCfFfIfLfOfRfUfXf[f^fafdfgfjfmfpf
hfsh.msg
Cause: The available free memory is less than 512KB, or the
cache size is less than 256KB.
Action: Install more memory in the system, and then start
your machine again.
Cause: The /Cache syntax in the 386 HPFS IFS line in the
CONFIG.SYS file is not valid.
Action: The format of the Cache parameter is /Cache:nnnn, where
nnnn is a decimal number that represents kilobytes.
Correct the Cache parameter in the 386 HPFS IFS line in
the CONFIG.SYS file. The specified cache size will be
used the next time the machine is started. Until then,
the cache size is 20% of available memory.
Cause: The /Heap syntax in the 386 HPFS IFS line in the
CONFIG.SYS file is not valid.
Action: The format of the Heap parameter is /Heap:nnnn, where
nnnn is a decimal number that represents kilobytes.
Correct the Heap parameter in the 386 HPFS IFS line in
the CONFIG.SYS file. The specified heap size will be
used the next time the machine is started. Until then,
the maximum heap size is limited by available memory.
Cause: The /I syntax in the 386 HPFS IFS line in the CONFIG.SYS
file is not valid.
Action: The format of the /I parameter is /I:{path}, where
{path} is the path where you installed OS/2 LAN
Server. Correct the /I parameter in the 386 HPFS IFS
line in the CONFIG.SYS file. The specified path
will be used the next time the machine is started.
Until then, the 386 HPFS assumes your LAN root directory
is C:\IBMLAN.
Cause: The /Autocheck syntax in the 386 HPFS IFS line in the
CONFIG.SYS file is not valid.
Action: The format of the Autocheck parameter is
/Autocheck:{drivelist}, where {drivelist} is a list of
your 386 HPFS drives; for example, /Autocheck:cde.
Correct the Autocheck parameter in the 386 HPFS IFS line
in the CONFIG.SYS file. The list of autocheck drives
will be checked the next time the machine is started.
Until then, only the 386 HPFS boot drive (if one exists)
will be checked.
Cause: A drive letter in /Autocheck that is not valid has been
ignored.
Action: The format of the Autocheck parameter is
/Autocheck:{drivelist}, where {drivelist} is a list of
your 386 HPFS drives; for example, /Autocheck:cde. Valid
characters for {drivelist} are the letters A-Z (or a-z).
The character that is not valid has been ignored.
Correct the Autocheck parameter in the 386 HPFS IFS line
in the CONFIG.SYS file. The valid drive letters have
been autochecked.
Cause: The cache size specified for the 386 HPFS is too small.
The minimum size of 256KB will be used.
Action: Change the /Cache option in the 386 HPFS IFS line in the
CONFIG.SYS file to be 256KB or more. Start your machine
again to make the new cache size go into effect.
Cause: The cache size specified for the 386 HPFS is too large.
A default of 50% of available memory will be used.
Action: Change the /Cache option in the 386 HPFS IFS line in the
CONFIG.SYS file to a value less than what it currently
is. Start your machine again to make the new cache size
go into effect.
Cause: The cache size specified for the 386 HPFS is too large.
A default of 20% of available memory will be used.
Action: Change the /Cache option in the 386 HPFS IFS line in the
CONFIG.SYS file to a value less than what it currently
is. Start your machine again to make the new cache size
go into effect.
Cause: The heap limit size specified for the 386 HPFS is too large.
A heap limit size of 64KB will be used.
Action: Change the /Heap option in the 386 HPFS IFS line in the
CONFIG.SYS file to a value less than what it currently
is. Start your machine again to make the new heap limit
size go into effect.
Cause: The heap limit size specified for the 386 HPFS is too
small. A heap limit size of 64KB will be used.
Action: Change the /Heap option in the 386 HPFS IFS line
in the CONFIG.SYS file to be 64KB or larger. Start your
machine again to make the new heap limit size go into
effect.
Cause: There is not enough memory for both the 386 HPFS cache
and the heap.
Action: You can reduce the amount of memory being used by your
system. To do this:
- Change the amount of memory you have configured for
your device drivers to use.
- Do not use device drivers that consume large amounts
of memory.
You can also add more memory to your machine.
Start your machine again after you have obtained more
memory or reduced the amount of memory being used.
Cause: An option that is not valid exists in the 386 HPFS IFS
line in the CONFIG.SYS file.
Action: The option displayed in the error message was found in
the 386 HPFS IFS line in the CONFIG.SYS file, but it is
not a valid 386 HPFS option. It has been ignored.
Remove the option from the 386 HPFS IFS line in the
CONFIG.SYS file.
Cause: The file system driver file name specified in the
386 HPFS IFS line was not found in the specified path or
in the NETPROG subdirectory of the specified LAN root
directory (/I option).
Action: The file system driver (FSD) file name normally is
HPFS200.386 and is specified as such in the CONFIG.SYS
file:
IFS=C:\IBM386FS\HPFS386.IFS C:\IBM386FS\HPFS200.386 ....
Ensure that the 386 HPFS FSD file is in the directory
that matches the IFS line in the CONFIG.SYS file. If
you cannot locate the FSD file, install OS/2 LAN
Server again.
Cause: The file system driver file name specified in the
386 HPFS IFS line was found, but it is damaged and
cannot be used.
Action: The file system driver (FSD) file name normally is
HPFS200.386 and is specified as such in the CONFIG.SYS
file:
IFS=C:\IBM386FS\HPFS386.IFS C:\IBM386FS\HPFS200.386 ....
Ensure that the 386 HPFS FSD file specified in the IFS
line in the CONFIG.SYS file is the one that was
originally installed. If it is not, install OS/2
LAN Server again.
Cause: You entered information for the /RUNCHKDSK parameter
incorrectly. The format of the /RUNCHKDSK parameter is:
/RUNCHKDSK=nnn
where nnn is a decimal number that is greater than 0. This
is the number of times CHKDSK /F will run on those drives
that are specified by the /AUTOCHECK parameter. CHKDSK /F
will be run once even if this parameter is syntactically
incorrect or if it is not present on the 386 HPFS IFS line.
Action: Correct the parameter and restart the workstation.
Cause: HPFS386 could not access the target drive to determine
if it should run CHKDSK /F on it.
Action: Boot from a diskette and run CHKDSK /F against the drive.
Cause: The drive may be locked or in use by another process, or 386 HPFS
is not installed.
Action: Verify that 386 HPFS is installed and is active.
Either stop all processes that are accessing this drive,
or boot with a 386 HPFS boot diskette and run MMUTIL again
to remove the multimedia format from the drive.
Cause: A disk error occurred while trying to read in the critical sector
indicated.
Action: The HPFS format relies on sectors 16 and 17 to store drive layout
information for the drive. If sectors 16 and 17 cannot be accessed,
no information is available on the drive. Run MMUTIL again. If
the error still occurs, run diagnostics on the physical disk
containing the drive.
Cause: The information read from the indicated sector was not valid.
Action: The HPFS format relies on sectors 16 and 17 to store drive layout
information for the drive. Sectors 16 and 17 do not contain valid
HPFS data. Verify that the drive you are trying to remove the
multimedia format from is an HPFS drive. If the drive is formatted
as HPFS, run CHKDSK to verify that the disk is correct.
Cause: A disk error occurred while trying to write critical sector
information.
Action: The HPFS format relies on sectors 16 and 17 to store drive layout
information for the drive. If sectors 16 and 17 cannot be written,
the multimedia format cannot be removed. Run MMUTIL again.
If the error still occurs, run diagnostics on the physical disk
containing the drive.
Cause: A disk error prevented the multimedia format from being removed.
Action: You can continue to use the drive in the current multimedia format.
No information on the disk has been updated.
Cause: A disk error prevented the multimedia format from being removed.
Action: The HPFS format relies on sectors 16 and 17 to store drive layout
information for the drive. Only sector 16 could be written
successfully. The drive may be in an inconsistent state. Run
CHKDSK to verify that your drive is correct.
Cause: One of the parameters specified on the command line is not a valid
parameter for MMUTIL.
Action: Verify that the parameters are specified correctly.
Cause: The write of a critical sector prevented an upgrade of the drive
to the multimedia format.
Action: Try the operation again. Repeated failures may indicate problems
with the existing disk sectors. Back up the files from the current
drive. Reformat the drive with the desired attributes, and restore
the backed-up files to the drive.
Cause: MMUTIL must run PROFILER when applying the multimedia format to a drive.
MMUTIL could not start the PROFILER utility because of the error
specified.
Action: The error number specified is an OS/2 error number. You can obtain
more help on that particular error by typing HELP SYSxx, where xx
is the error number listed in the original error.
Cause: PROFILER was run, and it detected files that did not meet the
multimedia format requirements. PROFILER could not correct the
problems associated with these files.
Action: You must correct the files that PROFILER listed as not meeting the
requirements. To correct the files, back up the current version of
the file. Delete the current version. Apply the multimedia format
to the drive. Then restore the backed-up version. The new version
will be created with the proper requirements.
Cause: The file listed could not be examined by the PROFILER utility.
Action: The error number specified is an OS/2 error number. You can obtain
more help on that particular error by typing HELP SYSxx, where xx
is the error number listed in the original error.
Cause: The PROFILER utility attempts to create a backup file named
PROFILER.TMP.001 in the same directory as the file it is trying
to correct. The PROFILER utility could not make a copy of
the file being corrected.
Action: The error number specified is an OS/2 error number. You can obtain
more help on that particular error by typing HELP SYSxx, where xx
is the error number listed in the original error.
Cause: The PROFILER utility could not delete the file listed in the
original error message. The PROFILER utility attempts to delete
the original file after making a copy of that file. The PROFILER
attempts to delete the PROFILER.TMP.001 file in case errors
occur after copying, but before deleting, the original file.
Action: The error number specified is an OS/2 error number. You can obtain
more help on that particular error by typing HELP SYSxx, where xx
is the error number listed in the original error.
Cause: The PROFILER utility could not rename the PROFILER.TMP.001 file
to the original file name.
Action: The error number specified is an OS/2 error number. You can obtain
more help on that particular error by typing HELP SYSxx, where xx
is the error number listed in the original error.
Cause: The PROFILER utility attempts to maintain the access control
present on the original file. The NetAccessGetInfo API call used
to obtain the access control information for the file listed
failed because of the LAN Server error listed.
Action: The error number specified is a LAN Server error number.
You can obtain more help on that particular error by typing
HELP NETxx, where xx is the error number listed in the
original error. Failure to obtain the access control
information prevents the file from being corrected. You must
manually correct the file if this is being done as part of the
multimedia format application.
Cause: The PROFILER utility attempts to maintain the access control
present on the original file. The NetAccessSetInfo API call used
to set the access control information for the file listed
failed because of the LAN Server error listed.
Action: The error number specified is a LAN Server error number.
You can obtain more help on that particular error by typing
HELP NETxx, where xx is the error number listed in the original
error. The new version of the file is no longer protected by
the original access control. You must reset the access control
profile that originally existed on this file.
Cause: The PROFILER utility was attempting to correct a file that had a
read-only attribute. PROFILER removes the attribute before
doing the correction and replaces it afterward. The read-only
file attribute could not be changed by the PROFILER utility.
Action: The error number specified is an OS/2 error number. You can obtain
more help on that particular error by typing HELP SYSxx, where xx
is the error number listed in the original error.
If the error occurred before attempting to correct the file,
the file has not been corrected and must manually be corrected.
If the error occurred after correcting the file, the file
no longer has the original read-only file attribute. Run PROFILER
again, specifying the file name that was being corrected, to check
whether the file has been corrected or not.
Cause: The disk driver reported an error reading or writing
to the disk.
Action: Shut down the system, start the computer again, and run
CHKDSK /F on the disk.
Cause: The system was not shut down properly.
Action: Run CHKDSK /F on the disk, or add the disk-drive letter
to the /Autocheck list in the IFS line in the CONFIG.SYS
file and start the computer again.
Cause: Either the 386 HPFS could not find space in the internal
memory heap, or the 386 HPFS could not allocate more
memory from the system to increase the memory heap.
Action: You can increase the maximum amount of memory the 386 HPFS
uses and the amount it preallocates by specifying the
/Heap option in the IFS line in the CONFIG.SYS file.
You can also reduce the amount of memory used in other
areas of the system (for example, reduce the cache size
or run fewer applications), or you can add more memory
to the computer.
Cause: The 386 HPFS received an error from the disk driver
while attempting to access a disk sector.
Action: Run CHKDSK /F soon to restore full performance and
to replenish the spare sector pool for the volume.
Cause: Either the 386 HPFS could not find space in its internal
memory heap, or the 386 HPFS could not allocate more
memory from the system to increase the memory heap.
Action: You can increase the maximum amount of memory the 386 HPFS
uses and the amount it preallocates by specifying the
/Heap option in the IFS line in the CONFIG.SYS file.
You can also reduce the amount of memory used by other
parts of the system (for example, reduce the cache size
or run fewer applications), or you can add more memory
to the computer.
Cause: The 386 HPFS could not access a critical sector on a 386 HPFS
volume. Although corrective measures were taken to maintain
normal operation, the volume may not be accessible once you
restart the machine.
Action: Back up all files and access control profiles on this volume
before turning off the machine. You can use the BACKUP, XCOPY,
and BACKACC utilities to do this. CHKDSK and FORMAT will be
denied access to the volume until the machine is restarted.
Run CHKDSK /F after you restart the machine.
Cause: While attempting to hotfix a defective sector, the 386 HPFS
discovered that the volume had no free hotfix sectors left.
Action: Run CHKDSK /F to allocate new hotfix sectors and restore
performance.
Cause: The 386 HPFS could not access a critical sector on a 386 HPFS
volume. The volume may not be accessible following a restart
of the machine.
Action: Try to back up all files and access control profiles on this
volume. You can use the BACKUP, XCOPY, and BACKACC utilities
to do this. CHKDSK and FORMAT will be denied access to the
volume until the machine is restarted. Run CHKDSK /F after
you restart the machine.
Cause: The disk device driver for this volume does not support
memory above 16MB.
Action: Remove the /USEALLMEM option from the 386 HPFS IFS line
in the CONFIG.SYS file. Start your machine again to make
the change go into effect.
Cause: The 386 HPFS server did not enable directory limits on the
drive because it could not obtain space from its own
memory heap, or the 386 HPFS could not allocate more
memory from the system to increase the memory heap.
The drive is still operational.
Action: You can increase the maximum amount of memory the 386 HPFS
uses and the amount it preallocates by specifying the
/HEAP option in the IFS line in the CONFIG.SYS file.
You can also reduce the amount of memory used by other
parts of the system (for example, reduce the cache size
or run fewer applications), or you can add more memory
to the computer.
Cause: The 386 HPFS server did not enable directory limits on the
drive because it encountered a disk error during a read
operation. The volume is still operational.
Action: Run CHKDSK /F on the volume. If the failure occurred while
you were enabling directory limits, then retry the command.
Otherwise, refresh the DASD information using the
following command:
NET DASD drive /REFRESH
Cause: The 386 HPFS server could not mount the volume because
the volume's format contains extensions that are not
supported by this version of the file system. This
error can occur if a downlevel version of the file
system is used.
Action: Ensure that the proper version of the file system,
HPFS386.IFS, is used.
Cause: Another process has locked the drive. Consequently, file
operations cannot proceed.
Action: Wait until the drive is unlocked.
Cause: The 386 HPFS received a bad-command error from the disk
driver that was possibly caused by memory damage.
Rather than risk further damage to the data on the disk,
the 386 HPFS has stopped the system so that the problem can
be corrected.
Action: Start the computer again and run CHKDSK /F on your
386 HPFS disks. Ensure that your disk driver is
compatible with other system software. Run diagnostics
on the system memory.
Cause: The 386 HPFS ran out of space on the disk for directory
structures and has used up all of the directory
structures set aside for emergency use.
Action: Start the computer again and run CHKDSK /F on your
386 HPFS disks. Archive and delete any unneeded files to
free space on the disks.
Cause: The 386 HPFS was unable to read a critical file-system
structure from the disk. The 386 HPFS cannot continue
without this structure.
Action: Start the computer again and run CHKDSK /F on your
386 HPFS disks. Run diagnostics on the disks to locate
and mark the faulty sectors. If the problem persists,
you may have faulty hardware.
Cause: The 386 HPFS was unable to read a critical file-system
structure from the disk. The 386 HPFS cannot continue
without this structure.
Action: Start the computer again and run CHKDSK /F on your
386 HPFS disks. Run diagnostics on the disks to locate
and mark the faulty sectors. If the problem persists,
you may have faulty hardware.
Cause: The 386 HPFS was not able to write a critical file-system
structure to the disk. Rather than risk further loss of
data or disk damage, the 386 HPFS has stopped further
attempts at using the volume.
Action: Start the computer again and run CHKDSK /F on the
disk. Run diagnostics on the disk to locate and mark
the faulty sectors. If the problem persists, you may
have faulty hardware.
Cause: The 386 HPFS was not able to find space in its internal
memory heap and was not able to allocate more memory
from the system to increase the memory heap.
Action: Start the computer again and run CHKDSK /F on your
386 HPFS disks. You can increase the maximum amount of
heap the 386 HPFS uses and the amount it preallocates by
specifying the /Heap option in the IFS line in the
CONFIG.SYS file. You can also reduce the amount of
memory used in other areas of the system (for example,
reduce the cache size or run fewer applications), or you
can add more memory to the computer.
Cause: The 386 HPFS received an error from the disk driver while
writing to the swapper file after the file system was
already flushed.
Action: No action is necessary. The volume was already flushed,
so no data should have been lost.
Cause: The 386 HPFS was unable to reopen a file opened by the
minifile system driver at boot time. You may have
system software that is mismatched.
Action: Ensure that the version of the HPFS you have is compatible
with the version of the operating system you are
running.
Cause: The 386 HPFS ran out of reserved hotfix sectors on the
disk. Rather than risk further loss of data or disk
damage, the 386 HPFS has stopped further attempts at
using the volume.
Action: Start the computer again and run CHKDSK /F on your
386 HPFS disks. Run diagnostics on the disks to locate
and mark faulty sectors. If the problem persists, you
may have faulty hardware.
Cause: The listed file is not in the specified path.
Action: In order to make a 386 HPFS boot diskette with the
MAKEDISK utility, you must have the listed file in the
specified path. Ensure that the listed file is in the
specified directory and that you have the proper access
to the listed file. Then run the utility again.
Cause: The listed OS/2 error occurred while deleting the listed
file from the diskette.
Action: To get more information about the OS/2 error, type:
HELP message#
where message# is the error code.
Be sure that you have a backup copy of the original OS/2
2.0 Diskette 1 diskette, and then run the utility again.
Cause: The listed OS/2 error occurred while copying the listed
file from the boot drive of your workstation to the diskette.
Action: To get more information about the OS/2 error, type:
HELP message#
where message# is the error code.
Be sure that you have a backup copy of the original OS/2
2.0 Diskette 1 diskette, and then run the utility again.
Cause: The MAKEDISK utility did not work correctly because
of the errors indicated by previous error messages.
Action: Fix the problems indicated by the previous error messages.
Be sure that you have a backup copy of the original OS/2
2.0 Diskette 1 diskette, and then run the utility again.
Cause: The MAKEDISK utility encountered an error while
creating the listed file.
Action: Do one or more of the following:
- Fix any problem indicated by previous error messages.
- Ensure that you have the original MAKEDISK.CFG file on
the hard disk.
- Ensure that the listed file is not write-protected.
- Ensure that you have access to the hard disk.
Ensure that you have a backup copy of the original OS/2
2.0 Diskette 1 diskette, and then run the utility again.
Cause: You have specified an incorrect parameter for the
MAKEDISK utility.
Action: Check the spelling of the parameter. The only valid
parameter for MAKEDISK is as follows:
/BOOTDRIVE:d
where d is the boot drive for the OS/2 program.
The parameter can be abbreviated by using the first
letter.
Cause: The Fault Tolerance configuration for this machine is
specific to this machine. This configuration has been copied to
your 386 HPFS bootable diskettes.
Action: When any changes are made to the disk configuration of
this machine, either by adding new partitions, changing partition
sizes, or changing the mirroring state of any drives, then the
Fault Tolerance configuration for the 386 HPFS bootable diskettes
for this machine needs to be updated. Use MAKEDISK /FT to update
the bootable diskettes.
Cause: Either Fault Tolerance is not activated or the file may be
inaccessible.
Action: If Fault Tolerance is not activated, the bootable diskettes
do not need updating with the Fault Tolerance configuration file.
If Fault Tolerance is activated, verify that the Fault Tolerance
configuration file (C:\FTCFG.SYS) can be located, and run
MAKEDISK /FT again. C:\FTCFG.SYS is a file with hidden and system
attributes. Use attrib -h -s C:\FTCFG.SYS to unhide the file.