Ummm, no. Not if you have a card properly installed. On virtually all motherboards today that have integrated graphics (not all boards do), when you install a card, the integrated graphics is automatically disabled in the BIOS. This is necessary to free up any shared system RAM, but also specifically to direct video to the card just so you can boot into the BIOS or Safe Mode or a different OS. To have both integrated and card graphics enabled (for multiple monitors, for example), you have to manually go back into the BIOS and re-enable the integrated graphics again. Just understand that you will lose some of your system RAM to the integrated.if you boot to the bios you are using your graphic card ???
??? Ummm, sorry, but again not true. Again, this is how virtually ALL motherboards works, home or server grade and that is how it has been for many, many years. That is, if previously you had a graphics card installed and you remove the card, the integrated is automatically re-enabled. If it wasn't, you would be hosed. You would not be able to see the prompt to boot into the BIOS.try removing the video card see if you see the bios
server-grade motherboards are designed to be used too boot in remote for repairs service not home pc
This is because the same folks who made big screen TVs and audio equipment for home theaters also made many of the monitors for computers. Since the video signal in DVI and HDMI was the same, it made no sense economically or logistically to have both HDMI and DVI connectors on their TVs and monitors. Plus, the DVI connector is huge. So the big screen TV industry shoved HDMI down on to the computer industry, whether we wanted it or not.I have some comments, HDMI computer connections are more common now,
I sense sarcasm but really, W10 is great and works perfectly for the vast majority of users. Considering there are already over 300 million W10 users, and virtually every single one of those 300M computers are unique, that is a pretty major accomplishment. And for sure, W10 was designed to support legacy hardware (assuming the manufacturers fulfill their responsibility and do their part to develop compatible drivers), but W10 was really designed to take advantage of all the wonderful advances in modern hardware - like SSDs, UEFI, DDR4 and more. For example, I built this new computer for W10 with a modern Z170 UEFI motherboard that uses DDR4 and SSDs. And of course, I use Hybrid sleep mode. It takes less than 7 seconds from sleep to the prompt to enter my PW. W10's resource management is much more refined so "housekeeping" and other background tasks happen way back in the background so users don't notice it. So W10 is fast in other aspects too.but this might be the amazing WIN10 design work
Not really. The system clock relies on the RTC (real-time clock), a hardware counter and part of the motherboard. The RTC is kept "alive" by the CMOS battery circuit when the system is powered down and unplugged from the wall. By default, Windows syncs the RTC to a NIST Internet time server every 604,800 seconds (once a week). I typically change mine to 86400 (every 24 hours).My W7 can't keep correct, update time 7 years since it was introduced and after gazillion updates ! that's Microsoft too.
Ummm, it does not appear you read what I posted in my last reply.Time is displayed in Windows so Windows should correct it. Any clock needs adjustment from time to time, relying on isolated computer hardware and not on atomic clock in Colorado in COMPUTERS is idiotic.
That is unacceptable. But that is a hardware issue, not the OS. As Tim suggested, yours being off by so much is the classic sign the CMOS battery is bad. Since they only cost a couple $, I recommend you replace it. Most likely, as Tim noted, it is a CR2032 3V "wafer" battery. Just be sure to unplug from the wall and touch bare metal of the case interior BEFORE reaching in to discharge any static in your body. And don't touch the new battery with your bare fingers - skin oils promote corrosion and attract dust. I put a clean, cotton sock over my hand. Once inserted, connect power and boot directly into the BIOS setup menu. Check/reset the date and time and make sure your drive boot order is correct. Then "Save and Exit" to boot normally and your date and time should be correct.My clock in W7 works well when is set, but with any interruption of the system it shows for weeks wrong time and date, does not correct itself, it rely on me to correct it manually, that is totally unacceptable this after all COMPUTER.
The main reason came before that to ensure collaborated works from geographically separated sources were properly sequenced for US military and government communication networks.clock synchronization for remote radio telescopes( which is why the whole Internet Time system was started.
1ms/week would be nice but realistically is setting expectations way, WAY too high! That's 52ms/year. That would take over 19 years to drift just 1 second!!! The most accurate and expensive non-radio/GPS controlled watches in the world don't come anywhere near that.A modern mobo really should stay within 1 millisecond a week imho
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.