how come windows 200 takes so long to boot on my amd system? it takes just about as long as it does on my celeron system.
the amd system has a much faster hard drive, a better shipset, much faster video card, ddr ect.
relevent specs are for the fast one are:
amd 2100+ cpu
a gigabyte board (can’t remember model #) with the k333 shipset.
512 megs pc2700 ddr ram
seagate 120 gig 72,000 rpm hard drive
radeon 8500 all in wonder
relevent specs for the slow one are:
celeron 533a
some stock hewlet packered motherboard
256 megs 100 mgz sd ram
56,00 rpm maxtor 20 gighard drive
intel i810 intergrated video card
just to make sure bench mark tests do indeed conferm the amd system is much faster.
whats the deal? does win2k have a do nothing for x seconds timer (where x is increased with increased system speed)? ufos? the illminati? the white album? swamp gas? gremlins?
It’s because you called it winblows. It’s mad at you.
But seriously, a distinct possibility is a driver issue. My XP used to pause for quite a few seconds on my network card driver. I fixed it by getting a new network card. There’s a utility called bootvis that monitors and optimizes XP’s startup times; I don’t know if there’s an equivalent for 2000 or not.
thanks i will look into that. it’s not really a bother or problem. just one those why? kind of things. i first noticed it when i started up both computers at the same. the fast several hadware changes so i don’t think it’s a driver issue.
You are probably maxing out the data transfer rate of your hard drives. Just because one spins faster does not necessarily mean it can shove all of that data across the cables faster.
I’m not certain if this is a Win2K thing, but I certainly remember it on Win98SE… If the network card is not assigned an address in Control Panel, the system will do a scan for a DHCP server to tell it what the IP address should be. This can cause the system to hang for several seconds if there is nothing connected. If you put a specific IP address like 192.168.1.1 in the TCP/IP control panel, this might fix the problem.
I think a big factor in why boot time doesn’t decrease much when you get a faster computer is that lots of hardware initialization code (not only in the drivers, but in the BIOS, which has nothing to do with what OS you’re running) has built in delays for specific amounts of time. Poke register X and then wait 100 milliseconds before poking register Y, etc. This adds up.