OSDev.org

Be careful, muazzam. The Miniluv watches you.

muazzam: consider moving

Doctor wrote:muazzam: consider moving

I don't understand you, moving what?

I guess Doctor meant moving yourself to some another country. Perhaps that isn't needed just for watching YouTube lol, and Combuster suggested a solution as well, that hopefully works.

Now I can get a VESA mode number from a specified width and height. In this demo, the bit depth is 24 bits per pixel. So when I input 800x600, the mode is actually 800x600x24bpp.
The numbers on the left are the number of timer ticks in hex, but at the top it is zero because I haven't initialized the PIT yet.
Green means success, yellow (not shown here) means warning, and red means error.

My OS waiting for a user to login with credentials setup on build, and displaying the contents of a file reading form an INITRD. I prompt them for username and password using the program in Bash, then use the -D option to define a macro for my authenticator. The login loops until credntials are legal.

(Yes it's running on a chromebook. I am using one of Koding.com's vm's as my build-run-test machine)

wxwsk8er wrote:Yes it's running on a chromebook.

I was just going to ask what Linux distro is that.

I was just going to ask what Linux distro is that. [/quote]

My own, with the best ever looking windows (with loads of sarcasm)

Hehe. There was a time when I wanted to make my own Linux distro. But all I ever actually did was boot a Linux kernel using ISOLINUX. xD

omarrx024 wrote:Hehe. There was a time when I wanted to make my own Linux distro. But all I ever actually did was boot a Linux kernel using ISOLINUX. xD

I wanted to do so once too. I have achieved a minimal busybox system inside an initrd.

wxwsk8er wrote: (Yes it's running on a chromebook. I am using one of Koding.com's vm's as my build-run-test machine)

Seems like interesting. But how can we test graphical operating systems?

muazzam wrote:Seems like interesting. But how can we test graphical operating systems?

I haven't tested it out, but right now I just run qemu on the terminal and forward the output there with the -curses option. It works booting from the grub menu, and also seems to run my OS just fine. It should work for graphical os's. My desktop machine didn't have a network card and so I was using an ethernet connection in a less than ideal location. So now I just startup my chromebook and get back at it .

After 5 days of a hell of debugging, I finally got my putch function to work in VESA mode. Yes, yes, like the image says: it's resolution independent. The screenshot shows text mode, VESA 800x600 and VESA 640x480, both in 24-bit color modes.
Scrolling was pretty easy and fast without even SSE/MMX.
Going to start work on cursor emulation, shouldn't be too hard.
Link to 1366x768 screenshot -- I have feelings for people with small monitors. xD
And once again, the font is by muazzam, thanks!

omarrx024 wrote:Link to 1366x768 screenshot -- I have feelings for people with small monitors. xD

What feelings do you have for the people using cellphones to go online?
What feelings do you have for the laptop manufacturers who take away the vertical resolution of 800 and replace it with smaller ones, e.g. 768?
Do you think there's content very worthy of large screen resolutions? (btw, the image isn't showing; perhaps, the view limit has been reached)

alexfru wrote:(btw, the image isn't showing; ...)

It's showing, I just clicked on it now.