pouët.net

Blueberry information 1218 glöps

• general:
• level: user
• personal:
• first name: Aske Simon
• last name: Christensen
• cdcs:
• cdc #1: Nexus-7 by Andromeda [web]
• cdc #2: Tint by The Black Lotus [web]
• cdc #3: Gift by Potion
• cdc #4: STS-02: Electric Kool-Aid by Synesthetics
• cdc #5: Rink a Dink: REDUX by Lemon.

• demotool Windows Crinkler by Loonies [web] & TBC
• Interesting request, producing a DLL using Crinkler. I went on a little investigation to figure out if this was (reasonably easily) achievable. There are a bunch of issues:
  
  - Crinkler produces an EXE file, rather than a DLL. The format is almost the same - there's just a flag that indicates that the file is a DLL. Adding an option to Crinkler to set that would be very easy. It can also be easily patched in manually, by changing 00 to 20 at offset 1B in the output file. So far so good.
  
  - To produce an export table containing the exported functions, use the /EXPORT option. This process is different from how exports are usually specified (since the intended use case is somewhat different). Every exported function needs its own /EXPORT option on the Crinkler commandline.
  
  - The DllMain function is not published though an export, but rather through the entry point. Specifying this function for /ENTRY is indeed the correct way. It is called automatically when the DLL is loaded (by LoadLibrary or via import) and can't be called explicitly.
  
  - EXE files produced by Crinkler use a fixed base address of 0x400000 (the usual base address for EXE files) and do not include relocation information. Thus, to be loadable into the same address space as the host program, that program must be placed somewhere else. This can be achieved via the /BASE option to the Visual Studio linker. To further shrink the amount of address space taken up by the Crinkler-produced DLL, specify a small value to /HASHSIZE.
  
  - The Crinkler entry point performs decompression and function import and then calls the user-specified entry point. This code depends on certain registers having specific values at entry (specifically, EBX points to the PEB), which might not hold for DLL entry point invocation. Also, this code does not save the registers required by the calling convention, which could mess up the calling function.
  
  - The export table produced by Crinkler is part of the compressed data, so it is not available before the decompression code has run. I don't think anything actually tries to look at the export table before calling the DLL entry point (which will do the decompression), but you never know...
  
  Anyway, I tried to see if I could produce a DLL with Crinkler this way and load it. It got as far as actually loading the DLL into memory and calling the entry point (decompression code), but somewhere between here and being fully decompressed, something goes wrong, and the initilization fails. I have not been able to locate it further.
• isokadded on the 2019-10-11 19:13:54
• demotool Windows MacOSX Intel Clinkster by Loonies [web]
• Most likely the tools do not have permission to write to the directory because it is placed within "C:\Program Files". Try placing it somewhere outside "C:\Program Files" and see if it works. It might also help running the script as administrator.
• isokadded on the 2019-09-21 22:45:09
• musicdisk Windows Tiny Sound Planet by Eos & LNX [web] & Titan [web]
• Lots of great music in here. This would be perfect to have running in the background while doing synth coding - if it wasn't for the fact that it quits any time Esc is pressed. :-/
• isokadded on the 2019-09-07 18:39:54
• demo Windows fr-036: zeitmaschine by farbrausch [web]
• Still one of my favorites. And it is even more awesome in 144Hz. :)
• isokadded on the 2019-09-03 23:11:00
• 4k Windows One Way Trip by Pungas de Villa Martelli [web]
• Yet another fractal flyby, but a pretty nice one at that. :)
• rulezadded on the 2019-08-19 20:28:14
• demotool Windows Crinkler by Loonies [web] & TBC
• By the way, a nice trick I found for debugging a crash in Wine:
  
  Copy the .pdb file for the program you are trying to run next to the .exe file. This will cause the Wine crash dump to include symbol information.
• isokadded on the 2019-08-18 22:15:37
• demotool Windows Crinkler by Loonies [web] & TBC
• I investigated the Wine crash.
  
  To implement forwarded RVA imports by link-time forwarding, Crinkler needs to inspect the actual DLL inported, rather than just the LIB file. In versions prior to 2.1, we just loaded the DLL using LoadLibrary, but this does not work with the 64-bit Crinkler, since you can't load a 32-bit DLL into a 64-bit process. For this reason, we implemented our own DLL loading and parsing function in 2.1.
  
  Apparently, the DLLs in Wine (at least kernel32.dll and user32.dll) have a different structure, which causes this function to crash.
  
  This issue could possibly be fixed in Crinkler, but there is a workaround for running the current Crinkler on Wine:
  
  Copy kernel32.dll and user32.dll from C:\Windows\SysWOW64 on a real Windows to the current directory (from which you run Crinkler) on your Wine machine. This will cause Crinkler to find those DLLs instead of the ones in the Wine installation. This is actually a good idea in any case, since this will prevent picking up bogus forwarded RVA imports from the Wine DLLs.
• isokadded on the 2019-08-18 22:11:49
• 1k Windows Searching For The Silver Lining by Fulcrum [web]
• What jco said.
• rulezadded on the 2019-08-10 21:18:12
• 4k Windows Storm Riders by Unknown Artists [web] & xzm
• I smiled at the nod to ASD. Nice technique and colors!
• rulezadded on the 2019-08-10 21:14:31
• 4k Amiga OCS/ECS A Hymn to Hipparchus by Offence [web] & Brainstorm [web]
• Really cool and well utilized technique. And joyful Cinter music!
• rulezadded on the 2019-08-10 21:01:28