netx still seems to work fine...
Mike Jacoubowsky
for what it's worth, netx is still doing fine...no problems that I can
attribute to anything other than my more-often-than-used-to "Senior
moments."
(Completely unrelated, but...is it just me, or has anyone else come across
stuff they did 5-10 years ago that seems beyond their present abilities?
Kind of amazing how ingenious I was at one time. Nowadays, my VCRs all
flash "12" unless they're the new type that tap into the time-synch pulse on
PBS stations!)
--Mike-- Chain Reaction Bicycles
http://www.ChainReactionBicycles.com
Dave Kearns-NSCV
I'm convinced that NETX was the last truly workable client Novell
produced - too bad it can't handle NDS.
</personal opinion>
"Mike Jacoubowsky" <Mik...@ix.netcom.com> wrote in message
news:90fmvm$lu...@nexus.provo.novell.com...
Barry Schnur
rather complicated as both Novell and Microsoft started down the 'complex is cool' road.
Barry Schnur
Novell Support Connection Volunteer Sysop
http://support.novell.com/forums/
Please post replies ONLY via the Newsgroup
Dave Lunn
Was???? Was??? What was! Is. I am not sure if any of my clients *never*
have to go back and bring up DOS, and half of 'em still use it daily.
Dave
Mike Jacoubowsky
does something funny where it connects to the server at something like 300
baud or so. You have to reboot the machine (sometimes several times) to get
it to work right. Haven't tracked it down yet to make sure it's not some
sort of strange hardware problem with the built-in Davicom lan chip...
--Mike-- Chain Reaction Bicycles
http://www.ChainReactionBicycles.com
"Barry Schnur" <bsc...@home.com> wrote in message
news:3a30539c...@90.1.1.1...
> Was -- I have no clients running DOS only, or even Win 3.1 only.
>
> I would NOT run NETX for Win9x.
Barry Schnur
Barry Schnur
wasn't a happy camper with Client 32. I do have one workstation I support where it seems
ok though.
Dave Lunn
Works original version, and requires a machine dedicated to that function
alone even though it produces but one document per month. Same client has
another user who is still PO'd at me for killing off the ws that she was
running Print Shop Plus on, and I only did that last month. Have another
client that uses only Multimate 3.3 and Quattro 1.0 for docs and ss. Please
don't tell Felton this, he'll blab it and I'll be embarassed in front of
everyone.
Dave
Barry Schnur <bsc...@home.com> wrote in message
news:3a30539c...@90.1.1.1...
Barry Schnur
the sysop 'business' on CompuServe as an early TeamB sysop back in 1988.
Don Crawford
> Some days is harder than others. I have one client who will not forsake MS
> Works original version, and requires a machine dedicated to that function
> alone even though it produces but one document per month. Same client has
> another user who is still PO'd at me for killing off the ws that she was
> running Print Shop Plus on, and I only did that last month. Have another
> client that uses only Multimate 3.3 and Quattro 1.0 for docs and ss. Please
> don't tell Felton this, he'll blab it and I'll be embarassed in front of
> everyone.
>
> Dave
>
We certainly wouldn't do anything to draw Felton's attention to this message!
Heck, he might suggest I upgrade to your level of stuff! <G>
-- Don Crawford
Novell Support Connection SysOp
Mike Jacoubowsky
--Mike-- Chain Reaction Bicycles
http://www.ChainReactionBicycles.com
"Barry Schnur" <bsc...@home.com> wrote in message
news:3a2e9b41...@90.1.1.1...
Barry Schnur
Set the frame type (don't let it use auto detect)
Set the duplex (don't let it use auto detect)
Set the speed (don't let it use autodetect).
Make sure you don't have extraneous bindings on the NIC (NetBeui/TCPIP).
Dave Lunn
You must be the guy who runs 123 1.1 and report writer. Or are you maybe
the one using Twin? I suppose it's Judy instead of Sidekick and Wordstar
1.0 too huh?
DAve
Don Crawford <Don.Cr...@Novell.Support.Connection> wrote in message
news:VA.00000a35.1af20287@don...
Ben A L Jemmett
boot on the 8086, and my 2.1 keydisk is enb0rkified I think.
--
Regards,
Ben A L Jemmett - Usenet replies to bal.j...@ukonline.co.uk.
(http://web.ukonline.co.uk/ben.jemmett/, http://www.deltasoft.com/)
Dave Lunn
Want an extra copy of report writer (never opened) for it? All copy
protedted and everything. I think I can still find both of mine.
Dave
Ben A L Jemmett <bal.j...@ukonline.co.uk> wrote in message
news:90lsk9$f9...@nexus.provo.novell.com...
Don Crawford
> You must be the guy who runs 123 1.1 and report writer. Or are you maybe
> the one using Twin? I suppose it's Judy instead of Sidekick and Wordstar
> 1.0 too huh?
>
TRS-80 with NewDOS 80...
Dave Lunn
I think I have a TRS 80 I gotta get rid of at a client's need parts?
Dave
Don Crawford <Don.Cr...@Novell.Support.Connection> wrote in message
news:VA.00000a42.04f0c034@don...
Ben A L Jemmett
of 1-2-3 for a while (SmartSuite 97 for free, not bad).
> All copy
> protedted and everything.
Better than my copy of 1-2-3. Loads a program by CPS called NOKEY before
starting. It's on a Lotus labelled disk though :)
Mike Jacoubowsky
or half duplex? I know you full duplex is preferable out of the server when
running to a switch, but what are the pros/cons for a workstation? My
assumption is that full duplex would be faster, but is there any trade-off?
--Mike-- Chain Reaction Bicycles
http://www.ChainReactionBicycles.com
"Barry Schnur" <bsc...@home.com> wrote in message
news:3a31babd....@90.1.1.1...
Barry Schnur
>or half duplex? I know you full duplex is preferable out of the server when
>running to a switch, but what are the pros/cons for a workstation? My
>assumption is that full duplex would be faster, but is there any trade-off?
>
discussion this summer).
We've been having a bit of a backroom discussion on this subject. One of the other sysops
who knows this area MUCH better than I do provided these comments:
Here is a collection of rules/recommendations:
1) Most important:
There is no universal recommendation as whether to use full or half
duplex. It depends entirely on the hardware you have.
2) The most important thing about half/full duplex setting of the NIC must
match the half/full duplexing of the switch port to which the NIC is
connected. Mismatches between the duplex setting will lead to undetected
collisions which will cause packet loss leading to poor performance or even
loss of communication.
3) NCP over IP is *much* more sensitive to packet loss than NCP over IPX.
So if you experience a severe performance degradation by going from IPX to
IP, this is probably due to a half/full duplex mismatch somewhere in your
net.
4) Hubs only support half duplex. Only switches can potentially support
full duplex, but not all switches do.
5) Automatic negotiation (NWAYS) works only if both the NIC and the
switch support NWAYS, and if both the NIC and the switch are set to
automatic. If one of the two does not support NWAYS or if one of the two
is statically configured to half or full duplex, the other end will not be
able to determine whether the link is operating at half or full duplex
speed, and it will default to half duplex.
6) The half/full duplex configuration of the server and the workstation
does not have to match. For example the server can communicate full duplex
with a switch while the workstation uses half duplex.
7) If both the switch and the workstations are set to full duplex and the server
is set to 100M with the workstations at 10M, this should work. This full duplex
configuration however will give you only limited performance benefit at the workstation
unless you push the workstation link very hard.In fact, one of the major advantages of
using full duplex is that you completely eliminate collisions and so you don't get the
performance degradations due to collisions when charging the link more than 30%
Don Crawford
> I think I have a TRS 80 I gotta get rid of at a client's need parts?
>
Now, there's a thought! (Actually, I got rid of the TRS-80 some years ago,
just after seeing one in the Smithsonian!)