PMode VBE Test Image

[pkd]

Hi all,

This Mini OS is for testing out the PMode VBE interface and is available as Open Source.

If you would be kind enough to help test if it works on different graphics cards and computers it will be appriciated, please send me your results if possible.

It is available at http://doyle.id.au/html/pkd_s_osdev.html

Thanks
pkd

[Pype.Clicker]

- tested under BOCHS (2.2.1, home-compiled). tells "no pmode VBE interface supported", as expected ...

- tested under VMware 3.1.1 build-1790 ... same message (more surprising :-/ )

[pkd]

Thanks for testing,

I should have mentioned that it wont work under Bochs,and not sure about VM-Ware, But it should work from floppy

OK bye.
pkd.

[Brendan]

Hi,

I tested the VBE test on 8 computers (I didn't worry about trying Bochs). Here's the results:

On 3 computers (no details provided) it displays "No Pmode VBE Interface...(Reset to Exit)".


WORK MACHINE
Pentium IV 1.66 Ghz
256 Mb RAM
40 Gb hard drive
8 Gb hard drive
NVIDEA RIVA TNT2 Model64 Pro video card
NETGEAR FA311/FA312 PCI Ethernet card

COMPUTER D
AMD-K6 3D processor 166Mhz
16Mb Memory
1.44 Mb floppy
CDROM using IDE interface - working (looks crappy)
SiS 6326 video card
NE2000 compatible ethernet card

COMPUTER P
Dual Pentium III 1 GHz
512 Mb RAM
Adaptec AIC-7899 dual-channel SCSI on motherboard
2 * 9 Gb Quantum ATLAS SCSI hard-drives
IDE CD-ROM (50x generic)
Ethernet on motherboard plus 2 PCI ethernet cards

On these 3 computers the screen flashes blue and it triple faults.



COMPUTER H - configured with win95
160Mhz Cryix/Pentium
16Mb Memory
1.44 Mb floppy
514Mb Hard disk
CDrom using IDE interface
Cirrus Logic 5430/40 PCI video card
ESS ES688 Audiodrive sound card
NE2000 compatible ethernet card

COMPUTER O - configured with linux
Pentium Pro 200 MHz
128 Mb RAM
Adaptec AHA-2940 SCSI controller
Compaq ST32550W SCSI hard-drive
IBM DCAS-34330W SCSI hard-drive
IBM DGHS09U SCSI hard-drive
Sony CDU-76S SCSI CD-ROM
Ethernet on motherboard

For these 2 computers it displays "Pmode Initialized..." and stops (doesn't triple fault, respond to keyboard or do anything after displaying the message).


Cheers,

Brendan

[pkd]

Ok thanks brendan,

Looks like ive still got some work to do.

pkd

[bubach]

Tested it on 2 computers.
My own with Gforce 2 and my mothers with NVIDEA RIVA TNT2.

On both computers i could see the "VBE test loading.." mess, then it seems like the screen turns blue (not sure, it is fast) before it resets..

/ Christoffer

[pkd]

I think that the blue screen and reset problem is my A20 code,
Have changed to using the Keyboard controller method instaed of port 0x92, and updated the file on my web site,

If you could please test the new code it would be appriciated,

Thanks
pkd.

[Brendan]

Hi,

Have changed to using the Keyboard controller method instaed of port 0x92, and updated the file on my web site,

If you could please test the new code it would be appriciated,

Ok, using my previous post as a reference, Computer D and Computer H now display the "No Pmode VBE Interface...(Reset to Exit)" message. All other computers behave the same as previously reported.


Cheers,

Brendan

[pkd]

Hi All,

Have updated file again using two a20 methods, hopefully it works this time.

Thanks for everybodys patients

pkd

[distantvoices]

Have tested VBE_test and got following results:

Test under VMware 4.5.1: No VBE PMode Interface detected.

Test on real hardware: AMD k7 Thunderbird, Abit Mobo, 128 mb ram, average graphics adapter with vbe 2.0 bios:

detects pmode vbe 2.0 interface and lists several modes.

I have tried several of these modes: it seems to try a mode switch but then it triple faults.

HtH

[pkd]

Ok, Im not sure whats going on with the tripple fault on mode switch, but at least Ive got it this far.

The Interface must be working to some extent as I get the mode numbers, and the mode info thru it, but the exception handlers not picking it up, Have to think about it a bit more.

Thanks again to everyone whos tested.

pkd.

[Pype.Clicker]

trying to download the VBE_test.zip leads to 404 error ...