Hi lets say I want to load" AddAtomA" from GetProcAddress, but instead of passing a string I pass a ordinal, here I use 0x02 for AddAtom:

This works fine on XP SP2, my question is will this change per OS (or service pack)? And also how can i make this work on multiple windows OSs?

-Thanks

per OS (AND service pack) since Win95 to date. I wonder why they do that. No way they would add to or take away from every single API but they change every API syntax (dword) causing the ordinal to change. I guest this is their way of keep the OS beyond (too much) scope. Just another form of protecting the OS and it secrets i guest.

When someone find something great, MS takes it away with a new service pack. If we were them, we probaly do the same...

Thanks that helped me out. Is their anyway I can be consistent using ordinals or am I just out of luck?

My goal: Use GetProcAddress without passing the API names as strings (and work at least from Windows 98 - Windows XP)

Microsoft should never have supported import-by-ordinal in the first place. There's nothing really great about them: doesn't mean much wrt. speed, doesn't add any obfuscation value, et cetera. The only thing you can save is a tiny bit of exe size, but that's utterly irrelevant unless you're doing <4k intros.

I would do it just like any other search procedure. Cmp to see what OS is running than use what-ever Ordinals needed. You will surly end up with lots of cmp's and extra PROC's but big deal, you still get all the speed that ASM has to offers and disk space is cheap these days.

It's more fun than work. I do it all the time to keep in-step with 95 - xp the standard way ( I skip the ones i no longer have no interest in)

That's why I always say "my crazy code". More cmp and jmp that would drive anyone nuts in minutes. So yes, you can, if your up for the task.

f0dder, we might as well take advantage of that. So, using ordinals is cheaper If one choose to be backward compatible, JohnCal concerns about using ordinals got to be as good as any other, if not better. How to do it ? Others knows better because I never tried it before.

Good Luck

iic2, if you need to have special-cases to support different OS (heck, even service pack) versions, you're going to lose any speed advantage ordinals could gain you (which I doubt is measurable anyway), your app will likely break on any OS/SP version you haven't tested, and one will have to question why you bother.

The only valid reason for import-by-ordinal would be some crazy-ass imports that aren't available in named form, but fortunately those are relatively rare... and usually something you shouldn't be messing with anyway.

stupid question: why would you want to use the PE import table if you could just use GetProcAddress?

f0dder, Too late. I done it all ready, and I could had done it using ordinals and would have founded a way to make it easy to work with. I test everything with every OS by nature. Speed is not a problem. JohnCal, has his reasons. I'm sure he been around. He need help now, not me. I bet he knows the things you mension and just need to be sure of a few things. I was just throwing out ideas based on one of his questions.

See you latter