openMSX bugs | MSX Resource Center (페이지 8/15)

Scribe (1743)

22-11-2020, 16:45

maybe the script can check if there already is a cart inserted, store the cart's path / rom mapper, and then reinsert it after changing the machine?
Not sure if the cart is already inserted, and thus can be detected, at the time the script runs?

By Manuel

Ascended (19469)

22-11-2020, 16:50

Good idea! This works indeed!

Script example.tcl:

set carta [lindex [carta] 1]
machine Sanyo_PHC-28L
carta $carta

openmsx -script example.tcl -carta mygame.rom

By FiXato

Scribe (1743)

22-11-2020, 16:50

IMHO it does make sense that switching a machine does not automatically reinserts the same carts, but I also think it would make sense for the -cart CLI option to be parsed after the script.
Or perhaps more logically, process the CLI arguments in the order they are put.
So, openmsx -script script.tcl -carta mycart.rom would first process the script and then insert the cart, while openmsx -carta mycart.rom -script script.tcl would first insert the cart, and then run the script.

By ericb59

Paragon (1102)

22-11-2020, 17:24

@FiXato : I thought it would have turned out like this, indeed.

Maybe you have an idea to solve my problem.

As you can see I have several TCL machine configuration scripts, MSX1 to MSX Turbo-R.

When I run a compilation with Fusion-C, my Build Script, also launch openMSX to test the compiled program.
I indicate to the Build script with external parameters, which TCL script will be launched at the end of the Build (So which MSX will be launched).
In the case of compiling a ROM, the name of the final file is only known by the Build Script, which is why I wanted to integrate it as a variable in the openMSX launch command.
If I integrate it into the TCL script, I am forced to have a file name engraved in stone.

Do you see any other solution?

By Manuel

Ascended (19469)

22-11-2020, 18:57

Did you see my post Eric?

Just add these 2 lines that capture what is inserted and reinsert it again after the machine command.

Also, you can make the scripts a lot smaller by saving the things you do there as normal settings.

By ericb59

Paragon (1102)

22-11-2020, 19:11

Ha no ! Sorry I missed your previous post.
I will try this solution.
Thank you !!

By ericb59

Paragon (1102)

22-11-2020, 19:49

Great it works !
Thank you ...

I have a subsidiary question :

If I'm using a slotexpander in slot b
extb slotexpander

How am I suppose to add other expansions or Rom on this slot expander ?

is it something like that : extb1 fmpac ??

By Manuel

Ascended (19469)

22-11-2020, 20:58

All new slots just get new letters. Here's the situation, showing off some improvements in the OSD menu as well:

By wouter_

Hero (525)

23-11-2020, 19:51

mzoran wrote:

I am seeing some display issues with SDLGL-PP renderer and odd scaling factor (simple scaler). This program should produce perfectly straight parallel lines:

10 SCREEN 7
20 FOR X=0 TO 511
30 LINE (X,0)-(X,211),(X MOD 15)+1
40 NEXT X
50 GOTO 50

But there appears an offset where lines after a certain y coordinate become 1 pixel shifted to the right.
If I set scaling factor to an even value or set renderer to SDL things look as expected.
Any hints on what am I doing wrong ?

Hi mzoran,
This was recently fixed. Thanks again for reporting.

By Manuel

Ascended (19469)

23-11-2020, 22:02

Maybe you like this better:

It shows which are the actual MSX slots in the cartridge slot overview.