[comp.sys.ibm.pc] Novell ignores directory structure!

mark@intek01.UUCP (Mark McWiggins) (04/17/88)

We've been experiencing a weird Novell Netware bug.  It sometimes just
ignores the directory structure completely.  For example, when I remake
a certain program in one of my directories, the program somehow winds
up in another directory *on another disk*!

This only seems to happen when there are two files with the same name
in different directories.  Is anyone else experiencing this?  Do you
have a fix?

Thanks in advance for any insight.

-- 

Mark McWiggins			UUCP:		uunet!intek01!mark
DISCLAIMER: I could be wrong.	INTERNET:	mark@intek01.UUCP
						(206) 641-5014

cig@genrad.UUCP (Charles I. Ganimian Jr.) (04/19/88)

In article <286@intek01.UUCP> mark@intek01.UUCP (Mark McWiggins) writes:
>We've been experiencing a weird Novell Netware bug.  It sometimes just
>ignores the directory structure completely.  For example, when I remake
>a certain program in one of my directories, the program somehow winds
>up in another directory *on another disk*!
>
>This only seems to happen when there are two files with the same name
>in different directories.  Is anyone else experiencing this?  Do you
>have a fix?
>

I have been experiencing the same problem, if the file already exists
in the search path it is over written.  The only work-around I have found
is to .\ in the makefile and this is a poor solution.  I am trying 
to get and answer from a BBS conference in New York but so far I have
come up with nothing.

Does anyone know of a fix?  Has anyone paid Novell $894.96 for unlimited
support and is willing to find and answer?

>Thanks in advance for any insight.
     DITTO!
					
					charlie g.

gof@crash.cts.com (Jerry Fountain) (04/20/88)

In article <286@intek01.UUCP> mark@intek01.UUCP (Mark McWiggins) writes:
>We've been experiencing a weird Novell Netware bug.  It sometimes just
>ignores the directory structure completely.  For example, when I remake
>a certain program in one of my directories, the program somehow winds
>up in another directory *on another disk*!
>
>This only seems to happen when there are two files with the same name
>in different directories.  Is anyone else experiencing this?  Do you
>have a fix?
>
>Thanks in advance for any insight.
>

The cause of your problem is easy to see by checking your drive mappings.
Novell's SEARCH drives are *not* like a normal DOS path, they also allow
a program to grab a data file via a search drive (or almost any open/write
operation).  The way LINK often works is to delete the old EXE, then open
is (via create for example).  The problem is that Novell sees the open file
on a search drive, assumes that is the file that LINK wants and then 'opens'
the existing file just as it should.

The only solution is to EXPLICITLY declare the path (as most unixeese might
do) via a '.\filename' type declaration.  I have also observed other programs
exhibit the same behavior (LIB for example).


-- 
-----Jerry Fountain-----
UUCP: {hplabs!hp-sdd,sdcsvax,nosc}!crash!pnet01!gof   ARPA: crash!gof@nosc.mil
MAIL: 523 Glen Oaks Dr., Alpine, Calif. 92001         INET: gof@pnet01.CTS.COM

jjw@igloo.UUCP (John Welch) (04/21/88)

In article <286@intek01.UUCP> mark@intek01.UUCP (Mark McWiggins) writes:
>We've been experiencing a weird Novell Netware bug.  It sometimes just
>ignores the directory structure completely.  For example, when I remake
>a certain program in one of my directories, the program somehow winds
>up in another directory *on another disk*!
>
>This only seems to happen when there are two files with the same name
>in different directories.  Is anyone else experiencing this?  Do you
>have a fix?

	Do you have any path-fixing TSR programs loaded? I use DPATH30 to
allow me to access Wordstar (yeah, ugh, alright, but I know it) to be able to
find ALL the files. DPATH30 has a mode that will allow you to open, FOR WRITE
ACCESS, a file in a directory specified by the path. Thus, by having PATH set to
C:\;C:\UTIL;C:\DOS, if I were on D: and tried editing AUTOEXEC.BAT, it would
not only come up with C:\AUTOEXEC.BAT, but all the changes would be done to
the file on drive C:, without ever warning me this is happening.

	Don't know if this is your problem, but it might be.



-- 
==========================================================================
  John Welch                             ..{codas,ihnp4}!ddsw1!igloo!jjw
 "Oh, reality - it's not for me, and it makes me laugh,
  but fantasy world, and those Disney girls... I'm coming back!"