GloriousCow

26 ms·

1.
by GloriousCow 24d ago
Thanks. This should be fixed for Tandy 1000 now. On PCjr there is no backslash key, you have to type a backspace using alt + /, so I will need to define a macro that does that for you. The Tandy 1000 will need its own OSD since the ta
2.
by GloriousCow 24d ago
feel free to fork MartyPC to build it for your Amiga
3.
by GloriousCow 24d ago
yes, swipe up to show a keyboard. this currently only supports the 5150/5160 completely as it is a Model F keyboard and the Tandy/Jr have some differences.
4.
by GloriousCow 24d ago
I need to know what keyboard layout you're using. If it is not a standard US keyboard it will need a mapping
5.
by GloriousCow 24d ago
DOS has the 'keyb' utility and 'keyboard.sys' to support different layouts, using various code pages. If you have a CGA card, you're stuck with the code page of the ROM your card came with, which in most cases was c
6.
by GloriousCow 24d ago
great emulator and nice guy too. maybe i should ask him if i can use his HDD sounds
7.
by GloriousCow 24d ago
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.
8.
by GloriousCow 24d ago
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 P
9.
by GloriousCow 24d ago
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'
10.
by GloriousCow 24d ago
It is indeed a Marty McFly reference. The original demo I was trying to run was called 8088 MPH and is full of Back to the Future references. I was trying to Run Back To The Future, so I figured I'd call my emulator either Marty or Mc
11.
by GloriousCow 24d ago
Yeah the OSD is only the Model F and the Tandy has some difference so the OSD keyboard may not work quite right with the Tandy. I have to make all new pixel-art for a Tandy 1000 keyboard and PCjr keyboard. Fun
12.
by GloriousCow 24d ago
I am very close to emulating the Covox - I emulate the Disney Sound Source, which is just a Covox with a FIFO
13.
by GloriousCow 24d ago
People will generally get angry no matter what you do. People are also angry it is MIT licensed. 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 bee
14.
by GloriousCow 24d ago
easy - the PCjr keyboard interface. 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 tran
15.
by GloriousCow 25d ago
What would you say is missing or not working well?
16.
by GloriousCow 25d ago
Hi, thanks for checking out MartyPC. I'm the developer if there are any questions.
17.
by GloriousCow 25d ago
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 d
18.
by GloriousCow 25d ago
When I started this emulator four years ago, this was the first PC emulator written in Rust so it was novel. I've heard the comments here loud and clear :) You all don't think Rust is novel anymore and I should lose that bit.
19.
by GloriousCow 25d ago
What keyboard layout are you using? I can't reproduce on a US layout.
20.
by GloriousCow 25d ago
I've built out a full keyboard-remapping system, to support any keyboard layout. I need help building these files. Are you using DVORAK? If you are willing to help, please open a Github issue with some info about your keyboard, and I&#
21.
by GloriousCow 25d ago
I haven't implemented the Soundblaster card yet, although it's quite high on my list of things to do.
22.
by GloriousCow 1mo ago
Thanks for checking this out. I've uploaded all the binaries to GitHub if you're struggling with copy & paste. There's also a new example in Braille. https://github.com/dbalsom/executable_unicode
23.
by GloriousCow 1mo ago
For the 'hello' program, you need to use DosBox-X with the 'cpu cputype=8086' parameter. You can use 86Box or MartyPC as well but those take more effort to set up and get the executable onto them.
24.
by GloriousCow 1mo ago
Try copying from the links provided after each emoji block. That goes to my disassembler which should independently verify the md5. I think blogpspot unfortunately mucks with the emoji.
25.
by GloriousCow 1mo ago
having the emojis survive copy & paste from a browser is surprisingly frustrating. I would have expected there to be well-defined semantics for this, but a lot of things insert variation selectors (U+FE0F) after certain emoji which bre
26.
by GloriousCow 4mo ago
The actual output of microcode disassembly is just a text file - a line of code for each microcode word, in essentially a a new dialect - a type of static assembly language. reenigne had to invent names for a lot of things, that will now be
27.
by GloriousCow 4mo ago
We also had decoded the 386's match-decoder PLA, so we knew roughly the locations of different opcodes were in the microcode itself, which was very helpful. Some opcodes have very specific operands, so would have unique field reference
28.
by GloriousCow 4mo ago
Intel had given us some clues - they had written somewhere that the 386 had 2560 microcode words. The microcode array has 37 banks - each bank resolves one bit from the 37 bits that comprise a microcode word. But which way to decode them?
29.
by GloriousCow 4mo ago
I worked a bit on the extraction process so I can chime in here a bit. The first part is to just mark the x,y locations of where all the bits are, generally by the intersection of the rows and columns of the microcode array. Then you have t
30.
by GloriousCow 4mo ago
nand2mario has made a Verilog implementation from it. It currently runs DOOM, but some of the more fiddly protected-mode bits prevent it from running full operating systems (besides DOS). I'm sure the bugs will get ironed out eventuall

More ›