Actually the font is Topaz8 (technically an 8x8 pixel font, but I’ve stretched it so it’s 8x16), if you Google AmigaOS 1.3, you’ll see my GUI inspiration I’ve implemented the mouse now...eekee wrote:You have! The colors remind me of my 8-bit Ataris, the title bar style my Atari ST, and the font printing in graphics mode in QBasic. (It's the VGA ROM font, isn't it?) Nostalgia fusion!bloodline wrote:I've gone proper old school for the style.
What does your OS look like? (Screen Shots..)
Re: What does your OS look like? (Screen Shots..)
CuriOS: A single address space GUI based operating system built upon a fairly pure Microkernel/Nanokernel. Download latest bootable x86 Disk Image: https://github.com/h5n1xp/CuriOS/blob/main/disk.img.zip
Discord:https://discord.gg/zn2vV2Su
Discord:https://discord.gg/zn2vV2Su
Re: What does your OS look like? (Screen Shots..)
Ohhh! I wondered why the font reminded me of 8x8 fonts. I was trying to think where I'd seen it, didn't think it was Amstrad PCW for some reason, and there aren't many other old systems I actually spent time on.bloodline wrote:Actually the font is Topaz8 (technically an 8x8 pixel font, but I’ve stretched it so it’s 8x16), if you Google AmigaOS 1.3, you’ll see my GUI inspiration I’ve implemented the mouse now...
Kaph — a modular OS intended to be easy and fun to administer and code for.
"May wisdom, fun, and the greater good shine forth in all your work." — Leo Brodie
"May wisdom, fun, and the greater good shine forth in all your work." — Leo Brodie
-
- Posts: 14
- Joined: Mon Oct 19, 2020 10:32 am
- Libera.chat IRC: segfaultdev
Re: What does your OS look like? (Screen Shots..)
Hello again! I managed to partially port microui to flat:
It is running on VESA 1024x768 mode, with 16-bit colors. I am not planning to use microui(for several compatibility issues like 64-bit integers or floats and for the design),
but make my own library instead. Also, I redesigned completely the font and made it 8x10 instead of 8x8. Now it also has an underline and italics mode(not in the picture),
apart from the bold and normal mode. Finally, I replaced the USTAR filesystem(OK for read-only drives, but not for writing) with my own filesystem, but I plan to add FAT32.
SFS or even ext2 support.
It is running on VESA 1024x768 mode, with 16-bit colors. I am not planning to use microui(for several compatibility issues like 64-bit integers or floats and for the design),
but make my own library instead. Also, I redesigned completely the font and made it 8x10 instead of 8x8. Now it also has an underline and italics mode(not in the picture),
apart from the bold and normal mode. Finally, I replaced the USTAR filesystem(OK for read-only drives, but not for writing) with my own filesystem, but I plan to add FAT32.
SFS or even ext2 support.
-
- Posts: 14
- Joined: Mon Oct 19, 2020 10:32 am
- Libera.chat IRC: segfaultdev
Re: What does your OS look like? (Screen Shots..)
Hello! This is not an OS, but rather a single-stage bootloader with "GUI" designed for my OS. It is not that much, but I am very proud of it as it is the first time I have to slowly replace instructions with shorter ones to meet the 512-byte barrier. For you to imagine how close I am to that barrier, note that I had to put "images" instead of "options" as it was too big . Here it is:
And if that was not enough, I made it load a config file from the image(a flatfs image, in this case, but it is "easily" portable to FAT12/16) with all the entries to put into the menu, so you can edit them with a text editor. And finally, I made it load from folders too.
I will post the source code soon, if anyone is interested to use it.
I will post the source code soon, if anyone is interested to use it.
-
- Posts: 14
- Joined: Mon Oct 19, 2020 10:32 am
- Libera.chat IRC: segfaultdev
Re: What does your OS look like? (Screen Shots..)
OK, maybe I am posting too much messages recently, but I have remade the bootloader in the post above for the third(and I hope the last) time, improving the menu, adding the ability to make the entry name different than the file name and it no longer uses the null entry of the GDT to store data(I had to do that to fit it in 512 bytes). It is also a lot more optimized, and can load files up to 480 KiB. The only drawbacks are that the default GDT has only a code entry(and the null entry, of course) and that it uses my own filesystem, flatfs, but it can be easily ported to FAT12/16 as with the previous iteration. Here you have the source code and here you have an image:
Re: What does your OS look like? (Screen Shots..)
Wow! That's quite impressive that you fit all that in 512 bytes!
-
- Posts: 14
- Joined: Mon Oct 19, 2020 10:32 am
- Libera.chat IRC: segfaultdev
Re: What does your OS look like? (Screen Shots..)
Thanks! I made it for my own OS, but now I can choose an entry to boot from, allowing me to test multiple kernels or boot programs from the same drive. I have also seen your bootloader, NexBoot, and it looks pretty nice, the only reason I am not using it is because I want to load a raw binary instead, but it is a nice and pretty small bootloader.nexos wrote:Wow! That's quite impressive that you fit all that in 512 bytes!
Re: What does your OS look like? (Screen Shots..)
Thanks! My bootloader is still in development, it just hasn't been updated in a while . I remember a while back FASM did a contest to see how much one person could fit in 512 bytes. You're bootloader is definitely advanced enough to be in there .segfaultdev wrote:Thanks! I made it for my own OS, but now I can choose an entry to boot from, allowing me to test multiple kernels or boot programs from the same drive. I have also seen your bootloader, NexBoot, and it looks pretty nice, the only reason I am not using it is because I want to load a raw binary instead, but it is a nice and pretty small bootloader.nexos wrote:Wow! That's quite impressive that you fit all that in 512 bytes!
-
- Member
- Posts: 27
- Joined: Thu Apr 19, 2018 5:31 am
Re: What does your OS look like? (Screen Shots..)
After a lot of work I finally managed to boot my operating system from a USB stick on a real computer. In the image you can see the Live version of the OS running in 1280x1024 vbe mode. USB mouse and keyboard are also supported. There is currently not a lot you can do with it, but it still feels like a big accomplishment.
here.
If anyone is interested, source can be found Currently working on https://github.com/Remco123/CactusOS
Re: What does your OS look like? (Screen Shots..)
That's pretty damn good! Have you a prebuilt disk image I can try?GhelloWorld wrote:After a lot of work I finally managed to boot my operating system from a USB stick on a real computer. In the image you can see the Live version of the OS running in 1280x1024 vbe mode. USB mouse and keyboard are also supported. There is currently not a lot you can do with it, but it still feels like a big accomplishment. here.If anyone is interested, source can be found
CuriOS: A single address space GUI based operating system built upon a fairly pure Microkernel/Nanokernel. Download latest bootable x86 Disk Image: https://github.com/h5n1xp/CuriOS/blob/main/disk.img.zip
Discord:https://discord.gg/zn2vV2Su
Discord:https://discord.gg/zn2vV2Su
Re: What does your OS look like? (Screen Shots..)
hello from 2116. very nice indeed.
-
- Member
- Posts: 27
- Joined: Thu Apr 19, 2018 5:31 am
Re: What does your OS look like? (Screen Shots..)
Thanks bloodline,
I just published a new release so you can download a bootable ISO file there.
Link: https://github.com/Remco123/CactusOS/releases/tag/V1.2
PS: Your OS is also really nice, good job!
I just published a new release so you can download a bootable ISO file there.
Link: https://github.com/Remco123/CactusOS/releases/tag/V1.2
PS: Your OS is also really nice, good job!
Currently working on https://github.com/Remco123/CactusOS
Re: What does your OS look like? (Screen Shots..)
GhelloWorld,
Just a small note, I thought you might want to know, I booted your ISO in QEMU with the "-machine q35" parameter and your image got to:
[255] [Error]: Boot partition not found/present
If I remove the "-machine q35" parameter (now emulates older hardware) it boots just fine.
Anyway, good work.
Ben
Just a small note, I thought you might want to know, I booted your ISO in QEMU with the "-machine q35" parameter and your image got to:
[255] [Error]: Boot partition not found/present
If I remove the "-machine q35" parameter (now emulates older hardware) it boots just fine.
Anyway, good work.
Ben
Re: What does your OS look like? (Screen Shots..)
GhelloWorld is probably doing the same thing my BIOS bootloader does and trying to find the boot partition through direct ATA access — the q35 'machine' only provides SATA, so you either need to use BIOS reads or try for EFI. It also defaults to a PCIe Intel Gigabit ethernet controller that doesn't work my e1000 driver...BenLunt wrote:[255] [Error]: Boot partition not found/present
Re: What does your OS look like? (Screen Shots..)
You're so far ahead of where I'm at, your window movement is so smooth (also are you using a hardware sprite for the mouse? )... I'm going to have to look at your source code later and discover your gfx compositing secrets! I can't believe the level control you have over the VBE mode!GhelloWorld wrote:Thanks bloodline,
I just published a new release so you can download a bootable ISO file there.
Link: https://github.com/Remco123/CactusOS/releases/tag/V1.2
PS: Your OS is also really nice, good job!
Also I was a bit surprised that you have opted for a single-click-open for the icons... I kept opening two of each app
CuriOS: A single address space GUI based operating system built upon a fairly pure Microkernel/Nanokernel. Download latest bootable x86 Disk Image: https://github.com/h5n1xp/CuriOS/blob/main/disk.img.zip
Discord:https://discord.gg/zn2vV2Su
Discord:https://discord.gg/zn2vV2Su