Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

271–280 of 364 posts

Re: MS Teams channels cannot contain MS-DOS device names

#271

Earlier quoted context omitted.

In the mid-90s there was a fun and short period of time where IRC clients like mIRC could be set to auto-receive files through DCC.. and would happily write to names like LPT1 (which of course would just write the data directly to the recipient’s printer)

Also, send a COM1 file containing "+++ATH" to someone you dislike to see them disconnect. I just made this up but it should work, right?

For the absolute worst modems, I believe you could just send that in a PING on IRC and their client would write the string back and hang up

Re: MS Teams channels cannot contain MS-DOS device names

#272

Earlier quoted context omitted.

It's still being played heavily and professionally in Korea and there are many non Korean tournaments too. I watch pro matches everyday!

> heavily Sadly not the case, as much as I love ASL the scene has zero new blood. SC2 really killed the Brood War scene, and League of Legends really killed SC2. The days of packing an aircraft hanger with 30,000+ fans for OSL finals are long gone. I was invited to the Stormgate alpha, and while I can't say anything about it (NDA), I am hopeful it will bring new life into RTS esports.

IvOry just qualified for ASL. That’s definitely new blood.

Re: MS Teams channels cannot contain MS-DOS device names

#273
post #246

Earlier quoted context omitted.

Probably. I just remember installing from a dozen+ 3.5" floppies onto my pizzabox '386 and breathing a sigh of relief when it booted.

I think I needed 17 floppies ... and I could only scrounge up about 8, so I assumed it wouldn't need the earlier ones again and reused them for later parts. It worked! I didn't use Slackware much though, as I had no way to connect that machine to the internet, so it was really hard to learn how to do stuff.

I think I actually still have an "Introduction to Slackware Linux" book.

Re: MS Teams channels cannot contain MS-DOS device names

#274

Earlier quoted context omitted.

mormon family.

Thanks, Mormons are some of the most nicest and chill Americans I've met in Europe. Had no idea alcohol is taboo.

They're also good at getting security clearances since they never do anything, so those might've been CIA agents.

Re: MS Teams channels cannot contain MS-DOS device names

#275

Earlier quoted context omitted.

Arch wasn't around in 1998. I'm going to put my money on Slackware.

I used to love slackware, by far the best linux experience. It just worked well.

I still do. It still does...

Re: MS Teams channels cannot contain MS-DOS device names

#276

Reminds me of the rumor that the reason it went "Windows 7", "8", "10" and skipped "9" is because the fear of a codebase that went: if(version.StartsWith(“Windows 9”)) { /* 95 and 98 */ ... }

Is the Windows version ever exposed as a string in the Windows API? Seems strange in my mind, but I have no experience with Windows. On the one hand it sounds like something Microsoft would do for backwards compatibility, but on the other hand it seems like a weird API to provide. I found GetVersion[1] but that returns the version as two numbers. [1] https://learn.microsoft.com/en-us/windows/win32/api/sysinfoa...

I don't know if the rumor is true, but even if Windows itself doesn't provide an API that looks like that (I also looked around real quick and didn't find anything), it's not unreasonable that there could be libraries that provide the version that way.

Re: MS Teams channels cannot contain MS-DOS device names

#277

Earlier quoted context omitted.

Thanks, Mormons are some of the most nicest and chill Americans I've met in Europe. Had no idea alcohol is taboo.

They're also good at getting security clearances since they never do anything, so those might've been CIA agents.

>They're also good at getting security clearances since they never do anything

I never understood why you should mass deny security clearances to people who like to "party".

Re: MS Teams channels cannot contain MS-DOS device names

#278

Circa 1998 I was a teenage Linux zealot who would attend LAN parties carrying a Linux box. It actually worked -- at the time, WINE practically existed to support Starcraft, Quake 2 could run natively, and that covered like 95% of what people were playing. One time I thought it would be funny to run a shell script that looped through every Windows share on the network and tried to open `CON/CON` on it, resulting in a…

Was that over IPX? I don't think I ever configured IPX on Linux. By the time I was using enough Linux to run Starcraft on Wine, it already supported IP.

Re: MS Teams channels cannot contain MS-DOS device names

#279

Reminds me of the rumor that the reason it went "Windows 7", "8", "10" and skipped "9" is because the fear of a codebase that went: if(version.StartsWith(“Windows 9”)) { /* 95 and 98 */ ... }

Is the Windows version ever exposed as a string in the Windows API? Seems strange in my mind, but I have no experience with Windows. On the one hand it sounds like something Microsoft would do for backwards compatibility, but on the other hand it seems like a weird API to provide. I found GetVersion[1] but that returns the version as two numbers. [1] https://learn.microsoft.com/en-us/windows/win32/api/sysinfoa...

[deleted]

Re: MS Teams channels cannot contain MS-DOS device names

#280
post #235

Earlier quoted context omitted.

This is really cool! Did you build a similar house?

Not similar, I built that house. (I'm Kenton.) Or do you mean the new one, alluded to on the site? It's almost done... not ready to share yet. ;)

Great site - I am reading all your posts about the LAN party house now. Do you have the real estate listing of the house when it was up for sale? I'm just curious as to where it was located - you mentioned a sliver of land, and I saw the asking price ($2M in Palo Alto) so I'm curious to see what it looked like from the outside and its location, if you don't mind sharing!
Post reply on HN