Aprom 090821: yet another OS in for testing

[Artlav]

Hi.

I've been developing an OS project for quite some time now, and hope to get some feedback.
You can get the images here:
http://orbides.1gb.ru/ape090821.zip
Containing a floppy and bootable CD images.

What interests me is if it works on anything other than bochs, qemu and a one PC.
So, if you can and willing to test it on real hardware or an uncommon emulator, feedback and ideas are highly appreciated.

What to look for:
There are 2 modes - GUI mode is started by default, console mode is the second option in GRUB.
In console mode, i'm interested in mutex tests - mt and mt_asm commands.
They should output a column of A and B lines, no intersections, no exceptions.
Other commands are undifferentiating for now.

In GUI mode, first thing is if it works at all.
It should select a VESA 800x600x16 mode automatically. If it doesn't, nothing will happen.
There should be 4 tasks, last one may appear after some seconds on slow emulators.
The switching is in upper-left corner, whole screen per task.
If the mouse doesn't work (does it? another axial thing to test), the tasks are switched every 2 seconds.

I didn't decided yet what are bugs and what are features in the GUI, so testing anything but mouse working, button clicking, graphics showing is only useful for ideas and suggestions.

Thanks for the testing.


Screenshots:

[AUsername]

Nice.

(You even use the method I do for keeping track of builds ^-^)

It's pretty fun to play around with but a couple of bugs:

Bochs 2.3.7:
1. Booting directly into VESA mode causes it to hang

2. In the console calling apic causes
"[APIC0] APIC register 0 not implemented"
"[APIC0] failed assertion "(addr & 0xf) == 0" at apic.cpp:542"
"[APIC0] APIC register 0 not implemented"
*Triple fault?*

3. Calling mt & mt_asm react weirdly, sometimes they loop continuously, or they crash at random points and at one point mt caused a sudden restart (triple fault?)

4. vbe does nothing?

5. if you don't type in a command and then press the up arrow you get an up arrow as a character and you can't backspace.


VPC 2007:
Hung the first time I booted into graphical mode.
When the VESA mode works it's SLOW. Looks like 5-10 FPS?
And mt/mt_asm still loop for no apparent reason.
The font also didn't change like it did in Boch (in console mode)
Don't know if that's a Boch bug or a VPC bug.


Was still pretty cool to play with. Good luck. ^-^

[Artlav]

Thank you for testing and goodwish.

2. In the console calling apic causes
"[APIC0] APIC register 0 not implemented"
"[APIC0] failed assertion "(addr & 0xf) == 0" at apic.cpp:542"
"[APIC0] APIC register 0 not implemented"
*Triple fault?*

Relatively correct - it's does nothing useful so far.

3. Calling mt & mt_asm react weirdly, sometimes they loop continuously, or they crash at random points and at one point mt caused a sudden restart (triple fault?)

They are supposed to loop, giving out a column of A B lines.
Which exceptions was there? Anything coherent?

4. vbe does nothing?

Yes, it was an old way to start the GUI.

When the VESA mode works it's SLOW. Looks like 5-10 FPS?

Slow in every window, or specific ones?

The font also didn't change like it did in Boch (in console mode)
Don't know if that's a Boch bug or a VPC bug.

The font is supposed to change - init loads the russian console font.

[earlz]

not working for me at all..

Code: Select all

[earlz@EarlzBeta-~/ape] $ qemu -fda ape090821.img -m 32 -boot a
qemu: fatal: Trying to execute code outside RAM or ROM at 0xfc00ff40

EAX=f000ef57 EBX=00000000 ECX=0000c112 EDX=0c8bfc43
ESI=00827f0e EDI=00000000 EBP=00000000 ESP=88000ff7
EIP=fc00ff40 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00cf9300
CS =0008 00000000 ffffffff 00cf9a00
SS =0010 00000000 ffffffff 00cf9300
DS =0010 00000000 ffffffff 00cf9300
FS =0010 00000000 ffffffff 00cf9300
GS =0010 00000000 ffffffff 00cf9300
LDT=0000 00000000 0000ffff 00008000
TR =0048 003f0000 00002088 0000893f
GDT=     f03f8000 0000004f
IDT=     00108000 000007f7
CR0=e0000011 CR2=00000000 CR3=00380000 CR4=000002d0
CCS=00000000 CCD=83850f7f CCO=INCL
FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
FPR0=0000000000000000 FPR1=0000000000000000
FPR2=0000000000000000 FPR3=0000000000000000
FPR4=0000000000000000 FPR5=0000000000000000
FPR6=4326000000000000 FPR7=423000867eba0000
XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
Abort trap (core dumped)

I get the same error using both the regular boot option and the [console] boot option

I might write out a floppy and test it a bit later on a few machines.. I have a P2.. think it'll work with that? lol

[Artlav]

not working for me at all..
...
I might write out a floppy and test it a bit later on a few machines.. I have a P2.. think it'll work with that? lol

Then, it's time for the next version.
http://forum.osdev.org/viewtopic.php?f=2&t=20771

It should work on P2.