@briankrebs this toot brought back memories. One of my first commercials was a spot called “Patch Tuesday” for a little company called Novell.
#netware
@kotinotter ikr?
RE: https://mastodon.social/@geerlingguy/115405861044215226
Just like the good ol' days. 🙂
I've commented before how these two #Microsoft #Win11 machines can see everything on my lan ... except each other 🤦♂️
#CoPilot tells me this is a known issue and I can either activate #smb1 protocol 😱 or perform a simple 7-step work around, 🤔 basically enabling #netbios over #TCP
Wrapping a non-error-correcting protocol inside an error-correcting protocol, for you non-nerds 🤓 instead of using an error-correcting protocol alone, b/c someone just can't say goodbye to #novel #netware🦕💩🧟♂️
#1995
Episódio 166 – 30 anos de Internet comercial no Brasil – Parte B
https://retropolis.com.br/2025/08/13/episodio-166-parte-b/
#Podcast #ADSL #anos2000 #AOL #Arachne #atari #BancoRural #BBS #BOL #BolhaDaInternet #Cello #CentroIn #Cisco #discador #EditoraAbril #elm #Encarta #Eudora #Fax #Firefox #FolhaDeSoPaulo #Frontpage #GIF #GilbertoGil #HotlineBBS #IG #internet #ISDN #Ita #microsoft #Mosaic #MSDOS #MSX #mutt #navegador #Netscape #Netware #Novell #Oi #PCComputing #PegasusMail #pine #Qualcom
#DOScember | Novell | The wired world of DOS networking
#DOScember | Novell | The wired world of DOS networking
#DOScember | Novell | The wired world of DOS networking
Un día como hoy 19 de junio, pero de 1924, nace Raymond Noorda, el Padrino de las Redes. De 1983 a 1994, lideró #novell y su #Netware para dominar las LAN, enfrentando a Microsoft. Un visionario de la "coopetición". Revive su historia en #retrocomputingmx #HistoriaTech #network
Sabías quién es Drew Major? El genio detrás de #Netware, el SO de red que conectó las empresas en los 80/90. Su código hizo posible las #LANNET antes de que existiera Internet. Un héroe retro en #retrocomputingmx #novell #HistoriaDeRedes
Linus actually has a good point. Filesystem case sensitivity has always, always been controversial. #NetWare was so secure because of the #filesystem case sensitivity (among other things) and then they allowed spaces. And I remember people fucking with NetWare servers by using weird filenames . In my AP compsci classes we were hiding warez that way. And now you see fucking EMOJI in filenames, and the spec changes on social whims at a drop of the hat. #tech #linux https://www.phoronix.com/news/Linus-Torvalds-Anti-Case-Fold
Hmm. I think, I will switch back to using AIR instead of Novell #NetWare for #GlobalTalk.
Something made AppleTalk on NetWare 4.11 crash for the second time now and AURP stopped working...
After starting AIR again now (with the latest nodelist from @kalleboo), I do see 87 zones now :)
@ahihi
I also can see your zone :)
The screenshot shows the #NetWare tool ATCON.NLM, the AppleTalk Console (with german locale, sorry for that).
#GlobalTalk
The latest #MARCHintosh Daily News just arrived via #GlobalTalk ! And even through my #NetWare server :-)
Thank you @dillera !
But page 10 seems to have some issues here... could you resend pages 9 and up? Thanks!
I've created a Python script which downloads the #GlobalTalk nodelist from @kalleboo, gets IPs for all hostnames and uploads the list as a #NetWare AURP.CFG file to the server (via FTP).
Together with CRON.NLM, which restarts AURP.NLM on NetWare, this should make it possible to follow all nodes :)
Hallo #GlobalTalk people! Can you still see the zone BabCom?
I've changed my AURP setup - removed AIR and made #Novell #NetWare 4.11 my AURP router system!
I can see many zones, although I've only added 3 IPs right now (unknown connections are allowed).
I'm just working on a method to update the AURP IP list. :)
@jamiesaker You had to ask. :D Let me add my tiny little contribution to your reach. I'm mostly into #DOS and OS/2 stuff myself, and I love maknig old hardware do stuff that nobody even thought of when they were new. Like running a web+ftp+irc server on a 286 (see http://floppy.museum). Or just re-living the old days, whether it's creative dying in #Sierra games or the hilarious exploits of #LucasArts adventures. I also run a #Novell #NetWare server on a 486, obviously under OS/2 because paravirtualisation was a thing on PC in 1994. #retrocomputing #os2
Another #Floppy #Museum and #BBS update!
TL;DR: The BBS is now served from the Novell server, and I've crammed a Novell client onto the http://floppy.museum/ floppy disk so it also runs a BBS node!
Long story:
For a while now, my BBS has been down because of corruption of message files, in turn caused by incompatibilities between OS/2's SMB implementation and that of #Samba. And since the latter has dropped support for old clients entirely, I had to do something to not only revive, but ensure the long-term survival of my BBS.
In my previous post on the subject, I bragged about my #OS/2 and #Novell #NetWare server. It's now serving most of my retro gear, including the machines that run my BBS nodes. I'm hoping this solves the problems I've had running multiple #Synchronet nodes.
And just for kicks, I managed to free up even more space on the floppy disk that the Floppy Museum boots and runs from, and squeezed in a Novell client. After a bit of fiddling to free up some RAM, I got a BBS node running, too! So now it has an HTTP server, an FTP server, an IRC server *and* a BBS node! All on an old 286. Beat that, The Cloud!
So fire up your Telnet clients and connect to floppy.museum, port 23!
(For anyone interested, the math challenge you get when connecting is a piece of nginx+lua code, you can find it here: https://github.com/ltning/telnet-challenge-proxy)
#retrocomputing #retro #286 #butwhy
TL;DR: The BBS is now served from the Novell server, and I've crammed a Novell client onto the http://floppy.museum/ floppy disk so it also runs a BBS node!
Long story:
For a while now, my BBS has been down because of corruption of message files, in turn caused by incompatibilities between OS/2's SMB implementation and that of #Samba. And since the latter has dropped support for old clients entirely, I had to do something to not only revive, but ensure the long-term survival of my BBS.
In my previous post on the subject, I bragged about my #OS/2 and #Novell #NetWare server. It's now serving most of my retro gear, including the machines that run my BBS nodes. I'm hoping this solves the problems I've had running multiple #Synchronet nodes.
And just for kicks, I managed to free up even more space on the floppy disk that the Floppy Museum boots and runs from, and squeezed in a Novell client. After a bit of fiddling to free up some RAM, I got a BBS node running, too! So now it has an HTTP server, an FTP server, an IRC server *and* a BBS node! All on an old 286. Beat that, The Cloud!
So fire up your Telnet clients and connect to floppy.museum, port 23!
(For anyone interested, the math challenge you get when connecting is a piece of nginx+lua code, you can find it here: https://github.com/ltning/telnet-challenge-proxy)
#retrocomputing #retro #286 #butwhy
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst