Conference jamin::pathworks32

You may also want to ask this in the TAPE::INFOSERVER notesfile.

    hello !
    
    Let me explain a little bit more
    If I create a service in the infoserver
    INFOSERVER>CREATE SERVICE service_name for DKX: CLASS V2.0
    I can see and connect it from PW 6 but not from PW32
    
    I thing it should be a Pathworks issue I couldnt find any reference in
    TAPE::INFOSERVER.
    				Thanks in advance     Josep.

    PATHWORKS 32 V7.0 does not support InfoServer disks. It only supports
    CDs.
    
      Anita Murphy

Re:3
Since he is talking about disk's being changed, it sounds like he IS talking
about CD's. 

re:2, why do you need to do a CREATE SERVICE command?  A FAT-based CD should
automatically create a V2.0 service, that is, if it can read the label and
determine the record type.
Still, if v6 can see it, pw32 should see it too.

    
In order not to have to connect again when changing CDs, the customer 
can create a service name on the InfoServer that represents
a CD. For example, if they have the MSDN CD loaded, the default service
name is the same as the CD's Volume label (MSDN). If they create service
names on the InfoServer, such as CD1, CD2, etc, for all CD drives, and
connect to those service names instead, then they can swap CDs and keep the
connections.


If you use the MS-DOS "NET USE" or Explorer, you won't see any InfoServers,
because the InfoServer software supplied with PATHWORKS 32 V7.0 for use on
NT V4.0 Servers does not include an InfoServer Network Provider. You need 
to use the command line utility infocon for browsing, connecting etc. However, 
after you have connected an InfoServer drive using infocon, the connected drive 
does appear in Explorer. Infocon was meant to be used by a system administrator 
on an NT V4.0 Server, where you have installed PATHWORKS 32 V7.0 with InfoServer 
support. The system administrator can then create an InfoServer file share on this 
Server that any desktop client can use.

The storage group has taken the InfoServer NT drivers and added Net 
Provider Software that allows using the Explorer to View and connect 
InfoServers. The part number is QA-YSHAG-H8.

It's available for internal use also: 

 The kit can be retrieved using a web browser from the following location:

    http://dtb13.shr.dec.com/InfoServer/wnt_client/v10/

  or copy from

    tape::ess:[public.ess.kit.wnt_client_v1]
 
The storage product is V1.0 now and supports NT 4.0 connections to CD-ROMS
only. V1.1 will add hard disk connections.

Currently, we plan to add disk support and the InfoServer network provider 
to PATHWORKS 32 V7.1.

     
    Hello all
    
    First Paragraph of reply 5 , is what I m looking for , but the fact
    is that as stated in reply 3 , if I create a service for a CD as you
    said I can not see it with the command INFOCON \\infoserver_name.
    with Pw 32 , the same service with PW 6 appears OK. Perhaps this
    limitation has any relationship with the fact that fixed disks are
    not supported.
    I checked it at office with same results that at customer side
    Is this the expected behaviour?
    					Thanks  Josep.

re .6

I think I understand what you are saying.

INFOCON (ie, a PATHWORKS 32 Windows NT Server) can see a service for a CD that
is Automounted on a Infoserver, but cannot see a service that you manually
created by the "Create Service" command that is pointing to that same CD
drive.

However, a PATHWORKS V6 client can see both the Automounted service and
the manually created service?

If this is the case, do you see any differences in the two Services as seen
from the InfoServer with the SHOW SERVICE servicename FULL?

I wonder if a PATHWORKS 32 client using INFOCON still looks for a service with a 
V2.0 Class, or is it now looking for an ISO_9660  class?

      HI !
    
      Thanks a lot , your clue solved the problem.
      The only that must be done is creating the service as ISO_9660 class
      instead of a V2.0 class.
    
                                                  Josep Burgues