Incredibly cursed error message that I just got on a work PC trying to launch Task Manager:
"Too many files are currently in use by 16-bit programs. Exit one or more 16-bit programs, or increase the value of the FILES command in your Config.sys file."
...now, that message is pretty cursed on its own (Task Manager is not 16-bit and should not be affected by 16-bit open files limitations), but this is 64-bit Windows 10.
Which doesn't even support 16-bit applications.
@bhtooefr god windows 10 is such a great os to hear about
@bhtooefr 64bits / 16bits = 4...
were you trying to run more than 4 16bit programs at once?
@bhtooefr I'm guessing this was probably some new stuff reusing an old error code from a header file: "oh, this code ERR_TOO_MANY_FILES sounds right" but they never checked what the error text displayed to the user said.
@bhtooefr ah, Raymond Chen actually wrote a blog post at Microsoft about this type of issue: https://blogs.msdn.microsoft.com/oldnewthing/20181203-00/?p=100375
@kepstin ...interestingly, MSDN says that ERROR_TOO_MANY_OPEN_FILES returns an error of "The system cannot open the file.": https://docs.microsoft.com/en-us/windows/desktop/debug/system-error-codes--0-499-
So now, I'm wondering if the PE loader or something really low level was coded to use that error when it failed to load a file, then some time around Windows 7 (SP1, maybe, I find references to this error happening on Win7 SP1 specifically), Microsoft changed the error description to match the error name?
@bhtooefr GENERAL PROTECTION FAULT
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!