(also posted at Gigabyte's forum) I'm switching from a 790X-UD4P (AMD X4) to a Z68-UD3H-B3 board with an i7-2600K. With a Win 7/64 Home Premium SSD, I made a Windows system image before the switch and recovered it afterward (Sysprep didn't work). Afterward, everything looked ok except for two big problems. First, there's no USB and thus no mouse. BIOS USB settings are enabled and mouse works with Windows install disks, as well as with my XP drive (or it did until a repair install went south), and with the latter even before sticking in the Gigabyte CD. So what could be the difference between drives causing this? I was assuming it was a matter of drivers, but after getting into the Gigabyte CD with keystrokes and a file manager on the Win 7 drive, nothing has changed.
Second problem. After the switch neither the XP nor Win 7 drive is connecting to the internet. Cable modem and router are ok, and the cable company and the lights on the modem assure me that the signal is there, but something's stopping the connection. Is there something in one of the drivers or BIOS settings or something else that would casue this? I've got F11 BIOS, which is the latest.
I just went back to the 790X board to buy some time to figure this out. The same Win 7 drive boots fine and obviously has no problem with mouse or internet (haven't tried XP yet). Anyone got an idea what's going on and might be done? Hope it's not a BIOS bug... Thanks,
Second problem. After the switch neither the XP nor Win 7 drive is connecting to the internet. Cable modem and router are ok, and the cable company and the lights on the modem assure me that the signal is there, but something's stopping the connection. Is there something in one of the drivers or BIOS settings or something else that would casue this? I've got F11 BIOS, which is the latest.
I just went back to the 790X board to buy some time to figure this out. The same Win 7 drive boots fine and obviously has no problem with mouse or internet (haven't tried XP yet). Anyone got an idea what's going on and might be done? Hope it's not a BIOS bug... Thanks,
Comment