VOGONS

Common searches


Search results

Display options

Re: DOSBox-X branch

It's done. - Numeric keypad = - F13-F24 as shifted F1-F12 - Japanese keyboard keys - Korean keyboard keys The mapper is built so that if you have a US english keyboard like mine you can still bind some of your keys to the Japanese/Korean ones to test regardless. NOTE: For Japanese Windows 95, the …

Re: DOSBox-X branch

Hm... are you aware though that scan code 0x59 on the PC is already associated with the right shift key in scan code set 2 and 3? Well that's a different scan code set. The key I'm talking about is 0x0F in scan code set 2 and 3: http://www.win.tue.nl/~aeb/linux/kbd/scancodes-10.html#ss10.3 . This …

Re: DOSBox-X branch

Alright, looking around, it looks like the IBM PC never had a numeric equals sign key (that I can find). In fact almost every IBM PC keyboard I can find has no equals key on the numeric keypad. Do you mind if I just go ahead and map that to the same handling as the normal equals key? No, because I …

Re: DOSBox-X branch

Well, it's about getting the correct scan codes generated inside DOSBox-X, nothing else. Even on a real PC, any key will simply generate the appropriate scan code, and it's up to the OS and the installed drivers/TSR's to do something with them. As for the F13-F16, I'm talking about the ones on an …

Re: DOSBox-X branch

I just tested DOSBox-X, and it's basically perfect. I only have one small issue - certain keys are not passed at all. Specifically the following keys: - [Apple] Keypad = (make code 0x59, break code 0xD9); - [Apple] F13 (make code 0x64, break code 0xE4); - [Apple] F14 (make code 0x65, break code 0xE5 …

Re: PCEm. Another PC emulator.

Well, from what I see, we know the fix for this time/date "bug". All that has to be done is for someone to add a configuration setting to PCem which can enable/disable changing the date/time inside the emulated PC. I could try doing that. That way the wolf is not hungry anymore and the sheep is …

Re: PCEm. Another PC emulator.

Here is a link to my PCem patchset (basically adds Phoenix S3 Trio64 and Phoenix S3 Trio32, makes it so the correct VRAM information is always returned from CRTC 0x36, and rewrites keyboard handling using raw input): http://citadel.ringoflightning.net/92.patch .

Re: PCEm. Another PC emulator.

Submitted my patchset to you. Includes both the S3 changes (forking of Trio64 into three by adding the Phoenix ones, which mainly differ in the VRAM amount, and in case of the Trio32, in how it identifies as), and the keyboard changes. Also, the 32-bit modes now work fine, though in 1024x768x32-bit …

Re: PCEm. Another PC emulator.

- SarahWalker: What is that, and how do I use it? Edit: Found what Bitbucket is, but it seems I should have thought of it earlier. I got my copy of the PCem source from here: http://www.retroroms.net/modules/newbb/viewtopic.php?topic_id=7657&forum=3 , and not from the repository. I'll see if I can …

Re: PCEm. Another PC emulator.

By the way, this is the changes I did to the keyboard handling: In WIN.C: I added this: #define _WIN32_WINNT 0x0501 In the very beginning. Near the beginning, I also added this: RAWINPUTDEVICE device; I added these two procedures before WinMain: UINT16 convert_scan_code(UINT16 scan_code) { switch( …

Re: PCEm. Another PC emulator.

- SarahWalker: About the top quarter issue, what's running it Little Big Adventure 2, a game from 1997 for DOS and Windows 95, this is specifically the DOS version running that uses DOS4GW. The OS is MS-DOS 6.00. System Configuration: Award VX430 with WinChip 240. S3 Trio64 card (but the problem …

Re: PCEm. Another PC emulator.

This is it: http://goput.it/v/hmmf.png . Colors are completely screwed up, and fonts aren't rendering correctly. Also, found another bug, on all video adapters - in some 256-color modes, only the top quarter of the screen is rendered. This is an example: http://goput.it/v/6782.png .

Re: PCEm. Another PC emulator.

Whew, did more work on the keyboard handling. Made all known escaped keys (those beginning with E0) sent, and even devised a way to disambiguate eg. E0 71 from F1 and E0 F1, and so on. Also noticed it was incorrectly passing E0 8A as the break code of E0 2A (fake shift issued by some keys) instead …

Re: PCEm. Another PC emulator.

Forked out the S3 Trio64 a bit, now there's 3 of them: - 9FX Vision Trio64: 9FX BIOS, 1 MB VRAM, identifies as Trio64; - Phoenix S3 Trio64: Phoenix Trio64 BIOS, 4 MB VRAM, identifies as Trio64; - Phoenix S3 Trio32: Phoenix Trio32 BIOS, 2 MB VRAM, identifies as Trio32. Now to get back to fixing the …

Re: PCEm. Another PC emulator.

Keyboard handling rewrite is done, it even respects the mapping at "ScanCode" at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout now, and I also made it pass on scan codes 0xF1 (make, no break) and 0xF2 (make, no break) correctly (these are the Hancha and HanYong keys found on …

Re: PCEm. Another PC emulator.

PcEm is compiled to use ASCII layout. You may try to either compile it with UNICODE define, or switch to DIrectInput8 and pass IID_IDirectInput8W as parameter in DIrectInput8Create function. http://msdn.microsoft.com/en-us/library/windows/desktop/microsoft.directx_sdk.reference.directinput8create …

Re: PCEm. Another PC emulator.

Well, I'd say Microsoft's own DOS/V drivers are the standard in this case. The only problem is, we obviously doesn't have the source code of Microsoft's JDISP.SYS. If we did, everything would be much simpler, since we'd just need to look there to see what it does.

Page 6 of 7