jzIntvImGUI (Mattel Intellivision) + Launchbox

[5thWolf]

Can anyone help me get jzIntvImGUI working with with Launchbox?
I have the emu working and running games. I just don't know what settings I should use in the emulator details in LB. Best I got is it launches the EMU and just sits on the main screen.

[launchretrogirl2562]

I dont think jzIntvImGUI has commandline arguments to pass from launchbox? At least I can't find anything relating to that.

I think if u use the jzIntv then it will work.

[5thWolf]

Yeah I am about to. I don't like how this emu runs anything in Fullscreen!

You by chance know the settings and commands for jzintv?

Edited Thursday at 12:44 AM by 5thWolf

[launchretrogirl2562]

yes.
jzintv.exe [options] [rom_file]

• -f1 - Fullscreen mode
• -z# - Display size (0-7, where 6 = 1728x1080)
• -p [path] - ROM path for BIOS files
• -q - Quiet mode (suppress stdout)
• --kbdhackfile=[file] - Custom keyboard mappings

so that would be for instance:

jzintv.exe -f1 -q %romfile%

U might have to play around with the rom part. Standalone romfile/rompath...

[launchretrogirl2562]

I run my mattel intellivision in Retroarch by the way.

Might be another path to explore.

https://docs.libretro.com/library/freeintv/

[5thWolf]

12 minutes ago, launchretrogirl2562 said:

yes.
jzintv.exe [options] [rom_file]

• -f1 - Fullscreen mode
• -z# - Display size (0-7, where 6 = 1728x1080)
• -p [path] - ROM path for BIOS files
• -q - Quiet mode (suppress stdout)
• --kbdhackfile=[file] - Custom keyboard mappings

so that would be for instance:

jzintv.exe -f1 -q %romfile%

U might have to play around with the rom part. Standalone romfile/rompath...

Hmmmm... Ok lets see if I can get it on LB!

[5thWolf]

When I launch it I see a command window but it immediately disappears. Tried most of the checkboxes for quotes or space before file. Here is what I have so far:

Will do the fullscreen command if I get it running.

[launchretrogirl2562]

Do you have these files?
Executive ROM: Commonly named EXEC.BIN or EXEC.INT.
* Graphics ROM: Commonly named GROM.BIN or GROM.INT.

extra bioses

* Entertainment Computer System ROM: Commonly named ECS.BIN. Required to play ECS games.
* Intellivoice ROM: Commonly named IVOICE.BIN. Required to play Intellivoice games.

Edited Thursday at 01:24 AM by launchretrogirl2562

[launchretrogirl2562]

from the website:

the main files (listed below) are also needed to play all the games. They need to reside in the directory where jzIntv is installed. These files are NOT part of the installation and can be obtained from the Intellivision Lives or Rocks CD.

* Executive ROM: Commonly named EXEC.BIN or EXEC.INT.
* Graphics ROM: Commonly named GROM.BIN or GROM.INT.

* Entertainment Computer System ROM: Commonly named ECS.BIN. Required to play ECS games.
* Intellivoice ROM: Commonly named IVOICE.BIN. Required to play Intellivoice games.

(The above files should reside in the directory where jzIntv is installed.)

[launchretrogirl2562]

Full commandline commands:

Usage:
    jzintv [flags] gamefile

Specifying a game image:
    jzIntv supports most, if not all, known formats for Intellivision
    game ROM images.  When invoking jzIntv, provide the full path to
    the game-image file.  If you omit the file extension, jzIntv will
    search for an appropriate file by trying the following extensions:
    .rom, .bin, .int, and .itv.  The overall ROM search process is
    somewhat involved.  See the jzIntv documentation for details.

    If the filename ends in .bin, .int, or .itv, or if jzIntv does not
    recognize the file's extension, it will assume the file is in BIN+CFG
    format.  In that case, jzIntv will look for a matching .cfg file.

    Systems with case-sensitive file names (Linux, UNIX, etc.) need to
    ensure the filename extensions are in lower-case.  On all systems,
    jzIntv expects to receive file names with lower-case extensions.

ROM Image Flags:
    -e /path/to/exec.bin          Specifies path to the EXEC ROM image.
    --execimg=/path/to/exec.bin   By default, jzIntv looks in current dir.

    -g /path/to/grom.bin          Specifies path to the GROM ROM image.
    --gromimg=/path/to/grom.bin   By default, jzIntv looks in current dir.

    -E /path/to/ecs.bin           Specifies path to the ECS ROM image
    --ecsimg=/path/to/ecs.bin     By default, jzIntv looks in current dir.
                                  Only needed when ECS is enabled.

Intellivision Hardware Flags:
    -s#     --ecs=#               ECS.           0: Disable, 1: Enable
    -v#     --voice=#             Intellivoice.  0: Disable, 1: Enable
    -W#     --voicewindow=#       Sets averaging window for voice filter.
    -Vname  --voicefiles=name     Saves voice WAV files to name####.wav.

