Re: Palatable Windows IO using Ada

"Dmitry A. Kazakov" <mailbox@xxxxxxxxxxxxxxxxx> wrote in message
news:o2i2brhcp49x$.1lmgnwrqgqzf7$.dlg@xxxxxxxxxxxxx
Once I managed to install Windows NT 4.0 on a 486DX 66MHz / 12Mb. It took
about one day. The system booted in 10 minutes or so.

Our main server is a 90 MHZ Pentium running Windows NT 4.0 Server. (It's
fast enough, as it only has to manage a dozen user accounts and less than
100 e-mail messages per day.) It takes about 90 seconds to boot; it's faster
than our Windows 95 test machine (which is a 250 MHZ machine).

The "bad old days" were not really *that* bad. :-)

Randy.


.

Relevant Pages

  • Re: Lost NT 4.0 Domain access on all win2k machines
    ... > to their original NT server 4.0 domain controller, ... TEST MACHINE was established and tested ok - identical to the ... > after looking around at microsoft web sites to see what has to be done to ...
    (microsoft.public.win2000.networking)
  • Re: The Etch-P Pavilion
    ... Computers are like everything else - if you don't use ... IBM p75 "win95B, putty, and act as a test machine" ... 9- IBM PC300PL "win95B,News Server Hamster" ...
    (comp.sys.ibm.ps2.hardware)
  • help decipher system Event Viewer Kerberos error
    ... I found the following error in my System Event Viewer for the past 2 weeks ... This is a test machine that mimics production. ... server from the domain, rebooted, and added it back to the domain. ... The target name used was ...
    (microsoft.public.windows.server.general)
  • Re: SP6 and problems with XML
    ... Would you know which DLL or OCX is causing the behaviour? ... > runtime on the production server. ... > test machine with the files you have on the server, ... when I compile my app and upload my DLL to my production app ...
    (microsoft.public.vb.enterprise)
  • Re: SP6 and problems with XML
    ... Would you know which DLL or OCX is causing the behaviour? ... > runtime on the production server. ... > test machine with the files you have on the server, ... when I compile my app and upload my DLL to my production app ...
    (microsoft.public.vb.bugs)