Troubleshooting
Troubleshooting
in
an
MS
Windows
environment
2 Attempt a remote NFS mount.
Attempt a remote NFS mount of
the
logic analyzer using File Manager. In
the
Disk
menu
of File Manager, the Network Connections field should appear.
If
this field does not appear, this indicates
that
the
MS
Windows-based NFS
software was not properly installed.
Select a Drive Letter
under
New
Connection.
If
a drive letter does
not
appear,
then
check
the
LASTDRNE= command
in
the
CONFIG.SYS
file.
The
LASTDRNE= command should
be
set
to a drive
letter
that
would make a
disk drive designation available to use as a drive for
the
remote file server
while still allowing
the
last three disk drive designations
to
be available for
printers. For more information about
the
CONFIG.SYS file, refer
to
the
documentation for MS-DOS.
• Normal Response
When Connect is selected, the drive
letter
and
the
mounted
remote
file server should
appear
under
the
Network Drive Connections
window.
• Error Messages
If
error messages appear, then resolve
the
error
messages using
your
NFS documentation.
Check
to
make sure all of the appropriate fields in
the
Network
Connections
menu
have the correct information.
If
all of
the
fields
have correct information, then
refer
to your documentation for NFS
and
for File Manager for more information.
A Device Busy
error
message appears when
you
try
to
mount as
control if someone else has already
mounted
as
control.
An
error message is also received
if
you
try
to
mount
too soon
after
power-up.
You
need
to wait
at
least 15 seconds after
the
Analyzer
Configuration
menu
is displayed before attempting to mount.
7-13
I
To Next Page
Loading...
