|
|
If I'd wanted to make a very bad joke, I would have asked how is life in a wheelchair, but this is too cynical.
|
|
|
|
|
My fiber is "only" 100 Mbps - I could have it upgraded, but I very rarely come across any server capable of utilizing the full full capacity. Most servers won't give me more than 50-70 Mbps, some are significantly below that.
How often do I have 15-20 simultaneous transfers running, each using 50-70 Mbps? Very rarely. Sometimes I have 4 or 5 transfers, filling up the pipe completely, but I never have an immediate need for all those streams; they are typically videos that I will watch later. If the transfer completes one minute later due to limited fiber capacity, it is perfectly fine with me. I do have friends who laugh: Mine is thicker than yours! - but that is all they get out of it. Their real "need" is perfectly well served at lower speeds. So I have never considered the upgrade to 1 Gbps worth the money. Mine is big enough - it is how you use it that counts.
|
|
|
|
|
I need to do some very low-level coding in assembler. I used to do a lot of this, but just need a bit of a refresher in syntax. Does anyone have a decent link for this?
I've been searching, and I can find the opcodes/symbols, but without the syntax. For example, what exactly is the LES format entered?
Even the Intel site doesn't seem to cover these "ancient technologies" anymore... 
|
|
|
|
|
|
|
That is awesome. Even though I haven't done assembly language programming since I had to write an OS/2 device driver a lot of years ago, that's a cool thing to have. Thanks!
Software Zen: delete this;
|
|
|
|
|
Oh, that's a keeper!
I wish I'd kept all my old (hard copy) reference manuals, but this'll do for starters!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I'm not sure how relevant the intrinsics are these days, but this documents them if you use them.
Intel® Intrinsics Guide[^]
Explorans limites defectum
|
|
|
|
|
Thanks! I had no idea I would ever need this again. In the 80's I had the appropriate manuals in hard copy, but that was a couple of lifetimes ago.
|
|
|
|
|
I still have a book on x86 assembly coding under DOS (so it covers the DOS ABI and Tandi graphics as well as assembly itself). This thing is so thick, I'm using it as a monitor stand.
|
|
|
|
|
Member 9167057 wrote: I'm using it as a monitor stand.
Still part of the foundation of computing!
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
|
You piqued my curiosity -- what are you doing that requires 8086 assembler?
|
|
|
|
|
Same here, I'm curious too now.
|
|
|
|
|
I am working on a legacy DOS app that I hope to modernize into a Windows app, but it will be in a series of stages. In this stage, I need to write a TSR (Terminate and Stay Resident) COM application to monitor some of the activity going on in the app.
I wrote similar TSR DOS apps in the mid-80's, but it has been a very long time. It took some special effort to get a DOS .COM app to compile at all with VS 2019 - no MASM (done under C++), and the Linker doesn't get some of the options that used to be available...
|
|
|
|
|
I figured the need had to be some type of legacy application or hardware. Good luck with the effort!
BTW, a friend's organization has some specialized hardware that runs only on a 286. They have had the same PC in production since ~1990. I have no idea what they will do when the PC finally fails.
|
|
|
|
|
That's the exact same problem the users of this application have - their old hardware (for DOS) is failing. That includes printers that handle straight ASCII output.
If your friend is interested, I might be able to provide some guidance or assistance on this...
|
|
|
|
|
Andreas Mertens wrote: If your friend is interested, I might be able to provide some guidance or assistance on this...
Thanks for the offer, but my friend is not responsible for the situation nor directly involved. The responsible folks are utilizing the time-old method "lots of praying" in lieu of replacing the hardware. When it eventually fails they will be forced to buy a new solution.
I suspect they are ignoring that corollary to Murphy's Law that states, "hardware failure will occur at exactly the worst possible moment".
|
|
|
|
|
Wow, is this a paid gig? Who is still using 8086 chipsets?
|
|
|
|
|
Essentially, all of us. It's still the common denominator if you don't want to make any assumptions on which platform your code is going to run.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I think it's reasonable to assume there will be at least a Pentium-compatible processor these days since it's more than twenty-five years old now.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I never was a fan of Intel, but are there not compatible microcontrollers?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I am not sure. The main ones Intel had/have were not compatible like the 8048 and 8051. I have not followed microcontrollers for a while now.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Tern still makes embedded controllers running 186 to 486 compatible chips. so there's still manufactures building with those chips. I worked with one of their 286 boards a couple years back, it was a lot of fun writing SPI and 2-wire code to communicate with the various other chips on the board.
Haven't touched assembly in years, for now c, is good enough in what i'm doing.
|
|
|
|
|
Yes, but 8086 is specifically 16 bit.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
