I can show how to create the manifest and use it [compile it] from fb.
However I cannot test this nor can I help debug unless it's very simple.
Replace each instance of myapp
in all code/instructions below
with the file name (minus extension) of your final executable.
Create this file, name it myapp.rc
[or prepend this to an existing .rc]
#define MANIFEST_RESOURCE_ID 1
MANIFEST_RESOURCE_ID RT_MANIFEST "myapp.exe.manifest"
Create this file, name it myapp.exe.manifest
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" >
Both of the files above must be in the same dir as your .bas source.
Compile using (you may need explicit path to fbc, and your other switches):
fbc -s gui myapp.bas myapp.rc
In theory the .rc and .manifest files, once compiled, do not need to
stay with the executable.
Perhaps a real Windows Expert will help you if you need further assistance.
I have only limited experience with manifests, none with dpi awareness.