[+] The plugin itself now supports multi-language through a .locale file. Those
are stored in a subdir "Lang" under the plugin dir. You can choose the
language to use in the configuration dialog. You can also make your own
language file by editing the "english.locale" file which contains some
remarks. (If you do so, it would be nice if you sent your language file to
the developer for distribution!).
[+] The plugin now supports .lst files created by the DiskDir plugin. If you
copy such a file (the whole file, not some contents!) to the Data-CD/DVD
project, you're queried if you wish the plugin to interpret the .lst as
a list file and put all files listed in it in the project instead of the
list file itself.
[+] Data and Audio Project contents can now be saved to disk, by executing
pseudo-file commands, and automatically at plugin init/shutdown
[+] Added "Estimated Free Space" entry to project directories. Total media
space is either retrieved from a media inserted in a selectable burner, or
(if not possible - no device inserted, burner busy etc.) based on a preset
or user-definable media type (execute the Free Space pseudo-file to change
those settings). Device/preset size is stored in configuration for each
project type. In case of oversize, a warning icon and text is displayed.
[+] Verify function re-made: wrote an own verify replacing the FoxBurner
internal one. Advantages: faster, more stable, waits for media re-insert
if it was ejected, can verify Data+VideoDVD Projects, verifies only files
actually in the project
[+] Configuration file is now searched for in the following folders, the first
folder where it is found (top-down) is used. If it cannot be found, a new
file with default settings is created in the first listed folder.
[wincmd-ini-path]\tcburner.ini
[wincmd-ini-path]\tcburner\tcburner.ini
[plugin-path]\tcburner.ini
[wincmd-path]\tcburner.ini
If I would have anything against old stuff I would not use TC. I care about usability only, not age.
The drive is used for burning CDs, it was able to do its job in 1998 and it still does in 2005 so it's everything else but useless. I give a sh** if a CD is burned in one minute or twenty because I am not in a hurry usually when I am at home. The drive is a SCSI model and as such way better hardware than today's IDE crap: It's robust and doesn't put any load on the system so it is perfectly suited as a background burner.
The usability factor of Windows 3.11 on modern hardware tends to zero and ghisler loses time creating workarounds for that old OS been used on 33 MHz PCs only.
On that hardware I would use TC for copying maybe but definetely not for using WDX plugins so I think that it's time to move on and stop putting limits on TC to leave it compatible with antique software not suited for the tasks TC can do today.
If there is no way to use it with TCBurner I will have to live with it, that's something Windows 3.11 users will be able to learn, too, I am sure.
icfu wrote:I have an old burner here that is not detected, even when I deactivate internal ASPI support: [...] Anything I can do?
Unfortunately not. The SDK I use does not include drivers for each and every (old) burner out there, like Nero and other full-featured burning apps have. So only burners that conform to this Windows standard burning interface stuffs are supported.
Are you sure that CDRWin supports the drive by specific drivers? The app is as small as TC Burner package.
"Full blown" is maybe true for Nero, but not for CDRWin.
Icfu
Last edited by icfu on 2005-03-10, 19:01 UTC, edited 1 time in total.
You're already the second one to say that. I guess if some more demand the old golden CD back, I'll put it back in, even if Poul Dam (who helped me a lot with the icons) will be sad then.
even if Poul Dam (who helped me a lot with the icons) will be sad then.
Plz say him a "Thank you for all (other) real good looking icons".
But IMO the plugin icon in "Network Neighbourhood" looks not good for me. IMHO it is too small, too inconspicuous and too unobtrusive for this great stuff.