Hi bob1at7shore
Quote:
Originally Posted by bob1at7shore  Can you tell us more specifically how you got it to work? What memory did you share? Did you make the instance of nero static? I tried many different things like that, but always got the same result you had. I want to give it another try.
Thanks |
Very cruedly explained i did this...
I have made a solution i studio 2008 doing the following...
1) I have a shared memory warpper, enabling me to reserve a named part of memory and then streaming any object into it.
2) Both the managing code and the actual burning code and access this memory block by name. The name of the block is passed to the process at startup...
3) The managing code creates a nero object, examining number of burner present and then creates the corresponding memoryblocks and Burninfo objects containing the data to be exchanged between burning process and manager (i.e. progress - phase info and so on).
4) It then startes up the appropriate number of burning processes corrospondig to the number of present burndrives and passes on the name of the memoryblock, so that this process can share the Burninfo object with the managing code...
5) Now i have a burning process for each burndrive on the computer.
6) I communicate between the processes using IPC with SendMessage and wndproc override to send triggers telling the process or the manager, that the BurnInfo object has been updated in the shared memoryblock and that it should be examined... This is also used to command the burnprocess to start burning..
7) Every time a nero event updates the BurnInfo object, it is pushed into the shared memoryblock, the managing code is IPC'ed and then reads the object from the shared memory and updates the appropriate controls (progressbar and so on)...
All of the above i, for now, done very cruedly and needs a lot of cleaning up and retouching to be made failsafe. But the actual burning process works without any problems, so the actual multiple drive burning problem has been solved...
/FStampe