AnsweredAssumed Answered

Re-2: vrf Running two processes of VeePro Runtime

Question asked by VRFuser on May 3, 2005
Actually, I wrote that paper a long time ago.  The picture on the
front page and throughout the rest of the docuement is of my dog Trixie.
As far as I know, it's the only official publication HP ever delivered
with a picture of a family pet gracing the cover.  She's still kicking,
albeit with a lot more white in the fur on her face.

That DLL hasn't been built with a newer version of Visual C in quite a while,
so you may want to recompile with a newer version. 

I haven't been keeping track of this thread, so I'm not sure what problem
you're trying to solve, but feel free to contact me if you need me
to explain what's going on inside that DLL. 

The part that references Richter's book is used to implement a multiple-reader
single-writer guard to prevent data corruption, while allowing concurrent
access.  The rest of it is basically just using Win32 memory-mapped files
to chain a list of shared memory regions.  That code was taken from a larger
project that had a data acquisition process that continuously grabbed
measurements from a digitixer card -- a 1413, if memory serves.  The Vee
program sort of spied on the data, looking at snapshots every so often.

> > A long time ago there was a white paper on the
> > (ancient) HP-VEE Website about memory sharing
> > with vee. I think it was from Jeffrey Richter.
> > I have it here, but its not easy and you should
> > have some insight to C and Win32 API. But if
> > you like, I can send it to you.
>
> I was just taking a look at this, and darned if the author isn't mentioned.
> Richter is given as a reference. If the author wasn't Greg Goebel I can't
> imagine who was.
>
> ftp://ftp.oswegosw.com/pub/VEEExamples/SharedMemory
>
> The whitepaper is sharedme.pdf. It's about 99 parts C with 1 part VEE and
> presents a few of the memory sharing concepts from Richter's book, "Advanced
> Windows". The rest of the stuff in the SharedMemory folder is stuff that I
> played around with for a while some time ago. It's probably directly out of
> the whitepaper.
> -SHAWN-
>
>
>
> ---
> You are currently subscribed to vrf as: doomer@soco.agilent.com
> To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
> 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".
>


---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
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".

Outcomes