OSDev.org

the screenshots look nice, ill test it when i have some time (and am bored).

Microsoft VPC, Qemu, Bochs and my laptop (acer 5610Z)

buzz wrote:@octavio: can you please be a bit more precise. where does it behave slow?

At many places ,menu,buttons etc ,by slow i mean one second or more betwen i press the button and the action is done, also scroll bars do not works ,fire sdl demo and other programs do not work but the main problem is the absence of any doc explaining how to use this OS.
It is not slow compared to linux and windows but other hobby OS have very small reponse times.

It seems that a disk cache is not implemented so it has to read data from disk everytime and this causes the slow reponse time (i tested from a cd).

The terminal colors are not very visible a brightness leters color would be better.

* Ok, lighted the green terminal color to 0xFF, should be enough
* Disk cache is present and seems to work fine, all buffer which are not used within 5 seconds will be freed. Maybe this is causing the delay?
* A document with a short introduction will follow as soon as possible, thanks for the note.
* Some programs like Fire SDL are testing applications and are known to be unstable at the moment. Remember this is not a final release, just a developer snapshot. But maybe the package maintainer should only add working programms. Noted.
* Hmm, buttons, menus, etc are there right after clicking, the panel had some delay because of WindowTimer but are moved to threads now.
Maybe disabling debug at boot (remove debug=1 option in grub) can speed it up... please give it a try.

And thanks for testing

>all buffer which are not used within 5 seconds will be freed.
why?
> Maybe this is causing the delay?
Yes it reads data from cd frecuently and the cd is slow.
>Maybe disabling debug at boot (remove debug=1 option in grub)
don't know how to to it , cd is a read only filesystem and the system boots to fast to do anything at boot time.

you edit in in the .iso archive, then re-burn to CD.

no... ok it will work but its easier to press 'c' when it shows the boot menu, or if your screen is too slow just hit 'c' when it access the cdrom. now you can edit the lines in grub.

buzz wrote:no... ok it will work but its easier to press 'c' when it shows the boot menu, or if your screen is too slow just hit 'c' when it access the cdrom. now you can edit the lines in grub.

i see no diference.

Just keep pressing 'c' from the moment your bios boots. Chances are it'll eventually get into a GRUB console!

I tried it on a Q6600 with a Gigabyte DS4-P35. It hangs at "getting USB descriptor".

@cyr1x: Maybe you can send me the kernel log? We'll add a disable function for usb, so that you can boot even with usb problems.

@octavio: forgot to mention that scrollbars are working fine except the bar. You can press the up/down buttons and even use the scroll mouse.
Yesterday i've found a computer which does the "slow" response when pressing the buttons, even with no buffer clean. It seems that the major problem on this and also your computer are the syscalls.
What kind of computer do you have? As we do not support SYSENTER.. yet, there should be some speed up later on.

buzz wrote: What kind of computer do you have? As we do not support SYSENTER.. yet, there should be some speed up later on.

portable P3 600mhz with 128 MB ram
and P3 900mhz 512 MB ram
I would like to know how to read files on the hard disk or usb memory,the file browser only shows the files on the cd.

at the moment there is no automatic mounting of other devices than the boot device. you will have to take the *nix way and open the terminal and do "mount /dev/xxx destinationdir". Automatic mounting will be available within the next release

buzz wrote:@cyr1x: Maybe you can send me the kernel log? We'll add a disable function for usb, so that you can boot even with usb problems.

How do I get it? Anyway I tried the CD image so i can't save it

I tried running the ISO image on my server box called Io

- It runs awfully slow (as an indication, it took 15 minutes until it came with the bogomips reading)
- it mounted root as /dev/hdÇ256 - it's a SCSI machine, completely void of an ATA controller.
- After 45 minutes, the clock on the statusbar stopped

After 45 minutes, the clock on the statusbar stopped and I decided to post this (last message: Initializing APM...) as it was literally getting nowhere. My guess was that it was trying to locate the CD on the nonpresent ATA controller, while in fact it was on the third SCSI controller.

EDIT: the clock came back on.

I guess you are not using the right image... please use the image linked in the news articel, as the image on the download section are the official released. The newer ones do not try to automatic mount devices so no /dev/hdÇ256 should be there.

@cyr1x: Debug output is send via the serial line... at the moment the only way for writing the kernel log.