HELP nits

[Steve Fabian]

A sentence should be added to topics f_inode.htm and f_links.htm warning
that these functions return valid values only for local drives, but not for
mapped network drives.

A sentence should be added to topic f_junction.htm that the value
returned is always relative to the system on which the directory is located.
--
Steve

 

[rconn]

A sentence should be added to topics f_inode.htm and f_links.htm warning that these functions return valid values only for local drives, but not for mapped network drives.

Not necessarily true -- it's going to be dependent on your network redirector and the type of server you connect to. (I have no problems retrieving that info on my network.)

A sentence should be added to topic f_junction.htm that the value returned is always relative to the system on which the directory is located.

I don't understand your point here ...

 

[Steve Fabian]

rconn wrote:

| ---Quote (Originally by Steve Fbin)---
|| A sentence should be added to topics f_inode.htm and f_links.htm
|| warning that these functions return valid values only for local
|| drives, but not for mapped network drives.
| ---End Quote---
|
| Not necessarily true -- it's going to be dependent on your network
| redirector and the type of server you connect to. (I have no
| problems retrieving that info on my network.)

I use a simple Microsoft WinXP network, systems physically connected to
each other through the router. I just took a single directory containing
many files with WinXP junctions to files in other directories, and ran PDIR
both locally and on the other system which has the drive (and thus the
directory) mapped to a local drive letter. The inode results were the same
(apparently I was wrong about that), but the link counts were correct only
when PDIR was executed locally. On the remote machine the link count was
reported as 1 for all files. I did the test using 4nt V7 and V8, and tcc V9
... V12. The results were identical.

| ---Quote---
|| A sentence should be added to topic f_junction.htm that the value
|| returned is always relative to the system on which the directory is
|| located.
| ---End Quote---
|
| I don't understand your point here ...

Let there be a drive whose TRUENAME on the system where it is a local
drive in C:. Let \JPS\ be a junction to \JPSOFT\ on this drive. Map this
drive on another system as Z:; now the value of %@junction[Z:\JPS] will be
C:\JPSOFT.
--
Steve

 

[rconn]

I use a simple Microsoft WinXP network, systems physically connected to
each other through the router. I just took a single directory containing
many files with WinXP junctions to files in other directories, and ran PDIR
both locally and on the other system which has the drive (and thus the
directory) mapped to a local drive letter. The inode results were the same
(apparently I was wrong about that), but the link counts were correct only when PDIR was executed locally. On the remote machine the link count was reported as 1 for all files. I did the test using 4nt V7 and V8, and tcc V9 ... V12. The results were identical.

You might want to consider upgrading to a slightly less neolithic version of Windows (one that actually supports inodes and symlinks).

You could also try pressing Microsoft to release an updated redirector for XP, but you're not likely to get much joy from that.

Let there be a drive whose TRUENAME on the system where it is a local
drive in C:. Let \JPS\ be a junction to \JPSOFT\ on this drive. Map this
drive on another system as Z:; now the value of %@junction[Z:\JPS] will be C:\JPSOFT.

This seems a bit too obvious to require a detailed explanation in the help.