[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::pwv50ift

Title:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:CPEEDY::KENNEDY
Created:Fri Dec 18 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4319
Total number of notes:18478

4199.0. "drive letters swapped - V5.0C ECO3" by LNZALI::BACHNER (Mouse not found. Click OK to continue) Mon Mar 10 1997 11:12

A customer frequently observes the following (mis)behaviour:

from his PC (running Windows 95 or NT 4.0, I'm not sure), he connects to two
network shares on a PATHWORKS server, and assigns them drive letters - say L:
and M:.

After some time, either
- the contents of L: and M: are swapped, i.e. when looking at the L: drive 
  from the explorer he sees what originally was in M: and the other way round;
or
- both drive letters show the same contents.

I could not find anything about this problem in STARS - is it a known issue
already ?

Thanks for your help,
Hans.
T.RTitleUserPersonal
Name
DateLines
4199.1Have them get current - V50E.PATRLR::MCCUSKERMon Mar 10 1997 11:382
This was fixed somewhere back a few releases, not sure where/when.  Have them
goto V50E.
4199.2V5.0D-ECO3 not latest but greatest ???STKAI1::BLUNDBERGCollission speed full!!!Tue Mar 11 1997 08:115
    If I were you I'd choose V5.0D-ECO3 since I've had som bad experience
    with V5.0E regarding NT workstations, thats MY opinion.
    
    Bjorn
    CSC Sweden
4199.3PATRLR::MCCUSKERTue Mar 11 1997 10:322
Of course, V50D-ECO3 doesn't support NT4.0.  Thats not to say it doesn't work,
as Bjorn has pointed out it does for him ;^).
4199.4VMSNET::S_VORESmile - Mickey's Watching!Tue Mar 11 1997 13:448
    Hmmm?  Where in the SPD does it mention a specific version of NT client?
    
    The only thing I see (this is from the 5.0C SPD, I don't have a 5.0D
    version handy) is this..
    
     Services provided by PATHWORKS for OpenVMS are accessible to PATHWORKS
     LAN Manager-based clients as well as to Microsoft LAN Manager clients.
    
4199.5Its in there...PATRLR::MCCUSKERTue Mar 11 1997 18:1418
>Hmmm?  Where in the SPD does it mention a specific version of NT client?

Well, I had to look a bit to find a V50C SPD (30.50.16), but its there on 
page 13, Client Software:

The following versions of client software are supported for use in conjuction with
PATHWORKS for OpenVMS:

	...

	Microsoft Windows NT workstation software V3.1 or V3.5
	
	...

V50E has a similar section which includes NT 4.0.  I didn't search out a 50D
SPD, but I'm quite confident it does not include NT4.0

Brad
4199.6VMSNET::S_VORESmile - Mickey's Watching!Wed Mar 12 1997 08:3139
    duuuh, how'd I miss that?  it's on pages 18/19 in the on-line copy in
    TIMA/STARS/DSNlink, but still... how'd my search yesterday for "NT" and
    other combinations miss it?  I dunno.
    
    hey - does this mean that we can stop answering questions from folks
    who are trying to connect from NT Server as well?  How 'bout Windows
    95?  How 'bout PATHWORKS for DOS and Windows version 6?  :-)
    
    
    
    The following versions of client software are supported for use in con-
    junction with PATHWORKS for OpenVMS:
    
    o  PATHWORKS for DOS V4.1, V4.1A (SPD 55.07.xx)
    
    o  PATHWORKS V5.x for DOS and Windows (LAN Manager) (SPD 55.07.xx)
    
    o  PATHWORKS for OS/2[R] V5.0 (SPD 55.24.xx)
    
    o  LAN Manager V2.2 workstation software for DOS, Windows, and OS/2
    
                                    19
    
    o  Microsoft Windows NT workstation software V3.1 or V3.5
    
    o  Microsoft Windows for Workgroups V3.11
    
    
    The TCP/IP transport is included with the PATHWORKS V5 for DOS and Win-
    dows client. PATHWORKS for DOS V4.x clients operating in a TCP/IP en-
    vironment require the PATHWORKS for DOS (TCP/IP) V2.0 software.
    
    PATHWORKS for DOS and Windows clients that access the services of a
    PATHWORKS for OpenVMS server via remote methods require PATHWORKS Re-
    mote V5.0 or later.