I've spent the last couple of weeks working with the support folks at Raxco trying to determine why my disk defragmenter (PerfectDisk 7.0) crashes whenever it is scheduled to run an offline defragmentation. After I sent a crash log to them they replied and said it was wblind.dll that was causing the problem with their application. I was able to work around it by excluding the particular executable from withing WB but it seems odd that I would have to do that for one executable but not the main program executable. The program doesn't seem to use custom windows or anything else so I'm not sure what the problem is but I thought someone might want to take a look just in case. BTW, I'm using the latest beta of WB5.