#1 Burning Software

Hello,

I'm a bit of newb to starburn. I am trying to deploy it on another computer other than the development computer. I am running the .NET samples. When I read the FAQ it says to use the installation.bat files in the Starburn/Bin/Core/StarburnX, but there aren't any .bat files in that directory. Did that not get included on your latest installation package? Thanks in advance!

Jacob Bolton

Hello,

Jacob, yes the "installation.bat" file was not included into the latest package of StarBurn SDK.

To deploy the StarBurnX on another you should:

- copy the StarBurnX.dll to another computer and register it using the regsvr32 utility. Use the command line to call the regsvr32 utility - regsvr32 tarBurnX.dll

- copy the RocketDivision.StarBurnX.Interop.dll or the RocketDivision.StarBurnX.Interop2.dll file from the "StarBurnSDKPath\Bin\Core\StarBurnX\NET\" to another computer;

- copy the ogg.dll, vorbis.dll and vorbisfile.dll files from "StarBurnSDKPath\Bin\Core\Common\" to another computer if you burn the CD-AUDIO Disc from the ogg audio files.

- copy the StarBurn_SuperVideoCD.iso and (or) StarBurn_VideoCD.iso file(s) from "StarBurnSDKPath\Bin\Core\Common\" to another computer if you burn the VideoCD and (or) Super VideoCD discs.

The "installation.bat" will be included into the next StarBurn SDK package!!

Regards,

Dmitry Bortsov

Rocket Division Software

Thanks. Knowing which files to install is a big help. In my case I will only need the StarBurnX and Interop2 DLLs.

However, I'm still wondering where to install them. Suppose there is another application on the computer that uses StarBurnX. If I install StarBurnX.dll in my own application directory and register it, the COM-related registry entries will now point to my "private" copy of StarBurnX.dll (which might be a different version than what the other app installed). If my app is then uninstalled and StarBurnX is removed, the other app will be broken. Do I understand this correctly?

It seems like there should be a special directory for shared COM DLLs like StarBurnX and that StarBurnX.dll should be reference-counted.

Hello,

1) You will overwrite StarBurnX registration information on the users's computer if your version of StarBurnX will be the same as version installed on user's computer. During installation of your product you can determine the installed version of StarBurnX by means of the information from Windows registry:

For the Win64 you should look into the key - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\TypeLib\{93CBA48A-1C58-4648-B22D-8F3588CB8D95} where is the {93CBA48A-1C58-4648-B22D-8F3588CB8D95} is the StarBurnX TypeLIB UID.

2) Concerning to the "COM shared folder" - i think you could install your StarBurnX DLL into the Windows system directory (Windows/System32). If the DLLs is already present on the user's machine, the setup program should compare its version with the version you are installing.

3) As far as I know the COM registration information is NOT the "reference-counted"!

4) Be informed that you can activate ( create ) COM object by specifying the version of its object!! Possible to have registered the several different version of COM ( StarBurnX ) component.

I hope this information will help you!

Regards,

Dmitry

Rocket Division Software