Melbourne?... Australia or Florida?
Spectre wrote to poindexter FORTRAN <=-
goodies from there that year. Then each end of financial year they'd
throw out a bit more. Was good while it lasted.
[...]I started with Netware 2.2 on a Mac network running on Token Ring
Did NetWare 2.2 server really run on a Mac or was it just a client?
Netware ran on a generic 386 PC. Clients were all Mac.
Yep, token passing topologies were the thing back then, when Ethernet was all shared space. Before ethernet switches, collisions were a serious
issue and the network could seriously degrade.
My first switched network used a 6 port 10 megabit ethernet switch as a core switch, and 24 port hubs as user switches. That was fancy stuff back then.
I did a lot of stuff with ARCnet back then - seriously lenient. We'd run
it on different grades of coax, accidentally plug hubs into hubs, and it still worked. Passing a token meant that it'd degrade gracefully. Having
to set a network ID via jumper was a pain, though.
Someone once joked that you could tell who was a network person by asking them how many syllables were in the word "coax".
I was a member of a Novell user group in the SF Bay area from 1991-1996, and we'd met once at their office in San Jose. I remember being in my 20s and amazed at an office campus with day care, a spa, hair salon, day care, a food court with high chairs so you could have lunch with your kid, a pond, walking paths...
Fast forward many years later and I wondered why my current office space looked familiar. My current employer had bought the Novell campus and I
was working in the same place.
I never understood why anyone really wants a Windows Server system, and ac>> I pity everyone who has to work on such systems (me included).
In the past, NetWare always was the better option and today a
Linux-based system would be my preferred choice.
Novell's high cost got Microsoft's foot in the door, and just good enough (but significantly cheaper) gave them an opening.
So, given your choice of Netware for file and print services, and a UNIX environment for IP management, or a couple of NT boxes with GUIs to do it all, lots of companies took the Microsoft path.
Active Directory versus Novell DS was the final killer. With Microsoft owning most of the client OSes that was a done deal.
I made a good living setting up Linux environments with mail, groupware
and file/web services for startups back in the early 2000s for people who couldn't afford "WOEA", but now I think G suite does a better job than bringing it in-house.
My eBay finding of NetWare 4.11 and GroupWise will arrive approx.
friday and the seller told me that he included some other Novell
products he is clearing out :)
Please don't make me run a Novell network at my house. Please don't make
me want to run a Novell network at my house...
Going from a 286 to a 386, or 386 to 486? Amazing.
Yep. And so Token-Ring had a real advantage :)
Yep. And so Token-Ring had a real advantage :)
I believe it was a bit horses for courses... an over large ethernet could have bad collision problems, and multiple collision problems as the
fallback was stop for a predetermined time and try again, so two of more nodes with collisions could keep colliding. But in a low utilisation/node density you could get better throughput than with token-ring. But a load that could bring ethernet to its knees would still be chugging along with token ring. A little like comparing a diseasal to petrol/gas or a
racehorse to a war-horse to completely different schools of thought.
Hmm, as Token-Ring had 16 MBit/s and Ethernet had 10 MBit/s, at least the
acn wrote to poindexter FORTRAN <=-
Someone once joked that you could tell who was a network person by asking them how many syllables were in the word "coax".
Could you explain this one to me? Sorry :)
I don't ever recall anything much causing network saturation though either. The only time I ever ran into issues was bulk copying via samba you could lock all the other nodes until copying finished.
Someone once joked that you could tell who was a network person by asking pF>> them how many syllables were in the word "coax".
Could you explain this one to me? Sorry :)
"normal" people pronounce it with one syllable, network people with two syllables.
I am/was certain TR had a lower signalling rate though.. Was there more
than one version maybe? Ahh there was 4 and 16Mbps versions...
I don't ever recall anything much causing network saturation though
either. The only time I ever ran into issues was bulk copying via samba
you could lock all the other nodes until copying finished.
either. The only time I ever ran into issues was bulk copying via samba you could lock all the other nodes until copying finished.
Well, that is a network saturation then :) And *that* wouldn't
happen in a TR network.
On 06-11-21 12:30, Spectre wrote to acn <=-
Sometimes you need to coax the coax into working :)
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 137:15:20 |
| Calls: | 2,073 |
| Files: | 11,136 |
| Messages: | 947,618 |