Andrew Tween wrote:
> I think that the external BitBltPlugin won't load into an old VM due to the
> version number checks that prevent loading of a plugin with a (major?) version
> greater than the VM's (major?) version.
> But having failed to load it, the VM doesn't then use its internal BitBltPlugin,
> and keeps trying to load the incompatible, external one instead. Hence a blank
> screen.

Hm ... yes that's entirely possible. It would happen if you implicitly 
use the latest proxy version (which has been bumped a couple of times). 
You could try to compile with an older version instead (just #define 
VM_PROXY_MINOR to be the least version with which it compiles).

> I think I should alter the installer to check the current VM version before
> copying the BitBltPlugin into the executable dir.
> The best check I can come up with (for Windows) is ...
> 
>     SmalltalkImage current vmVersion ~= 'Squeak3.7 of ''4 September 2004''
> [latest update: #5989]'
> 
> Is there a better check that would also work for custom built VMs?

No, unfortunately there isn't. We should add that information, too.

Cheers,
   - Andreas