- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
04859 | Misc. | Minor | Always | May 23, 2012, 02:14 | May 25, 2012, 17:33 |
Tester | Robert Gault | View Status | Public | Platform | MESS (Official Binary) |
Assigned To | micko | Resolution | Fixed | OS | Windows XP |
Status [?] | Resolved | Driver | |||
Version | 0.146 | Fixed in Version | Build | Normal | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 04859: coco, coco3h: System crash regarding -ramsize and internal UI | ||||
Description |
Using the example of coco emulation, there are errors and crashes when using varying -ramsize values and using the internal menu to select a new computer to use on the fly. Using the example below, you get this message: RAM device ':ram': Cannot recognize the RAM option 4k (valid options are 512K ,128K,2M,8M). |
||||
Steps To Reproduce |
- Ensure you have no .ini or .cfg for coco or coco3h. - mess coco -ramsize 4k - Scroll lock to gain keyboard control - TAB - Choose "Select New System" - Select set "coco3h" Crash |
||||
Additional Information | If you run each system with default settings, no crash occurs (without any .ini ot .cfg files). | ||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | coco, coco3h | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
1
No.08632
Tafoid Administrator
May 23, 2012, 03:01
|
This may not just be limited to the Color Computer. It appears to be a greater issue where wither .ini contents or command-line parameters are being used and not reset per-system when a new one is selected via the in-game menu. There are no problems when stopping MESS after the first system and restarting MESS with the other system. |
---|