There's a way to register a dll upon creation of the thread... It's described in the vbadvance samples... but it's really a moot point. You should just include the requirements and crate an installer for the dll. Then when you distribute the blitz program/game then you also create an installer that will register the dll.
I've run into another snag with the blitz printer userlib too... For some as yet unknown reason, after the printer dialog is released, the dll resets the printer back to the default. If I don't get that figured soon then it might not be worth pursuing for a printer userlib without creating my own printer dialog. Which I really don't want to do. Printer dialogs that aren't the system dialog tend to look........ cheap.
Kanati
I've run into another snag with the blitz printer userlib too... For some as yet unknown reason, after the printer dialog is released, the dll resets the printer back to the default. If I don't get that figured soon then it might not be worth pursuing for a printer userlib without creating my own printer dialog. Which I really don't want to do. Printer dialogs that aren't the system dialog tend to look........ cheap.
Kanati