Re: SQL*Net <--> Windows95

From: Anton Dischner <dischner_at_med.uni-muenchen.de>
Date: 1996/07/26
Message-ID: <dischner-2607961239370001_at_news.lrz-muenchen.de>#1/1


Hi all,

make shure you use 16-bit for Win 3.x and 32-bit only on win95 and WinNT products only on NT.

Installing Win 3.x Oracle on Win95 etc will cause endless trouble !

Kind regards,

Toni

In article <4t1dt6$6461_at_red.interact.net.au>, grant_at_towersoft.com.au (Fuzzy) wrote:

> posborn_at_menlosoftware.com (Paul Osborn) wrote:
>
> >Hi;
 

> >A site is currently running Oracle 7.0.15 on a Pyramid server. They
> >want to be able to connect to Windows95 clients (16M RAM, 486/Pentium)
> >using SQL*Net 2.n.
 

> >My question is: What is the least amount of upgrade pain they need to
> >go through to be able to connect the Windows95 clients to the Pyramid
> >server using SQL*Net 2.n?
 

> >Concerns would be:
> >Is 16M RAM per client enough?
>
> Unless there is a ridiculous amount of work done on the client, this
> should be fine.
>
> >Can they get away with upgrading to Oracle 7.1 and SQL*Net 2.1, i.e.
> >does SQL*Net 2.1 support Windows95?
>
> Yes, it works just fine. Be aware that there are 16-bit and 32-bit
> versions of all the Oracle client stuff (some are still buggy) so you
> need to be careful to get what you need.
>
> >Thanks,
> >Paul
>
> Ciao
> Fuzzy
> :-)
 

-- 
A. Dischner, SGI&AIX sysadmin, Oracle DBA       | Don't let friends
Institut fuer Klinische Chemie                  | use WinDose
Klinikum Grosshadern                            | Just say NO. 
Ludwig Maximilians Universitaet Muenchen,  GER  |            
Marchioninistr.15 81366 Muenchen 49-89-70953202 | 
Received on Fri Jul 26 1996 - 00:00:00 CEST

Original text of this message