Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

261–270 of 364 posts

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

#261
post #218
post #20

Earlier quoted context omitted.

The Something Terrible in this case is early DOS which did not have separate folders. So the device files were in the same namespace as the user's files, so the user couldn't name a file CON or LPT1. These are preserved for backwards compatibility. To this day you can write a program that writes to a CON file in any folder, and the program will print the write to console.

Another interesting aspect of this, which I remember specifically from reading MS-DOS manuals in the 90s as a kid (I was an incredibly fun 12 year old) is that this choice was an intentional one done in the name of flexibility. These device names were correctly written with a colon, but you are allowed to omit the colons. For instance: copy con lpt1 And copy con: lpt1: were interchangeable. If they’d chosen to not sa…

> Also, side note, the “copy con outputfilename.txt” idiom is one that I still can’t ever remember how to do the equivalent on UNIX/Linux!

cat > outputfilename.txt

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

#262
post #244

Earlier quoted context omitted.

I worked at a bank that had a windows-based trading system and for some reason created folders to hold the details of each book. There were issues when a trader decided to call a book "LPT1".

What is a 'book' in the context of trading?

short for "orderbook" - the set of pending trades pertaining to a client account

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

#263

Earlier quoted context omitted.

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

I’d bet RedHat 5.2.

That was my first. Then Slackware 3.6. Both as cover CD:s of computer magazines because that download was too much to handle on 56k.

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

#264
post #215

Earlier quoted context omitted.

This brings back memories. Every LAN group had that one friend like you. I'm sure you made up for it if, like my BSD friend, you were handy with network troubleshooting and always brought spare CAT-5.

Well eventually I just... provided all the machines... and the house... https://kentonshouse.com

You're a gentleman and a scholar.

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

#265

Earlier quoted context omitted.

love this story very much. I had no idea WINE had been around for that long and was able to play starcraft etc. I have really great memories of playing starcraft with friends back in the day.... that game had enough staying power that we could all get into and out of in middle school and then again in college!

Wine is nearly as old as linux. First released in 1993. I had some awkward conversations with my parents as a teenage nerd looking into "winehq". They didn't believe me that it had nothing to do with alcohol.

Even today, Blizzard games tend to run pretty easily on Wine. I always attributed it to them using a fairly old tech stack, but maybe it's the reverse and Wine development has just continued to go above and beyond for those games.

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

#266

Earlier quoted context omitted.

Microsoft, when confronted with a problem, think "I know, I'll build it on top of SharePoint."

Is Teams built atop SharePoint, or does it just integrate with it?

Creating a new team makes a sharepoint group complete with calendars, a site, email addresses, and file folders.

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

#268

The only thing defensible there is that channel names can't end with a period - the same should be true of all URLs. Kids especially when told to type in a URL will put the period/full stop after it in the instructions they're reading from then wonder why it doesn't work...if it simply wasn't allowed browsers could just strip it off.

Similarly, when drafting some sort of communication (email, documentation, etc.) one might have a URL as the last "word" of a sentence (or comma-delimited clause, etc.) and apply typical rules of grammar that say not to use a space between the last "word" and the subsequent punctuation. Then upon saving (or upon viewing, or sometimes upon hitting the space bar, depending on implementation) the automatic linkification kicks in, and in my experience enough of them aggressively trim such punctuation (period, comma, etc.) before setting the href that people can get away without thinking about this, but some linkification functions end up keeping it, yielding a 404 error when clicked. High-usage products like email clients and chat apps tend to aggressively trim, while lower quality products like ticketing systems tend not to, as far as I can tell.

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

#269

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...

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

#270
post #265

Earlier quoted context omitted.

Wine is nearly as old as linux. First released in 1993. I had some awkward conversations with my parents as a teenage nerd looking into "winehq". They didn't believe me that it had nothing to do with alcohol.

Even today, Blizzard games tend to run pretty easily on Wine. I always attributed it to them using a fairly old tech stack, but maybe it's the reverse and Wine development has just continued to go above and beyond for those games.

I know WoW is aware that's it's running in Wine. There are some setting greyed out in game with a message of not compatible when running in Wine.
Post reply on HN