That's what I'd do if the program I'm running in the console was an nt console app. Unfortunately it's an 16-bit DOS application, and thus doesn't have much of an access to the win API =) SolVBE thus accepts the console if it's either 1. the only console around 2. has 'solvbe' in the title (eg. …

New alpha: http://iki.fi/sol/solvbe_alpha_050304.zip Now TN is playable - handled the keyboard by passing window events to the console window. Still a lot to do before this is a "complete" product, but I'm going to play TN for a while now.. (I think I'll get irritated by the 320x200 window soon …

Ok, I didn't bother looking into the irq stuff too deeply because of your suggestion, and wrote a routine that finds the correct console with acceptable accuracy. And it works! I can play TN now 😁 😁 😁 A new alpha will pop up later on again..

Good point on the keyboard. That does, however, create another problem (don't they always) - how to figure out which vdm window is what we should be talking to. Mouse is more than just window size problem, btw - client app can change the valid mouse region etc. However, mouse is now pretty much …

I take the mouse interrupt (int33h), but the mouse callback routine should be called whenever mouse moves, which is the mouse irq interrupt.. which I haven't implemented yet. Instead, I hooked the timer, for now, and do the callback from there. Like I said above, that's enough for TN; I can fix this …

NOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!!!!!!!!! 😵

qbix, I will. Although dosbox and vdm extension are somewhat different beasts, at least it can give me some kind of insight on what applications expect from the keyboard. zorbid, I don't think there are any conflicts, as long as vdmsound leaves VESA alone =). I started a new thread on the PC …

New alpha: http://iki.fi/sol/solvbe_alpha_040304.zip Mouse is pegged to timer interrupt instead of mouse irq, so it relies on the fact that a game reconfigures timer to run *fast*. Possible solutions: rewrite to use the mouse interrupt and generate those whenever we get windows mouse messages, or …

Quick status report - I finally figured out the mouse problem. Partially my mistake, partially bad specs.. but it's solved now. Good news is that the TN ingame, while in 320x200, worked straight away. 320x400 is a tweaked mode and doesn't work currently. Bad news is that before I write keyboard …

Terra Nova: Strike Force Centauri demo had mission(s) that didn't exist in the game itself.

FYI - software I've tried. Gateways by Trauma (assembly98 winner demo) - works perfectly in all modes (8bit, 15bit, 16bit, 24bit, 32bit) Terra Nova: Strike Force Centauri - movies work, menus work, you can get to "your room", but from there on mouse is mandatory, so I haven't tried ingame yet. …

Now, there's about five different boards in vogons where I might post this, but I guess this is the least offensive place :disapproving:.. Anyhow, I've started to hack together an universal VESA driver for windows DOS boxes. I've put an alpha online at: http://iki.fi/sol/solvbe_alpha_030304.zip …