If you'd buy a full license for DLLWrapper we'll provide 90 days e-mail support with 48 hours maximal response time regarding installation and building issues after date of purchase - that means you can get quick, free-of-charge help if DLLWrapper is not installing or running as it should. Please understand that we can't provide support of any kind for the free-of-charge trail version of DLLWrapper.
However, we can NOT provide free support for wrapping a certain 32 bit DLL that you like to call from a 64 bit host of course, as there are trillions of possible use cases which are all individual and might lead to specific problems that have to solved individually, too. For such cases (or if you simply don't like to do the wrapping by yourself) we provide a wrapping service for a very moderate fee which will build a wrapper package for a DLL provided by you according to your needs as long as you can provide the necessary header file and / or documentation to the DLL as well.
Our wrapping service charges only 30 EUR per DLL function to be wrapped
(minimal fee is 600 EUR, always plus German V.A.T) - and if you don't want to wrap
another DLL by yourself you won't have to buy an additional license for DLLWrapper!
If you're interested please contact us by clicking here and attaching the necessary files.
Please note however, that we typically won't be able to test the wrapping DLL in any way as we usually would need more than only the DLL to wrap but also the complete software and / or hardware environment in which the DLL is supposed to run for this. Therefore the test of the wrapping DLL is never part of our wrapping service but your responsibility - if you'll find bugs during your test (which can't be ruled out because no tests can't be run by us) and inform us accordingly we'll provide a fixed version of the wrapping DLL as part of the wrapping service until it is tested error-free by you. Finally, please be aware that it might not be possible to wrap all DLL functions transparently - see the chapter "Limitations" in the DLLWrapper user manual for some explanation. In such a case we'll try to provide the best possible work around...