- --
Viewing Issue Advanced Details
| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 09479 | Media Support | Major | Always | 7 hours ago | 7 hours ago |
| Tester | Robbbert | View Status | Public | Platform | MAME (Self-compiled) |
| Assigned To | Resolution | Open | OS | Windows (x64) | |
| Status [?] | New | Driver | |||
| Version | 0.288 | Fixed in Version | Build | x64 | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary |
|
||||
| Description |
This system is marked as working. According to the manual, the system waits for a boot disk and will then boot without requiring further intervention. There's no software list, so I tried my only LB186 disk and it didn't boot. The system is also supposed to be able to use standard IBMPC boot disks, so I tried a number of them, without luck. |
||||
| Steps To Reproduce |
>mame lb186 -flop1 e:\data\pc\ok\freedos360k_1_20061014.img Cursor flashes faster but nothing else happens. In the debugger, nothing is loaded into memory, and code execution stays in the BIOS. Tried a bunch of pc disks, MAME rejected most of them, however 360k ones were accepted, but none did anything. |
||||
| Additional Information |
Tested in 0.277, the system works there, able to boot one disk "freedos360k_1_20061014.img". Seems quite picky; other disks that work in pc's get the "Non-system disk or disk error" response instead. In 0.288, there's no messages, doesn't seem to read the disk at all. |
||||
| Github Commit | |||||
| Flags | Regression | ||||
| Regression Version | |||||
| Affected Sets / Systems | lb186 | ||||
|
Attached Files
|
|||||
Relationships
| There are no relationship linked to this issue. |
Notes
0
| There are no notes attached to this issue. |