#1 Burning Software

Hello Support,

Just I started the working with Vista64 machine. I am using Starburn SDK in VB.Net 2005 environment version - Version 10.0.0.1 ( Build 2008-07-14 )

I found the problem while initializing the Starburn SDK .

The code is as ...

Public starBurnX As RocketDivision.StarBurnX.StarBurnX

starBurnX = New StarBurnX()

IS NOT WORKING.

I tried to debug. But when control comes to the "starBurnX = New StarBurnX()" statement, an EXCEPTION is thrown. Here it is..

" FatalExecutionEngineError was detected
Message: The runtime has encountered a fatal error. The address of the error was at 0x7fa775fb, on thread 0xa0. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack. "

After this program gets stopped again and again. So I am not able to continue with the program. I also tried to register the DLL STARBURNX.DLL and it get registered but same problem is coming again and again. So everything is stopped now with developement bcoze nothing is going to continue.

My computer is VISTA 64 bit. I am trying to send you some of the information :-

Operating System : Microsoft® Windows Vista™ Ultimate
Operating System Version : 6.0.6001.65536
Physical Memory : 140296192
Language : English (United States)
Application Major Version : 1
Application Minor Version : 0
PlatForm : 2
ServicePack : Service Pack 1
DirectX Version : 4.09.00.0904

Can you please tell me why it is happening?

Its URGENT please.

Any help will be appreciated.

Thanks in advance

Hello,

You should set the x86 target platform for your project!

Note that you CANNOT use the StarBurnX for development the native 64 bit application!

Regards,

Dmitry!

Hello Support,

I am using StarBurnX VB.NET Samples. Having a simple query regarding development.
1) I am using same concepts as in VB.NET samples. I am having a query regarding releasing any COM(as StarBurnX is wrapper) object using Runtime.InteropServices.Marshal.ReleaseComObject(...) after it's use is complete.

2) Example : I am using objectToDelete(Type: DataFile) for removing a file from object. After removing a file from object should I manually remove objectToDelete, using above function or wait for .NET garbage collector to GC that.

3) It's of NO connection with burning, I guess but just for Good Programming practice I want to do that because after removing that object holds values which are pointing to nothing.

I was not sure about should I ask you this question because it is not related to StarBurn at all, but I thaught Dima will clearly give me a proper solution to this question because I may follow something but later I will get some errors and can't figure out what was the cause of problem while burning or some where-else.

I guess I am not troubling you with a lot of questions but the help files you have provided are having very less information. And lot of information is available on web but what to follow is the main question. But with StarBurn forum only I am getting a lot of information and which I mainly require . Thank you for such a good forum in which answers are clear and immediate replies for any question are available. Can I get some more help files to refer while development or sources, links to follow to clear concepts.

Thank you once again.

Hello,

As far as I know use of the ReleaseComObject is a good practice ... so i guess you may use this method:) If you has decided to use ReleaseComObject you should use this method always.

Regards,

Dmitry

Hello Dima Sir,

1) What is StarBurnX12.dll.manifest?
2) Do I need include in my distributable dlls with StarBurn.dll & StarBurnXV12.dll?

Thank you.

Hello,

This manifest can be used with "Isolated COM".

Please read this article: http://msdn.microsoft.com/en-us/library/ms173402(VS.80).aspx

Regards

Thank you Dima Sir.

I guess this is related to C++.
I am using .NET. Is this manifest intended for .NET users also?

Yes!! It's common feature of Windows OS !!

Regards,

Dmitry