News:

MASM32 SDK Description, downloads and other helpful links
MASM32.com New Forum Link
masmforum WebSite

Interupt Address Table

Started by Farabi, December 04, 2010, 12:55:09 PM

Previous topic - Next topic

Farabi

Can I use the built in interupt function if I know its address? Like address pointer from LIDT or something?
Those who had universe knowledges can control the world by a micro processor.
http://www.wix.com/farabio/firstpage

"Etos siperi elegi"

BogdanOntanu

Short answer: NO.

Long answer: you are understanding something wrong if you consider this.

For example: there is no such concept as: "the built in interupt function"
Ambition is a lame excuse for the ones not brave enough to be lazy.
http://www.oby.ro

Farabi

Sorry about the terminologi.
So, why I want a interupt able to be used on 32-bit mode. Because Interupt can save my time building a driver.
Those who had universe knowledges can control the world by a micro processor.
http://www.wix.com/farabio/firstpage

"Etos siperi elegi"

BogdanOntanu

Quote from: Farabi on December 04, 2010, 01:31:35 PM
Sorry about the terminologi.

It is not about terminology ... it is about concepts that you do not understand ...

Quote
So, why I want a interupt able to be used on 32-bit mode. Because Interupt can save my time building a driver.

Very wrong.

1) First of all and IF you are capable enough then you DO WANT to learn how to make drivers in windows. This is a very much appreciated skill and can get you a very good job for your lifetime.

2) Then you can not access the IDT table unless you are in Ring-0 in Kernel mode and this requires a driver anyway.

3) Even inside a kernel mode driver you should NOT access the IDT table directly because this ia a critical system resource and you will most likely destroy the integrity of the OS IRQ handllers and schedulers and will generate critical errors on hardware.

Instead you should learn about IRQ_Dispatch_Level and such driver terminology and concepts.

4) The Interrupts in 32 bits are NOT THE SAME as interrupts from BIOS or DOS or real mode. They are not a magic API or a set of predefined function to help you access hardware without drivers or without deep hardware understanding and knowledge.

You are way better by using the user mode API interfaces and/or eventually  IOCTLS to known drivers. (but only in extreme cases)

This way you achieve independence from hardware and avoid the huge time/knowledge/understanding and money costs that are required for drivers development.
Ambition is a lame excuse for the ones not brave enough to be lazy.
http://www.oby.ro

donkey

"Ahhh, what an awful dream. Ones and zeroes everywhere...[shudder] and I thought I saw a two." -- Bender
"It was just a dream, Bender. There's no such thing as two". -- Fry
-- Futurama

Donkey's Stable

baltoro

Here are a couple of excellent internet sources for developing driver code:   
OSR Online. OSR has the best forums on the internet for discussing driver development.
Also, OSR has a version of the DDK Online,...you can download this from Microsoft (at least you used to be able to).
Summary of Kernel-Mode Support Routines
Initialization and Unload Support Routines
Device Installation Functions

Microsoft has lots of informative sites too. Getting Started with Windows Drivers
Kernel-Mode Driver Framework
Windows Driver Kit Documentation

Baltoro

Farabi

Those who had universe knowledges can control the world by a micro processor.
http://www.wix.com/farabio/firstpage

"Etos siperi elegi"