StarBurn_UpStartEx returning Error 37

xexx · **Joined:** Tue Oct 31, 2006 12:25 am **Posts:** 43

Hi

What does a 37 result from a call to StarBurn_UpStartEx mean?

StarBurn version: 6.10.10.4112

anton (staff) · **Posted:** Fri Dec 08, 2006 11:17 am

You could perfectly answer this questions yourself. After looking to StarBurn.h or it's Pascal equivalent. "Wrong OS version". I can bet you've tried to run OCX over Windows 98/Me. This is not supported. If it's something else - please send us complete debug log to support@rocketdivision.com. Thanks!

xexx wrote:

Hi

What does a 37 result from a call to StarBurn_UpStartEx mean?

StarBurn version: 6.10.10.4112

xexx · **Joined:** Tue Oct 31, 2006 12:25 am **Posts:** 43

Hi Anton

Yes, naturally StarBurn.pas was the first place i looked, but if you check it, you'll see it only goes up to index 36.

I'm not using the OCX, just the DLL. Windows version is "ME", is that a problem?

I'll send you the log once I get it from the user.

anton (staff) · **Posted:** Sat Dec 09, 2006 5:54 pm

Both are problems of the StarBurn. Confirmed and fixed. From now Pascal header would contain all of the error codes from C one and library initialization routine would show only warning for OSes < Windows 2000. Thanks for feedback.

xexx wrote:

Hi Anton

Yes, naturally StarBurn.pas was the first place i looked, but if you check it, you'll see it only goes up to index 36.

I'm not using the OCX, just the DLL. Windows version is "ME", is that a problem?

I'll send you the log once I get it from the user.

xexx · **Joined:** Tue Oct 31, 2006 12:25 am **Posts:** 43

OK, when will the fixed updates be available?

anton (staff) · **Posted:** Sun Dec 10, 2006 9:39 am

With the next StarBurn release. End of December 2007.

xexx wrote:

OK, when will the fixed updates be available?

xexx · **Joined:** Tue Oct 31, 2006 12:25 am **Posts:** 43

Hmm, I was planning to advise my customers of this release very shortly, but this sounds like it will be a common issue which will make the software unusable on affected systems.

Are there any workarounds?

anton (staff) · **Posted:** Mon Dec 11, 2006 12:16 am

1) This is very bad idea to issue your customers with RC or beta builds. Unless there's a reason to do this (like checking bug fix happending on customer machine only).

2) Yes. Wait for the release.

xexx wrote:

Hmm, I was planning to advise my customers of this release very shortly, but this sounds like it will be a common issue which will make the software unusable on affected systems.

Are there any workarounds?

xexx · **Joined:** Tue Oct 31, 2006 12:25 am **Posts:** 43

Alas when I purchased and was sent the DLL's I wasn't advised they were not safe for distribution and now my code depends on the updated version.

Does the issue affect all ME installations?

Also, i assume by "End of December 2007" you mean end of this December

anton (staff) · **Posted:** Mon Dec 18, 2006 6:15 am

1) This is common practice.

2) Yes.

3) Yes.

xexx wrote:

Alas when I purchased and was sent the DLL's I wasn't advised they were not safe for distribution and now my code depends on the updated version.

Does the issue affect all ME installations?

Also, i assume by "End of December 2007" you mean end of this December

#1 Burning Software

StarBurn_UpStartEx returning Error 37

Who is online