[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/db/driver/mysqli.php on line 264: mysqli_fetch_assoc(): Couldn't fetch mysqli_result
[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/db/driver/mysqli.php on line 326: mysqli_free_result(): Couldn't fetch mysqli_result
Pete's QBASIC Site Discuss QBasic, Freebasic, QB64 and more 2008-01-24T17:45:27-05:00 http://petesqbsite.com/phpBB3/app.php/feed/topic/2574 2008-01-24T17:45:27-05:00 2008-01-24T17:45:27-05:00 http://petesqbsite.com/phpBB3/viewtopic.php?p=16462#p16462 <![CDATA[Error during run-time initialization]]> Statistics: Posted by Seb McClouth — Thu Jan 24, 2008 5:45 pm


]]>
2008-01-24T11:10:13-05:00 2008-01-24T11:10:13-05:00 http://petesqbsite.com/phpBB3/viewtopic.php?p=16455#p16455 <![CDATA[Not sure but]]>
Just a thought,

Ted

Statistics: Posted by burger2227 — Thu Jan 24, 2008 11:10 am


]]>
2008-01-24T06:22:38-05:00 2008-01-24T06:22:38-05:00 http://petesqbsite.com/phpBB3/viewtopic.php?p=16454#p16454 <![CDATA[Error during run-time initialization]]>
At first I had one big module, to make things easy. But as I had always done before, I now again working on seperate modules. But since everything seems to go wrong only bootsect.bas I see at this point no use in creating the other modules.

I'm now stuck with the error L2029: 'INTERRUPTX' : unresolved external.

And ofcourse the 'error during run-time initialization'.

You happen to know how to fix this?

Statistics: Posted by Seb McClouth — Thu Jan 24, 2008 6:22 am


]]>
2008-01-23T17:23:17-05:00 2008-01-23T17:23:17-05:00 http://petesqbsite.com/phpBB3/viewtopic.php?p=16449#p16449 <![CDATA[Re: Oh, no!]]>
Not another version of Linux!

Aren't there enough already? :roll:
MIGHT!! No saying I will... QBinux is cool enough for now...

Statistics: Posted by Seb McClouth — Wed Jan 23, 2008 5:23 pm


]]>
2008-01-23T17:10:09-05:00 2008-01-23T17:10:09-05:00 http://petesqbsite.com/phpBB3/viewtopic.php?p=16448#p16448 <![CDATA[Oh, no!]]>
Aren't there enough already? :roll:

Statistics: Posted by burger2227 — Wed Jan 23, 2008 5:10 pm


]]>
2008-01-23T14:54:08-05:00 2008-01-23T14:54:08-05:00 http://petesqbsite.com/phpBB3/viewtopic.php?p=16447#p16447 <![CDATA[Error during run-time initialization]]>
Also I'm not quite sure where you're going with this, but if this is supposed to be a "real" OS and not just something that runs in DOS, you can't use QB's runtime library and you can't use int 21.
For the time being it is a Shell (or as I call it a platform-OS). Like you have Bash for Linux QBinux is actually relying on the core, which runs ofcourse on Dos (the most stable OS ever from Microsoft, atleast thats what I think.).

If I plan on making a real os... it'll be with the orginal Linux but I might call the distribution McClouth Linux or something.

Could you explain how to get the libraries? I've reinstalled the whole PDS, but I never had that problem before. Only this time.

Grtz

Statistics: Posted by Seb McClouth — Wed Jan 23, 2008 2:54 pm


]]>
2008-01-23T14:49:13-05:00 2008-01-23T14:49:13-05:00 http://petesqbsite.com/phpBB3/viewtopic.php?p=16446#p16446 <![CDATA[Error during run-time initialization]]>
Grtz

Statistics: Posted by Seb McClouth — Wed Jan 23, 2008 2:49 pm


]]>
2008-01-23T00:29:23-05:00 2008-01-23T00:29:23-05:00 http://petesqbsite.com/phpBB3/viewtopic.php?p=16440#p16440 <![CDATA[Error during run-time initialization]]>
(The error message you got occurs when you use a runtime library with different string or math settings that your object files.)

btw You need an InterruptX in that for loop, or your message will never display...

Also I'm not quite sure where you're going with this, but if this is supposed to be a "real" OS and not just something that runs in DOS, you can't use QB's runtime library and you can't use int 21.

Statistics: Posted by Plasma — Wed Jan 23, 2008 12:29 am


]]>
2008-01-23T14:50:41-05:00 2008-01-22T16:15:10-05:00 http://petesqbsite.com/phpBB3/viewtopic.php?p=16436#p16436 <![CDATA[Error during run-time initialization]]> Error during run-time initialization when I try to run the file.

Batch-file for compiling:

Code:

@ECHO OFFdel *.objdel testrun.exebc /o /Ot /Fs /G2 /Fpi /E /X boot\bootsect.bas;ren bootsect.obj a.objlink a,,nul,..\..\devel\bc7\lib\qbx.lib+..\..\devel\bc7\lib\bcl71efr.lib;ren a.exe testrun.exedel *.obj
boot\bootsect.bas

Code:

'$INCLUDE:'include/qbinux/config.bi''         bootsect.bas                   Copyright (C) 2005, 2006, 2007, 2008 Sebastian McClouth'' Print some insane message         RegsX.AX = &H300         INTERRUPTX &H10, RegsX, RegsX           ' read cursor pos         RegsX.CX = 24         RegsX.BX = VAL("&H" + "00" + "07")'page 0, attribute 7 (normal)         FOR count = 1 TO LEN(msg1)         RegsX.AX = VAL("&H" + "e" + HEX$(ASC(MID$(msg1, count, 1)))) 'write string move cursor         INTERRUPTX &H10, RegsX, RegsX         NEXT count'ok, we've written the message, now we get the current cursor position'and save it for posterity.         RegsX.AX = &H300                                 'read cursor pos         INTERRUPTX &H10, RegsX, RegsXGOSUB empty8042'GOTO HEADSYSTEM 'needs to end here anyway' This routines checks that the keyboard queue is empty' No timeout is used - if this hangs there is something wrong with' the machine, and we probably couldn't proceede anyway.empty8042:RegsX.AX = &HB00INTERRUPTX &H21, RegsX, RegsXIF (RegsX.AX AND &HFF) <> 0 THEN            DEF SEG = &H40: POKE &H1C, PEEK(&H1A): DEF SEGEND IFRETURN

Code:

'$INCLUDE:'include/qbinux/autoconf.bi'DECLARE SUB INTERRUPTX (IntNum%, InRegs AS RegTypeX, OutRegs AS RegTypeX)DIM SHARED msg1 AS STRINGDIM SHARED RegsX AS RegTypeXDIM SHARED UTS AS UTSNamemsg1 = "Loading..."UTS.SysName = "QBinux"UTS.NodeName = "(none)"                       'set by sethostname()UTS.Machine = "i386"                              'hardware typeUTS.DomainName = "(none)"                   'set by domainname()'' The definitions for UTS.Release AND UTS.Version are defined in' qbinux/version.bi, and should only be used by qbinux.version.bi
include/qbinux/autoconf.bi: (not sure but I think I've forgotten sumfin here)

Code:

'$INCLUDE:'include/qbinux/utsname.bi'TYPE RegTypeX              AX   AS INTEGER              BX   AS INTEGER              CX   AS INTEGER              DX   AS INTEGER              BP    AS INTEGER              SI    AS INTEGER              DI    AS INTEGER              flags AS INTEGEREND TYPE
include/qbinux/utsname.bi:

Code:

TYPE UTSName        SysName    AS STRING * 64        NodeName  AS STRING * 64        Release      AS STRING * 64        Version      AS STRING * 64        Machine     AS STRING * 64        DomainName AS STRING * 64END TYPE
Yes are true QBinux-codings and as you can see based upon Linux, sometimes even the same code (translated to QB ofcourse).

Grtz

Statistics: Posted by Seb McClouth — Tue Jan 22, 2008 4:15 pm


]]>