Quote:

Well we are, to a degree, comparing apples and oranges. Both systems would have to have the same o/s, the same memory arrangement, the same available resources etc. Tough to duplicate the error then.




But the error has been duplicated on my two computers (XP) and on a Vista laptop, which suggests that it's not a simple resources problem.
Quote:


Is it possible the jukebox sets the folder to be read by the jukebox alone, and something it writes there stops itself? Not likely. But on exit it might not work properly, leaving the folder 'corrupt'.




This is a red herring - Windows misuses the read-only bit in the folder for its own purposes, and allows you to think you've changed it from read-only to read-write when nothing has really changed. If the folder were left 'corrupt', you wouldn't be able to write anything to it next time round, and the fault would be evident at an earlier stage of the Juke Box sequence.

Quote:


I still like my possible explanation.




I did think a memory leak was the likely cause at first, but I wouldn't expect this to happen at the same point in the Juke Box sequence for several different computers. Remember also that there appears to have been some corruption of the Windows system, in that other programs misbehave after these BIAB hangs. That sound more like a pointer being set to an address it shouldn't be touching. BIAB 2010 tended to throw up a lot of access violation errors, 2010-5 seems to be better in this regard.
Quote:


Normally I write down the song times, make a folder, and stick in 50 minutes worth with the less desired tunes at the end in case I get weary. That means 11 or 12 songs at the most. Never had a problem with that........


When the two of us are playing without our keyboard player we tend to choose alternately from a sub-set of the trio repertoire which is suitable for clarinet, guitar and BIAB.

But if we all did things the same way, life would be so dull...