[ from "Danny Nissan" <[EMAIL PROTECTED]> on info-afs mailing list ]
>
>
>Hello Elaine : some more questions to clarify -
>
>1) How much conventional memory does the PC-Interface take ?
>2) Does it support MicroSoft NDIS interface ? What version ? Can it coexist with
> any NetBios based NOS ?
> I guess NetWare coexistent is with ver 3.X using the netx redirectore (?) -
> any plans for ver 4.x ? What about vlm technology ?
>3) What kind of name resolving (DNS , NIS) mechanism does it use ?
>4) Does the product include TCP/IP stack ? If not , which stack does it support?
>5) I understand that PC-Interface is a 16bit application (?) - Any plans for
> 32bit ? Was it tested under any Win/NT version ?
Since Transarc will have to go to the developer to answer this (which will take
some time), I thought I would resend an excerpt from a discussion on this
product here on this mailing list from July 22. Most of the answers to your
questions are contained in it. Perhaps Transarc can still get the complete and
official answers to send out though. It would also be nice if Locus can start
subscribing to the info-afs list so they can enjoy first hand interaction with
the AFS community. I'll bcc our contact there so they can take the lead on this.
Mark Giuffrida
University of Michigan
[EMAIL PROTECTED]
[ Excerpt from [EMAIL PROTECTED] from July 22 info-afs mailing list]
>Advantages:
> Small client footprint (64K).
> Bundled with LanWorkPlace for DOS (or you can use NDIS driver)
> Works with Netware for those who care.
> Translator gives ability to run a script when connection is made.
> You can then do more user screening, klogging, version checking,
> stat gathering, etc.
> Ability to pass back messages to Windows users at both connection
> time to the translator as well as anytime you are on the translator.
> Translator software currently runs on Suns and IBM AIX, HPs.
> Translates all non 8x3 pathnames into an 8x3 pathname (this also
> has a disadvantage)
> Translator based concurrent licensees (unlimited is also an option
> if you can afford that kind of money).
> Locus has been a very responsive company for our test inquiries, and
> willingness to do what it takes to have us use the product. They
> claim they are going to start the port to Chicago and also make sure
> it talks to DFS on translators which can run DFS.
> Although we won't use it, it can support printer sharing, has a terminal
> emulator.
>
>Disadvantages:
> When client connection is established, username and password are
> transmitted to the translator in a scrambled format. It would be nice
> if it used Kerberos instead. Locus has indicated they are interested
> in doing this work in a future release.
> No acl changing tool.
> No protection group setting tool.
> Translation into 8x3 pathnames is somewhat crytic. There is a DOS
> utility to see the translation, but no windows utility. The
> translation can cause some strange effects when a program removes
> and recreates the file (thus recreating the cryptic name literally).
> Can't use a DNS translator name from DOS (but you *can* from Windows).
> Locus also ships a PCLIB (API) which allows one to write their own
> login program.
