🚀 go-pugleaf

Having written a Visual Basic Control using the Control Development Kit,
I get a General Protection fault calling LocalAlloc.

Does anyone know if this is a bug in the CDK, a restriction of the CDK,
a restriction in DLL's in general, or have any helpfull suggestions?

Changing the code to do GlobalAlloc makes everything work fine, but I cant
do this for real as Global memory belongs to the DLL client under whose
task it was allocated - when that client terminates the Global memory 
disappears but the DLL remains (assuming another client is using it)
and UAE's when it tries to access the global memory!

I've tried Microsoft support (in the UK) - they expressed surprise and
said they would try it and get back to me.  I'm still waiting.

Thanks in advance for any help
==============================================================================
  Keith Bedford				keith.bedford@hemel.bull.co.uk
  Bull Special Products Division
  Maxted Road  -  UK03-HM14
  Hemel Hempstead
  Herts  HP2 7DZ		Tel:	+44-442-88 4250
  England			Fax:	+44-442-88 4570
==============================================================================