From: Rod Pemberton on

"Mike Gonta" <mikegonta(a)gmail.com> wrote in message
news:1191968909.829686.87350(a)k79g2000hse.googlegroups.com...
> On Oct 9, 8:47 am, s_dubrov...(a)yahoo.com wrote:
>
> > I browsed Mike's source to see if there was an unmatched CLI|STI, but
> > there doesn't seem to be.
>
> Hi Steve,
>
> Not on purpose, however the interrupt handler that displays the
> interrupt number
> does hang in a spin loop with interrupts disabled.
> I've added code to shut the floppy drives off. There is also now an
> indicator
> "PM" or "RM" to indicate the mode of the interrupt.
>

1010 I'm getting RM0D for the problem machine. The other works but has the
same issues as 1007.

RM 0D? I patched 1007 heavily and was only seeing RM 13 15, and PM 10 13 15
16 1c, and the 06 fault. I wasn't seeing 0D.


Rod Pemberton

From: Esra Sdrawkcab on
s_dubrovich(a)yahoo.com wrote:
> On Oct 7, 3:09 pm, Mike Gonta <mikego...(a)gmail.com> wrote:
>> On Oct 5, 8:22 am, s_dubrov...(a)yahoo.com wrote:
>>
>>> Thanks for the source..
>> Thanks Steve,
>> I've made some major changes.
>> Please give the latest version another try.
>>
>> The latest aeBIOS version is here
>>
>> http://mikegonta.com/aeBIOS
>>
>> Mike Gonta
>>
>> look and see - many look but few see
>
> Hi Mike,
>
> V20071007
> Boots to 'Hello World!" on..
>
> Pentium MMX Laptop (dell) Phoenix Bios. (c) 1985-1988.
> Pentium MMX Desktop (compaq presario).
> Pentium 4 Desktop (dell dimension 8250).
> :-)
>
> Steve
>
Virtual pC 2004
Just get the strap line:

aeBIOS version 20071011 - mikegonta.com/aeBIOS

then cursor blink and freezes.
From: Rod Pemberton on

"Rod Pemberton" <do_not_have(a)nohavenot.cmm> wrote in message
news:fekdmu$24r$1(a)aioe.org...
> 1010 RM0D

1013 PM06 (aeBIOS problem machine)


Rod Pemberton

From: Rod Pemberton on

"Rod Pemberton" <do_not_have(a)nohavenot.cmm> wrote in message
news:feu4dt$6go$1(a)aioe.org...
>
> "Rod Pemberton" <do_not_have(a)nohavenot.cmm> wrote in message
> news:fekdmu$24r$1(a)aioe.org...
> > 1010 RM0D
>
> 1013 PM06 (aeBIOS problem machine)
>

1014 (lockup)

This version has no PM or RM error number (No fault is a good sign,
correct?). It just hangs in the int 13 BIOS call - motor left running. The
interrupts that are being called:
PM 10,13,15,16,1C,50,56
RM 15,1C,50,56

When I try it with the boot from DOS program, it gets to the A:\ but as soon
as I type a key, RM/PM 51 triggers and then a RM/PM 06.

So, I'm thinking maybe two problems. What'd you change from 1013 to 1014?
Sorry, deleted all the old versions...


Rod Pemberton

From: Rod Pemberton on

"Rod Pemberton" <do_not_have(a)nohavenot.cmm> wrote in message
news:ff6rdb$oe9$1(a)aioe.org...
>
> "Rod Pemberton" <do_not_have(a)nohavenot.cmm> wrote in message
> news:feu4dt$6go$1(a)aioe.org...
> >
> > "Rod Pemberton" <do_not_have(a)nohavenot.cmm> wrote in message
> > news:fekdmu$24r$1(a)aioe.org...
> > > 1010 RM0D
> >
> > 1013 PM06 (aeBIOS problem machine)
> >
>
> 1014 (lockup)
>
> This version has no PM or RM error number (No fault is a good sign,
> correct?). It just hangs in the int 13 BIOS call - motor left running.
The
> interrupts that are being called:
> PM 10,13,15,16,1C,50,56
> RM 15,1C,50,56
>
> When I try it with the boot from DOS program, it gets to the A:\ but as
soon
> as I type a key, RM/PM 51 triggers and then a RM/PM 06.
>
> So, I'm thinking maybe two problems. What'd you change from 1013 to 1014?
> Sorry, deleted all the old versions...
>

If I relocate second.asm to any address below 1000h, I get the same
problem - lockup in middle of int 13h.
If I relocate second.asm to any address between 2000h and 3000h, I get a
reboot.
If I relocate second.asm to 3000h, I get RM05.
If I relocate second.asm to 3500h, I get PM06 in the middle of int 13h.
(Good? Bad?)

The EBDA segment at 40:E says 020F. I haven't found anything conclusive,
but my suspicions are that the BIOS is using the EBDA or perhaps writing
data somewhere near there.


Rod Pemberton