[fpc-devel] FPC_REQUIRES_PROPER_ALIGNMENT

2004-10-12 Thread Marc Weustink
Hi, Florian and I had a discussion on IRC and we decided to continue it here. F:> I guess the main problem will be that the typeinfo structures has changed to fit sparc 's alignment M:> this will be on sparc only ? F:> on cpus which define FPC_REQUIRES_PROPER_ALIGNMENT F:> mainly, the data after s

Re: [fpc-devel] bug report

2004-10-12 Thread Marco van de Voort
> >Did any of the BIOS calls have an address to data as one of the > >arguments? > >If so, read the documentation for the GO32V2 unit, most notably > >copyfromdos/copytodos. > > No, a call is made with simple arguments such as the x,y screen > position or a color (attribute) and a character to wr

[fpc-devel] bug report

2004-10-12 Thread Chess Player
>Did any of the BIOS calls have an address to data as one of the >arguments? >If so, read the documentation for the GO32V2 unit, most notably >copyfromdos/copytodos. No, a call is made with simple arguments such as the x,y screen position or a color (attribute) and a character to write. Eventual

Re: [fpc-devel] bug report

2004-10-12 Thread Tomas Hajny
On Tue, 12 Oct 2004 08:58:09 +0200, Jonas Maebe wrote > On 12 okt 2004, at 07:04, Chess Player wrote: > > > To give the windows version a more rigorous test, I compiled > > a DOS filter program I wrote as a partial replacement for > > ANSI.SYS. It failed to display ANSI pictures properly; > > it

Re: [fpc-devel] bug report

2004-10-12 Thread Jonas Maebe
On 12 okt 2004, at 07:04, Chess Player wrote: To give the windows version a more rigorous test, I compiled a DOS filter program I wrote as a partial replacement for ANSI.SYS. It failed to display ANSI pictures properly; it seems that BIOS calls don't work. (I can't use the CRT unit because piping