Qbasicnews.com

Ok, I've tried everything and can't figure this out. It's irritating, too, because it's what's holding me back from working further on a project.

I made the switch from storing my tile data in conventional memory to XMS using FLib's XMS routines. It runs just fine in the IDE, but when I try to compile it to an EXE, at the first appearance in the code of each XMS command I use it gives me an unresolved external error. I don't even know what that means, let alone how to fix it. If it's something in the FLib code, then I'm screwed. If there's something I'm supposed to be adding in mine or some sort of compilation switch I ought to use, I'm totally in the dark. There's nothing in the documentation. I tried compiling the example programs using XMS and it returned the same errors to me.

Has anyone else ran into this problem/how may it be fixed? (Sorry if this has been addressed.. I searched and searched but found nothing dealing with this problem specifically. Kinda makes me wonder if it's something I'm just doing wrong...)

Hmm...FL has had some trouble with the MoveToXMS and MoveFromXMS commands atleast on my computer (sigh ). I too wanted to store strings in XMS using FL but it simply doesnt work on my computer. But I dont get the 'Unresolved External Error' ?=
I tried contacting Smoky but even he couldnt understand what is wrong.

Now atleast I know there is someone else facing a similar problem :bounce:

Hey, not sure if you've found anything out or not, but I found that building FLib for QB45 allowed me to compile the EMS/XMS stuff. Only problem is my code is definitely not portable at the moment to stinky QB45. I tried to just copy it over and all, but not being able to use arrays in type declarations just plain sucks. Is there any way around that? (Or, even better, heard back on the unresolved external issue from ol' Smoky?)

Sorry I havent heard anything from Smoky. But I have found something incredible C/C++ and Allegro! :bounce:

See my post:
http://forum.qbasicnews.com/viewtopic.php?p=41445#41445

What is allegro and C/C++? Its power + speed + portablility + stability packed all into one!

"Unresolved External" is a linking error. It happens when LINK.EXE finds a reference to a shared variable, a function or a routine (symbol) and it can't find the associated code or definition in any of the modules it is trying to link together. It may happen 'cause you are not including all your modules or 'cause BC is having trouble with memory thus not compiling things properly. It may be also that the QLB file (which is used to run your program from within the file) has the functions/procedures but for some reason the LIB file is bad assembled so it doesn't. I'd try to compile/link from command line to solve the issue, or recompile the library again by hand.

Sorry to be a bother, na_th_an, but could you possibly give me the syntax for compiling/linking from the command line? I'm using QBX with future71.qlb/lib. Also, is there a link anywhere to the QBasic Online Help that is on this server? I can't remember the addy...

Many thanks.

For BC.EXE : http://faq.qbasicnews.com/?blast=QbCompilerParams

General explanation in my article as well: http://faq.qbasicnews.com/?blast=PushingTheLimitsOfQb

And QB Help: http://qbasicnews.com/qboho/