It is insane because IBM wanted a wireless keyboard. If you're not familiar with the PCjr keyboard, it has two IR transmitters (they are electrically the same, just having two gives you a better transmission path). The PCjr system has an IR receiver.
Now, a normal keyboard cable is a standard two-wire serial protocol with clock and data. Being wireless, you have no clock, so you have to synchronize clocks, or have clock recovery built into the protocol. The PCjr does the former, using the 8253 timer chip.
The keyboard has no way of knowing if the system has received a keystroke, so the system must receive every keystroke - they can't be stored in a fifo, they can't be resent if the CPU missed it.
This rules out the possibility of using system interrupts - so when you type a key on the CPU and the IR receiver gets the start bit - the NMI line is raised, the 8253 is programmed to time the clock bursts from the IR receiver, and the CPU reads out every bit of the scancode.
The PCjr also famously has no DMA, so things like floppy drive transfers are both extremely slow and somewhat unreliable - the IBM floppy controller is somewhat additionally weird is that they disable interrupts as well. The only way the PCjr knows what the controller is doing is by polling its status register, and there is enough ambiguity that it sets a 555 timer that will reset the FDC and start everything over if things time out.
The combination of these two decisions means its inadvisable to type while your floppy drive is transferring data
One of the amazing things about this project is that the author built physical harnesses for real early CPUs so that he could build test suites against the real hardware and ensure the emulation is 100% correct, down to every timing and quirk of the original hardware.
To add on top this, the author wrote multiple blog posts on their setup [0, 1, 2]. The project itself is hosted at https://github.com/dbalsom/arduinoX86
besides the fact that it was written in rust, rust happens to be a really nice language to write emulators, you don't have to think much about threading and not much abut memory management, rust makes that easy => you can concentrate on your pixels. Moreover LLM grasp it very well so that you can get a bit more spare time for your emulator-side-project.
It was very long since I wrote any sort of C++ and using rust was pretty refreshing.
Second "besides": marty's PC may not have a lot of breadth in terms of supported hardware, but it gets the accuracy totally right. It's a very special kind of achievement.
(I'm not a rust fanboy :-) I just appreciate the language for writing my emulator)
For not well off geeks you could just solder a bunch of resistors together and get vastly better sound than from the crappy PC speaker and there were games that supported it and I wrote some software for it (which unfortunately is gone I think). I had a lot of just having this on the pc in the house.
"Not long after its introduction, Creative Labs introduced its competing Sound Blaster card. The Sound Blaster was fully compatible with AdLib's hardware, and it also implemented two key features absent from the AdLib: a PCM audio channel and a game port. With additional features and better marketing, the Sound Blaster quickly overshadowed AdLib as the de facto standard in PC gaming audio. AdLib's slow response, the AdLib Gold, did not sell well enough to sustain the company."
Key is Scancode 0x2B, or as a VKEY code: VK_OEM_5 (0xDC)
Javascript says the key I pressed was keycode 220 (same number as 0xDC) or key "\".
I had Tandy 1000 as the selected machine. When I look at the onscreen keyboard, I don't see a backslash key underneath backspace, but I do see one next to left shift. For keyboards that have the alternate backslash there, it is listed as having a scancode of 0x56 and a VKEY code of VK_OEM_102 (0xE2). (I haven't actually checked information specific to the actual Tandy keyboard)
Not just the OSD keyboard, my real backslash key is also pressing backspace. You can't do your classic DOS commands like "cd\" without a working backspace key.
they're planned at some point. I need to write a utility or custom controller rig with a pico that can step the head on an MFM drive in patterns i can record, then model stepping to cylinder in the hard disk controller.
This comment is itself a meta comment but here we go I guess...How is it possible that half the comments in this thread are about the title itself? It’s not even a made-up title, it’s taken straight from the project’s README...I keep seeing people complaining almost aggressively that others are touting Rust as a useful tool (which, to me personally, it certainly is). Does someone have a financial stake in opposing Rust’s development, or what?
When I started writing MartyPC over four years ago, writing an emulator in Rust was still somewhat novel. The development of the 'egui' immediate-mode graphics framework made it possible to make one with an advanced interactive debugger.
By mentioning Rust people have been able to more easily find MartyPC as an example of how (or how not to) write an emulator in Rust.
Perhaps the tag as outlived its usefulness, especially if people find it pompous or something. I'm not trying to be Rust cultist, I swear.
Rust's user community is toxic and unbearable. That's enough to explain the widespread resentment against it. Their fanboys are annoying. CommonLisp used to have a similar community problem.
Yeah, I love Rust as a language but I engage with the community as little as possible. They are not pleasant to be around. Language is dope though, I really enjoy it.
I write Rust code. I don’t mind it. But the truth is, I use very little of the language.
I visit the Discord, and I see all the crazy overcomplicated shit these people are writing.
If I had to try and make heads or tails of some of that shit I’d go crazy.
I actually think some of it is actual trolling by Rust itself.
And yes, the people are toxic. It’s like they really believe C and C++ and everyone else did literally everything wrong. And some of their justifications are seriously weak sauce.
And remember, I like Rust. At least the parts I use. But it’s easily going to eclipse C++ in complexity if it continues the way it has been operating.
Yup, definitely the Rust users who are toxic. Totally not the people going into every thread about Rust to tell everyone about how toxic Rust users are. Nope.
I believe a true engineer should love problems not only languages. But it seems like majority of Rust devs only love the language and try to convert all the problems into Rust problems.
If you have problems in C/C++? Write Rust.
If you have problems in Python? Use Rust.
If you have an issue with your product? Rewrite it in Rust.
Is your company in pinch? Launch a new product in Rust.
If you burn your finger while you’re cooking? Write Rust.
If you have a mental problem? Read a Rust book.
You don’t have a girl friend? You have Rust next to you.
If you hate yourself? Writing Rust will solve your life problems.
its just ppl trying to be different from their boring parents. wish i had enough karma to flag them too but i keep getting downvoted into oblivion for making fun of written in rust posts
I am not the OP of this post, but they're just using my github description. when I first wrote it, Rust was a novel choice for an emulator, and it helped people find examples of emulators written in Rust.
believe it or not I didn't tailor it for the HN meta
"cross-platform" and Rust, as advertised in the current title/link label, is incompatible for sure. Can't get that to run on my older OS X machine nor my Amiga. :)
Yep, before UNIX and C there were no systems programming languages, and after getting the clay tablets from UNIX and C, all civilisation was built upon them. /s
At least when you spend long time around some programming circles.
It is insane because IBM wanted a wireless keyboard. If you're not familiar with the PCjr keyboard, it has two IR transmitters (they are electrically the same, just having two gives you a better transmission path). The PCjr system has an IR receiver.
Now, a normal keyboard cable is a standard two-wire serial protocol with clock and data. Being wireless, you have no clock, so you have to synchronize clocks, or have clock recovery built into the protocol. The PCjr does the former, using the 8253 timer chip.
The keyboard has no way of knowing if the system has received a keystroke, so the system must receive every keystroke - they can't be stored in a fifo, they can't be resent if the CPU missed it.
This rules out the possibility of using system interrupts - so when you type a key on the CPU and the IR receiver gets the start bit - the NMI line is raised, the 8253 is programmed to time the clock bursts from the IR receiver, and the CPU reads out every bit of the scancode.
In software.
The combination of these two decisions means its inadvisable to type while your floppy drive is transferring data
But honestly I wanted to learn the Rust programming language and I thought writing an emulator was a good a project to learn as any.
I have been working on a emulator in C++ in collaboration with a friend, it is also cycle-accurate. It is called XTCE-Blue.
[0]: https://martypc.blogspot.com/2023/06/hardware-validating-emu...
[1]: https://martypc.blogspot.com/2023/05/exploring-dma-on-ibm-pc...
[2]: https://martypc.blogspot.com/2023/10/bus-sniffing-ibm-5150.h...
It was very long since I wrote any sort of C++ and using rust was pretty refreshing.
Second "besides": marty's PC may not have a lot of breadth in terms of supported hardware, but it gets the accuracy totally right. It's a very special kind of achievement.
(I'm not a rust fanboy :-) I just appreciate the language for writing my emulator)
https://github.com/necroware/silly-sound-bastard
From Wikipedia,
"Not long after its introduction, Creative Labs introduced its competing Sound Blaster card. The Sound Blaster was fully compatible with AdLib's hardware, and it also implemented two key features absent from the AdLib: a PCM audio channel and a game port. With additional features and better marketing, the Sound Blaster quickly overshadowed AdLib as the de facto standard in PC gaming audio. AdLib's slow response, the AdLib Gold, did not sell well enough to sustain the company."
Are you using DVORAK? If you are willing to help, please open a Github issue with some info about your keyboard, and I'll build support for it.
/s
[1] Physical location of a key https://w3c.github.io/uievents/#keys-codevalues
[2] Mapping of a key https://w3c.github.io/uievents/#keys-keyvalues
The naming is terrible and I have to look it up every single time
Javascript says the key I pressed was keycode 220 (same number as 0xDC) or key "\".
I had Tandy 1000 as the selected machine. When I look at the onscreen keyboard, I don't see a backslash key underneath backspace, but I do see one next to left shift. For keyboards that have the alternate backslash there, it is listed as having a scancode of 0x56 and a VKEY code of VK_OEM_102 (0xE2). (I haven't actually checked information specific to the actual Tandy keyboard)
I have to make all new pixel-art for a Tandy 1000 keyboard and PCjr keyboard. Fun
I was trying to Run Back To The Future, so I figured I'd call my emulator either Marty or McFly.
Unfortunately I found out about the FM Towns later, so I renamed it from Marty to MartyPC so you could google "MartyPC Emulator" properly.
By mentioning Rust people have been able to more easily find MartyPC as an example of how (or how not to) write an emulator in Rust.
Perhaps the tag as outlived its usefulness, especially if people find it pompous or something. I'm not trying to be Rust cultist, I swear.
I’m amused by the implication of human bots.
What?
I visit the Discord, and I see all the crazy overcomplicated shit these people are writing.
If I had to try and make heads or tails of some of that shit I’d go crazy.
I actually think some of it is actual trolling by Rust itself.
And yes, the people are toxic. It’s like they really believe C and C++ and everyone else did literally everything wrong. And some of their justifications are seriously weak sauce.
And remember, I like Rust. At least the parts I use. But it’s easily going to eclipse C++ in complexity if it continues the way it has been operating.
but I see your point.
If you have problems in C/C++? Write Rust.
If you have problems in Python? Use Rust.
If you have an issue with your product? Rewrite it in Rust.
Is your company in pinch? Launch a new product in Rust.
If you burn your finger while you’re cooking? Write Rust.
If you have a mental problem? Read a Rust book.
You don’t have a girl friend? You have Rust next to you.
If you hate yourself? Writing Rust will solve your life problems.
believe it or not I didn't tailor it for the HN meta
(To clarify: I like Rust. I use it every day. But this is going too far.)
There was a time for CoffeeScript, PureScript, Elm, Ruby and whatever else you can think of.
Naturally Lisp has to have monthly entries.
/s
I've heard the comments here loud and clear :) You all don't think Rust is novel anymore and I should lose that bit.
At least when you spend long time around some programming circles.