On 19.09.2013 17:28, Tomas Hajny wrote:
Now with with a new PC running Windows 8 ... the
compiler bugs. It works fine with small program but not with one
which executable about 1.5 Mb large (which is my case, I did not checked
till which size it works!).
My program should run in prompt comm
On 18.09.2013 18:48, Philippe wrote:
(first time I am using the mail list ... I may do it wrong!)
I have a quite big program (now with more than 200.000 lines), first
build with TP7. For example it accesses CGA memory through absolute
address ...
Years ago I moved to FPC. And it compiled ok und
Yes, I know these DSK-file crashes, but this is something else.
Anyway,
I deleted the file fp.dsk - SIGSEGV.
I deleted the remaining files - SIGSEGV.
Always helps run old fp.exe 0.9.2 18.05.2004 from 1.0.11
before run fp.exe from 2.6.2. Both versions use CWSDPMI v7.
I still think that fp.exe wil
On Thu, September 19, 2013 21:55, Sven Barth wrote:
> On 19.09.2013 17:28, Tomas Hajny wrote:
.
.
>> 2) You still need at least a linker for the GO32v2 target (FPC internal
>> linker does not support this target) and that is the somewhat tricky
>> part.
>
> Hmm? Looking at compiler/systems/t_go32
In our previous episode, Sven Barth said:
> It's still maintained. Though it's mostly used on DOS/GO32v2 systems and
> likely with less big projects.
One of the problems with dos maintenance is that there are very few
bugreports with source, and IDE problems are not always reproducable.
Currently I'm quite busy but definitely I will try it and let you know.
Thank you.
On Thu, Sep 19, 2013 at 11:07 AM, Tomas Hajny wrote:
> On Wed, September 18, 2013 20:49, Lubomír Čabla wrote:
> > I am running pure DOS 7 from Windows 98 US, no drivers, no TSR programs.
> > Just COMMAND.COM, no
On Wed, September 18, 2013 18:48, Philippe wrote:
Hello Philippe,
.
.
> I
> have a quite big program (now with more than 200.000 lines), first build
> with TP7. For example it accesses CGA memory through absolute address
> ...
>
> Years ago I moved to FPC. And it compiled ok under Windows 98
>
On 18/09/13 17:48, Philippe wrote:
> (first time I am using the mail list ... I may do it wrong!)
>
>
>
> I have a quite big program (now with more than 200.000 lines), first
> build with TP7. For example it accesses CGA memory through absolute
> address ...
>
> Years ago I moved to FPC. And it
(first time I am using the mail list ... I may do it wrong!)
I
have a quite big program (now with more than 200.000 lines), first build
with TP7. For example it accesses CGA memory through absolute address
...
Years ago I moved to FPC. And it compiled ok under Windows 98
then under XP.
N
On 2013-09-18 09:20, Michael Van Canneyt wrote:
>
> The fptimer unit implements a timer with a thread, but this forces the use of
> threads on your application
The way I like it! ;-) Especially considering how thread friendly these
[common place] multi-core CPU's are these days.
Regards,
- G
On Wed, September 18, 2013 20:49, Lubomír Čabla wrote:
> I am running pure DOS 7 from Windows 98 US, no drivers, no TSR programs.
> Just COMMAND.COM, no AUTOEXEC.BAT and CONFIG.SYS.
>
> Run
>
> CWSDPMI -p -x
>
> DPMI stays in memory, start FP.EXE - again SIGSEGV.
.
.
OK, thanks.
> Can you tell
Am 18.09.2013 23:34 schrieb "Marcos Douglas" :
>
> On Tue, Sep 17, 2013 at 2:41 PM, Sven Barth
wrote:
> > On 17.09.2013 17:27, Marcos Douglas wrote:
> >>
> >> On Tue, Sep 17, 2013 at 12:18 PM, Marcos Douglas
wrote:
>
> Another thing you could try (just for testing): change your exceptio
Could you try to delete the files generated by fp.exe
before restarting it:
fp.exe generates three files:
-fp.ini
-fp.cfg
and
fp.dsk
Try first to only remove fp.dsk
and see if it cures your sigsegv or not.
fp.dsk is a binary file that contains configuration information
that mi
13 matches
Mail list logo
