V
Vince C.
Hi.
This is a complaint. Yes! I've just made a brand new install of W2K server and -
I swear - I can't count the number of times I had to reboot during the setup
phase. But I can tell you I wasted at least 50% of my time just rebooting and
waiting for the box to calm down before logging on (Ok, I know I don't have to
but I already got into troubles by logging just too early - my server is a test
machine and not that recent).
Here's the approximative count:
1. Install from diskettes & CD - reboot once to get into the GUI (45 minutes)
2. Install & configure AD - reboot
3. Install nVidia drivers from the disk - reboot
4. Install service pack 4 - reboot
5. Fine tune to get rid of errors and warnings (e.g. event 5781/5782) - reboot
(after each of 5-6 attempts)
6. Install VIA chipset - reboot
7. Install FastTrack driver - reboot
8. Install firewall - reboot
9. Connect to the Internet and apply patches (WU) - reboot
10. Install IE6.01 SP1 - reboot
11. Install IE patches - might reboot, it did!
This is the optional part but since I only have this machine, let's go:
12. Install motherboard USB-specific drivers - reboot
13. Uinstall NetBEUI from every network interface (installed by USB drivers,
even on the Internet card! wow! be secure! use NetBEUI on your Internet
adapter!) - reboot
14. Uninstall Netware client and protocol from every NIC (installed by USB
drivers) - reboot
15. Install sound drivers - reboot
16. Install up-to-date nVidia drivers - reboot
17. Install DirectX - reboot
18. Install Media Player - reboot
19. Install DVD Player - reboot
What else?... Well, I think it's finished. Had it been an ordinary W2K Pro,
there would have been all 19 steps.
On my machine it takes approx. 5 minutes to reboot completely due to the
hardware checks. Select reboot; Windows is: saving your settings (what damn
settings?), closing session, shutting down, rebooting; wait for BIOS POST, till
FastTrack finishes scanning, drive detection, booting windows, till windows:
starts, preps network connections (almost 10 seconds), applies security policy;
wait till firewall activates, wait till disk calms down; log on, hear the
beautiful logon sound, wait till you get control and... Aaaaaaaah! finally you
can type and use your menu!...
It only takes 2 or 3 minutes to pick up the driver, click and install. The
reboot process took me then about 25 x 5 min. which gives 2 hours just watching
my PC reboot!
And on IBM servers (X series) it can take much more than 5 minutes for a reboot
to complete.
I've installed Linux in one go with all the drivers, kernel, system, GUI,
software aso. I just had to reboot my PC once: after I compiled my kernel.
That's why I'm pissed off.
Vince C.
This is a complaint. Yes! I've just made a brand new install of W2K server and -
I swear - I can't count the number of times I had to reboot during the setup
phase. But I can tell you I wasted at least 50% of my time just rebooting and
waiting for the box to calm down before logging on (Ok, I know I don't have to
but I already got into troubles by logging just too early - my server is a test
machine and not that recent).
Here's the approximative count:
1. Install from diskettes & CD - reboot once to get into the GUI (45 minutes)
2. Install & configure AD - reboot
3. Install nVidia drivers from the disk - reboot
4. Install service pack 4 - reboot
5. Fine tune to get rid of errors and warnings (e.g. event 5781/5782) - reboot
(after each of 5-6 attempts)
6. Install VIA chipset - reboot
7. Install FastTrack driver - reboot
8. Install firewall - reboot
9. Connect to the Internet and apply patches (WU) - reboot
10. Install IE6.01 SP1 - reboot
11. Install IE patches - might reboot, it did!
This is the optional part but since I only have this machine, let's go:
12. Install motherboard USB-specific drivers - reboot
13. Uinstall NetBEUI from every network interface (installed by USB drivers,
even on the Internet card! wow! be secure! use NetBEUI on your Internet
adapter!) - reboot
14. Uninstall Netware client and protocol from every NIC (installed by USB
drivers) - reboot
15. Install sound drivers - reboot
16. Install up-to-date nVidia drivers - reboot
17. Install DirectX - reboot
18. Install Media Player - reboot
19. Install DVD Player - reboot
What else?... Well, I think it's finished. Had it been an ordinary W2K Pro,
there would have been all 19 steps.
On my machine it takes approx. 5 minutes to reboot completely due to the
hardware checks. Select reboot; Windows is: saving your settings (what damn
settings?), closing session, shutting down, rebooting; wait for BIOS POST, till
FastTrack finishes scanning, drive detection, booting windows, till windows:
starts, preps network connections (almost 10 seconds), applies security policy;
wait till firewall activates, wait till disk calms down; log on, hear the
beautiful logon sound, wait till you get control and... Aaaaaaaah! finally you
can type and use your menu!...
It only takes 2 or 3 minutes to pick up the driver, click and install. The
reboot process took me then about 25 x 5 min. which gives 2 hours just watching
my PC reboot!
And on IBM servers (X series) it can take much more than 5 minutes for a reboot
to complete.
I've installed Linux in one go with all the drivers, kernel, system, GUI,
software aso. I just had to reboot my PC once: after I compiled my kernel.
That's why I'm pissed off.
Vince C.