BlueIllusionOS 0.06 - Status Update & New Disk image

[distantvoices]

Not much happened above the hood recently, but quite some nifty changes are visible already. The image can be retrieved as usual from the loco in my signature.

Look at this screenie f. ex.:

[center]
[img width=600 height=350]http://www.distantvoices.org/bilder/bi006_GUI_graphicsdemo.png[/img]
[/center]
It has got some features which might please the user.

I know it works in vmware. I 've not yet had a chance to test the vm86-fallback which turns on in case my vm86 task craps out (which it does for sure on certain cpu's). It won't continue to boot on pc's with certain cdrom drives. Standard or not standard, sometimes cdrom drives don't speak the lingo one expects them to. crap.

The font is still atrocious.

Ugh, and the scheduler doesn't deal out timeslices as quick as it should. Maybe I should increase the pit rate from 100 hz to 1000 hz? this might actually increase responsefulness, as rr threads currently blocking don't lose their timeslices - and you know, the average thread except the very cpu bound ones spends more time waiting for some io stuff to be done.

Need to refine this thing. Meh, and the low level memory management needs to be reworked too. Too much hassles lingering around in the overcomplicated stuff I've worked out there. that's not sophisticated, thats idiotic...

Too much to do and less time available than is requested ... ah, but it's fun to study around for the m.sc.

Stay safe.

[Pype.Clicker]

(seems like i *really* should bring a CDRW at work)

btw, do you have guidance for me to use that .iso file in BOCHS or QEMU ?

[distantvoices]

That'd be as easy as "qemu -cdrom blueillusion.iso"

But the qemu emulated cdrom expects other commands than I issue to real drive & vmware drive. *mmpf* I get "no media in drive" errors.

Oh well ... more debugging to do.

btw: in case of successful bootup (either in graphics or text mode) user "root", password "admin"

[Pype.Clicker]

ata: 1 signature doesn't fit 0 ... ch0 cl0
ata: 1 signature doesn't fit 1 ... ch0 cl0
ata: 2 doesn't support atapi packet interface 0 0
ata: ATAPI device type 0 may not be supported
ata: cdrom drive found at 2:heads: 0 cyl: 0 sect/cyl: 0
ata: init DONE
fssrv: init ..... done
guisrv: init ... done
ata: No media in drive

at least i'm glad to see that almost all the messages have been converted (with the exception of 'maus init' and '80277 Controller gefunden').

Oh, and, sorry to say that, but your icons as roughly as ugly as your font i should still have the collection of .bmp i used for the clicker logo. If you want them, i could contribute to BlueIllusion's look&feel

[Pype.Clicker]

oh, and btw, BOCHS says
"CDROM boot failure code : 0003
Boot from CD-Rom failed
FATAL: could not read the boot disk."

I enabled ATA channel 1 (edit options->disk options) with 0x170/0x370, irq 15, inserted the cdrom device as master, with filename "blueillusion.iso", and left BIOS auto-detection enabled.

0. Return to previous menu
1. Floppy Disk 0: /dev/fd0, size=1.44M, inserted
2. Floppy Disk 1: none
3. ATA channel 0: enabled: yes, ioaddr1: 0x1f0, ioaddr2: 0x3f0, irq: 14
4. (disabled)
5. Second HD/CD on channel 0: enabled: yes, cdrom, inserted on '/dev/cdrom', 0 cylinders, 0 heads, 0 sectors/track, model 'Generic 1234', biosdetect 'auto', translation 'auto'
6. ATA channel 1: enabled: yes, ioaddr1: 0x170, ioaddr2: 0x370, irq: 15
7. First HD/CD on channel 1: enabled: yes, cdrom, inserted on 'blueillusion.iso', model 'Generic 1234', biosdetect 'auto'
8. (disabled)
9. ATA channel 2: enabled: no
10. (disabled)
11. (disabled)
12. ATA channel 3: enabled: no
13. (disabled)
14. (disabled)
15. New hard drive support: yes
16. Boot from: cdrom drive
17. Skip Floppy Boot Signature Check: no

00000514204e[HD ] atapi_cmd_error channel=00 key=02 asc=3a
00000520745i[BIOS ] CDROM boot failure code : 0003
00000526086i[BIOS ] Boot from CD-Rom failed

[distantvoices]

Ah, I 've found out: simply send datalength alongside with atapi_read_capacity command and atapi_read_toc

then it works happily in the qemu.

Now I need to do something about the qemu graphics stuff - it used to work. Now it doesn't. Oh sorrow.

[bubach]

haven't testing it yet, but have some style suggestions..
just use the normal 8*16 ( or whatever) ROM BIOS font, it looks nice in SolarOS. ( IIRC that is, and solarOS doesn't use something entirely diffrent)
And don't be afraid of using some open source icons, like http://www.kde-look.org/content/show.php?content=23966..
I don't want to see another version with that font.. Other then that, good work..

[distantvoices]

OK, I'm currently uploading a new iso image. Link in my signature.

Have tested it in vmware: works in both 32 and 16 bpp modes.

have tested it in qemu 0.7.2 - boots up and starts fine now - from the *.iso file. works in 16 bpp mode pretty nice.

YOu'll get a choice now ere switching to gui mode: a small menu with 4 options. enter a key from 1 to 4, and there you are.

If 32 bpp mode looks crap, give the 16bpp mode a try.

@pype: ah, of course I'd like to give these icons a try. shan't be a problem to incorporate them into BlueIllusion.

@bubach: oh well, you 're right, I *might* switch over to that font actually. Just give me some time to let it boil in its own sap.

Stay safe

[Pype.Clicker]

http://prdownloads.sourceforge.net/clic ... p?download

(haa. i have CDRW here ... let's make another attempt)

[Warrior]

Some nice icons =). Hey, have you considered Freetype? From what I've heard it isn't too hard to implement. Good job on BI it's looking very nice.

[distantvoices]

Ugly Icons these are. I have no patience with painting programs. A mouse is simply not suited for doing drawing stuff in my opinion. That's a task for pencil and brush and chalk.

Anyway ... Here 's what I look like in real life - as seen throu my OS:

[center]
[img width=600 height=350]http://www.distantvoices.org/bilder/bi006_GUI_me[/img]
[/center]

Scared? Really? No? I thought so... *gg*

[ZetItUp]

i Cant login :/
how do i do? =)

[distantvoices]

That'd be as easy as "qemu -cdrom blueillusion.iso"

But the qemu emulated cdrom expects other commands than I issue to real drive & vmware drive. *mmpf* I get "no media in drive" errors.

Oh well ... more debugging to do.

btw: in case of successful bootup (either in graphics or text mode) user "root", password "admin" ---> here, this info:

click on a user in the list left of the logo (in the login manager), and the name of the user will appear in the upper of the two lineedits.

In the lineedit above (set focus to it by clicking on it - a black rectangle will be drawn around it upon acquiring focus - and enter the password: in case of the user "root" it's "admin"

Stay safe

[Warrior]

What I've noticed:

Virtual PC
64MB Ram

Well the login when I highlight the user, erase then name, and click the same user again the text wont come back in the box.

Now in the desktop enviroment sometimes the old mouse cursor will be left at the old x,y pos.

Other than that everything runs fine.

[Pype.Clicker]

- successfully got the login screen. Trying to log in "root:admin" results in weird display when i try to erase characters (and actually fail to log in)

- finally logged in. display of icons seems terribly slow ...
- mouse cursor appears "wrapped" when moved at right edge of the screen
- calculator display turned off at the 3rd digit clicked.
- hangman stalled qemu and now i have a non-moving mouse cursor on my X server >_<