Conversation

Notices

1. Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 16:56:20 JST Foone🏳️‍⚧️

   MSDN's "the past doesn't exist" policy is so harmful. Yeah sure, you're not gonna get a 0x2000 wParam in SYSCOMMAND since Windows 3.1 or whatever, but this code still is checking for it and I have no idea what it means, and MSDN pretends 0x2000 doesn't exist b

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 16:57:21 JST Foone🏳️‍⚧️

     in reply to

     SOME OF US ARE STILL REVERSE ENGINEERING PROGRAMS FROM WINDOWS 95 AND NEED THE WIN95 DOCS, MICROSOFT

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 16:57:51 JST Foone🏳️‍⚧️

     in reply to

     I'm gonna have to go dig out my MSDN CDs and find one from the win95 era

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 17:00:59 JST Foone🏳️‍⚧️

     in reply to

     • *neptunyl⁷-hydroxide :neptune: :neobot_cofe:

     @ada I think microsoft doesn't like that, or someone would have already put one up

   • *neptunyl⁷-hydroxide :neptune: :neobot_cofe: (ada@zoner.work)'s status on Friday, 20-Dec-2024 17:01:06 JST *neptunyl⁷-hydroxide :neptune: :neobot_cofe:

     in reply to

     @foone@digipres.club honestly i wonder if it's worth it to back all of it up on a public mirror or smth

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 17:12:08 JST Foone🏳️‍⚧️

     in reply to

     darn. I got some from the winnt 3.x era (July 1994) and there's a bunch of winapi docs but they're compressed and you gotta run the (16bit) decompressor to use 'em

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 17:19:32 JST Foone🏳️‍⚧️

     in reply to

     it needs a win32 version of the EXPAND.EXE tool that includes the /r flag.

     windows 10 seems to have an expand tool, but it lacks /r.

     fortunately they included copies of EXPAND.EXE on the disc!

     ... for WinNT Alpha and WinNT MIPS

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 17:20:06 JST Foone🏳️‍⚧️

     in reply to

     they did technically include EXPAND.EXE for i386, except THEY COMPRESSED IT. So I need expand.exe to get a copy of expand.exe!

   • Tim 🎮 (timixretroplays@digipres.club)'s status on Friday, 20-Dec-2024 17:22:02 JST Tim 🎮

     in reply to

     @foone and it's particularly galling too because surely the entirety of the documentation and resources from that era might be... A few dozen megs in size? You can't buy a system today that would struggle to serve that. It's a rounding error in terms of ongoing resources to support.

     Needs 16 bit software to extract? That's an intern's afternoon puzzle to solve. Not compatible with your current CMS? Zip it and link to it from anywhere, when that Foone person needs it they'll know what to do.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 17:22:36 JST Foone🏳️‍⚧️

     in reply to

     maybe the MS-DOS expand (which has no /r) can extract WinNT EXPAND.EXE (which might)

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 17:23:57 JST Foone🏳️‍⚧️

     in reply to

     it can!

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 17:27:08 JST Foone🏳️‍⚧️

     in reply to

     I think all these files are the raw postscript they used to make the Microsoft Win32 Programmer’s Reference, Volume 1

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 17:30:09 JST Foone🏳️‍⚧️

     in reply to

     actually it turns out all this was pointless. The EXPAND with windows 10? it has -R. I was accidentally running some other expand utility I had installed

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Friday, 20-Dec-2024 17:44:41 JST Foone🏳️‍⚧️

     in reply to

     no luck. The docs don't mention anything about 0x2000, neither do the header files.

     I think this code is just wrong, and they were checking for a code that can't be sent