Xander - Lees comments for you:
"If it was DBPro, I would advise that the exe be created as a seperate EXE and PCK file. As it is Classic, there is no such option.
Any solution could not involve changing the DB Classic executable saver in any way, as the code cannot be revisited.
He could try saving as EXE instead of FINAL, so the media is not included. I doubt this will help though.
I had a look on the HASP site, and found this line:
'Protection against Memory Dumping: Removes essential data from the
protected software executable, so that a complete executable cannot be recreated from dumped memory. The protected application cannot run without HASP SL security environment intact.'
I suspect it scans the executable predicting to find a specific layout so it can extract 'key' sections. When it fails to find a standard executable, such as DB classic executables are, it simply fails. To bypass this would be to bypass their security measures, which is not in their interests to do. If the converter tool had options to switch off these invasive levels of protection, it could work but I would need to download the tool and have a look, but that might take a few hours, which might not be the best use of my time.
If he can try saving as EXE, looking for any tick-boxes in the conversion tool of HASP SL (evaluation version is free) or perhaps wrapping the executable in an exe compression system (which would cheat by effectively wrapping the un-orthodox exe within an orthodox exe). Failing all these, let me know and I will delve deeper."
Bite my shiny metal ass
