Certain locations and offsets in DF have changed, so the old reveal.exe doesn't work. I even tried patching the locations directly into reveal.exe and it didn't quite work right.
I do agree on the bulkiness of the .NET runtimes, especially as I needed multiple versions to get tweak running, and I'm not even sure which versions are required, I ended up installing everything I could find. It was frustrating.
reveal.exe does work when it has an appropriate memory.ini, I just tried it on v0.28.181.40d and it worked flawlessly. Also, my
config generator is capable of generating config files for Rick's old tools, since that's why I originally wrote it; I even have configs back to v0.28.181.39a, I could've had more, but I deleted the very old ones.
v0.28.181.40d:
[generic]
DWARF_FORTRESS=0x009845D4
[address]
MAP_DATA=0x015C4D58
MAP_X_COUNT=0x015C4D70
MAP_Y_COUNT=0x015C4D74
MAP_Z_COUNT=0x015C4D78
MENU_STATE=0x01393260
FOCUSED_CREATURE=0x00D870F4
STARTING_DWARF_COUNT=0x00853A89
STARTING_POINT_COUNT=0x00852C0A
MOUSE_X=0x009FC294
MOUSE_Y=0x009FC298
MOUSE_Z=0x009FC29C
CREATURE_VECTOR=0x01583228
[offset]
MAP_DATA_DESIGNATION_OFFSET=0x0264
MAP_DATA_OCCUPANCY_OFFSET=0x0664
CREATURE_NAME_OFFSET=0x0000
CREATURE_X_OFFSET=0x0094
CREATURE_Y_OFFSET=0x0096
CREATURE_Z_OFFSET=0x0098
CREATURE_BODY_PART_HEAL_VECTOR_OFFSET=0x02FC
I've never installed a .net runtime directly myself, except once when I upgraded Vista's 3.0 to 3.5. I've always installed it through installing Visual Studio. But I can say that .NET 1.0 is different from .NET 2.0, I don't know how 3.0 and 3.5 fit into the picture.