leoh@hardy.hdw.csd.harris.com (Leo Hinds) (01/31/91)
Would anyone that has a working set of PIFs for using NCSA's telnet/ftp while under windows please send me a copy of the PIF(s) ... thanks leoh@hdw.csd.harris.com Leo Hinds (305)973-5229 Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n creireg ?!!!!!!? ... znlor arkg gvzr
silk@dorm.rutgers.edu (Daniel Turner) (01/31/91)
leoh@hardy.hdw.csd.harris.com (Leo Hinds) writes: >Would anyone that has a working set of PIFs for using NCSA's telnet/ftp >while under windows please send me a copy of the PIF(s) ... thanks >leoh@hdw.csd.harris.com Leo Hinds (305)973-5229 >Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n >creireg ?!!!!!!? ... znlor arkg gvzr Me, Too!! Daniel Axler Turner -->-->--> silk@dorm.rutgers.edu
iho@cac.washington.edu (Il Oh) (01/31/91)
silk@dorm.rutgers.edu (Daniel Turner) writes: >Would anyone that has a working set of PIFs for using NCSA's telnet/ftp >while under windows please send me a copy of the PIF(s) ... thanks I haven't had any trouble using NCSA telnet or ftp with or without PIFs. What seems to be the trouble? Are you using the Windows-compatible version of the packet driver with the -w switch? -- "And now, adding color | Il Hwan Oh a group of anonymous, Latin-American | University of Washington, Tacoma meat-packing glitterati" | iho@cac.washington.edu -- Pink Floyd, Final Cut |
mcdonald@aries.scs.uiuc.edu (Doug McDonald) (01/31/91)
In article <15488@milton.u.washington.edu> iho@cac.washington.edu (Il Oh) writes: >I haven't had any trouble using NCSA telnet or ftp with or without PIFs. >What seems to be the trouble? Are you using the Windows-compatible >version of the packet driver with the -w switch? >-- Neither have I. But what is a -w switch? Doug McDonald
krg2@po.CWRU.Edu (Kevin R. Glazier) (01/31/91)
In a previous article, leoh@hardy.hdw.csd.harris.com (Leo Hinds) says: >Would anyone that has a working set of PIFs for using NCSA's telnet/ftp >while under windows please send me a copy of the PIF(s) ... thanks > I have the same problem. When I first installed Windows 3.0 on my system, I ran NCSA telnet as a DOS application with no PIF file and it ran fine. But recently I reformatted my hard drive and re-installed Windows. Now I can't get telnet to run at all, even with various PIF files. All I can suggest is to get a copy of WINQVTNET (available at cica). I use it on my system with no problems. Hope this helped. Later. -- Kevin R. Glazier | Michelson 540 | "War is our profession, C/4th/C | (The Officer's Club) | but peace is our goal..." U.S.A.F. | ******************** | -Strategic Air Command "The price of freedom is eternal vigilance." -- Thomas Paine
iho@cac.washington.edu (Il Oh) (01/31/91)
mcdonald@aries.scs.uiuc.edu (Doug McDonald) writes: > iho@cac.washington.edu (Il Oh) writes: >>I haven't had any trouble using NCSA telnet or ftp with or without PIFs. >>What seems to be the trouble? Are you using the Windows-compatible >>version of the packet driver with the -w switch? >Neither have I. But what is a -w switch? "Windows-compatible" switch. It's how you tell the Windows-compatible packet drivers to operate in such a mode. -- "And now, adding color | Il Hwan Oh a group of anonymous, Latin-American | University of Washington, Tacoma meat-packing glitterati" | iho@cac.washington.edu -- Pink Floyd, Final Cut |
leoh@hardy.hdw.csd.harris.com (Leo Hinds) (02/01/91)
In article <15488@milton.u.washington.edu> iho@akbar.UUCP (Il Oh) writes: >silk@dorm.rutgers.edu (Daniel Turner) writes: >I haven't had any trouble using NCSA telnet or ftp with or without PIFs. >What seems to be the trouble? Are you using the Windows-compatible >version of the packet driver with the -w switch? I was experiencing trouble around the same time I was having the mouse on drugs problem. Having read this message I decided to try it again, and amazingly enough, it seems to work (currently as a dos window while in 386enh mode!) ... thanks for the incentive to try again! P.S. This is EXTREMELY SLOW ... sometimes 50-80 characters behind my typing (I am a Columbus typist). leoh@hdw.csd.harris.com Leo Hinds (305)973-5229 Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n creireg ?!!!!!!? ... znlor arkg gvzr
leoh@hardy.hdw.csd.harris.com (Leo Hinds) (02/01/91)
In article <1991Jan31.015311.27838@usenet.ins.cwru.edu> krg2@po.CWRU.Edu (Kevin R. Glazier) writes: > I have the same problem. When I first installed Windows 3.0 on my >system, I ran NCSA telnet as a DOS application with no PIF file and it >ran fine. But recently I reformatted my hard drive and re-installed >Windows. Now I can't get telnet to run at all, even with various PIF >files. All I can suggest is to get a copy of WINQVTNET (available >at cica). I use it on my system with no problems. Hope this helped. I tried WinQVT/net before trying NCSA telnet ... but had to give up as >80% time it would die upon startup, the remaining <20% of the time it would die (system hung or unrecoverable application error) within 10 minutes ... therefore being useless for me. As my "mouse on drugs" hasn't been bothering me lately, I might try it again ... possibly with a little more success ! As a side note ... a recent reading in some PC trade rag regarding the Hercules TIGA card (I think) mentioned buggy screen drivers resulting in MANY "Unrecoverable application error"s & mouse on drugs symptoms ... leoh@hdw.csd.harris.com Leo Hinds (305)973-5229 Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n creireg ?!!!!!!? ... znlor arkg gvzr
leoh@hardy.hdw.csd.harris.com (Leo Hinds) (02/01/91)
In article <2214@travis.csd.harris.com> I wrote: >I was experiencing trouble around the same time I was having the mouse on >drugs problem. Having read this message I decided to try it again, and >amazingly enough, it seems to work (currently as a dos window while in >386enh mode!) ... thanks for the incentive to try again! One interesting side note ... for some reason the <Alt T> (FTP into the PC) times out while I am doing this under windows, but is ok if under DOS. A ping from UNIX host to PC responds ok though (as executed from the NCSA telent terminal session). Any thought from anyone? leoh@hdw.csd.harris.com Leo Hinds (305)973-5229 Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n creireg ?!!!!!!? ... znlor arkg gvzr
wjhauber@iastate.edu (Hauber Wayne) (02/01/91)
In <2200@travis.csd.harris.com> leoh@hardy.hdw.csd.harris.com (Leo Hinds) writes: >Would anyone that has a working set of PIFs for using NCSA's telnet/ftp >while under windows please send me a copy of the PIF(s) ... thanks I am using a PIF file to start NCSA Telnet under Windows. If I recall correctly, the key thing is to check "exclusive" "full screen" and "close on exit". I have memory set to 52 and kb desired set to -1. NCSA telnet won't tolerate running in a window hence the full screen setting and it WON'T run in the background as a server without losing characters. -- Wayne Hauber | (515) 294-9890 Programming Consultant/BITNET Inforep | ga.wjh@isumvs.bitnet Iowa State University Computation Center | wjhauber@iastate.edu
mcdonald@aries.scs.uiuc.edu (Doug McDonald) (02/01/91)
In article <wjhauber.665359864@calvin.cc.iastate.edu> wjhauber@iastate.edu (Hauber Wayne) writes: > >NCSA telnet won't tolerate running in a window Not true. It runs fine in a window - in 386 mode of course. >hence the full screen setting >and it WON'T run in the background as a server without losing characters. Also not true. In fact, it runs fine for me in the background and doesn't lose characters, even if I set its priority to 25. This is with either the INTERNAL WD8003E driver or the appropriate packet driver from the current distribution of drivers on ftp.ncsa.uiuc.edu that says they support Windows 3. There may, of course, be other cards that could cause problems. Doug McDonald
jackz@izuba.ee.lbl.gov (Jack Zelver) (02/06/91)
In article <wjhauber.665359864@calvin.cc.iastate.edu> wjhauber@iastate.edu (Hauber Wayne) writes: >... >I am using a PIF file to start NCSA Telnet under Windows. If I recall >correctly, the key thing is to check "exclusive" "full screen" and "close >on exit". I have memory set to 52 and kb desired set to -1. > >NCSA telnet won't tolerate running in a window hence the full screen setting >and it WON'T run in the background as a server without losing characters. This is very misleading... I manage several diverse PC systems on different subnets here and we have NCSA Telnet running under windows in NON-exclusive, NON-full screen modes. They've been running this way ever since Windows 3.0 became available, using the modified packet driver set for W3.0. (Under 386 enhanced mode, of course) I leave mine running in background as a server all the time unless I'm using it. Never have lost a character (that I know of!) yet. My pif file is pretty much the default that came with Win3.0 except that I allow background operation and close the window on exit. Neither of these is required, except you won't run in background unless you allow it, of course. The ethernet cards are WD8000's, 3C501's, and 3C503's. Just make sure you use the correct packet drivers. Jack Zelver Lawrence Berkeley Laboratory U.C., Berkeley jszelver@lbl.gov