Testing OS reports 2

[octavio]

Since this topic was closed i created a new one.
I have been testing some oses and here are the results:

computer1
pentium 75Mhz 8MB vesa 1.2 cirrus logic
keyboard and ps2 mouse
ide controler doesn?t work (burned).

computer2
pentium3 930Mhz 256MB vesa 3.0 tnt
keyboard and ps2 mouse
40GB hd fat32 fs

all tests where made with the same
floppy on both computers ,the floppy was error free.



dex4u:
runs fine
commands dir,help,vesa,more are ok
run,pong,testbmp,c:,d:,e: didn?t work

sekios 0.31:
no problems, 'h'and 't' commands are ok

bos 0.04:
all commands work but only report 7MB of memory on computer 2

s.o.s v0.2:
on computer 1 it seems to work but is hard to use
it needs a better and easier user interface.
i just press ctrl-f1-f5 keys and set graphics mode.
on computer 2 after 'loading kernel... ' nothing happened
probably a problem with the floppy driver.

bcos:
in first boot stage works and also vesa videomodes but not the mouse
in next stage:
on computer 2 it stops after 'timing cpus'
on computer 1 stops after '[device manager] pci ide controller: pci/1045/c621'

manrix:
on computer 1 stops after ' starting init version 1.0 ...'
on computer 2 GPF errorcode 0
cs=8
es=10
ss=10
eip=104eb8
esp=202123
ebp=202143
edi=111000
esi=10e044
eax=4400101d
ebx=563d000
ecx=202174
edx=10e044
note: blue-red text is hard to read.

xolo3 xs32 v1.05:
on computer 2 stops after 'initialisation du timer ...'
on computer 1 seems that it requires a frech keyboard
so i only tested commands 'ls cls help ver' that are ok.

and finally i tested my own OS
( http://www.terra.es/personal2/t933191278/home.htm )
to verify that both computers
and the floppy were ok.

[Candy]

The point behind closing the thread was that OS test reports came in a thread per OS, which makes this entire forum a lot clearer.

[Pype.Clicker]

nice job. Very colorful demonstrations in your own os

just one thing i'm missing is why i have 4 "NE2000" and 8 "RTL8139" cards listed on my system in PCI info.

the point was to have a dedicated board, with one thread per OS

Yep. thought i like that "burst of reports" from you, it is clear that if all the concerned developers try to react to your feedbacks and see what's going wrong (if something goes wrong), it will become a complete mess ... or it will switch to private messages

[octavio]

Candy wrote:
>The point behind closing the thread was that OS test reports
>came in a thread per OS:

Ok i already created a thread of my OS.

just one thing i'm missing is why i have 4 "NE2000" and 8 "RTL8139" cards listed on my system in PCI info.

Because the pci detection program is not perfect, i don?t know very well how to detect non multifunction devices.
I have tried with the multifunction device bit but it fails with some hardware, or i'm using wrong algorithms.

>Very colorful demonstrations in your own os
Yes colors is the most important think in OS marketing ;D