redefine your header using _stdcall. Â Vee uses _cdecl by default.
I might be having a problem with the definition file but not sure. The attached Vee program does write data to the parallel port but gives the error 739, stack pointer corrupted after return from compiled function.
--- You are currently subscribed to vrf as: Dave.Andersen@gdc4s.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
<div><span class="postbody"><font size="2">Hi, i m newbie in VEE Pro, currently doing some testing using VEE Pro and instrument DDM (GW iNSTEK, GDM-8246).
How am i get this problem resolve...</font></span></div><div><span class="postbody"><font size="2">Appreciate for help.
</font></span><span class="postbody"><font size="2"></font></span></div><div><span class="postbody"><font size="2">Regards, Jess</font></span></div>---You are currently subscribed to vrf as: rsb@soco.agilent.comTo subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to"owner-vrf@it.lists.it.agilent.com".Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
---You are currently subscribed to vrf as: rsb@soco.agilent.comTo subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to"owner-vrf@it.lists.it.agilent.com".Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
You could bump the limit up to 1.2501 -- 2 digits beyond the spec, thus "invisible"