ForNext
Member
Hi all,
I recently bought me an IBM 5160 that I was able to put to use after a low-level format of the harddisk and installing MS-DOS 3.3 on it.
However, I noticed an 'Internal Stack Overflow' after operations for some time.
At first I suspected the keyboard (interrupt) because of the output on the screen (all 'Y' characters), but I found out that wasn't the problem.
After that I dove into the bios and from there into the timer interrupt because I suspected the cause lay there.
I checked the interrupt table and routines associated with those and saw nothing starnge in the IRQ8 (timer) but some perculiar code in the 0x1C routine.
I wrote a program to put that code into a binary file and checked this with IDA.
It looks like there is a (bios)program that attaches itself to Int0x1C and calls 5 times on Int9 (keyboard interrupt).
If I change the code and put an IRET right at the start everything is ok.
Will have to dig further into it (detaching hardware and see what happens).
But I was wondering if anybody is familiair with this problem.
Best regards,
Dirk.
I recently bought me an IBM 5160 that I was able to put to use after a low-level format of the harddisk and installing MS-DOS 3.3 on it.
However, I noticed an 'Internal Stack Overflow' after operations for some time.
At first I suspected the keyboard (interrupt) because of the output on the screen (all 'Y' characters), but I found out that wasn't the problem.
After that I dove into the bios and from there into the timer interrupt because I suspected the cause lay there.
I checked the interrupt table and routines associated with those and saw nothing starnge in the IRQ8 (timer) but some perculiar code in the 0x1C routine.
I wrote a program to put that code into a binary file and checked this with IDA.
It looks like there is a (bios)program that attaches itself to Int0x1C and calls 5 times on Int9 (keyboard interrupt).
If I change the code and put an IRET right at the start everything is ok.
Will have to dig further into it (detaching hardware and see what happens).
But I was wondering if anybody is familiair with this problem.
Best regards,
Dirk.