Image File Execution Options & ApplicationGoo
-
Hi everyone, Does anyone have *any* idea how the ApplicationGoo registry key parameter works on Win2K? In fact, does anyone have a list of what parameters are available under the keys within Image File Execution Options? For those that know even less than me about this... Under the key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Image File Execution Options there are a Image File Name keys such as; qpw.EXE, cqw32.exe, install.exe, wpwin8.EXE, setup.exe (some of the vendor specific ones are obviously recognisable). Under each name key there are parameters such as DisableHeapLookAside, GlobalFlag (these seem to be booleam values as REG_SZ) and then there's the mysterious REG_BINARY ApplicationGoo... I'm guessing its something to do with Win2K compatibility i.e. when Win2K starts executing an image file it checks this and gives appropriate warnings, but I could be utterly wrong. I've hunted the Internet & MSDN for a quite a while but can't find anything of substance. Any ideas out there? Am I just being particularly dense? Someone give me some pointers? Anyway, kudos to the first on the buzzer with the right answer. TIA, Trevor
-
Hi everyone, Does anyone have *any* idea how the ApplicationGoo registry key parameter works on Win2K? In fact, does anyone have a list of what parameters are available under the keys within Image File Execution Options? For those that know even less than me about this... Under the key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Image File Execution Options there are a Image File Name keys such as; qpw.EXE, cqw32.exe, install.exe, wpwin8.EXE, setup.exe (some of the vendor specific ones are obviously recognisable). Under each name key there are parameters such as DisableHeapLookAside, GlobalFlag (these seem to be booleam values as REG_SZ) and then there's the mysterious REG_BINARY ApplicationGoo... I'm guessing its something to do with Win2K compatibility i.e. when Win2K starts executing an image file it checks this and gives appropriate warnings, but I could be utterly wrong. I've hunted the Internet & MSDN for a quite a while but can't find anything of substance. Any ideas out there? Am I just being particularly dense? Someone give me some pointers? Anyway, kudos to the first on the buzzer with the right answer. TIA, Trevor
ApplicationGoo looks like version resource stored in registry, at least on my machine. Have no idea what they're using it for. Maybe for comparing currently executing image with the one executed before? Tomasz Sowinski -- http://www.shooltz.com