Recent changes to feature-requests

#208 Support for RS-232 emulation with v 2.00 ROM

SD Snatcher — Tue, 23 Jun 2015 02:27:13 -0000

Confirmed: The Sony HBI-232 uses the RS-232 BIOS v2.00, just like the Sony HB-G900P built-in RS-232.

#277 Debugger generic bug/improvement

Eugeny Brychkov — Thu, 30 Apr 2015 12:39:35 -0000

Wish: I find backtrace feature very useful. I do not know if it's possible, but would be great having backrace to specific breakpoint. One time I pressed F8 on call, and it did wrong thing. I was doing backtrace for 20 minutes pressing the button, but was able to roll back only 1/5 of execution progress...

Debugger generic bug/improvement

Eugeny Brychkov — Mon, 27 Apr 2015 22:01:00 -0000

Hello, I just started working with OpenMSX debugger, and will be logging all the wishes/problems I notice. Bear with me I am the user of BlueMSX, and probably will be writing some stuff which I think was very useful for me in BlueMSX debugger.
I use windows platform.

in the main debugger window, I can not resize panels. If I make debugger full screen, I have long tall section for code, and small sections for regs, dum, stack, flags etc. It would be great if I can resize the sections to fit the screen, and the debugger remember these settings.
it would be really helpful if I can change values of flags in the flags window. For now the only way I found to change flags is to go to registers and change hex value of AF. That's uneasy because I need to remember what original AF was, and need to make bitmap hex value of flag I need to change to put it in hex. That would be solved if I can just doubleclick onto flags state (e.g. there's "(C)", I double click on it, and it changes to "(NC)"). This is needed for emulating/debugging of the proper flow for devices which are not supported by OpenMSX yet.
the same way as (2) it would be great if I can change DI to EI and back with doubleclick.
I noticed when I press F8 (step over) debugger does not highlight changed registers with red. It works when I use F7 (step into). It would be very helpful if F8 would do that too - so that I instantly see (without tracing whole sub) which registers it changed.
I tried to load .SYM file generated by LINK (MSX linker), it did not work. Probably symbols need some other format.
I added debuggable viewer - "memory". I am currently troubleshooting device which changes pages on write to specific address. So I put "internal" dump window onto location I write page# byte to, and watch "memory" debuggable view. When I write byte to internal dump window, debuggable view does not change its contents (however there's now other data in the location being displayed). Only when I take "memory" window by its slider and move top/down a little, view changes to proper contents of the memory.

That's all for now... Thank you!

Support android tv and moga and shield controllers

Alex Wulms — Thu, 02 Apr 2015 16:31:18 -0000

Request received from Bassamation S:

Thank you openmsx developers ,,
we can't play openmsx with the controller becouse please make it possible for moga and shield controllers ,, and make an android tv version becouse this is the only msx emulator that run the games well and on the normal game speed ,,
Thank you ,, and l hope you consider my request , thank you .

Support for kanji ROM maskROM dumps

Leonard Oliveira — Fri, 20 Mar 2015 20:58:56 -0000

Dumps of KANJI ROM font data made through hardware readout are different from software made dumps because the driver circuitry for the ROM will alight the data in a different manner.

Contained in the zip file are a SVG/PNG image of the MSX Datapack sample circuitry for JIS LEVEL1 font circuitry and a C program which reorder the software made dump in the same way the hardware made dump is.

Keep in mind that attempting to use a software made dump into a hardware repair does not work (nor does work attempt use a hardware made dump on emulator) due to this slight issue with the addressing of ROM caused by the circuitry.

#56 64kB and 16kB VRAM support for V9938

Manuel Bilderbeek — Sun, 18 Jan 2015 21:09:26 -0000

The following you get when executing this program in the emulated Canon V-25:

10 screen 5
20 VDP(0) = 14 : REM should enable screen 8
30 goto 30

On real Canon V-25, I get a solid green color....

See https://www.youtube.com/watch?v=TKtNpNhHIMk

Tests that l_oliveira did give different results: when trying color 15,1,1 he gets a purple screen and with 15,0,0 he gets a black screen.

#9 Copy/paste from/to openMSX

Manuel Bilderbeek — Thu, 15 Jan 2015 21:24:41 -0000

Paste-to options are nowadays:
- the Type feature in Catapult (which works with any keyboard layout nowadays)
- the type_from_file console command to type the contents of a file

Copy-from options:
- the get_screen command on the console. Put to file e.g. via save_to_file test.txt [get_screen] (for text modes only)
- indeed via the printer (e.g. llist for a basic program in RAM)
- via the listing command if it's about a basic program in RAM

#226 -borderless option for screenshot command

SD Snatcher — Sat, 03 Jan 2015 23:03:10 -0000

This feature would be of great help when capturing series of screenshots.

#56 64kB and 16kB VRAM support for V9938

Manuel Bilderbeek — Fri, 19 Dec 2014 13:49:32 -0000

https://www.youtube.com/watch?v=uOT1cqKHG1c shows what happens with 64k VRAM if you try to display page 2 of screen 5. I confirmed this on a Canon V-25.

openMSX does NOT emulate this behaviour correctly. This is what you get in openMSX (a static image):

#274 Support for Dir-as-disk in OSD menu

Manuel Bilderbeek — Mon, 15 Sep 2014 11:49:56 -0000

status: open --> closed
assigned_to: Manuel Bilderbeek