On Thu, Oct 10, 2019 at 10:00 PM Rugxulo wrote:
> >ia16-elf-gcc -mcmodel=small -Os -mregparmcall -mnewlib-nano-stdio \
> > tinyasm.c ins.c -o tinyasm.exe
>
> What is the resulting size of the .EXE with your build? (He said it
> uses at least 128k RAM, right?) At least for development and
Hi,
On Thu, Oct 10, 2019 at 11:08 AM TK Chia wrote:
>
> > BTW, what is the proper way to build Tinyasm with IA16-GCC? Is there a
> > specific set of switches you use?
>
> To really crunch down the size, you can add some options to turn on
> optimizations and use a more efficient function call int
On 10/10/2019 10:08 AM, Eric Auer wrote:
Hi Stephen,
repeated LBA cache write error on CF card? That sounds
like a serious bug report for lbacache! Have you tried
to keep lbacache outside UMB, in other words not using
loadhigh? You could also try the lbacache TUNS option
to allocate additional s
Hi Stephen,
repeated LBA cache write error on CF card? That sounds
like a serious bug report for lbacache! Have you tried
to keep lbacache outside UMB, in other words not using
loadhigh? You could also try the lbacache TUNS option
to allocate additional stack space. If TICKLE readahead
is used,
Hi, Jerome.
Sorry for the late reply. But, I've pretty much given up trying to run
FreeDOS on this system. I tried installing it to the CF Card directly as a
raw disk via Virtual Box, but it just wouldn't use the disk. I kept getting
an LBA cache write error. I found that if I just hit "retry" ove
Hello Rugxulo,
BTW, what is the proper way to build Tinyasm with IA16-GCC? Is there a
specific set of switches you use? Or have you not tested (much) with
it yet?
The bare minimum is to enable the "small" memory model (separate text
and data segments), like so:
ia16-elf-gcc -mcmodel=small t
My reply is at the bottom. Please put your reply there too.
On Thu, 10 Oct 2019, Mateusz Viste wrote:
On 10/10/19 7:49 AM, David Griffith wrote:
On Wed, 9 Oct 2019, Mateusz Viste wrote:
Would you mind sharing what was the bug?
It has something to do with memory allocation for the undo slot
Hi,
On Tue, Oct 8, 2019 at 11:48 AM TK Chia wrote:
>
> I did a quick disassembly of the precompiled nasm.exe and ndisasm.exe in
> nsm09839.zip, and indeed --- for some reason --- they were built to use
> 186+ instructions such as `leave' and immediate pushes.
>
> So perhaps it will be good to try
On 10/10/19 7:49 AM, David Griffith wrote:
On Wed, 9 Oct 2019, Mateusz Viste wrote:
Would you mind sharing what was the bug?
It has something to do with memory allocation for the undo slots and far
pointers. William Lash says he might have something that could work.
I see - this is still
Hi,
On Tue, Oct 8, 2019 at 10:17 AM C. Masloch wrote:
>
> On at 2019-10-05 18:49 -0500, Rugxulo wrote:
> > I know 8086tinyplus can't handle 186+ ENTER/LEAVE properly.
>
> If the 16-bit NASM uses 186+ instructions, that's a bug (or possibly
> wrong option?) on the part of the compiler.
They seem
My reply is at the bottom. Please put your reply there too.
On Thu, 10 Oct 2019, Rugxulo wrote:
Hi,
On Wed, Oct 9, 2019 at 1:21 PM Tom Ehlert wrote:
and - please : THIS IS NOT THE LIST TO HAVE DISCUSSIONS OF FROTZ PERFORMANCE.
If he's testing it atop DOS, especially FreeDOS, then I don't
Hi,
On Thu, Sep 26, 2019 at 9:01 AM R Moog wrote:
>
> It's not as much hurting a nonexistant bottom line by now, but chasing down
> every owner of every piece
> in these versions of Windows and convincing them to re-license their stuff.
> It's a huge hassle.
Yes, it's a hassle, and sometimes i
Hi,
On Thu, Sep 26, 2019 at 9:04 AM Michael C Robinson
wrote:
>
> ReactOS won't replace Windows 9x/ME because it is not dos based.
But it does have a partially working NTVDM nowadays. Seriously, rule
out ReactOS and WINE entirely (i.e. try them with your workload on
your personal machines!) befo
Hi,
On Wed, Oct 9, 2019 at 1:21 PM Tom Ehlert wrote:
>
> and - please : THIS IS NOT THE LIST TO HAVE DISCUSSIONS OF FROTZ PERFORMANCE.
If he's testing it atop DOS, especially FreeDOS, then I don't see the
problem. (You've complained about off-topic stuff for freedos-devel in
the past, but this i
14 matches
Mail list logo