eox ran fine on a real computer a few years ago.
but with the time I only started to test my kernel in vmware/bochs and I somehow restarted the whole project about 2.5 times, so the revision 3 kernel was only tested in vmware & bochs (quadsmp)
so.. I don't know if eox3 runs smoothly on a real PC, could somebody please check this out?
bootable floppy image:
http://www.stud.uni-karlsruhe.de/~uvvm/ ... ld2211.img
I think I should go and get a bootable USB stick - my dev laptop has NO FLOPPY DRIVE.....
If you see a message "system halted", everything is fine.
THANKS for your time
eox3 compatibility test
Re:eox3 compatibility test
No, sorry, doesn't boot at all, hoped to see a GUI, or something.. but it didn't happen..
Maybe you could use these information pieces:
GRUB: (thanks to my fast mouse clicking )
Maybe you could use these information pieces:
GRUB: (thanks to my fast mouse clicking )
And this is from BOCHS.OUTroot (fd0)
Filesystem type is fat, using whole disk
kernel /eox.exe
[Multiboot-kludge, loadaddr=0x101000, text-and-data=0x694c, bss=0x880, symta
b=0xb8, strtab=0xfffffffc(bad), entry=0x101000]
00001120509i[VGA ] VBE known Display Interface b0c2
00001170000i[WGUI ] dimension update x=640 y=400 fontheight=16 fontwidth=8 bpp=8
00001185000i[WGUI ] dimension update x=720 y=400 fontheight=16 fontwidth=9 bpp=8
00004000778i[VGA ] VBE known Display Interface b0c2
00004050000i[WGUI ] dimension update x=640 y=400 fontheight=16 fontwidth=8 bpp=8
00004065000i[WGUI ] dimension update x=720 y=400 fontheight=16 fontwidth=9 bpp=8
00004500000i[WGUI ] dimension update x=640 y=400 fontheight=16 fontwidth=8 bpp=8
00129884500p[WGUI ] >>PANIC<< POWER button turned off.
00129884500i[SYS ] Last time is 1088603333
00129884500i[CPU ] protected mode
00129884500i[CPU ] CS.d_b = 32 bit
00129884500i[CPU ] SS.d_b = 32 bit
00129884500i[CPU ] | EAX=00fde6ed EBX=00000700 ECX=001078cd EDX=0000004c
00129884500i[CPU ] | ESP=0007fe78 EBP=00067eac ESI=0002a7af EDI=001081cc
00129884500i[CPU ] | IOPL=0 NV UP DI NG NZ NA PO CY
00129884500i[CPU ] | SEG selector base limit G D
00129884500i[CPU ] | SEG sltr(index|ti|rpl) base limit G D
00129884500i[CPU ] | DS:0010( 0002| 0| 0) 00000000 000fffff 1 1
00129884500i[CPU ] | ES:0010( 0002| 0| 0) 00000000 000fffff 1 1
00129884500i[CPU ] | FS:0010( 0002| 0| 0) 00000000 000fffff 1 1
00129884500i[CPU ] | GS:0010( 0002| 0| 0) 00000000 000fffff 1 1
00129884500i[CPU ] | SS:0010( 0002| 0| 0) 00000000 000fffff 1 1
00129884500i[CPU ] | CS:0008( 0001| 0| 0) 00000000 000fffff 1 1
00129884500i[CPU ] | EIP=0010128e (0010128e)
00129884500i[CPU ] | CR0=0x60000011 CR1=0x00000000 CR2=0x00000000
00129884500i[CPU ] | CR3=0x00000000 CR4=0x00000000
00129884500i[ ] restoring default signal behavior
00129884500i[CTRL ] quit_sim called with exit code 1
Re:eox3 compatibility test
hmm...
the >>PANIC<< POWER button turned off thing is normal.
the last thing that was done then is some videostuff.
i get the same grub messages, so the kernel should be loaded properly.
I think your bochs doesn't like my strange videomode. I think I'll disable that and make two test releases.
Which bochs version do you have?
Mine is ver 2.0.2, january 21 2003, compiled with 4 cpus.
thanks
NOTE: there is no gui yet. just a textmode startup screen.
after initialization is done, the kernel halts.
the >>PANIC<< POWER button turned off thing is normal.
the last thing that was done then is some videostuff.
i get the same grub messages, so the kernel should be loaded properly.
I think your bochs doesn't like my strange videomode. I think I'll disable that and make two test releases.
Which bochs version do you have?
Mine is ver 2.0.2, january 21 2003, compiled with 4 cpus.
thanks
NOTE: there is no gui yet. just a textmode startup screen.
after initialization is done, the kernel halts.
Re:eox3 compatibility test
ok, downloaded the newest bochs 2.11, now I know what you're speaking about..
I can't see anything.
I just skipped the videomode initialization and everything works fine without an error
Maybe the kernel worked fine before but you couldn't see anything because the colorpalette was all black (black text on black background looks just too good..). I'll play around a little bit...
I can't see anything.
I just skipped the videomode initialization and everything works fine without an error
Maybe the kernel worked fine before but you couldn't see anything because the colorpalette was all black (black text on black background looks just too good..). I'll play around a little bit...
Re:eox3 compatibility test
So did I, and I know >>PANIC<< power off means that I pushed the power off button (virtually )mpp.eox3 wrote: ok, downloaded the newest bochs 2.11, now I know what you're speaking about..
I can't see anything.
Where can WE download YOUR new version ?I just skipped the videomode initialization and everything works fine without an error
Maybe the kernel worked fine before but you couldn't see anything because the colorpalette was all black (black text on black background looks just too good..). I'll play around a little bit...
Re:eox3 compatibility test
still hacking the vga registers...
this will take a while.. But I know now where exactly the problem is. I just have to make it bochs compatible..
this will take a while.. But I know now where exactly the problem is. I just have to make it bochs compatible..
Re:eox3 compatibility test
k got the vga to do what I want. Build 2258 works now in bochs 2.11 too:
http://www.stud.uni-karlsruhe.de/~uvvm/ ... ld2258.ima
http://www.stud.uni-karlsruhe.de/~uvvm/ ... ld2258.ima