OSDev.org

Hi,
I implemented an floppy driver and keybrd driver. When i don't install both driver os work but while i initialize and install them it doesn't work. In keybrd the interrupt is 33 and in floppy interrupt 38 and irq 6.

Fourth revision of the same question and now it's not the screen, but the keyboard that's involved. Why? Do you even know yourself?

Is this relevant, and if that doesn't work, can you at formulate, test, and post the smallest amount of code after which you would expect an interrupt from the floppy drive?

I think it's a waste of time to even bother with a floppy driver in 2016.
ATA and AHCI are not that difficult if you know what you're doing.
P.S: This should be in OS Development, not OS Design & Theory.

Technoguy wrote:Hi,
I implemented an floppy driver and keybrd driver. When i don't install both driver os work but while i initialize and install them it doesn't work. In keybrd the interrupt is 33 and in floppy interrupt 38 and irq 6.

• In what way does the OS work when you don't install the drivers?
• In what way does the OS not work when you do install the drivers?

Also

• We don't care what interrupts/IRQs you're using if you don't give us any code
• "Keybrd" is not a word, it's spelt "keyboard"

Okay, i am really sorry brothers. I am a student learning in high school in class 8 but i like os development. I will never do this mistake.

Combuster wrote:Fourth revision of the same question and now it's not the screen, but the keyboard that's involved. Why? Do you even know yourself?

Is this relevant, and if that doesn't work, can you at formulate, test, and post the smallest amount of code after which you would expect an interrupt from the floppy drive?

. void floppy_install(38);

Technoguy wrote:. void floppy_install(38);

It doesn't even make sense because (assuming this was copied/pasted from your OS) that line is just a function prototype.

omarrx024 wrote:I think it's a waste of time to even bother with a floppy driver in 2016.
ATA and AHCI are not that difficult if you know what you're doing.
P.S: This should be in OS Development, not OS Design & Theory.

. What your os is i think your os is the only one which is the ghost of computer. You know even windows support floppy. The baddest and the black side os is your one.

omarrx024 wrote:I think it's a waste of time to even bother with a floppy driver in 2016.
ATA and AHCI are not that difficult if you know what you're doing.
P.S: This should be in OS Development, not OS Design & Theory.

. What your os is i think your os is the only one which is the ghost of computer. You know even windows support floppy. The baddest and the black side os is your one.

Technoguy wrote:. What your os is i think your os is the only one which is the ghost of computer. You know even windows support floppy. The baddest and the black side os is your one.

What the heck is that supposed to even mean?

omarrx024 wrote:

Technoguy wrote:. What your os is i think your os is the only one which is the ghost of computer. You know even windows support floppy. The baddest and the black side os is your one.

What the heck is that supposed to even mean?

. Sorry

omarrx024 wrote:

Technoguy wrote:. What your os is i think your os is the only one which is the ghost of computer. You know even windows support floppy. The baddest and the black side os is your one.

What the heck is that supposed to even mean?

I think what he's trying to say is that your OS is really bad, even worse than Windows, because it doesn't support floppy disks. He's saying that your OS is worse than Windows because Windows supports floppy disks while yours doesn't. He's describing your OS as a ghost and as black as attempted metaphors for "very bad".

I guess, he meant, that your OS is on the dark side of the Force.

omarrx024 wrote:I think it's a waste of time to even bother with a floppy driver in 2016.
ATA and AHCI are not that difficult if you know what you're doing.
P.S: This should be in OS Development, not OS Design & Theory.

If ATA/SATA/AHCI/USB are not difficult, then a floppy driver is easier too, so why not implement it?

The fact is that floppies are still capable to make things easier, and are actually vital if you use old ISA machines trying to make sure that you're dealing only with code that runs natively in the best minimum or maximum i386 (386DX/387) as the absolute minimum platform for your base system and toolchain when compiled/built.

~ wrote:If ATA/SATA/AHCI/USB are not difficult, then a floppy driver is easier too, so why not implement it?

The fact is that floppies are still capable to make things easier, and are actually vital if you use old ISA machines trying to make sure that you're dealing only with code that runs natively in the best minimum or maximum i386 (386DX/387) as the absolute minimum platform for your base system and toolchain when compiled/built.

Because floppies are old technology. Few people (if any) still use them today. I think we should try to keep up with modern hardware, not backwards-compatibility with old hardware.
And I didn't say USB is easy; I know it's difficult, but unlike floppy drives, coding a USB driver will be worth the effort.