I've only had a couple of problems with referencing and they were easy enough fixed by hand. I seem to have the problem with .bum files or any texture with the name .bump or .bum in it. If you don't find one of these you can expect Poser to lock up on ya. I've actually been able to cancel out of most others. The two problems I had with referencing were with those textures that were previously .bum files, were renamed to .jpg files later, but the code still contained the reference to .bum. That locked up as well and would not permit a cancel Once I changed the code manually, it loaded faster than grease lightning. There must be something in the Poser code that directs it to let no .bum file escape alive, because it goes after them as if it's very life depended on it!! :) A little less ferociousness where this is concerned would be in order. As Emily notes, when I hit cancel, just......stop looking! I have multiple runtimes as well, each containing it's own libraries, textures, etc. Has anyone tried to put all their runtime textures in the one native Poser runtime to see if that helps speed things up???