Interesting thing I found out with my system. I have a drive for XP setup as well as one for 7 and I just switch the order of the boot sequence (less of pain to me than using dual booting utilities) in the bios. I did this upon a restart, thinking that XP wouldn't be affected by a completely separate OS on a completely different hard drive (in fact, the 7 drive is a SATA while the XP drive is PATA). So the method I used to solve the problem before with 7 not recognizing my network devices, by turning the entire system off at the PSU, was not performed this time due to my ignorance of any happenings that may occur in XP.
Turns out, XP did the exact same thing. All my network devices were unrecognizable. I had to shut down the entire system at the CPU and then boot into XP again for it to recognize the network adapters. This is definitely and issue with the motherboard I'm using. Come to think of it, I've actually had many problems with this board and Vista. It would literally hang at the pre-BIOS stage for nearly a minute or more before it would start properly. I thought the board was just faulty, but it seems Vista (possibly something to do with EFI emulation or something) was forcing the BIOS into a loop and would take forever to correct itself. After installing XP and using that exclusively, I didn't have a single problem with the board.
I think it'd be safe to say that it can be narrowed down to three problems, one the board needs a BIOS update in order to function properly, two Abit needs to look into what EFI emulation does to this board, and three MS may be able to correct it at their end by tweaking their EFI emulation for Vista and 7. I could be entirely wrong about the EFI thing, though, but I don't believe this board uses EFI at all. I'm pretty certain it's a problem with the BIOS in some way, however.