turn on INT13Ex
in [Win32 Kernel]
|
From: Boba on 7 May 2010 10:42 Hello, I need a BIOS call to turn on the INT 0x13 Extension? tia Boba
From: Tim Roberts on 8 May 2010 22:33 "Boba" <Boba(a)somewhere.net> wrote: > >I need a BIOS call to turn on >the INT 0x13 Extension? tia It's an odd question. You don't "turn on" the INT 13 extensions. They are either present, or they are not. However, you posted this in a Windows group, and in Windows INT 13 is irrelevant. Windows doesn't use INT 13 for I/O. What are you really trying to do? -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc.
From: Boba on 8 May 2010 23:21 Hi Tim; "Tim Roberts" <timr(a)probo.com> wrote in message news:3i7cu5doq4brrg7tg0nouf6iipmmop0doo(a)4ax.com... > "Boba" <Boba(a)somewhere.net> wrote: >> >>I need a BIOS call to turn on >>the INT 0x13 Extension? tia > > It's an odd question. You don't "turn on" the > INT 13 extensions. They are either present, > or they are not. I've thought so too (since at least the times it was introduced). Turned out, in some BIOSes, the INT13+41 call comes back w/carry flag set if the POST has not found any bootable disks supporting the extension, in which case I need to 'turn it on' myself. > However, you posted this in a Windows group, and > in Windows INT 13 is irrelevant. Windows doesn't > use INT 13 for I/O. I don't see anything wrong with using BIOS calls for kernel writing. > What are you really trying to do? I am trying to fix a problem with some software which relies on that extension. Thanks. Boba TC
From: Jonathan de Boyne Pollard on 10 May 2010 10:55 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <blockquote cite="mid:eI39yay7KHA.5848(a)TK2MSFTNGP06.phx.gbl" type="cite"> <blockquote type="cite"> <p wrap="">However, you posted this in a Windows group, and in Windows INT 13 is irrelevant. Windows doesn't use INT 13 for I/O.<br> </p> </blockquote> <p wrap="">I don't see anything wrong with using BIOS calls for kernel writing.<br> </p> </blockquote> <p>As M. Roberts said, you are <em>posting in a Windows newsgroup</em>, in particular the one for Win32 programming with (roughly) the <code>KERNEL32.DLL</code> API. This newsgroup isn't about writing kernels, or even about kernel-mode programming on Windows NT. Firmware APIs are entirely irrelevant to the Win32 programming discussed here. And as M. Roberts also said, once it is past the very early stages of the bootstrap process, the IBM PC/AT firmware disc I/O services are wholly irrelevant to Windows NT.<br> </p> </body> </html>
From: Boba on 10 May 2010 11:53
Hi Jonathan; "Jonathan de Boyne Pollard" wrote in message news:IU.D20100510.T145610.P537.Q0(a)J.de.Boyne.Pollard.localhost... > ... > ...once it is past the very early stages > of the bootstrap process, what ng is the most appropriate for posting a question regarding these stages? is ntldr a part of kernel? |