BarryKJ: I first came across the problem on my desktop PC, which has all the RealTracks I own installed on it, along with the latest version of BIAB 2010.5 build 304.

In order to check whether it's something unique about this PC, I ran the same test on my laptop, which does have all the RealTracks I've been using so far, but doesn't have room for the 83-101 set I've just purchased. BIAB on the laptop fails at the same song in the songlist - although it does play the last song, which isn't played on my desktop.

Mac: My desktop doesn't have any power saving options set, and I've set my laptop to be "Always On", so I don't think that's the problem - this fault occurs within a few minutes of my starting the Juke Box.

I'll move a small subset of the songs into a temporary directory, and see if I can identify a faulty song.

Having said that, I believe that no program should hang or start messing around with the operating system if it is running a faulty data file - especially if the program itself created the faulty file! If I had written such a program, I'd be very keen to investigate the characteristics of a faulty file which could produce such an effect, and take steps to detect the fault before the damage could be done. This is especially true for a program like BIAB which runs "live", not in a back office somewhere. At a pragmatic level, I can always remove or rewrite a faulty file to get things moving again, but I would expect some protection from BIAB.

PS I'm really enjoying BIAB - this is not intended as destructive criticism, but as a way of improving an already very impressive product. I'd rather collaborate in investigation than walk away.