#1 Burning Software

Hi,

I'm using the OCX, using code very similar to your C# burning example and (in fact, I have this issue w/ your example, but it happens worse on mine, for some reason) when the burn process starts, the GUI stops updating completely even though the burn process happens in another thread. I have stopped making it build the joliet image to check the space used (I'm going to write my own code to figure out the used space), but it still happens. The progress bar is updated here and there, but I can't (for example) drag the GUI around, or see what is happening on the form, etc.). CPU usage is low, I have 2 GB of memory, etc.. Also, the Commit Charge in Windows Task Manager jumps almost 300MB when I register the StarBurn license. My software is wizard-like, and the Commit Charge doesn't go up until I hit the screen where I load the StarBurn SDK.

I suppose I could just wait for the changes to the OCX and redo it (it'll be easier anyway), but I think this issue is due to the CallBacks. Any ideas?

Edit: I wanted to add that I AM using the appropriate cross-thread calls, as recommended by MS (using Delegates).

Thanks,
Amro

Hi!

We recently fixed some issues with memory consumption and maybe the problem you are having has gone in the latest OCX. I sent you the latest build, please check if the problem still exists.

Regards,
Alexander Orlovsky

thanks much. i'll try it later tonight.

I can't seem to register the new OCX w/ regsvr32.

regsvr32 StarBurn.ocx is the cmd i'm using. it says it can't find the file, but they're in the same directory..and i can register the old ocx w/ the same command.

Amro

I've fixed the GUI lockup issue (removed the thread-safe callbacks MS recommends..I can't debug it now b/c Visual Studio complains..but I can deal w/ that some other way. The memory issue still remains..and I think the OCX I received is corrupt (I've reverted to the older one I had until you get a chance to send it again ).

the new ocx works great. thanks. i wonder what the issue was w/ the other one

is there a way to cancel an ISO save? i see the cancel method stops joliet tree builds, but not saving of an ISO image file to the hard disk

Hi!

Concerning image saving I answered in the next thread.
The issue with OCX build was that MFC libraries were linked dynamically to OCX by mistake. Sorry for that.

Regards,
Alexander Orlovsky