OSDev.org

me239 wrote:Still working on the bootloader. Here is my xOS in FreeDOS(xOS only uses BIOS interrupts)
Here is it's MessageBox function

At least you got a mouse! I'm still trying to get mouse for the UOS. (My OS)

I do have program execution though!

David

Tommy wrote:

GhostXoPCorp wrote:wow tommy, you pretty much did what my dream was, build an os that looked like windows 3.1.

Me too I still wanted . I always liked the concept of GUI Windows 3.1 had: very simplist. Well, I added a bar on the desktop and
a system menu:

That makes you dream it even more?

Hi Tommy, your OS always wows me! So you haven't dropped the project? Can it load programs yet?
The GUI is nicer than 3.1.

David

Hi David

DavidBG wrote: So you haven't dropped the project?

No. I finally found what was wrong in my code. I have rewritten the mouse driver and fixed some bugs
with paging. Now, HyOS works very well on my laptop and I no longer have any reason to drop the project.

DavidBG wrote: Can it load programs yet?

Yes, it can load applications from a RAM disk. It was also able from a floppy but I removed the floppy
driver because I think this media is old, slow and no longer supported by newer computers since a while.
I need to work on a IDE driver, so I could load applications from a hard disk or a CD-ROM drive.

Tommy

I've just implemented a new, HID-based, keymap system for Pedigree and today I've converted the German keymap. I have an EnUS keyboard, but I still wanted to try the new keymap.
The result:

He was also able from a floppy but I removed the floppy
driver because I think this media is old, slow and no longer supported by newer computers since a while.

Will you support it again at some point in the future or perhaps with a module? I still have many computers with floppy drives and I don't like testing OS's on new PC's or in VM's.

Ferrarius wrote: Will you support it again at some point in the future or perhaps with a module? I still have many computers with floppy drives and I don't like testing OS's on new PC's or in VM's.

HyOS is still able to boot from a floppy, but he's no longer able to load programs on it. And I don't have a computer with a floppy drive. So, no! I won't reimplement a floppy driver in HyOS.

Just a few changes in the screenshot compared to last time. But our compiler is finally able to compile structs, simple classes, generics and a stripped down corlib. So now we're finally able to use System.String instead of char-wise output

http://mosa-project.org/news/4

Just implemented a test driver for the VMware emulated graphics card.

This screenshot shows an accelerated copy from one area of the screen to another. It's not much to look at, but it's kind of cool to know the copy is performed by the "hardware" rather than by a memcpy or something.

pcmattman wrote:Just implemented a test driver for the VMware emulated graphics card.

This screenshot shows an accelerated copy from one area of the screen to another. It's not much to look at, but it's kind of cool to know the copy is performed by the "hardware" rather than by a memcpy or something.

Have you got some docs for that one? I was just analysing the Virtualbox one last night

I used the following sources to assist me out:

• This document from xfree86 explains stuff like the initialisation process, caveats, and manipulation of the command FIFO for accelerated I/O.
• The haiku driver proved to be quite helpful for reference.
• A Black Hat paper discussing how to poison the host OS memory. Had a heap of information that I couldn't find anywhere else such as FIFO link psuedocode. Also discussed which 2D (and 3D) acceleration features were available across a number of tested VMware hosts - for example, it tells that SVGA_CMD_RECT_FILL is not available everywhere.

MIT licensing on Haiku and the xfree86 stuff is a massive bonus.

You can also refer to my source code which is currently a hacked-up test driver and will be changing a fair bit to integrate properly with the system.

Did you see this?

http://vmware-svga.sourceforge.net/

It seems to be a more up to date function with a reference driver implementation

Ok, so here is my OS booting in debug mode. At the time the screenshot was taken, it has full VESA support, a custom font, has switched to long mode, initialized multiprocessing support, located and traversed both the SMBIOS and ACPI tables, initialized a kernel debugger and initialized the High-Precision Timer (not necessarily in that order).

Quick screenie to show what I've just accomplished for the first time.

Started rewrite about 2 months ago (full rewrite, little reuse). Right now it can:

- Start from a harddisk with Grub booting it.
- Switch to long mode
- Read from the harddisk, detect partitions, detect an Ext2FS with creatoros=42 and use that as rootfs for its vfs
- Detect that there's a BochsVbe device, switch it to 640x480 mode
- Load a background image from the ext2fs drive in plain regular BMP format and display it as background image
- Load an init program in ELF format & swap it into user space
- Transfer control to init
- Make init perform a syscall
- Halt, because there are no syscalls actually implemented (but it does get to printing "Not implemented: syscall_exit" - so it does get there).

Happiness, since I can now start on practically any bit. Stuff I want to fix:
- IDE driver doesn't use DMA. It should.
- Nothing has interrupts because I haven't bothered to set up APICs yet.
- Multithreading and multiprocessing
- Proper pagefault handling (there's a bluescreen but 85% of the info is wrong - CR2 is right though).
- A proper GUI server that has syscalls for defining windows
- Keyboard and mouse support (for obvious reasons)
- Rendering text in the GUI (there's a font, but there's no renderer for it yet).
- Loads of testing & porting to other systems. Have only tested under bochs so far; expecting trouble in the near future. Vbox doesn't like being run inside vbox so that's hard to test. Qemu doesn't like it so far (but it might just be compiled without long mode support - dunno yet). Vmware haven't tried. Need to make a vmware graphics driver though.

Regards,
Candy

PS: the image is just one of many google image hits for "desktop background abstract industrial" - I figured a random pattern didn't look quite as impressive as this. It's still just a flat image that I loaded from disk.

After days of reading Open Firmware documentation and reverse engineering yaboot source I finally managed this:

Oh, this is the first hobby BIOS I've seen since now.

Can you tell me where to find this firmware documentation?