This forums is for OS project announcements including project openings, new releases, update notices, test requests, and job openings (both paying and volunteer).
As usual all feedback goes directly to the top of my ToDo list. I have just started a new job and is working 10-12 hour days to meet a deadline so I apologize in advance if I am a little slow to respond to any questions etc.
Are you using the floppy or the CD? Are you booting on real hardware or in an emulator? How far in the process do you get? Does the kernel start to initialize?
Note to others: use a Danish keyboard layout, or else it won't work.
I used QEMU, and it worked for the most part, but I had two problems:
1. Mouse input was a little weird. It only seemed to register clicks if I dragged the mouse a little or double clicked.
2. The GUI only allowed "16 Greys" video mode.
So the graphics work fine, but the mouse is still a little weird on QEMU. I tested it some more, and I noticed that I could drag a window under the dock, making it unreachable.
You've done some nice work. I didn't get the chance to test it extensively but here's a bit of negative feedback (I'm assuming this is what you're looking for, I'm not trying to bash - great work overall):
You might want the arrow keys to work properly in the console instead of printing digits.
Closing the GUI and re-running it will show a buggy loading screen, except for the loading bar (a bunch of random characters in QEMU, everything white in VirtualBox, didn't try it on real HW yet)
Not really related to the OS but the tetris game has a red character in the middle of the box - not sure what its purpose is
Something tells me that you're clearing the screen by writing black to black for the console. That makes your cursor not show unless you write something and delete it (where you will probably end up having grey on black).
I'm not sure how to kill a process (e.g., tetris).
For some reason, the arrow keys don't work for tetris under QEMU.
Pressing Ctrl+1 under the GUI seems like a bad idea. Try it and see what happens.
Is this system multitasking? If yes, shouldn't the console have an option not to wait until a process is finished or something like that?
Keep up the good work.
EDIT: Oh, I forgot to ask - are you running any video drivers when making screenshots? I thought there would perhaps be a VESA driver but I couldn't get the GUI working with anything other than 16 greys. The options in the dialog box are disabled.
"Computers in the future may weigh no more than 1.5 tons.", Popular Mechanics (1949)
[ Project UDI ]
It fails to load bga.elf, so I try to load it manually but it still doesn't work, It gives me a "bga not found" message ; ( by the way, i can't use the "shift" key, i think vmware "crashed" it with probably a broken keymap )
I've also tried to load vga.elf instead but I get "application exited with 65280" .
WhiteSpirit wrote:It fails to load bga.elf, so I try to load it manually but it still doesn't work, It gives me a "bga not found" message ; ( by the way, i can't use the "shift" key, i think vmware "crashed" it with probably a broken keymap )
I've also tried to load vga.elf instead but I get "application exited with 65280" .
i'm using linux as the host os
Is it me or is the "BGA not found" message obvious if you're on VMWare? BGA stands for Bochs Graphics Adapter, and it's AFAIK only supported on Bochs itself (when the appropriate settings are used) or QEMU (with -std-vga I believe). This also means any BGA code won't work and set up a graphics mode on real hardware, but just in Bochs. I see it as something useful to create or test graphics or GUI stuff in when you don't have any way of changing video modes (through the BIOS, VM86, ...) yet.
When the chance of succeeding is 99%, there is still a 50% chance of that success happening.
manonthemoon wrote:I just tried it out. It's really cool!
Thanks.
manonthemoon wrote:Note to others: use a Danish keyboard layout, or else it won't work.
Ops, I forgot to change the language to english for the release. I have updated my release procedure to avoid making this mistake again.
manonthemoon wrote:1. Mouse input was a little weird. It only seemed to register clicks if I dragged the mouse a little or double clicked.
Hmm, I can't reproduce it on my test setup (unfortunatly). I have added this as a bug. Could you please provide more information to help me investigate.
raghuk wrote:The only minor glitch I saw was that mouse cursor became very slow in higher resolutions (800x600 and above) and it crashed at 1280x1024.
I have added this bug to my bug tracker. Clould you please provide some more information. How did it crash? Did the kernel provide any usefull info? Whats the memory size of the virtual machine?
, But floppy is painfully slow
)
