🚀 go-pugleaf

>==========Peter da Silva, 6/19/95==========
>
>In article <mkl.803572041@duesentrieb>,
>Mario Klebsch DG1AM <mkl@rob.cs.tu-bs.de> wrote:
>>And please remember, windows was
>>the first OS, that was able to really handle more RAM than 640
>>KBytes.
>
>Someone else is telling me I hallucinated running Xenix. Damn vivid
>hallucination, if you ask me.
>
>The problem isn't that *application* need more RAM, it's that the basic
>operating system does. Look, AmigaOS runs in 512K. It *supports* up to
>2 gigabytes, but it runs in 512K.
>
>>>There's absolutely nothing in NT to justify the memory
>requirements. The copy
>>>I installed last week listed a 32M *minimum*. And damn, it's a
>frustrating
>>>system to work with... that hourglass gets real boring real fast.

What 32M minimum???!!!  Windows NT 3.5 Workstation requires 12M, and 3.5
Server requires 16M. And are you actually waiting for something when you see
an hourglass? NT is multitasking and multithreading. If you're seeing a lot of
the hourglass, you're using applications that were not written to take
advantage of the multithreading. And no matter what kind of applications
you're using, you should always be able to work in another application while
one is busy. (With 16-bit apps, you have to run them in separate memory spaces
to get them to preemtively multitask.)

>
>>Don't blame them for fixing some bad design decisions. Including the
>>graphic, mouse and the printer driver into windows was a good
>>thing.
>
>AmigaOS does this, too. And supports multiple video modes, so
>you can have
>high quality graphics and NTSC-compatible graphics for video
>production as
>well. In 512K.
>
>>There also has been a large demand for a standardisation of
>>the user interface. This also is a good decision. Add OLE,
>>multitasking, audio support, ...
>
>AmigaOS does all of this as well. It does some of it better. The
>Amiga desktop
>is a lot more intuitive than Program Manager, for example, and
>it's got a lot
>more control over the environment. In 512K.
>
>>But they did lots of mistakes, when switching to windows. Now, with
>>windows NT, they started working on these mistakes. A 32 Bit address
>>space was introduced, a new process modell, and access restrictions
>>were added.
>
>I just had to reboot an NT server because there's no way to kill a Win16
>task that won't shutdown gracefully. Every time I logged in on
>the console
>there was this Microsoft Word window sitting there, crippled.

Ever heard of the NT Resource Kit? You can download it for free from MS. It
has a process viewer and killer that will end just about any process,
including 16-bit applications. Don't blame NT for having shortcomings that
aren't really there - educate yourself a little bit about NT and you might
figure out that it is a pretty fantastic OS!

>
>>So, don't blame them, for enhancing their OS.
>
>I blame them for doing it so badly, and taking so long in doing so.
>
>There is nothing in NT to justify a 32M memory requirement. The
>only thing

It doesn't have a 32M memory requirement! By repeating this over and over you
only show your ignorance of the truth!

>it has over AmigaOS is memory protection, and the only reason
>AmigaOS doesn't
>is because the 68000 didn't support VM when the Amiga came out.
>
>It has nothing over UNIX, other than having a bunch of apps already
>written for it. It's just big, and bloated, because there was nobody in
>a position to say "let's do it right" who had the faintest idea of what
>"doing it right" involved.

It has many advantages over UNIX, while UNIX also has advantages over NT.

NT is not bloated, and it was done very well. 

Do you have even the slightest idea of the underlying architecture of NT? Have
you bothered to learn anything about it?

>-- 
>
>If the best part of waking up is Folgers in the cup...
>
>                    ... nothing worse can happen to you all day!


Chris Glasser
AT&T Global Information Solutions
Chris.Glasser@ColumbiaSC.ATTGIS.COM
(803) 939-6786