Re: CAWIN 95 Network Drive Mappings Problem

Fred W. Skinner wrote:

>         John,
>
>         APAR  II10243 dated 04/03/97 might have the answer you looking
> for. In summary,
> This APAR says that if your PC is running WIN95 OSR2 (that's version
> 4.0.950B under the properties of "My Computer"),you will not be able
> to run Network drives. IBM is working on a PTF. You can get the full
> text of this APAR from the IBM Supportline home page.
>
> -----Original Message-----
> From:   mcsnet!midrange.com!midrange-l-owner@Mcs.Net  On Behalf Of
> John Muirhead
> Sent:   Monday, June 09, 1997 5:20 PM
> To:     Midrange (LISTSERV)
> Subject:        CAWIN 95 Network Drive Mappings Problem
>
> Hi all,
>
> I have a problem w/ Client Access for Windows 95 and was wondering if
> anyone
> had encountered, or possibly discovered a fix for it.
>
> First, a little background info:  Our AS/400 is a "Black Box" running
> V3R2M0
> (recently upgraded) and the latest CUM tape has been applied (also
> recently).
> Our network is Token Ring and were using SDLC protocol .  Across the
> same network, were also using IPX protocol (Netware 3.12/4.11 servers)
>
> and
> NetBEUI for Windows 95 networking, peer-to-peer.
>
> The PC workstations have been upgraded to V3R1M1 and service pack
> SF36801 (By
> the managing AS/400 system) and then upgraded further by applying a
> recently downloaded service pack SF39584. We originally decided not to
>
> install
> the aforementioned service pack, but changed our minds upon reading
> the
> related APARs that said certain PTFs where recommended, but not
> required
> to
> use this service pack.
>
> CAWIN 95 seems to run O.K. for terminal emulation and mapped printers
> (virtual
> print), but fails miserably when attempting to map permanent drives
> (shared
> folders). PC workstations w/ mapped drives will unexpectedly reboot at
>
> startup
> when attempting to map these drives. If the mappings are removed, all
> is
> well.
>
> I've heard alot of rumbling about CAWIN95's continued instability in
> certain
> areas and the number of service packs available via IBM's web site may
>
> be
> proof of that.  I've also heard that some (particularly those on
> twinax)
> have no problems whatsoever.
>
> I've watched this mailing list for the last 6 months and noticed alot
> of
> discussion about CAWIN95, so you've probably "been there, done that",
> but
> if possible, could we start this discussion again...
>
> Anyone got any ideas?
>
> Thanks in advance.
>
> John Muirhead -- Tree Top, Inc.
> jmuirh@treetop.com

John, we now have the same problem with mapping network drives ( OSR2
with new Compaqs).

I found this APAR about it...APAR= II10243CLIENT ACCESS SUPPORT ON
MICROSOFT WINDOWS 95 OSR2


** Last updated 6/18/97 **

Microsoft Windows 95 OEM Service Release 2 (OSR2) is an OEM
Service Release of Windows 95.  Currently, there is no retail
version of Windows 95 OSR2 available.  It is available from
some PC Manufacturers who preload it on the new PCs they
sell to the public.

An OSR2 Version of Windows 95 can be identified by checking
the properties of "My Computer" for 4.0.950B or checking for
the version 4.0.1111 at a MS-DOS prompt.

³ There have been two problems found with Client Access and
³ OSR2 involving the netdrive function.  A fix is available
³ to resolve the problem (APAR SA61653).
Other than Network Drives, there are not any other known
problems with Client Access functions running on OSR2.

Customers experiencing problems with Client Access on OSR2
may wish to contact their PC Manufacturer for possible OSR2
fixes or to file an OSR2 problem report.  If the problem
persists, you may wish to report the problem to IBM Service.
IBM Service may require the following:

        1.  Your PC came preloaded with OSR2 from your
            PC Manufacturer.
        2.  Your PC Manufacturer supports OSR2.
        3.  You contacted your PC Manufacturer for any
            possible OSR2 fixes that are available.

You may also be asked by IBM Service to provide your make,
model, and serial number of your PC, along with additional
information pertaining to the purchase and support of your
Windows 95 OSR2 license.

Since each PC Manufacturer may modify Windows 95 OSR2 for
their particular systems, IBM may not support your
combination of operating system and hardware.  IBM will
accept a service call, though, if the above criteria is
met.  If your environment has not been tested by IBM, you
may request that it be added to IBM's test scenarios.

Some other sources of information on OSR2 support and
problems can be found from:

  - Microsoft Support:  www.microsoft.com/support
      Search on OSR2 for problem reports and downloads.

  - TechWeb:  www.techweb.com
      Search on OSR2 for articles discussing problems.

  - Novell:  www.novell.com
      If you are running Novell Client 32 with Client
      Access, search on OSR2 for problems with Novell
      Client 32 and ODI on OSR2.

Add'l keywords for search : OEM2 Windows 95B 4.00.950B


---
Jim Welsh
Programmer/Analyst
B&B Cash Grocery Stores, Inc.
http://www.netcom.com/~jimwelsh/welcome/welcome.html


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *