OSDev.org

I copied the source mentioned in the wiki.osdev.org but it dose not work when i boot it.
The driver which i had made worked but limited features.

What are the possible reasons for this???

In this quantum universe there is infinite possibilities.
So can you be more specific on the problem? What and how it does not work?

I check many times?But I failed.

I hav checked the following IRQ,IDT,Print Function,Layout.

Well, what is the expected result and the reality observation? By saying It Failed we have no idea what's going wrong.

- Do it tripple fault when a key pressed?
- Did you setup proper interrupt handlers and successfully get into break point?
- Is any keyboard code fetched from INs as expected?
- Have you ACK'ed the PIC? If no, you probably cannot get second key-stoke.

The interrupt is perfect.Incoming Keyboard interrupt are recognised in my System manager but ikry pressed is not getting saved or displayed.Mu display function is correct becaz i am useing it every ware and its working fine.

The reason it is limited is due to the fact it is an example and incomplete by design, you have to extend it yourself with your own new code

Wow what. this guy posting thrice in a row asking (relatively) noob questions, (yes, I do admit I'm noob, but still), yet claiming he has...

what...?

I had made it so advanced that it supported VGA, ATA, IDE, ACPI(Great Difficulty),ATA PI,ISO File System and now i am trying NTFS (I am Crazy).

???

And yet when someone asks for proof he/she shunts the question or goes dead. Wow.

(not being hostile or anything, but unbelievable.)

I wouldn't mind seeing some working ntfs code that isn't part of linux/bsd actually...

brain wrote:I wouldn't mind seeing some working ntfs code that isn't part of linux/bsd actually...

and the fact is even the linux ntfs driver only has the basic-est read support, iirc...

http://forum.osdev.org/posting.php?mode ... 1&p=203798
Look there

And also open the linux files read and understand and impliment it ,u can within a day or 2-3 days.Not the whole thing.Out of my 100% driver, 25% from linux and bsd and react.



And also let us stop proof ,proof,or something.Try to find solution in for the post.Even i knew someone would ask for the code as proof.But my NTFS Driver is iunder construction,i am just making the structure of the FS.

I heard that they discovered a problem recently with the NTFS underlying hardware that makes it disable the keyboard chip and stuff when you activate it. Can you paste your AHCI code so we can see if the AHCI OS layer is working well with your soundcard? There's a compatibility issue with Windows IIRC, but we need to see the code asap, before your BIOS fails...

gravaera wrote:I heard that they discovered a problem recently with the NTFS underlying hardware that makes it disable the keyboard chip and stuff when you activate it. Can you paste your AHCI code so we can see if the AHCI OS layer is working well with your soundcard? There's a compatibility issue with Windows IIRC, but we need to see the code asap, before your BIOS fails...

I seriously lol'd

brain wrote:

gravaera wrote:I heard that they discovered a problem recently with the NTFS underlying hardware that makes it disable the keyboard chip and stuff when you activate it. Can you paste your AHCI code so we can see if the AHCI OS layer is working well with your soundcard? There's a compatibility issue with Windows IIRC, but we need to see the code asap, before your BIOS fails...

I seriously lol'd

Aww! I thought we'd continue that seriously, and wait for the OP to reply..

(but, yeah, +1 to gravaera!)

Hahahahha, gravaera - the newest neural net spambot for osdev boards?