Math and electrical desgin

Analytical? I wouldn't know how to do that.

But more registers, and especially serious protections (that people actually use!) and better attention to security would have been nice.

On a PDP-11 with memory protection enabled, you couldn't execute data. A stack couldn't overflow in code space, or into any space. You couldn't write into code space.

Of course, the way people designed c didn't help a bit.

Viruses should be flat impossible. Some day they will be, but not on x86 or Windows.

snipped-for-privacy@eu.eu wrote in news:5e831d67$0$15173$ snipped-for-privacy@news.free.fr:

You're an idiot. He didn't kill any of them.

You and yours should be erased from the human gene pool.

snipped-for-privacy@eu.eu wrote in news:5e831d67$0$15173$ snipped-for-privacy@news.free.fr:

They were not even around then, idiot.

Really? I'm not dead, so I do not see how that is possible.

Show me one.

snipped-for-privacy@eu.eu wrote in news:5e831d67$0$15173$ snipped-for-privacy@news.free.fr:

PUAD

Puss Up And Die.

Oh tell us then what he did with snakes in a garbage cans? I'm curious.

Said the man when at the time kid, has learned to count snakes into a garbage cans ... I've nothing to learn from that kind of "man"

You're probably that kind of "deep-south" indigene, You a amoeba from the Bayou Numero Uno :-D

snipped-for-privacy@eu.eu wrote in news:5e8379ab$0$5886$ snipped-for-privacy@news.free.fr:

There was a woods behind our house. There were lots of things to collect. Walnuts, salamanders, crayfish, blacksnakes, snapping turtles... lots of things.

The walnuts went on the back porch to dry out.

The salamanders and crayfish were let go after examining them for a bit. The snakes got released, but not until after he sent me through the front door with one wrapped around my waist as a belt.

The snapping turtle became soup.

You need to learn some english grammar and composition. Not hard to count live brains cells into a your skull cavity. No more than two would fit inside that thick bone, boy.

It is not that you have nothing to learn. It is that learning is something out of your reach. You are ineducable.

S*it has a tendency to be that way, and you certainly are that.

English, you senile, drunken dumbfuck.

Better yet, have another bottle and...

PUAD

Puss Up And DIE.

Really impressive, bon appetit!

Yeah may be but yours is not so brilliant, I repeat my English is just perfect for you Decadent Numero Uno :-D

I'm a boy as you said, not a senile as you, laying in a wheelchair haunting the Usenet, where do you come from for eating those weird things? ... for sure you experienced eating Pangolins and other Civettes, Pffkr ! So decadent indeed ! :-D

BTW don't see any valuable contribution on electronics from you these months. You're a s***ty Numero Uno ! :-(

snipped-for-privacy@eu.eu wrote in news:5e838ec3$0$15201$ snipped-for-privacy@news.free.fr:

I am certain you do not examine my posts.

PUAD.

The main problem was the segmented memory model and the lack of 32 bit (or even 24 bit) (address) registers,

The segmented approach is quite OK if you have a RTOS mindset with multiple smallish independent tasks communicating with each other. The segmentation would allow also some memory protection between tasks and also within task code/datas/stack.

Unfortunately Intel published their RMX/86 RTOS as late as 1980, By that time many companies using x86 had already made their own incompatible RTOS kernels.

The problem with PDP-11 was the 64 KiB program address space. Not a problem if you had the RTOS mentality designing multiple small tasks living somewhere in the 256 KiB or 4 MiB physical address space.

Trying to shoehorn a large program into 64 KiB program address space was a mess, requiring overload loading etc.

There was a virtual Fortran implementation that allowed mapping one 8 KiB window to any part of the physical memory (256 KiB or 4 MiB) to access the big virtual Fortran array in physical memory,

Of course, this was as messy as switching segment registers on x86 in order to access different elements in a large physical memory array.

Later x86 models have some protection bits in the segment registers. If the OSes would have kept the segments sufficiently separate (at least 64 KiB between start of segments, one could not have overwritten wrong areas. Only in current processors are protection bits added to virtual memory page tables.

As OS/2 did. Microsoft simply refused to acknowledge that there is a right time to break some old badly-behaved programs to improve the security of every new program going forward. Unbelievable to me, but it was entirely deliberate.

CH

it's in the block of unicode called "Green and Coptic", but yeah also in that (and other) 8-bit "Greek" code pages.

Good grief, if you get confused by a capacitor labeled 22uf, you need a new job.

I learned at the age of 7-10 years which things to ignore. For example, that statements such as "no serviceable parts inside" and "bicycling prohibited" ought to be ignored :-)

Am 03.04.20 um 21:20 schrieb Joerg:

And "NO EXIT" means you can get out there.

cheers, Gerhard

I did that yesterday on the mountain bike, mud flinging off the tires and all. Milliseconds later I saw a sheriff's SUV but luckily its flashing lights didn't come on.

Datasheet abs max ratings are just suggestions.

Look, all I'm sayin' is that Boston women are, on the whole, a paler, uglier sort than women from the elsewheres of life.

You're getting in touch with your inner Woody Guthrie!

"As I was walking, I saw a sign there It was painted, "Priv't prop'ty But on the back side it didn't say nothing; This land was made for you and me."

You live in California, so I suppose it was inevitable. ;)

Cheers

Phil Hobbs

I live in the part of California where people wear the law on their belts :-)

No kidding, yesterday on my mountain bike I saw three people trotting down a highway on horseback.