(1987)
HN user
seritools
near lossless refers to being 89.65/90.26 = 99.32% of baseline, i'm pretty sure.
just look at that giant 8-line headline, insanity
then add a second r and it's suddenly piracy or torrent related!
This has the side effect of removing empty directories
yeah, this will inevitably break things. excluding those from the directory stripping shouldn't be too hard (TM)
as far as i can tell, no it does not. it only desaturates 00 in particular. the other colors you see in the screenshots come from matched formats/patterns. it does not do direct coloring based on byte value.
pretty sure 486 support only _just_ got disabled, and will be gone with 7.1: https://www.phoronix.com/news/Linux-7.1-Phasing-Out-i486
headlines often trade legibility for terseness, sometimes a bit too much though :)
EDIT: Headlinese: https://en.wikipedia.org/wiki/Headline#Headlinese
I miss the wobbly windows I had in Linux when we started playing with Compiz.
KDE still has them: Settings -> Window Management -> Desktop Effects -> Wobbly Windows
you can also just uninstall the "new" notepad, at which point Windows will let you run the old one again (which is still shipped!).
By using a version that is _that_ old you do lose out on some of the actually useful updates legacy nodepad received, such as LF line ending support.
You are mistaken:
The malicious code would execute in the security context of the user who opened the Markdown file, giving the attacker the same permissions as that user.
TIL I'm an AI
not even opposite, as mentioned in my comment it does have Initiator Mode, allowing it to act as a host
If the reason to connect them is to dump them, something like https://bluescsi.com/ in Initiator Mode might work: https://bluescsi.com/docs/Initiator-Mode
For a quick fix: `font-variant-ligatures: none;` on body or similar.
Infocom was bought by Activision, ActivisionBlizzard was bought by Microsoft.
Author here -- previous discussions/blog posts:
https://news.ycombinator.com/item?id=23313577
https://news.ycombinator.com/item?id=31112273
I specifically checked if DirectInput from DirectX 5 already supports/provides USB HID devices, and it does! Granted, even then it was unlikely to encounter 8 USB devices, let alone HID devices in particular.
Because I felt like it :) Also works for multiple versions/patchlevels.
But yeah, with the info provided it should be patchable. It's a `push esi` though, where esi has to stay 0 for a few further usages, so it's a bit more than a one-byte patch. It also wouldn't fully resolve the OOB write in the rare case where you _do_ have 9+ game controllers connected.
Usually dgVoodoo handles most of the games (that don't have actual bugs like this game) fairly well.
Otherwise, 86Box is a pretty good full-system emulator for everything up to the early 3D era.
As for DRM, there's various ways around it of course :)
am I right in thinking the DirectX library only exports a single function and _everything_ else is through DX interfaces
Yup! That's why I didn't have to create a gazillion passthrough functions.
The original DLL in my modern Windows installation has these 8 exports:
DirectInputCreateA
DirectInputCreateEx
DirectInputCreateW
DllCanUnloadNow
DllGetClassObject
DllRegisterServer
DllUnregisterServer
The game only calls DirectInputCreateA, and the rest happens via the COM object that that function creates.Author here -- given that r9x is also my project it wasn't entirely random :^)
AFAIK they are all backed up. For the blogpost I used the DX5 SDK docs, DX7 SDK docs, and the MSDN Library from VS2005 (last version to include 9x information).
The VS2008 version purged all API information regarding pre-Windows 2000.
According to https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B#Histo..., the last version to support Win3.1 is VC++ 1.52 (which was shipped with VC++ up to version 4).
Unless you mean NT3.1 of course :^)
this comment thread hasn't been talking about win16.
but you're right, win16 can only load some 32-bit PE files through something like Win32s
sorry, i was referring specifically to the x86 segmented memory model: https://en.wikipedia.org/wiki/X86_memory_segmentation (basically, near and far pointers)
it would, just without standard library support, as the default stdlib imports system APIs that older versions don't provide. Other than those and a "supported OS version" filed in the PE header there isn't really much else in your way (hence my Rust9x project)
likely no_std, and running via Win32s. Rust doesn't have support for segmented memory, so native 16-bit would be much harder
it's the "thin" browsers that are half-embedded in other apps, such as Google News. In the menu you can see "Running in Chrome" and "Open in <yourdefaultbowser>"
"can do things" in this case doesn't mean "is allowed to do things".
"Unsafe code allows to express the following, which is UB:"