What do you mean, you "cannot reasonably check for exceptions and/or carry out disassembly"? Does this mean that exception handlers do not get called? If so, use a trace exception handler and see how far it gets.
As for disassembling, that can be done on any computer. If the testing computer has another operating system installed, simply dump the whole contents of 0e0000h-0fffffh (and the contents of any option ROMs, if necessary) and analyze it with a standard tool such as IDA Pro. Otherwise, if both the testing computer and another computer has a diskette drive, grab a copy of MS-DOS or something, and use it to retrieve the BIOS onto a diskette so you can load it into the other computer for disassembly. Or, you could use a bootable Linux live CD and transfer it through your LAN, etc.
Trouble with int 13h
-
- Member
- Posts: 1146
- Joined: Sat Mar 01, 2014 2:59 pm
Re: Trouble with int 13h
@Gigasoft: I haven't made any exception handlers yet, as I was wanting to get onto implementing my kernel and not fuss with exception handlers. As for dumping the BIOS, I'll give that a try. But... how do I know what part of the disassembly my code's hanging at?
Never mind; I'm sure that'll help!
Never mind; I'm sure that'll help!
When you start writing an OS you do the minimum possible to get the x86 processor in a usable state, then you try to get as far away from it as possible.
Syntax checkup:
Wrong: OS's, IRQ's, zero'ing
Right: OSes, IRQs, zeroing
Syntax checkup:
Wrong: OS's, IRQ's, zero'ing
Right: OSes, IRQs, zeroing
Re: Trouble with int 13h
The exception handler, which you are not going to fuss with, tells you that? I think I've spotted a flaw in your plan.onlyonemac wrote:But... how do I know what part of the disassembly my code's hanging at?