x86 Programming

[m0skit0]

A lot of time? Why would it take a lot of time?

Advertising

[Nickolas]

A lot of time? Why would it take a lot of time?

I have to lod the image file and then unload it in order to boot into Windows to compile my OS and then load it again to test it... And this is repeated every single time i make a slight change.. LOL It is frustrating...

Advertising

[m0skit0]

Use a virtual machine. I recommend Bochs because you can debug with it, it has a separate advanced console for controlling the VM.

I strongly recommend using Linux. I had very little problems and you have tools that are rarely available on Windows, such as dd. NASM runs prefectly on Linux as well, no problem on that side. Bochs also runs like a charm.

On a side note, try to use the BIOS calls as less as possible. Try to do it yourself

[Nickolas]

On a side note, try to use the BIOS calls as less as possible. Try to do it yourself

My Assembly is still not that good... I actually use BIOS calls a lot... I'll try to fix that.. Is it possible to be able to call something only in certain BIOSes and not on others? (This never happened to me, I am just asking..)

[m0skit0]

Not that I know about. BIOS use such functions for compatibility purposes mostly, although some OSs still use such functions.

And I still insist: use Linux.

[Strangelove]

What do you got so far?

[Nickolas]

Not that I know about. BIOS use such functions for compatibility purposes mostly, although some OSs still use such functions.

And I still insist: use Linux.

I am on a MacBook so a triple boot between Windows Mac and Linux is gonna be weird...

[Nickolas]

What do you got so far?

Just a kernel capable of displaying a welcome screen... Now I want to port some apps from MikeOS to my OS just for testing... Or I may even try to implement my own..

[Nickolas]

It's been a lot of time since I posted something in this thread, so I have another question. My OS has changed a lot. It is now a 32-bit OS and runs in p-mode. (Yay ) Just for testing purposes I decided to make an installer. But I was too bored to write another bootloader for the installer or even change my normal one so I thought of another way. Here goes: The user boots into the os using a cd (I don't want him to be able to change the files of the os). The user runs an installer through the os. The installer copies the files to the specified HD. Everything happens correctly and the files get copied to the HD (I have drivers) (Yay again ) And now the question. How can I copy files to the bootsector of the HD?

Thanks in advance!

[m0skit0]

Nice work.

The user boots into the os using a cd (I don't want him to be able to change the files of the os)

This is nonsense because he can just copy the CD contents to the HD and modify them. If everybody would be as protective, you couldn't be able to write your own OS right now. And if this is your thinking mode, I don't want to help you either.

Good luck with it.