AnsweredAssumed Answered

vrf Kernal32 load problem (AKA Type Spoofin' for Ruby)

Question asked by VRFuser on Jan 18, 2008
Hi folks. Just wanted to let you all know I'm still around.

Barrie, you're problem is totally wacky. I glanced over the definitions, and I don't see anything obviously wrong. You know how these things go though:
they're almost *never* obvious. All I can say is I don't get how just importing can cause difficulties. Calling can be a whole different matter.
VEE is probably normal and it calls LoadLibrary & GetProcAddress when importing functions. If it's one of those two functions causing a GPF then we're all in trouble!

I got bit by a recent MS update too (last week). It seems SetFilePointer has finally been brought into line with the documentation (after something like
15 years!). One used to be able to call it with two DWORDs and get away with it when using huge files. That's not the case since last week. Unfortunately the Ruby Win32API extension doesn't understand QWORD, necessary for using the updated SetFilePointerEx.

Fortunately it's spoofable. One can split the Q into two Ds & tell the import facility the one Q parameter is two successive Ds and it works. This same principal can also be applied to VEE (which is why I thought of it in the first place and what makes this semi on-topic). All hail the Type Spoof, our nuclear friend.

You are currently subscribed to vrf as: To subscribe please send an email to: "" with the word subscribe in the message body.
To unsubscribe send a blank email to "".
To send messages to this mailing list,  email "". 
If you need help with the mailing list send a message to "".
Search the "unofficial vrf archive" at "".
Search the Agilent vrf archive at "".