For running the DOS port of FLTK you have to have set environment variable NANOSCR.
Before launhing the program try this DOS command:
SET NANOSCR=800 600 565

(width, height, RGB bits: 5-red, 6-green, 5-blue /16-bit videomode/)

Maybe helps this?: Dir("C:\prmpt\*.*")

But this command line: "fbc filetocompile.bas" can't work in normal DOS environment!

Because FILETOCOMPILE.BAS has longer name than usual 8+3 DOS file name format. Don't rely on the 3rd party LFN drivers. In some situations they may not work.

It works in QB 4.5? And what about the calls from C libraries? Do you use in your code some explicite linking with C-library files? (I don't know the proper FB syntax but simething like: "#INCLIB GCC.A" ). Or your code is just "pure" basic code without any attempts to call anythi...

Does work the cross-compilation from Windows compiler to DOS executable? In case you are trying to do a native compilation in DOS system with DOS FB-compiler to DOS executable it is rather some DOS specific problém than a problém in your code. It can be related to LFN (long file names) support. Or t...

Generally, in the DOS protected mode programming one of the most problematic things are any routines using hardware interrupts or hardware callbacks. There are often problems when interrupt handler wants to use memory which is swapped out from memory pool. So your application can be more stable if t...

Hm, interresting. Does the Phenom II X4 integrate some chipset functionality (like in southbridge/northbridge circuits) just on the chip itself? Because it sound like some kind of A20 gate problem. You should more experiment with various memory setups. By the way - does it occur if you run your samp...

The problem is probably somewhere in USB-PS2 emulation. If I understand correctly you use USB mouse in USB slot and have only CTmouse driver loaded. So you don't use DOS USB driver by Bret Johnson but you rely on BIOS emulation, right? In such cases you might try to turn off "USB input legacy e...

You could try my pascal unit Mimoza. It allows many exotic things in DOS text mode; besides other things also changing the size of chars. Firstly try the included compiled example. The pascal source is self-explanatory and contains assembler parts. It is not difficult to translate it into basic. htt...

It could be problem related to disk cache in protected mode. Most disk caching programs can have problems when are in protected mode (which is used by FBC). Before running FBC program you could load alternate DPMI server HDPMI32. Just enter on command line: "HDPMI32 -r". Then run your prog...

Sure!
Look at it: http://www.laaca.borec.cz/qmidi.pas
The most important parts are encapsulated in {$IFDEF FPC} ... {$ENDIF}

Yes, it is not hard to port QMIDI into FreeBASIC. Year ago I ported it into Freepascal - the same 32-bit DPMI DOS environment. You only have to encapsulate the interrupt callings into protected mode envelope.

DOS386 wrote: 2. It's not a DOS program, it's a no-OS program that can start from DOS and drop back there (no, I didn't test it myself)

Yes, but the key thing is that return from 64 long mode into 16 bit real mode is possible.

http://www.bttr-software.de/forum/board ... 6886#p6887

And what about this sample application and facts in that thread?

I have suspection than problem is in your path. LD utility has problems with long file names. Try to move Freebasic and your projects into domething like C:\FB