Video and Sound Flags:
    -z#     --displaysize=#       Desired display mode:
                                      0:  320x200x8bpp
                                      1:  640x480x8bpp
                                      2:  320x240x16bpp

    -f# -x# --fullscreen=#        Full screen display:
                                      0:  Windowed
                                      1:  Full screen

    -a#     --audiorate=#         Audio sampling rate.  0 disables audio.
            --audio=#             Synonym for --audiorate.
    -Fname  --audiofile=name      Records all audio to specified file.
    -w#     --audiowindow=#       Sets averaging window for audio filter.
    -B#     --audiobufsize=#      Internal audio buffer size.
    -C#     --audiobufcnt=#       Internal audio buffer count.
    -M#     --audiomintick=#      Minimum Intellivion cycles between
                                  explicit calls to snd_tick().

Input Configuration Flags:
    Currently, jzIntv does not offer a flexible method to re-bind keys.
    The kbdhackfile does allow you to crudely specify key bindings.

    --kbdhackfile=/path/to/file   Configure key bindings.

    -m#     --kbdmap=#            Specify initial keyboard map (0-3)

    Analog and USB joysticks have a rich set of configuration parameters.
    Run jzIntv with an empty configuration string to find out defaults
    are for your joystick and operating system.  For more information on
    configuring joysticks, see the file jzintv/doc/jzintv/joystick.txt

    --js0="config string"         Configures Joystick #0
    --js1="config string"         Configures Joystick #1
    --js2="config string"         Configures Joystick #2
    --js3="config string"         Configures Joystick #3

    The INTV2PC can drive either the Master Component or the ECS' controller
    inputs.  The following flags associate INTV2PCs with controllers:

    -i#     --i2pc0=#             Port # for INTV2PC for Master Comp inputs.
    -I#     --i2pc1=#             Port # for INTV2PC for ECS inputs.
            --intv2pc0=#          Synonym for --i2pc0
            --intv2pc1=#          Synonym for --i2pc1

    The Classic Game Controller can drive either the Master Component or
    the ECS' controller inputs.  The following flags associate CGCs with
    controllers:

    --cgc0[=#]                    CGC for Master Component inputs.
    --cgc1[=#]                    CGC for ECS inputs.

Intellicart .ROM emulation specific flags:
    -c#     --icartcache=#        Change caching policy for Intellicart
                                  .ROM programs:
                                  0:  Cache bankswitched memory (default)
                                  1:  Don't cache bankswitched memory
                                  2:  Only cache read-only, non-banksw.
                                  3:  Do not cache anything.

Misc Flags:
    -d      --debugger            Enable jzIntv's debugger.
            --sym-file=path       Load symbol table from 'path'.

    -r#     --ratecontrol=#       \_ Speed up by factor #.  Setting #
            --macho=#             /  to 0 disables rate control.

    -p path --rom-path=path       Append path to the ROM search path.

    -q      --quiet               Hide jzIntv's non-error output.

            --gui-mode            Tells jzIntv to listen for commands from
                                  a GUI over stdin.

    -J path --jlp-savegame=path   Enable JLP-style save-game support with
                                  'path' as the save-game file.

    -l      --license             License information
 -h -?      --help                This usage info

Environment:
    JZINTV_ROM_PATH               Controls ROM search path.  Components of
                                  the ROM search path should be separated
                                  by ";" characters.  jzIntv examines
                                  dirs specified by --rom-path before
                                  dirs specified by JZINTV_ROM_PATH.

Legal note:
    Intellivision(TM) is a trademark of Intellivision Productions.  Joe
    Zbiciak and jzIntv are not affiliated with Intellivision Productions.

 

jzintv.txt

Edited Thursday at 01:33 AM by launchretrogirl2562

[launchretrogirl2562]

first run it only from command line
Open command window

Go to the directory where you have jzintv installed.

For instance:

C:\Program Files\jzIntv\bin

then start jzintv with the path to your rom

I just tried and airstrike launches.

so just jzint.exe and passing the romfile (with complete path to rom) starts the game

so u should be able to launch it from LB

 

[5thWolf]

Yes I have the bios images, I can run games fine with just the emulator. Just not through LB.

With full path name I tried with and without quotes and still, command window just disappears immediately after I see it.

[JoeViking245]

1 hour ago, 5thWolf said:

With full path name I tried with and without quotes and still, command window just disappears immediately after I see it.

Edit emulator - NO boxes checked (except in Associated Platforms - Default Emulator). -f1 for fullscreen.

 

Edit game - point to the .int file

[5thWolf]

Oh man that's exactly what I have on my last attempt!
I just now tired, just incase, making the rom path be "..\emu\game.int" instead of "E:\emulators\emu\game.int".
But was same exact result.

Edited Thursday at 02:30 PM by 5thWolf

[JoeViking245]

2 minutes ago, 5thWolf said:

Oh man that's exactly what I have on my last attempt!
I just now tired, just incase, making the rom path be "..\emu\game.int" instead of "E:\emulators\emu\game.int".
But was same exact result.

To best help, you should tell us the actual paths you had in there.  I presume those are "example paths" and I'm surprised it let you [attempt to] launch the game using that relative path. It should have said [something like] "ROM file not found". 

Assuming the absolute path is E:\Emulators\emu\game.int, the relative path should be ..\Emulators\emu\game.int  (also assuming LaunchBox is in E:\LaunchBox\)

Can you share screenshots your version of the 3 I show above?