G E N E R A L

ABOUT

The tag itself returns a couple variables back no matter what you do (SharesDescription, SharesVersion and SharesError). These are always available unless there is a catastrophic failure of the tag.

Additionally you can use the ABOUT function to return more detailed information on the tag. The fields returned are mostly only of interest for curiosity or in debugging a situation.

Note below that though the tag returns it's SerialNumber, it's not used currently, and hasn't been for a very long time, but probably will be again soon.

For the curious, it also proves the total number of lines of c/c++ that the current build was using. This includes the scant comments in the source code. For instance, this build of the tag has 574 lines of code.

Description

The general product description.

Version

The version number of the software, ie 2.0.

Quality

The quality field will be one of the following four: "Alpha", "Beta", "Gamma" or "Omega". Quality relates the quality control status of the version of the tag you're currently using.

Alpha code is highly unstable and shouldn't be trusted for anything. Do not use on production machines.

Beta code is close to being finish and it is in a debugging phase. Do not use on production machines.

Gamma code is for use on production machines. As far as the beta testers have determined it works as it should.

When a product goes Omega that generally means it is long used Gamma code that is now no longer being maintained.

SubVersion

The subversion number of the software, ie 4 for "2.0beta4".

SerialNumber

Currently unused.

Lines

The total lines of c/c++ code in the software.

BuildDate

The ODBC DATETIME when the tag was last compiled (built).

Evaluation

Boolean field (0 or 1). 1 indicates the version of the tag you're using is a time-limited evaluation version. 0 is full commercial.

ExpirationDate

The ODBC DATETIME date when the tag will stop working.

S H A R E S

SHARES

<CFX_Shares ACTION="SHARES">

Lists all the shares on the local computer or any computer specified with the Computer parameter.

MaxUsers returns "-1" if there is no defined limit on the number of connections to the share.

Hidden. The share is normally hidden from users.

CurrentUsers. The current number of connections (usually the number of computers) made to this share.

ADD

<CFX_Shares ACTION="Add">

This creates an alias to a drive:folder location that is shared by all applications on the network.

SHARE is the name which you give to the share, such as "myShare". PATH is the physical path to your storage medium. USERS is the maximum number of users you wish to be able to connect to the network share. 0 forbids anyone from using it.

Example: <CFX_Shares ACTION="Add" SHARE="name" PATH="drive:path" COMMENT="comment" USERS="n|0" QUERY="s">

DELETE

<CFX_Shares ACTION="Delete">

Removes the specified share.

Example: <CFX_Shares ACTION="Delete" SHARE="name">

• 1.9 January 3rd 2001.

  Added IHTKPASSWORD. Upgraded reporting code.

• 1.8 September 29th 2000.

  Slightly changed Shares so it will work even on computers without active directory installed. It now defaults to local machine and can use a Computer parameter. To be honest, it should have logically been set up like this in the first place.

• 1.7 September 19th 2000.

  Upgraded error reporting code to v1.2.

• 1.6 August 31st 2000.
  

  NEW TAG: As mentioned for a while now CFX_NFS was torn into two new tags: CFX_Permissions and CFX_Shares. CFX_NFS is now "untouchable" and no further modifications or corrections to it's code base will be made. If you're still using NT 3.51 or NT4 then the CFX_NFS functions may work better for you. CFX_Permissions and CFX_Shares are meant to primarly work on NT5 (W2K) but effort will be made to make them backward compatible with legacy NT versions where possible.

  Some of the code for CFX_Shares is the same as was in CFX_NFS, but the rest is new. Also there are some differences to the field names, etc compared to the deprecated CFX_NFS.

• 1.5 August 9th 2000.
  
  • Fixed LocalDrives loss of precision for Tom. It wasn't accurately displaying partitions greater than 4gb (32-bits) when returning the field. Made the output 64-bits, ie, good for up to 1.84467441e19 bytes.
  • Added FreetoUser field for LocalDrives.
  • Fixed CACLS bug that occurs with unknown accounts types.

• 1.4 August 5th 2000.
  

  To be honest I don't remember what changes I made for 1.4 it's been so long. It was something minor but I didn't make any notes of it at the time. I believe it was an amplification of something said in the tests to avoid confusion.

• 1.3 July 3,4 2000.
  

  Completely rewrote all the function code except that relating to permissions. This way should be much better for large networks. Should have done it this way to begin with... but I didn't know then the MS internals that I know now.

  Still having some difficulties with mapped network drives. There are currently some scope issues with NETWORKDRIVES and MAPNETWORKDRIVE that are being investigated. All other functions are, as far as is know, functioning correctly. Hope to have this resolved by the next release.

  Added a few new functions, and since it's the holidays (vespucia's independance day) and no one's had a chance to really make production use of the v2 code yet, I changed some of the function fields. :) Head's up.

  (I hate legacy code getting in the way of improvements or having the code become overly complex and more apt to unforseen failure. Moreso since this software is running on a couple different US Mil & Space Support sites. Don't want anything blowing up that's not supposed too.)

  • Added DOMAINS
  • Added NETWORKPRINTERS
  • Changed SERVERS (faster, completely different than CFX_UserManager's SERVERS function)
  • Added NETWORKNEIGHBORHOOD
  
  
• 1.2 June 30 2000
  

  Oops. Forgot to clean up the Shares documentation and a few of the network drive functions. Sorry about that. Was in such a rush to get the thing out before the holiday weekend it slipped my mind. Should be fixed now.

  I'll up the ums2.1 with Shares1.2 in a few days.

• 1.1 June 28 2000.
  

  Some issues with deleted user accounts were addressed and the documentation cleaned up.

  Sorry about the photos. When I have time I'll scan in more artist imagery.

• 1.0 June 18, 25 2000.
  

  All of the functionality of this tag comes from the 2.0betas of CFX_UserManager. It seemed logical to strip out all the newly written file-centric code and place it all in it's own tag. Anyone who has used the 2.0betas 1 through 5 will be immediately familiar with most of the functionality of the new tag. Some of the names and parameters have changed, but the essense is the same.