| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 05549 | Core | Minor | Always | Apr 26, 2014, 13:00 | Apr 26, 2014, 17:01 |
| Tester | Robert Gault | View Status | Public | Platform | MESS (Self-compiled) |
| Assigned To | Resolution | Invalid report | OS | Windows XP | |
| Status [?] | Closed | Driver | |||
| Version | N/A | Fixed in Version | Build | Normal | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary |
 05549: Misleading error reports depending on starting method |
||||
| Description |
You can start emulation by two methods. 1) Start MESS and select an emulation. 2) Use a command line mess emulation. The error reports are not the same. Here is a specific error which will be reported separately. With revision 30011 coco, cocoe, coco2, and coco2b emulation are not starting. The error report given when starting MESS and then selecting one of these is "a ROM is missing" which should mean a .rom file in the roms directory. The error report given with a command line is: C:\mingw\mess>mess coco2 mc6847 NOT FOUND (tried in coco2 coco mc6847_ntsc) FATALERROR: Required files are missing, the system cannot be run. The second report is correct while the first is completely incorrect and misleading. |
||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | |||||
|
Attached Files
|
|||||
 No.10630
Tafoid Administrator
Apr 26, 2014, 17:00
|
Another SVN report. In both cases, it tells you that a rom is missing or not found. This is not an issue. ROMsets are typically made up of several files inside a folder (or zip) which makes up the complete ROM. Is something is missing, you must find the file and correct your romset. This again is not a bug. Closing |
|---|