Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07753 Crash/Freeze Minor Have not tried Sep 17, 2020, 16:46 Sep 18, 2020, 15:01
Tester robnielsen View Status Public Platform MAME (Official Binary)
Assigned To Resolution Invalid report OS Windows 10 (64-bit)
Status [?] Closed Driver
Version 0.224 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary MESS-specific 07753: sun4_60, sun4_65: Unable to boot from cdrom with sun4_60, sun4_65, and other sets
Description When trying to boot from cdrom there are various error messages displayed and ends with SHELL: See the attached image. I get the same error when I tried to use the sun4_65 and other sets.
Steps To Reproduce I followed the instructions at:, and when I ran it with the command:

mame64.exe sun4_60 -window -slot1 "bwtwo" "-scsibus:0" harddisk "-scsibus:1" "" "-scsibus:6" cdrom -hard sunos412.chd -cdrom SunOS_412.iso

The following is output:

m_cache_tag_shift 2
m_page_mask 000003ff
m_seg_entry_shift 0000000a
m_seg_entry_mask 0000003f
m_page_entry_mask 0000ffff
m_cache_mask 00003fff
Context Reg Test
Sizing Memory
Mapping ROM
Setting up RAM for monitor.

Setting up memory used in decompress.

Decompressing code to RAM ...
Remapping monitor's virtual addresses to RAM.
Starting real time clock...
Incorrect configuration checksum;
Setting NVRAM parameters to default values.
Setting diag-switch? NVRAM parameter to true
Probing /sbus@1,f8000000 at 0,0 dma esp sd st le
Probing /sbus@1,f8000000 at 1,0 bwtwo
Probing /sbus@1,f8000000 at 2,0 Nothing there
Probing /sbus@1,f8000000 at 3,0 Nothing there
Average speed: 62.40% (46 seconds)
Additional Information
Github Commit
Regression Version
Affected Sets / Systems sun4_60, sun4_65
Attached Files
jpg file icon Capture.JPG (240,997 bytes) Sep 17, 2020, 16:46 Uploaded by robnielsen
There are no relationship linked to this issue.
User avatar
Senior Tester
Sep 18, 2020, 12:11
These machines are marked as NOT WORKING.

sun4_60 doesn't even have a screen by default.
User avatar
Sep 18, 2020, 15:01

This machine (and in fact all the SUN machine drivers) are not at state where anything can be guaranteed to work in all instances. This is the reason they are flagged as MACHINE_NOT_WORKING in driver and you should get a message on a RED screen when you start up your emulation attempt stating this.

As a policy set down long ago from MAME's Developers that in most instances such flagged machines are not subject to accepting bug reports - this is the case here. I would contact the people who made the claims of things working and see if there is a previous version they can name/attest to booting and use that.