MESS Troubleshooting

From Ninerpedia
Revision as of 14:59, 14 September 2017 by Stephen Shaw (talk | contribs) (→‎Screen is black: add links to snug article)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

On startup

Error message concerning shared object file (Linux)

Q: When trying to start mess I'm getting an error message "error while loading shared libraries: cannot open shared object file: No such file or directory".

A: You must install SDL support, in this case the TTF library is missing. Check your software installation and add the required libraries.

Screen is black

Q: The system does not start. The screen remains black.

A1 (GRAMKracker): You have activated the GRAMKracker support, you have set the GK DIP switches to point to GRAM 0 (instead of OpSys), and you have not inserted the GRAMKracker cartridge, or the cartridge is empty. Please read the GK manual.

A2 (HSGPL): You switched on the HSGPL without previously uploading an operating system to the HSGPL. As the HSGPL is always active for the SGCPU, you will encounter the same problem there.

The HSGPL is a buffered memory card which replaces the console's ROM and GROM content. When you turn it on, MESS automatically unplugs all memory in the console until you turn off the card again. When you buy an HSGPL card you get a preloaded system. To achieve this in MESS, you have to set the HSGPL configuration switch to "Flash". This allows access to the card but prevents it from taking control. Now you can use a tool like DSRLDR to flash the (emulated) ROMs on the card using a ROM package. When done, you must copy the desired operating system version from the backup positions in the card to the location expected by the system (ROM and GROM). I have written a simple tool to perform this step. Finally, put the switch to the "on" position and reset the emulator.

The HSGPL was sold by the System 99'er User Group (SNUG), so you should ask them to provide you with a suitable ROM package.

Strange error message on startup

Q: Emulator refuses to start, outputs "Could not load controller file 猀慮癰敩w%d x %d.cfg"

A: You have attempted to start an emulation using MESSUI (version 0.142 and higher). There is a bug in MESSUI which causes a corrupted line to be inserted in the configuration file. As it seems this happens when you set the properties in the context menu of the system. To fix this problem, load the configuration file (systemName.ini or mess.ini) into an editor, search for a line starting with "ctrlr" in the configuration files (systemName.ini and mess.ini), remove this line, and save the file again.

There is currently no work-around except to avoid setting properties in MESSUI. It is recommended to use another front-end instead of MESSUI.

Error loading multicart: no pcb found

Q: I'm getting this message on startup.

A: You seem to have attempted to mount a cartridge using the (long obsoleted) "bin" format. Please use only RPK packages as cartridges. You can find almost all known cartridges on the FTP server of whtech.

During runtime

Plugging in a cartridge

Q: When I plug in a cartridge at runtime, the emulator resets, and then no cartridge is shown.

A: MESS 0.140 saves the currently mounted media to a system-specific ini file. You need to set writeconfig to 1 in mess.ini. Note that all inserted media will be automounted on subsequent starts.

New releases of MESS may require to recreate the ini file; this is possible with the command line switch -createconfig.

RS232/PIO output hangs

Q: When I try to output a file through RS232 or PIO, the computer seems to hang.

A: You have probably forgotten to "insert" an image into the RS232 or PIO device. Check the file manager and define an output file (similar to inserting a disk image into a drive). When printing to PIO or RS232, the contents are appended to the image file.