Add internal CD/DVD burning to TC? (FoxBurner SDK)

[Stevie1]

I too support the idea of adding a burning feature. maybe you could even get/buy the source code of TC Burner? It wasnt a bad Plugin at all.
why re-inventing the wheel, if someone already did

[Xtrician]

Support+++!

[Duke]

A burning function in TC is a complex thing and very specific.

I think TC should not support burning CD/DVD/BlueRay/HD-DVD... directly.

A better way is, TC support the commandline feature for tools, as ImgBurn or Deepburner. TC Support for external Burning Tools like IrfanView, UnPack Tools are welcome

Duke

[Sosna]

I think TC may not suport BluRay, VideoDVD etc, but simple ISO/UDF burning could be very useful for common user, that use burner only to backup their soft/archives.
Anyway, mr. Ghisler, is this feature still in your TODO list?

[iElectric]

Ghisler, what is status on this? Have you considered implenting it? Maybe already started?

[ghisler(Author)]

I'm currently working on the internal Unicode support. It's a HUGE change which affects almost all modules of Total Commander. When this is done, I will have a look at the FoxBurner SDK.

[byblo]

I'm currently working on the internal Unicode support. It's a HUGE change which affects almost all modules of Total Commander.

! This is what TC needing since a while. But I know it is a nightmare. Cheer up !

[dott]

When this is done, I will have a look at the FoxBurner SDK.

Also you should have a look at the StarBurn SDK that it is used by alcohol 120%

[Loc2262]

Hello to all!

I'm the guy you are (partly) talking about here, the coder of the TCBurner plugin. I was planning to continue working on it after quite a long break, since FoxBurner offers several nice new features and stability fixes now.

But if TC is going to natively use FoxBurner, there's no need to do the work. So could you tell me what's the status of those deliberations?

And I have a question about the TC filesystem plugin interface.

There's a problem with the latest FoxBurner when deinitializing it. Since when the plugin is unloaded, I get no Deinit call from TC, I need to call the FoxBurner deinit from the DLL unloading procedures. There seems to be a problem when an Exe (here: TC) loads a DLL (here: TCBurner) which loads a DLL (here: FoxBurner) which creates a background thread. When the first DLL is unloaded and tries to deinit the second DLL, the background thread is not ended correctly and the second DLL hangs waiting for the thread to terminate.

Therefore: is it possible to add a FsDeInit call to the plugin interface which is executed shortly BEFORE the plugin DLL is unloaded? That would help, since no problem occurs when I Deinit the FoxBurner from within a normal FsExecute function call e.g.

Thanks in advance for help!

[Loc2262]

Oh btw, concerning the questions about Foxburner's ease-of-use: since TC is coded in Delphi, and there is a Delphi wrapper component for the FoxBurner DLL (coded by me btw, I'm part of the FB coder team ), it is quite easy to use.

[eugensyl]

Hello Loc2262

I have tried to update only FoxBurner.Dll but plugin (TCBurner) doesn't work well.

It's a good point to continue your job. Maybe, if you can, make an option to save all CD files into ISO or any image file, too.

Keep walking! Improve yourself!

[Locutus]

Hello Loc2262
I have tried to update only FoxBurner.Dll but plugin (TCBurner) doesn't work well.

That's correct, the right plugin version must be used with the correct FoxBurner, since the functions and structures in FoxBurner changed with each version.

It's a good point to continue your job.

I can, as soon as the problem with the deinitialization is fixed. Otherwise TC will hang each time you close it and have used TCBurner before.

[Lefteous]

2Locutus
Hi,

in my opinion it would be better if the plug-in would be developed further by you instead by Ghisler for two reasons. First you already started the file system plug-in and are an expert of the FoxBurner SDK. second Ghisler has a very long wish and todo list. Ghisler and you could work together to extend the FS-plugin interface if needed. Of course it must be guaranteed that development of the plug-in works better than in the past few years. I guess money could really help here right? Well Ghisler has already considered to buy a SDK license so I think that shouldn't be the problem.

[m^2]

2Locutus
Hi,

in my opinion it would be better if the plug-in would be developed further by you instead by Ghisler for two reasons. First you already started the file system plug-in and are an expert of the FoxBurner SDK. second Ghisler has a very long wish and todo list. Ghisler and you could work together to extend the FS-plugin interface if needed. Of course it must be guaranteed that development of the plug-in works better than in the past few years. I guess money could really help here right? Well Ghisler has already considered to buy a SDK license so I think that shouldn't be the problem.

Couldn't agree more.

[Locutus]

Thanks Lefteous and m^2.

"Money" was part-reason why I stopped working on it back then. Voluntary payments were indeed more than disappointing. Lack of contributions and help was another reason, surely also lack of time.

Well, I cannot "guarantee" anything in this regard, but I'll sure do more than nothing. As for licensing the SDK: I'd not get anything from that since I'm paid hourly for my coding work for FoxBurner, and don't participate in any revenues.

Making the plugin open-source or at least a cooperation of some (Delphi) coders might be another option.