Einstein wrote:
I must mysteriously have used software from a minority of programmers I take it ? that's a good one 
It depends on what software you used. PD can give you a guru, most commercial software I used was fine. Memory protection still doesn't prevent freezes and hangs, screen corruption,they still happen eg nvidia drives with XP/Vista
Memory protection on its own provides no security, but stability. It's when mp is combined with resource access privilege checking that it shuts the door to malware trying to crawl in from the otherwise open memory.
Acknowledged this, but you gotta have it in the first place to prevent ONE form of security risk. There are many other holes in Windows that constantly need to be pluggged. So you still run an insecure system.
Regarding windows security issues, what about linux ?
Linux is said to be more secure but thats probably because its less popular (and not as hated as MS is). It doesn't attract as much malware development, doesn't necessarily mean its more secure, but it might..
Linux is a kernel. There's nothing stopping a linux based OS from providing GUI for any functionality you'd expect.
It's just that unix geeks have traditionally preferred CLI (aka shell) commands with cryptic and often unrelated names/options etc.
Heard that argument a billion times. Thats a cop out. Why? Because it hasn't happened. In 20 years. Linux needs to be assessed on what it is NOW, its had 20 years to mature, not what it COULD BE, if someone gave a rats at some indeterminate point in the future. Theoretically it *might* be possible to have an intuitive GUI for every function that a user might need to use, but NOT ONE DISTRO provides such a system. Tried all the big guns: Ubuntu, Mandriva, Fedora, SUSE, ALL REQUIRE eventually that you get your hands dirty with CLI. You CAN'T escape it. Linux is still a command line OS with GUI tacked on top of it, no matter how its dressed up. On the other hand Workbench and CLI are two sides of the one coin.
The amount of times I needed to set some GUI based tasks priority to -1 just to have a responsive keyboard (and other apps) is uncountable.
Really? What in god's name are you running? I've run ImageFX, and lightwave renders, whilst typing up an essay in Wordworth, and i couldn't out-type Wordworth on a 40 mhz '030. Oh I was IRC'ing at the time so a TCP stack was going as well and had YAM open..
And you want to improve it more? Download Executive for free and customize task scheduling to suit your needs.
fast boot up time.
And faster crash down time.
Blue screens happen at ghz speeds, GURU's at MHZ...
Also some browsers utilize multi-threading badly, or (almost) not at all.
Oh you mean the programmers haven't yet learned how to program their software in a system-friendly way so that they make way for higher-priority system tasks like responding to a command issued by the user to open a Start Menu? Why doesn't the OS over-ride this? Isn't it a PRE-EMPTIVE multi-tasking OS as opposed to a co-operative one? Why does the OS allow an application to take priority over system tasks? Also its OK when programmers program badly on Windows, thats the programers fault, but not when they do it on Amiga, thats AmigaOS's fault?
There's still a lot to like about AmigaOS, and computer OS's haven't come forward nowhere near as much as the hardware they run on. In fact Windows, Mac And Linux OS programmers should be ashamed.
BeOS which implements/-ed memory protection, and even more, QNX, which does that plus security haven't been accused of being unresposive (me exluded, haven't used any of them). So why should the three named mainstream OS learn from Amiga when all it does is next to nothing:
* No user mode/supervisor-mode context switch upon entering exec (exec is a library that is called like a library, but when it absolutely must it triggeres the cpu to enter supervisor mode
* Passing pointers, the IPC simply adds the message nodes to which the pointer points into the massage list (port)
* Scheduler completely discriminates and starves tasks as long as any higher priority one has an appetite for over-consumption
* No virtual memory
* And I must have forgotten (and be nonaware) of tons more.
Like I said, exec is a fancy task-switching utilty API[/quote] :lol:
You know nothing about Exec: its employs true pre-emptive multitasking, and its scheduler will only "starve" tasks if you prioritize something to an extreme: no programmer in his right mind would do it that way, but if you want you can try. And even then the system will still be responsive to the user as system tasks are prioritised highest anyway. Task switching is what you got in Pre-OS X days on Mac, and Win 3.11 days. Since then Windows has had pre-emptive multi-tasking but its not as responsive as AmigaOS Exec, not unless you have a factor of 1000 more ram (thats why Win and Linux NEED Virtual memory, ) and CPU cycles.
And Amiga doesn't have virtual memory because it doesn't NEED it. I've never run out of RAM and the most i had was 128 meg. But if you want it can be done, you could buy
GigaMem to do it...
I stand by my earlier conclusion Windows OS, OS X and Linux OS programmers should be ashamed at the total misuse of hardware resources in creating the worst user-experience versus computing power in the history of computing.
Sorry to bore everyone.