My installation attempts of XP have been unsuccessful. Windows XP copies some files and updates the setup program and then restarts my machine. Then when it reboots it hangs "detecting hardware configuration" or something similar to that. If I reboot I can cancel the Windows XP setup. I have tried formatting the hd, deleting the partion and recreating it, removing all of the pci cards(except my video card). I have also updated my bios... nothing seems to help.
My motherboard however, is a BioStar M7VKD and my video card is a STB Velocity 4400 PCI 16MB w/tv out(TNT). I suspect that XP does not like my motherboard chipset & video card combination. I'm not sure what I need to do to correct this problem. I did update my bios already and that didn't seem to work. It is hard to get support for my video card because STB was owned by 3dfx which was purchased by nvidia. I'm sure that I'm not the only one with this problem, so there is probably a work around. Any help would be greatly appreciated.
THANKS!
:confused:
did you check msīs hcl (hardware compatibility library)? they should tell you at least if your mainboard works at all with windows XP/2k
also sometimes it helps if you tell windows to install a "standard pci graphics adapter" and install the drivers after the rest of the installation is done...
Unfortunately, I have looked at the hcl from Microsoft, and according that list my motherboard is XP compatible, however, they show my video card as only Windows 98 compatible and not ME, 2000, or XP. It is running like a charm on ME, so I can't really trust their compatibility list.
As far as loading the standard driver ... I did format and attempt to do a clean install ... the install program hangs right after it restarts for the first time. At this point in the installation program, XP has just copied the files necessary for the install and is attempting to detect the hardware. I never get the option to select a video card ... it blows up really early in the installation process.
did it ask you for a driver cdrom or did it only take its own drivers? then copying the cdrom to your hard drive and deleting them might be an option.
i never installed XP myself though... :(
but the other versions of win**** had an option to start "safe recovery" or something if you try to install over an installation that hung during install.
if not, try to get a command line before installation (F5, F8). if this is possible, type "setup /?" to see if you can bypass the detection somehow.
sorry, this is probably not much help, but about all i can tell you right now :(
Originally posted by M.Hirsch
did it ask you for a driver cdrom or did it only take its own drivers? then copying the cdrom to your hard drive and deleting them might be an option.
i never installed XP myself though... :(
but the other versions of win**** had an option to start "safe recovery" or something if you try to install over an installation that hung during install.
if not, try to get a command line before installation (F5, F8). if this is possible, type "setup /?" to see if you can bypass the detection somehow.
sorry, this is probably not much help, but about all i can tell you right now :(
It didn't ask for a driver cd ... it never made it past the "setup is inspecting your hardware configuration..." There is no option to recover the installation ... when I reset my computer I can continue or cancel. If I continue it hangs at the same place, or if I cancel it boots back into Windows ME and cancels the install process all together.
There is no way to run the setup program with any switches (/?)
Does anybody else have any ideas??? :(
Fun innit?
Considering ME uses the same architecture as 98 and not the NT kernel (even if it does look a bit like 2k), its no surprise that your card runs in ME.
Here's what you can try and do. One of your mates must have a similar spec GFX card you can loan for your installation...preferably one that is 100% compatible with XP so you get no more grief.
Now, install XP on your box with the loaned card. When done, pull it out, plop your gfx card in and see what happens. I can't guarantee that this will work, but I've installed XP Pro a few times in the office and I've found that a component that stuffs you around during install time runs like a greased pig on a ski jump once the machine is up and running.
Just my 2c. Be interested to see if it works yeah? Ta :D
if it is in the HCL it is not the card it might be the combo but i'll bet what it is is the other cards in the system try moving your modem/ nic/ sound cards to different slots i know it sounds silly but just try it i think you will be suprised
i had the same EXACT problem and i was running an ATI rage 128 pro vid card, now i bought radeon 8500 like 2 days ago, now i'm back in 98 Se and i was wondering, jus tto be positive if i try and install XP will it **** up again, or am i all good?
and for you jeremy, it think it must be your vid card
It's almost a year later but yes I have the same problem with XP Pro setup.
Setup hangs at the b/w screen with "Setup is examining etc"
I too have w98 SE and an ATI AIW 128 Pro and am installing XP so that I can use my new ATI AIW Radeon 8500
Hopefully spliffstar187 will have found the answer for me and others..but PLEASE anyone with advice is appreciated.
Bob
After all, 3 strikes and one is out.
I tried to load Win XP Pro 3 times, upgrading from Win 2k Pro (Clean install with disk format), including the use of 6 floppies to get the XP cd to boot, as suggested by Microsoft. As a matter of fact, since there are so many articles and memos even from within the MS site on XP install errors and problems, that I will revert back to Win 2K Pro and wait for Microsoft to get the bugs out. This was an exasperating experience and an unncessary waste of time. There are just too many potential conflicts and problems, and my computer and parts are no more than 4 months old - no compatability issues with XP using the XP Upgrade Adviser. Unless someone just gets lucky or absolutley needs a feature that Win 2K Pro doesn't have, steer clear of XP until a reasonable solution is found for these errors, many of which seem to be just totally random.
just curious, is this a legal copy of xp or one from the net, such as kazaa, alot the install hang ups i come accross are because of a file transferr error with those copies, the problem seems to be all the viruses running araound on the file share system attack win 32, and exe programs, even though the virus has been removed it left damage. if you did get your copy this way, and you had any extraction errors when you opened it, you may want to consider buying a copy or obtaining a different copy. not saying this is how you came by your copy of xp, if it is a legal copy let us know some more specs on your computer, like hard drive specs and size, ram memory size, and type would be helpfull,pretty much list everything you have, even the jumper settings for the drives you have. it is almost impossible to answer a question when you only know part of the situation.
Sorry I didn't post a reply guys. I purchased a Nvidia GeForce MX200 64MB DDR card and everything worked just fine. It was a compatibility issue with the video card. I'm still not sure if it was the combination of video card and motherboard chipset or just the video card.
Everything has been working fine until recently when my system kept hanging when it was idle in XP Pro. It turns out that it was Windows Update Fix #811493 that was causing the problem. After uninstalling it my machine is stable again. If you guys do get XP installed and updated to all of the latest fixes beware of 811493, it may cause your system to freeze when it is idle.
Hi Jermy4,
Can you tell me what upgrade you did on your Bios? Unicore says my M7VKD won't support Win2000 but the specs on the board say it will. The Bios is dated 8/31/2001 but I'm having the same problems as you were doing a clean install of Win2000. Getting the error "cannot copy file" until setup quits. vince.
The Win XP Pro disk is from a major company as part of their corp license. The disk was copied by their IT dept. The disk was not downloaded from the net. The problem seems to be on the initial re-boot after copying the files. Since I used the six disks to boot up the CD (as directed by the MS site), perhaps there are no boot files on the CD at the initial re-boot. Hence, that's where the install process "stalls". Thanks.
I have recently had the same problem installing XP pro, Windows never starts, repartioned, reformated, setup files, restarted, over and over again and on a brand new 60GB drive. After Windows said it was gong to reboot the computer in 15 secs, it went through the whole setup file process, and then warned me about having to delete the previous setup files, did this also happen to you? All my hardware is compatible with XP. I have yet to resolve the problem, could it be due to harddrive jumper settings? Have you resolved this issue. Please Help.....Losing sleep over this, think I'm going mad.
I discovered that I needed to install my motherboard drivers and utilities before XP Pro would finally "adhere" to the drive. I forget because it was so many times, but I think I just inserted my MOBO CD Utilities disk (after trying to setup XP Pro) and loaded the necessary MOBO drivers and then XP worked. XP loaded and copied files apparently normally. XP just never seemed to reboot. I think this is when I decided to try to insert the MOBO driver CD. MY MOBO was a new Gigabyte model - Nov. 2002. I recall that the CD drive could recognize the CD setup progra,. I may also have entered CMOS/Setup and allowed booting from a CD, but I forget. Anyway, the MAIN POINT is that it was my motherboard problem, I believe in particular an Intel chip driver was missing which was loaded from my manufacturer's (Gigabyte) MOBO driver CD. The MOBO neede to have certain drivers, especially the INTEL driver, before it could boot normally.
I finally solved the problems with the Gigabyte machine by doing three things.
1.)Like the guy stated in the previous post, I grabbed the MOBO CD-ROM and opened every file, one after another and ran every last thing that was on it, especially if it said "driver".
2.) I changed the RAM cards and stopped using the smallest one to start like everyone suggested and started witht 512 Meg card and then added two more smaller cards, 256 and 128 for a total of 896. One of the two 256 cards I tried to use before may have been an ECC card because I tried it stand-alone in another machine that worked perfectly, .......and it crashed the machine. Stuffed it in a box and forgot about it.
3.) By this time, I had put Win2000 on two other machines and just put it on the Gigabyte box for commonality. I'll put XP on the computer I'll be buying this year. I know the XP will work now, but the MOBO floppy drive socket just plain quit and won't run any 3.5 that tests Ok in other machines, my 200 gig HD won't load onto the machine unless I change the Win2000 registry to 48 bit addressing, and every once in a while, just because the board is old and tired, it crashes the system and restarts just because I might shut down a graphics-intensive program (64meg Radeon installed) or start up some other programs and WONK!!! thar she blows.
I have decided to just consign this machine to second level importance in light of buying a new machine soon. I have definitely learned a lot. One of those lessons is to be prepared to spend more in "time" lost than "money saved" when dealing in older used parts and trying to put together machines from bits and pieces. You can't buy experience, but it sure costs a lot.
Happy computing,
Vince.
my solution was .. .
I have had this same problem recently, and thought I would add my 50cents to maybe help someone in the future.
I just unplugged all my drives, apart from the drive I am going install Windows on, unplugged all my USB cables, and it worked.
Jake
Thanks for the additional info.
However, as this thread is over 2.5 years old, I'm closing it. If anyone has any issues with this, then do not hesitate to PM me. :)