07395: ibmpcjr: Boot Error B when UI is enabled

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07395	DIP/Input	Minor	Always	Aug 12, 2019, 02:50	Aug 12, 2019, 10:00

Tester	Sterophonick	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	No change required	OS	Windows 10 (64-bit)
Status [?]	Closed			Driver	pc/ibmpcjr.cpp
Version	0.212	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07395: ibmpcjr: Boot Error B when UI is enabled
Description	When you enable the UI (pressing Scroll Lock) before the machine finishes the memory test, the machine will throw error B, indicating a keyboard problem.
Steps To Reproduce	1. Start the machine 2. Before the memory test finishes, press the Scroll Lock key to enable the MAME UI.
Additional Information	Potentially not a big deal, but can potentially get annoying when trying to boot into a floppy.
Github Commit

Flags
Regression Version
Affected Sets / Systems	ibmpcjr

Attached Files	0000.png (1,751 bytes) Aug 12, 2019, 02:50 Uploaded by Sterophonick Screenshot of the Error

No.16738 Tafoid Administrator Aug 12, 2019, 10:00	This is unavoidable on the real machine as well and it detects a "keyboard error" - possible stuck keys or something not right.... if keys are pressed during initial memory check (Thanks Osso for the link): http://www.vcfed.org/forum/archive/index.php/t-7100.html I can suggest 3 ways at least to handle this: - Remap scroll lock to something else uncommon so it isn't likely to be used. It isn't a common use key even for an older system - Start MAME with [b][i]-ui_active[/i][/b] or activate that command before hand in your .ini file so that you start emulation in "partial mode". This isn't going to guarantee you will not get the error, as other keys can also trigger this. - If you are using a certain floppy/disk image, you can provide that in command-line beforehand or even in an .ini so you don't even need to select a floppy to use during machine booting. Sadly, there isn't much we can do about this as the machine is functioning as expected. Closing as No Change Required.

No.16738

Tafoid

Administrator

Aug 12, 2019, 10:00

This is unavoidable on the real machine as well and it detects a "keyboard error" - possible stuck keys or something not right.... if keys are pressed during initial memory check (Thanks Osso for the link): http://www.vcfed.org/forum/archive/index.php/t-7100.html

I can suggest 3 ways at least to handle this:
- Remap scroll lock to something else uncommon so it isn't likely to be used. It isn't a common use key even for an older system
- Start MAME with [b][i]-ui_active[/i][/b] or activate that command before hand in your .ini file so that you start emulation in "partial mode". This isn't going to guarantee you will not get the error, as other keys can also trigger this.
- If you are using a certain floppy/disk image, you can provide that in command-line beforehand or even in an .ini so you don't even need to select a floppy to use during machine booting.

Sadly, there isn't much we can do about this as the machine is functioning as expected.
Closing as No Change Required.