home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.windows.x:20301 comp.protocols.tcp-ip:5656
- Newsgroups: comp.windows.x,comp.windows.ms,comp.protocols.tcp-ip
- Path: sparky!uunet!nih-csl.dcrt.nih.gov!helix.nih.gov!olds
- From: olds@helix.nih.gov (James Olds)
- Subject: Re: TCP/IP and X under MS Windows 3.1?
- Message-ID: <1992Dec16.232100.22980@alw.nih.gov>
- Sender: postman@alw.nih.gov (AMDS Postmaster)
- Organization: National Institutes of Health, Bethesda
- References: <+0d26sf@rpi.edu>
- Date: Wed, 16 Dec 1992 23:21:00 GMT
- Lines: 25
-
- In article <+0d26sf@rpi.edu> act@sun.ipl.rpi.edu (just another programmer) writes:
- >I am very curious about people's experiences running TCP/IP software
- >under Win 3.1. I am contemplating putting an Xserver onto a machine running
- >Win 3.1 and connecting it to a Unix host to run Unix apps over the net.
- >
- >So what kind of experiences have people had and/or recommendations. I've only
- >just begun tis so if there is any recommended reading that would also be
- >appreciated.
- >
-
-
- I am running Integrated Inference's Machine's X11AT Xserver and it
- runs very well under both Win 3.0 and 3.1. My one complaint is that
- the icons for the X apps when Windoze is running as the manager (as
- opposed to say mwm or twm) are very boring and non-informational.
- The software is running on a 386/25 with 9MB Ram, 100 MB HD and
- a VGA card. The network card is a 3com 3c502 running PC/TCP as
- a network kernel. Hope that helps.>
-
-
- --
- ****************************************************************************
- * James L. Olds Ph.D. Neural Systems Section *
- * domain: olds@helix.nih.gov NINDS, NIH, Bethesda, MD. 20892 USA *
- ****************************************************************************
-