AnsweredAssumed Answered

How to access NFS mounted files via VEE menu system?

Question asked by VRFuser on Jun 24, 1997
Howdy

Here's a seemingly simple item that has me stumped.  What I am
doing is to attempt to access my libraries of VEE functions- existing
on my Unix system- from my PC. I have NFS mounted the Unix file system
and created a symbolic link ( shortcut on the PC running WIN95 )
to my library directory. No problem.

DOS can't deal with any of this, which is no surprise, but no big loss.
(DOS complains about invalid directories when I attempt to cd to them).

Yet, I have no problem navigating to the libraries from
Explorer. Similarly I have no trouble with the "merge" or "open file"
or "save" from within VEE4.01. So it would seem that VEE is making
the correct 32 bit API calls.

However, when I try to merge the files from the VEE menu system
then I get an error that says that the file can't be found, even though
the indicated path is exactly correct and findable via Explorer.

And, when I link the menu file from my unix directory into the
VEE install directory on my PC, then vee doesn't recognize the menu file.
Yet when I copy the exact same file from the unix system into
the local PC directory then the menu file is recognized and incorporated
as is usual.

Seems strange that a "merge" works but teh menu doesn't , given that
all the menu pick does is a "merge" operation.

Has anyone gotten something like this to work?

Any hints?

thanks!

Stan Bischof
stanb@sr.hp.com


----------------------------------------------------------------------
Stan Bischof   Hewlett Packard Company   707-577-3994  stanb@sr.hp.com
----------------------------------------------------------------------

From: "Tom Sanders" <toms@symca.com>
Subject: Re: VRF: How to access NFS mounted files via VEE menu system?
To: hpvxd_xc@hpislsup.lvld.hp.com, Stan Bischof  <stanb@hpnmrsb2.sr.hp.com>


--- On Tue, 24 Jun 1997 15:29:27 -0700 (PDT)  Stan Bischof <stanb@hpnmrsb2.sr.hp.com> wrote:
> Howdy
>
> Here's a seemingly simple item that has me stumped.  What I am
> doing is to attempt to access my libraries of VEE functions- existing
> on my Unix system- from my PC. I have NFS mounted the Unix file system
> and created a symbolic link ( shortcut on the PC running WIN95 )
> to my library directory. No problem.
>
> DOS can't deal with any of this, which is no surprise, but no big loss.
> (DOS complains about invalid directories when I attempt to cd to them).
>
> Yet, I have no problem navigating to the libraries from
> Explorer. Similarly I have no trouble with the "merge" or "open file"
> or "save" from within VEE4.01. So it would seem that VEE is making
> the correct 32 bit API calls.
>
> However, when I try to merge the files from the VEE menu system
> then I get an error that says that the file can't be found, even though
> the indicated path is exactly correct and findable via Explorer.
>
> And, when I link the menu file from my unix directory into the
> VEE install directory on my PC, then vee doesn't recognize the menu file.
> Yet when I copy the exact same file from the unix system into
> the local PC directory then the menu file is recognized and incorporated
> as is usual.
>
> Seems strange that a "merge" works but teh menu doesn't , given that
> all the menu pick does is a "merge" operation.
>
> Has anyone gotten something like this to work?
>
> Any hints?
>
> thanks!
>
> Stan Bischof
> stanb@sr.hp.com
>
>
> ----------------------------------------------------------------------
> Stan Bischof   Hewlett Packard Company   707-577-3994  stanb@sr.hp.com
> ----------------------------------------------------------------------
>

---------------End of Original Message-----------------

Stan,
It all works fine here.  I am running Windows NT 4.0 not 95 which may be the difference.  It could also be
something funny with your NFS software on the PC.  I am running Netmanage Chameleon.

--------------------------------------------------------
Name: Tom Sanders, Symtx (formerly Symmetrix)
Date: 06/24/97    Time: 15:42:09
--------------------------------------------------------


Outcomes