#1 Burning Software

It's not in 10.5 you need 12 for it. Ask support@rocketdivision.com if you did not get a download link for preview version.

Hello Ben,

You can download the StarBurn SDK v12 Beta from our ftp:

link was removed

Note:
- you should update reference on StarBurnX for your application.
- this new version need new key. We will sent you this new key by e-mail.

Regards,

Dmitry

Alrighty, I have 4 computers 2 of which I use for dev and the other two for testing and personal. Two computers have windows 7 and the other two have xp. On the Windows 7 dev computer the starburnv12 registers fine however on my dev xp computer and other two personal computers it does not register. Is there something I am overlooking? Everything works perfect with v 10.5 on all computers, but not with v12. I've un registered, registered, changed paths, tried without SPTD and with SPTD installed (probably doesn't matter), etc but still does not register. Any Ideas?

Ben

Hello Ben,

1) " .. StarBurnX does not register .. " - does it mean that regsvr32.exe displays error during registration?

2) Do you register the x32 version of StarBurnX ?:)


Regards,

Dmitry

Hi Dmitry,

I found out what the problem is. I was registering Starburnx12.dll just as I was with Starburnx.dll, however unlike Starburnx.dll I saw in the C:\Program Files\Rocket Division Software\StarBurn SDK V12 Trident II\Bin\Core\StarBurnX\x86\ folder a starburn.dll library. So once I saw that, I figured it was required for the starburnx12.dll to be registered.. and it was. So now everything is all up and registering ok (on this computer). Thank you, I will let you know if the new library and SPTD work with the burning problem we are having.

Ben

Not sure about what burning problem are you talking about. I though it's componen registration issue you've sorted out, isn't it?

Hi yes the recent issue was getting the component registered, but the problem in its entirety has been the "drive is not ready to burn" error that more and more of our customers have been receiving. The updated library and using STPD is supposed to fix that as you have suggested from earlier posts. None of the customers are answering their phones so will just have to wait until I can test it out on one of the problematic computers.

AFAIR according to the logs you've sent there were no media in drive you've been trying to burn to. I would not blame StarBurn SDK here rather I'd suggest you to check your own code as for multi-device installations (quite popular among destop users, add virtual CD-ROM/DVD-ROM as well) you could swap actual enumerated burner with the other one. Or it could be brain-dead user putting recordable disc to say drive D: and willing your app to use drive E: for burn and so on. We've seen both of these cases millions of times with our StarBurn SDK customers and StarBurn users as well.

Hi Anton,

I am currently on the persons computer right now over a remote support session. I have verified the correct drive, correct recordable disk, there is no virtual drive software installed at all. We have installed on other windows 7 32 and 64 bit computers and have burned perfectly fine. I have uninstalled and updated the device drivers on all media, installled SPTD and enabled it in the software, disabled all firewall antivirus, made sure the customer was logged in as administrator disabled any type of service even remotely associated with virtual drives. I honestly don't know what to try next. It is not just my software, when I install the rocket division sdk and run the samples, I get the same error when trying to burn. Our customers are more than willing to let us on their computers so that we can find out what is happening. It does not make sense to be your sdk, but also doesn't make sense to be windows 7. Do you have or know of a burning application that uses the starburn sdk so that I can try it on this users computer and make sure its not your sdk? Should we ship the customer an external cd burner to try out? I am completely out of ideas, would it be possible for one of you to hope on this customers computer and see what is happening?

Thank you,

Ben

Sure. If you'd manage to have us remote session we'll be happy to take a look at the real time. For me and right now you can run FindDeviceExEx (double ex in the end) console sample and send both console output and log. As it's the most minimalistic thing. Thanks!

Hi,

I was in the middle of her session when we where disconnected. The last thing I did was copy the following libraries from C:\Program Files\Rocket Division Software\StarBurn SDK V10.5 Tomahawk\Bin\Core\Common\ : nlame.dll, ogg.dll, vorbis.dll, and vorbisfile.dll into my applications directory. We where disconnected but she later sent an e-mail stating that when she tried to burn in the program, it worked. Are any of these files required for starburn? She was using the version 12 (with sptd), would this work with version 10.5 (without sptd)? I sent her a build containing these files with the 10.5 without sptd since many of our distributors have 10.5 without sptd... but haven't heard back from her yet.

Thank you, and have a very merry Christmas.

Ben

No, they are optional for audio compression only.

Use SPTD for burning to isolate possible software conflict issues.

Merry Xmas too!!

Well after 1000's of other customers that have used our product, the issue existed only with two people. I can replicate the error by inserting a cd-r upside down into the cd drive as I am sure this is what the user had been doing. After I sent them a clearly labeled disk, it was the last I heard from them. We deal with many many people who have little to no computer experience.. adding it all together, I have concluded this error has been due to user error. The issue coincidentally occurred just as windows 7 had been released, hence my freaking out haha.

Thanks for all your help and patience!

"After I sent them a clearly labeled disk, it was the last I heard from them..." (c) you

Really? Did you made this CD from C4 plastic? )

OK, it's nice to know it was "human factor". Thank you very much for update!