heya homersux
"he disassembled assembly contains too much text information, i.e.
mov eax, dword ptr ds:[esi+4]"
yes, but i peronally think it is better readable like, but
it is more likely a programmer's own choise, there isn't bad or not bad way to present it.
but mabye i will be able to add a feature which the user can select whatever he want to see more/less about the assembly. (i'll see what i can do)
"it does not load all executible sections"
care to bring example infront of me?
"it cannot close a file (unmap from memory)"
actually its not a bug, i just didn't add it.

, i'll work on it.
"I'd like to see pvdasm geared
towards a specific functionality"
what more specific functions should you think to be added?, i did add Masm Source Code generator Wizard for example, plugin system..etc
well, i alweay said i would gladly take any new ideas to be added.
"pvdasm is certainly useful, I do use it from time to time"
glad to hear, i always stated that pvdasm can be used wisely if other tools can be played among, it does not exist to replace or to outlast any existing tool.
it brings out a variant options to the community.
"(filemap.exe it was called)"
haha

yes, actually i had VS6 to generate filemap.exe every time, because pvdasm was in the very begining a test about memory maped files

, but now i changed the VS6 generation settings
i do promise to do the best to keep pvdasm worthwhile.