Hi experts,
some interesting observations about an old 486 PC in the thread
with Dimitris about "Which freedos on 486" on freedos-user...
His BIOS answers with AH=86h, carry=UNCHANGED to int 15.e801,
also leaving AL unchanged. So it seems to be a good idea to
STC before INT 15 when doing the 15.
I looked at int 15h lately, int 15h is not supported on older BIOS versions
but every BIOS has it in the time called now. :)
Error code 86h means "function not supported" and if you get 80h it means
"invalid command"
Op woensdag 20 juli 2016 heeft Eric Auer het volgende
geschreven:
>
> Hi exp
Hi,
I think at this point a comparison should be done with Microsoft's version
on this machine to see if any differences can be detected. Also, I would
run Microsoft's OS in the emulator to see
On Wed, Jul 20, 2016, 3:34 PM Maarten Vermeulen wrote:
> I looked at int 15h lately, int 15h is not s
> FreeCom allows this command: "COPY CON"
confirm
> After that I can write text which echoes after enter in next line and
> it can't be interrupted nor with CTRL-Z
worx for me ... can be interrupted with CTL-Z
--
What N
Yeah,copy CON works for me as well.It works in the 1.2.1 Distro as
well.Could it be a TSR you have running or something?
On Thu, Jul 21, 2016 at 1:18 AM, dos386 wrote:
> > FreeCom allows this command: "COPY CON"
>
> confirm
>
> > After that I can write text which echoes after enter in next line