OSDev.org

I am proud to present after 3 weeks of work, the first public beta for OpenStar OS!

We have a website at http://os.openstar.pw with ISO downloads and screenshots for BETA 1.

Features:

• networking with a NE2000 Card
• FAT32/FAT16/FAT12 filesystem support
• Lua 5.1 built in to kernel
• Simple C to Lua compiler (Ronsor C/C-- unoptimizing compiler 1.0)
• cat supports HTTP urls.
• far - file archiving
• png viewer, bitmap fonts, file manager, settings, multi-user
• telnet server
• more: just go to Shell and ls /bin

USER/Pass: root/root

As your OS seems to be closed source, I'm struggling to see what interest it could be to me.

Why should I try it? What is your USP?

I've tried it, but I got stuck at the log in screen. I've looked for a password, but can't find it at your site.
From what I've seen on the log in screen, though, your mouse movement is weird (moving it one unit moves it about 10? units on the screen). Window movement is also weird; when I drag the window, instead of showing window contents being dragged or at least an outlined rectangle showing the movement, the window stays static until I let go of the mouse button.
Specifically on QEMU, I have encountered a bug I have had before in my own OS: if you press and hold a key while moving the mouse, you break the mouse driver. The fix is easy, however: on every IRQ12, before doing anything, read port 0x64 and test bit 5 (value 0x20) and only proceed with handling the IRQ if the bit is set, indicating the data comes from the mouse. If the bit was clear, ignore the IRQ and don't read from port 0x60; just send EOI to the two PICs/local APIC and do an IRET.

iansjack wrote:As your OS seems to be closed source,

Good reason to call it OpenStar

I think I connected to your VM via telnet a couple of weeks ago

Anyway I have a similar question to iansjack, who's your target audience?

matt11235 wrote:I think I connected to your VM via telnet a couple of weeks ago

Anyway I have a similar question to iansjack, who's your target audience?

anyone who complains their computer is too slow after Windows "rots", after my UEFI port it will be easy for people to install my OS to 'replace' windows.

So your OS is a faster, slot-in replacement for Windows 10 and will run all my Windows programs?

iansjack wrote:So your OS is a faster, slot-in replacement for Windows 10 and will run all my Windows programs?

No, see "Beginner Mistakes" - It's a faster, slot-in replacement that will do common things well (Word processing, web browsing)

"Beginner's Mistakes" is a great reference. It's rare to see such self-awareness.

I'm afraid that, without source or design documentation yet another OS is of little interest to me with respect to OS development. Linux does all I need, and I can study the source code.

iansjack wrote:"Beginner's Mistakes" is a great reference. It's rare to see such self-awareness.

I'm afraid that, without source or design documentation yet another OS is of little interest to me with respect to OS development. Linux does all I need, and I can study the source code.

I plan to release documentation and a portion of my source code with the final release.

The source will include command-line userspace utilities, the core C-kernel, and the C to Lua compiler.

Please explain the rationale behind a C to Lua translator? Lua has a VM so why not C to bytecode?