Nail on the head! I get a black screen without the computer. But it IS there because when I click on the screen I get beeps! Is that any help for you identifying the problem?

Henri

Well, I could imagine what the problem is - try the following:
1) start CB-Emu
2) right-click on any engine in the list and select 'Properties' in the popup menu
3) now open the tab 'Display': under 'Videomode' on the right side there is 'Auto' predefined, and I guess your Windows doesn't automatically select the correct video mode for your netbook
4) so try all 4 modes in this video submenu, i.e. select a mode, click 'Ok' to exit, and then start this module.

If any of these 4 modes is working for you, then let me know and I'll give you instructions how to change this automatically for ALL modules (else you would have to use the same procedure for each of them).

Franz

Tried out all functions, and OpenGL works perfectly. Thank YOU!!

Cheers,
Henri

Ok, I've attached a ZIP-file where I've changed all INI-files to this OpenGL video mode - just unzip it to your CB-Emu folder and overwrite all files.

Regards,
Franz

Angehängte Dateien

VideoFix.zip (507,7 KB, 78x aufgerufen)

Hallo Franz
Und schon hast Du wieder einen sehr zufriedenen Kunden mehr. Deine
grosse Arbeit müsste gesponsert werden OK, würde dann vielleicht
nicht mehr so viel Spass machen wie eine allsamt hoch geschätzte
freiwillige Leistung.
Gruss
Kurt

Aber das war doch eine Kleinigkeit, keine 2 Minuten Arbeit mit 'grepWin' zum Ersetzen dieser Option in allen ini-Dateien -
ihm hier zu beschreiben, wie er das unter CB-Emu machen müßte, hätte wesentlich länger gedauert.

Grüße,
Franz

Awesome! Playing the Conny on my EEEPC now. You are DA man!

Greetings,
Henri

I just was curious, because i remembered, that i had CB-EMU working on my EeePC 1000h (2 GB RAM, 128 GB SSD, Win 7, now Win10) and i found that GDI is working too (didn't try the other options)

But the N270 Atom CPU was too slow for most of the emulations (IIRC 6502 with 6 MHz was the limit, everything with faster CPUs had slow running clocks), so i removed it some years ago.

At least i can confirm, that it is working with Win 10 on the EeePC!

best regards
Robert

Yes, GDI is the oldest and simplest method and should in fact work on ALL Windows versions and graphic cards (it's also the slowest one, but graphic speed is not needed for a rather static chess board display).
For Direct3D and OpenGL you need special Windows drivers and/or support from the graphic card (I've never heard of BGFX before), on my notebook here (Windows 10 64bit) all 4 options are working.

Regards,
Franz

Hi Hans

The Teensy USB Development Board that I use and Berger coded for me just emulates a keyboard.

First you have to untick the read only attribute in the Montreux cfg properties (Screenshot 1).

Then you change the Steadykey to zero in the Core Input Option of the Montreux ini file (Screenshot 2).

Now you have to try and work out which square corresponds to the Unamed Key in the Root (Screenshot 3).

First on your keyboard, change all the Named keys (New Game etc) to none.

Then input a1 (Kbd A Kbd 1) into any Unnamed Key then return to machine and press the a1 square on your physical board. What happens then is that although you have programmed the Unnamed Key to the a1 square it probably indicates another square on the PC graphical board.

You now go back into the Root and change the wrong programmed Unnamed Key (a1) to the actual PC board square.

Now you have found your first correct square you continue doing this for all the 64 squares.

Final screenshot of my board working with the Montreux program.

I hope this helps you in understanding how it communicates.

Regards
Bryan