tag:blogger.com,1999:blog-5488830577558823919.post597830677475490242..comments2023-03-02T16:58:21.700+01:00Comments on Desarrollos en 8 Bits. ZX Spectrum, Commodore 64.: Que usar para programar para MSX/MSX2 en tu PC.Ibitatohttp://www.blogger.com/profile/09167276345380472054noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5488830577558823919.post-22858420914822210192021-03-24T21:59:19.606+01:002021-03-24T21:59:19.606+01:00Thank you very much.
I used MSX maaaaaany years a...Thank you very much.<br /><br />I used MSX maaaaaany years ago.<br />Now, in 2021, I decided to play with MSX emulators a little bit, to remember the past.<br />I tested the original MSXPAD (which lacks support to Windows 10) and discovered MSXPadRevived here (which brings that support). <br />To those interested, I'd like to note that there are 3 bugs in MSXPadRevived:<br />1) F6 gives error if there is already a D.DSK file in the project folder (so, we have to manually delete this file to proceed)<br />2) F5 silently launches the emulator, even if the source code has not been recompiled, due to the error in F6 (so, what you will see running is the OLD version of the program)<br />3) Included * .INC files cause crazy (non-existent) syntax errors due to the use of DOSBOX in Windows10.<br /><br />There is a simple solution to problem 3 above, just use DosBox-X instead of DosBox.<br />But there is no solution to problems 1 and 2 above in MSXPadRevived.<br /><br />So, I researched a little more and found that Slotman released a fix for the F5 and F6 bugs (problems 1 and 2), but only here on this page:<br /> https://www.msx.org/forum/msx-talk/development/loac-sc5-screen-in-pascal<br /><br />Following his instructions, I installed MSXPAD and then overwrote it with that NEW FIXED files and all errors were corrected. MSXPAD is now compiling normally on Windows 10, no errors !!!Anonymousnoreply@blogger.com