Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

221–230 of 364 posts

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

#221
post #66

I'm old[school], so if I'm at the windows command prompt and need to bust out a quick batch file or script I will do "copy con foo.bat" instead of using notepad or vscode. Old habits die hard!

Same! I know there are one or more ways to do this in a Unix/Linux shell, but despite being off Windows for almost 20 years I haven’t memorized it. I miss it though!

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

#222
post #215

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…

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

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

#223
post #147

Earlier quoted context omitted.

\\?\GLOBALROOT\ anyone? Now you're opening devices from the NT object namespace rather than files. Bonus: You can create the file C:\con\con using NT Native API filesystem calls. Someone even made a video of installing Windows into C:\con\con, and the kernel-side stuff works beautifully, and the explorer shell side dies horribly.

>the kernel-side stuff works beautifully, and the explorer shell side dies horribly. So, just like running Windows normally then? :D

NT is Dave Cutler's best ideas for OS design, atop which Very Bad People piled the Win95 API and UX

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

#224
post #114

So many of these limits seem arbitrary. Why 5? Why 500000? While they seem OK for most customers, why not make many of them MAXINT?

That sounds crazy to me and I understand why Microsoft or any company wouldn't want to do that. It seems completely reasonable to me to set reasonable limits to avoid excessive resource usage or unforeseen/untested/unwanted performance limitations.

Bingo. Everything has a limit and when you set it yourself you’re moving the “how many x can I make?” answer from the “unknown” column to the “known and testable” column.

Imagine if you add a feature tomorrow that, on startup, has to run something in linear time with the number of channels you have. If the upper bound were essentially undefined (and not practically testable if it’s max int(32)) it could be that in practice your new feature makes it so that getting above 23,456 channels effectively disables the server due to a timeout in a critical part of startup. But if you’ve defined that channel limit, you can be confident that a feature like that either does or does not break things, even when at your channel limit, because you can test that.

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

#225
post #215

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…

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.

CAT-5, lucky you :) We still got zapped!

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

#226
post #24

Why is it that most "chat/conference" apps become horrible sooner or later? I still remember when teams used to be an OK app. It even had a Linux desktop client. I remember when slack was actually fast, I remember Skype out being more reliable to make phone calls than my mobile/cell service. Today slack is extremely slow if you add few organisations to it (but at least you can add more than one). Teams has deprecated…

Because believe it or not, a chat/conference is the most easy gateway to an "everything app" just like with WeChat. Afterall, a chat/conference app is a microcosm of the "internet". Your chat app is great but imagine if we can send/share audio clips too. Your chat app is great but imagine if we can send/share video clips too. Your chat app is great but imagine if we can send/share live video too. Your chat app is gre…

That's why I'm not enthusiastic about Musk's vision for X...

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

#227
post #33

Earlier quoted context omitted.

> essentially leaking the existence of something terrible inside It's just a restriction imposed on SharePoint folder names bubbling up. Nothing fancy.

Those should obviously be UUIDs. Labels and titles should be a simple changeable, internationalizable attribute. Like usernames. You don’t use usernames as primary keys for anything, do you? What happens when people marry?

> Like usernames. You don’t use usernames as primary keys for anything, do you? What happens when people marry?

well it's extremly painful to rename the primary mail address or the UPN when it comes to microsoft 365 and active directory, especially in a hybrid environment. of course you can change upn's but it's definitly some kind of "primary key" for a user. in fact most systems at least use a UPN

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

#228

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!

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.

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

#229

Earlier quoted context omitted.

One man's tech debt is another man's API stability

One man's API stability is another man's perpetual nightmare, especially if the API is bad. Things have to change to get better, and if systems are designed in a way which prevents API improvements, then you will just have perma-crap software.

This seems an odd place to be making this argument though. Of all the things that you might do if you had carte blanche to break all backcompat in Windows, you’d really pick these reserved words? like, how important is it to make a file named just con or prn? Or a Teams channel or Sharepoint group for that matter? I’d be aiming more for something like the backslash as path separator, or eliminating all system dependencies on drive letters. (I know NTFS can mount elsewhere, but too much stuff uses and assumes drive letters.)

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

#230
post #50
post #2

Words: forms, CON, CONIN$, CONOUT$, PRN, AUX, NUL, COM1 to COM9, LPT1 to LPT9, desktop.ini, _vti_

Now I actually wonder were there ever any machines that had LPT9, COM9 I could barely see.

Back in the day many of my clients had Windows NT/2000 machines running RAS or RRAS with multi-port serial cards connected to modems for employee remote access. Usually these would be 8 or 16 serial ports per card with multiple cards installed per server.
Post reply on HN