until you forget about the scalar.
).
. It was in the 90's. COM1 was usually ISA port 2F8 on IBM PC but Windows was protected mode, passing everything through its wannabe 32-bit kernel subsystem with delays and bad data. I hated it because I knew what was coming. Later on my Symbian phone, I noticed it could not contain media or apps in the mail inbox for reasons. I knew it was game over for a phone as personal computer. They still don't support a display and keyboard on metal level.Not to derail this thread, but I’ve done similar stuff with feed trucks (the ones that feed cows) in order to talk to the scale head. I used an incredibly customizable software called BillRedirect. If you want a program to talk to com ports, there is no better. Period.
Bill Production keyboard wedge Softwares (RS-232 to keyboard Converter)
Redirection software that allows you to redirect data between these components: serial port / mouse / TCP Port / virtual keyboard and keyboard buffer. This software is perfect for barcode scanner applications or other serial data capture devices having a standard RS232 serial interface and/or...billproduction.com
Windows obviously, as most software is these days.
We had more registers..Commodore 64
IBM paid Phil Katz a pittance to globally license PKZIP technology which was widely used and saved IBM a fortune in data transmission time and size.
I did that on an Oric
Designed my own character set, wrote a little text editor that had 64 chars/line, it was the most that could be squeezed in. The ROM character set only gave you 40 chars/line. I designed the characters in an old maths exercise book with square rulings. The editor was written in a mix of basic and assembler. And... I had a Brother thermal typewriter, that had a serial port allowing it to be used as a printer. I made a little serial card, just +/- 5V was all that was needed, attached to the oric parallel port (printer port) and then was able to edit on the oric and print off on the brother. That was really a home-made word processor!That's an endoscope, very cool. Yes the card in my thing was only a small part of the whole project, the software was the other 95%. Unfortunately there's nothing much left to show! I wish now I'd taken some photos of the screen or something. But at the time, I never really thought of it. The only thing I've got left now is a few print-outs of satellite images that I managed to keep, and that circuit board.
It's hard to believe they had the nerve to try to get you to sign something like that. Unbelievable.
Ouch, I just got mugged down memory lane. Having to tell the vendor of some $$$HW that they messed up something really creative so their own test codes worked but they did not see that every second cache line would malfunction (write back problems). You see that when you use more address space than the cache can hold.
muforth on a new chip, and then programming the hardware DMA to work with the timer so we don't have to bit-bang the WS2812 LED protocol. that was a pretty cool achievement, but it'll be cooler when we get around to making it work with the full strand of 128 LEDs on the board.categorically false. javascript and json suck hard, and modern day web specifications like oauth2 contain headass language like "on its own, this specification will produce implementations that do not interoperate". i think when you put that into your so-called specification document you have failed at your task and should throw the entire thing out and find another job
Exactly. My best SW memory is a HW engineer telling me "I'll get back to you when we've fixed this"