Kube 1.0 (for testing)

[kubeos]

Hi,

The updated version of Kube has been posted at http://kube.freehostingnow.com/

Please test it on both real machines and emulators. I have tested it on 3 real machines and BOCHS so far and it works as expected.

NOTES:
The gui is not developed. It is mostly just a test for the mouse driver.
The filesystem is my own, so no FAT12 or 32.

WARNINGS:
Please do not try to use the sys command on a real hard drive. It will overwrite the MBR and the partition table. If you do use sys on another floppy be sure to copy the mouse.drv to that new floppy or else it will not be bootable.

http://kube.freehostingnow.com

Thanks in advance, and feel free to laugh at my 16-bit OS [/url]

[inflater]

Hi,
I will try it.

There is nothing about laffing on your OS, neither if it was 8-bit or 4-bit. I had a 16-bit OS too (and I have) and I am converting it to 32-bit ASM by help of one open source, ehhhm, it doesn't have a license I dont know if it is OSI ,small operating system.

//EDIT: Sorry, my antivirus is running high and it "surely knows" that inside of your archive is a boot virus (!). This is a false alarm because my antivirus is suspecting that he found a boot virus inside the new version of bootsector of my OS (PortixOS). I better write a e-mail to the virus laboratories, again.

inflater

[kubeos]

A note on converting 16 to 32bit OS...

I also am trying to move over to a 32bit OS. Basically I started with Tran's PMODE kernel and removed what I didn't need, and added what I did need. So now I am working on a 32-bit version of Kube with function calls similar to Linux.

I picked Tran's kernel as a starting place as it sets up the GDT, LDT, and V86 mode and gives me something to play around with and learn how pmode works. I also needed his v86 mode to access the floppy INT 13h services until I figure out a real floppy driver. Once I figure out how to do stuff without V86 then I should be able to rewrite everything myself and phase out any of Tran's stuff.

[inflater]

Once I got rid of the silly "Virus found" messages and turned off boot sector virus detection, I was successfully able to boot your OS.

After booting, I would recommend clearing the screen. Some BIOSes do not do that. Plus, I would reset the cursor to the position right after A:\>, in QEMU it will make 5 extra spaces. Not a big problem though, just a one little design error

By the way, the GUI looks neat for a beginner OS; do you maked that by yourself in ASM, by help of a hidden MS-DOS kernel (just kidding ), or ... in Basic?
One technical thing: When I boot GUI from the first boot menu and click on Shutdown, the GUI will reboot itself. It wont escape to the command line.

Next, I would add detections for drives. I typed B: along with DIR and ENTER keypress and it has frozen. Plus, I would add "Bad command or file name" to your OS, since it has some of a DOS look.
If I type "EDIT" and create a new file, I see about a 5-character mess after the position cursor.

Anyways, it's stable and it has its own filesystem (like PortixOS had...), so congratulations getting into OS development life!

inflater

[kubeos]

Thanks for the reply Inflater.

I suppose I should get QEMU and do some testing as a lot of people seem to use it.

As for the GUI, I definitely didn't use a hidden kernel or BASIC.. The kernel, CLI, GUI, and basic tools like sys and copy are all written with my own compiler. As for the shutdown button not working, I can't remember why I even have that button on there, the code doesn't do anything.

Drive detection would be a great idea, plus a routine to check if the file system on the drive switched to is even a kube filesystem.