The CD/DVD Burning actions are currently proving to be unreliable. On some machines they cause an access violation when FBCMD is closing, on others they hang and the machine requires a reboot.
The fault is in the CD/DVD burning library (poor threading design), however the vendor seems to have disappeared and is not responding to support requests. We are currently working to resolve the issues, either by fixing the bugs ourselves or by replacing the library with another (though no suitable alternatives have been identified so far).
We do not have an ETA for a resolution at this time, I will update this post when we do.
We are close to releasing an official update to FB7, however in the mean time we have a test build available with the rewritten CD/DVD burning actions.
This build includes the rewritten actions, however they are not installed by default (they will be in the next official update, we are still testing at the moment).
After installing this build, open the FB IDE and go to the Tools menu, Package Manager, find the CD/DVD Burning package, highlight it and then click remove. Then click on Add and select FBCDBurner2.bpl (you will need to change the file filter to *.bpl to see it) which should be in the FinalBuilder 7 folder. Restart FB and confirm that the actions are there.
You will then need to go to the options to edit the burner aliases as the naming convention has changed (unfortunately that is unavoidable). Just edit the aliases and select the drive from the list.
The Actions have changed a bit, with some options removed and some new options. We have tried to maintain backwards compatibility, and in our testing here that does seem to be the case (apart from the alias issue). The new api is the microsoft IMAPI2 api, which is proving to be very reliable. I have yet to see a single unexplained error, having burned my way through a pile of CDR's, DVD-R's, BD-R and rewritable disks of various flavours. My desk is a bit of a mess with empty media containers at the moment..
These new CDBurner actions are now in the update we just posted. If you had the test version installed (FBCDBurner2.bpl) then please removed them and restart FinalBuilder to avoid problems caused by having two packages with the same actions loaded. The installer is supposed to remove the file if it’s found but on one test system I tried the new build on it did not remove the test package.
I use the iso-action a lot and was somewhat irritated, when my scripts from v5 threw an exception at the iso action in FB7. After reading this post and installing the Windows Feature Pack für Storage (on Windows XP) the ISO-action is now working again.
However, there seems to be a problem with the “recurse” flag. At least I could not convince the action to create an iso from a folder structure (one entry under “specify files” and recurse set to “true)”. I tried this with a simple test script and it’s the same problem. The root files a in the iso, the subfolders and the contained files not.
Am I doing something wrong or may this be an issue due to changing the underlying technologie?
I’ve been waiting on feedback from another user on this issue but he seems to have gone quiet since I sent him the fix. I’m hoping we’ll be releasing an official update tomorrow, assuming nothing else major crops up overnight.
thanks for your quick reply. Recurse is now working as expected - that’s great! (saves me from editing all actions and adding the subfolders).
Could you check the connection between “specify files” in the “files” tab and the “edit list” button? After editing the list (e.g. adding a new item in the file selection dialog) the changes made in the file selection dialog are not reflected in the “files” tab. After closing the action and opening again, the changed file list is displayed. Looks like a refresh-problem to me.
Ok, took a bit longer than I expected, had fix, checkin, build & upload, download on my home pc, test… several times (too hard to test timing related issues over remote desktop).
I just upgraded from FB6 to FB7 (ver 7.0.0.787) and am seeing the following exception when my script executes the Create ISO Image action. The FB7 CD Burning Package is checked in the Package Management list. Let me know what other details I can provide.
Never mind - I worked on my reading comprehension and discovered that I needed to install both IMAPI2 and the Windows Feature Pack in order to make ISO images in FB7 on my WinXP system. It now seems to be working fine.