-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clock speed setup by keyboard doesn't work #18
Comments
What platform are you using? |
micro_8088 edit: bios 1.0 no-ide |
That's most certainly should work on Micro 8088. I don't believe that code changed lately.
|
I suspected it, so I already did that test before to open the issue, trying to modify the speed from the dos prompt. It doesn't change. I tried many times, i.e. boot (BIOS says 9.45 MHz) -> prompt ms-dos -> press Ctrl/Alt/- -> speed.com -> nothing changes. Just a question: should this function modify the BIOS value too? Because I did that test too, booting and then trying to modify the speed from dos prompt, by keyboard, and then reboot. No changes at all. I also suspected the keyboard, so I tried with another one, different model. Nope. |
I tested it and it works for me. |
It was OFF, but I tried to put it to ON, no changes. Just to be sure, I downloaded the same tool you're using, systest, and tried both switch modes. The single keys off the keyboard (ctrl, alt, keypad +, - , *) are working. BTW I believe it doesn't do any difference, but today I discovered I did a mistake while mounting the backplane, I put all caps 10 uF, but I've seen the C20 is 1 uF. If you think it could make any difference, I'm assembling a 2nd micro_8088, this time with the right cap. It will take a day or two yet... |
Hi,
not a big issue, but...
the Ctrl-Alt-Keypad -/+/* sequence doesn't work (at least for me). I checked the speed with the speed.com program and there is no difference at all.
Just to be sure, I tried to modify the clock speed by the Bios, and the speed.com routine correctly shows the different frequency.
The text was updated successfully, but these errors were encountered: