Please register or login. There are 0 registered and 408 anonymous users currently online. Current bandwidth usage: 326.30 kbit/s January 17 - 01:09am EST 
Hardware Analysis
      
Forums Product Prices
  Contents 
 
 

  Latest Topics 
 

More >>
 

    
 
 

  You Are Here: 
 
/ Forums / Other Hardware /
 

  Moved components from one case to another. Now it won't boot. What's that about? 
 
 Author 
 Date Written 
 Tools 
on line Mar 25, 2004, 05:51pm EST Report Abuse
Running out of room in old case so I took everything (PSU, mobo, hard drives, etc) out of old case (where things worked fine) and put them in new case.

Turn it on and it recognizes my hard drives, my cd drive and my floppy. Shows me the list of PCI devices. Hangs for a long time at "Verifying DMI Pool Data...." and then displays "Disk Boot Failure, Insert System Disk and press ENTER"

So I check that everything is hooked up right and it SEEMS like it. Try again. Same thing. Aaaaarg!

Switch boot device to be floppy and put in boot disk. Get IO error.

Switch boot device to be CD and put in the CD that came with the hard drive. Starts to boot up and then I get a "Fatal error TNT.11020 application X:\DOS\INSTALL\DL.EXE has caused an exception blah, blah, blah"

Now I'm ready to throw this thing out the window.

I must have done something to screw it up but I have no clue what. Has anyone else experienced something like this?

Any suggestions or feedback would be greatly appreciated. If you need any other information, please let me know.

Thanks in advance.

My configuration:
Mobo: Gigabyte KT600
CPU: AMD Athlon XP 2700+
RAM: 1GB
HDD0: Seagate 160GB
HDD1: Seagate 120GB
CD: HP


Want to enjoy fewer advertisements and more features? Click here to become a Hardware Analysis registered user.
Wildwood Mar 25, 2004, 06:08pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
I know you already checked, but...

I suggest that you go through your assembly. Make sure you have all of the cables properly connected and oriented the right way. And your hard drives, make sure the jumper didn't fall off and that the master/slave configuration is correct ( the master drive belongs on the end connector of the IDE cable no matter what people tell you about how it doesn't matter). Check your video card, memory and any PCI cards to be sure they're well seated in their slots.
Now look at your motherboard stand-offs. Are they all in the correct holes? Screws not too tight? Overtight screws can crack the motherboard and cause a short, though rarely.

Post back if it doesn't help. There are more possibilities, but these need to be checked first.


ioneabee Mar 25, 2004, 06:16pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
hmmmm
my first thoughts would also be with the mobo standoffs - but also run memtest86 as a bootable floppy to test your memory - what was the floor surface you were standing on when you re-built it ? nylon carpet ? possible classic case of static ??

http://www.pembrokeshirecomputers.co.uk
http://www.sap-calculations.co.uk
on line Mar 25, 2004, 06:16pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
Thanks for the quick feedback.

My original post didn't list all different combinations I've tried:
- tried with no IDE cables at all and just the floppy.
- tried with just the main hard drive
- tried with just the CD drive
- checked and rechecked all the connections (video card, wires (hdd led, power led, power switch, reset switch, etc)

I wondered if I could have messed up the motherboard somehow when handling it but I thought that if it actually detected my drives and got to the point of trying to boot that it was past any mobo problems. True or not?

I haven't checked the motherboard screws. I'll do that.

Thanks again and keep the suggestions coming.

on line Mar 25, 2004, 06:24pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
loneabee,

I was standing on a hardwood floor when I moved the components around and I was trying really hard to touch a metal surface before touching any component.

When you say mobo standoffs is there something special I should be looking at/for regarding them?

You also mentioned memtest86. If the bootup process that checks memory says that it found it and doesn't display any errors do I still need to do that test?


Jaymes Lee Mar 25, 2004, 06:36pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
Ah, brings back memories of when I had the same problem... I can't remember exactly how I fixed it, but I did disassemble/reassemble the thing several times... just try it a few times, try installing bare minimum peripherals (eg one hard drive at a time), swap out some parts if you have any lying around...

angryhippy Mar 26, 2004, 05:26am EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
They are talking about the standoffs because of the possibility of a short. Take the mobo out of the case and lay it on a piece of cardboard or something non conductive. Hook up the hard drive and the video card and memory. Connect the power cables and fire that sucker up and see if it will boot. You should only have standoffs where the mount holes on the mobo are.

Get Hippied out!
http://www.angryhippy.net
Me at work: http://tinyurl.com/3nvncb3
My rig! A Blah blah.With a blah blah! SWEET! http://tinyurl.com/4yujmff
Da Beast! http://tinyurl.com/3sapr2b
i5 3570K 4.6GHz http://snipurl.com/26r3cot
Win7-8 Pro 64bit
Wildwood Mar 26, 2004, 01:38pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
Memtest86 does a more thorough memory check.

Use the anti-static bag the motherboard came in if you're going to do as Payton says. If you have it.

Myself-
I would disassemble the comp and re-assemble it. Taking care to check that everything is done exactly as it should be. Sometimes I get in a hurry and set something up wrong. For me it's usually forgetting the Master/Slave jumpers on the drives.


jmerc Mar 26, 2004, 02:01pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
Did you check to make sure you have power going into the drive from the power supply?
Maybe you forgot to plug the hard drive to the psu.

Jay

Life is too short, make the best of it!
on line Mar 29, 2004, 07:59am EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
I was finally able to bring up the Seagate utilities that came with the Hard drives. I ran the extended hard drive test on both my drives and it said that it didn't find any errors on either hard drive.

So my situtaiton is this. The IDE drives are recognized and the utilities say there are no errors but when it tries to boot I get a "non-system disk" error.

I've checked and double checked and I have the jumper settings set up correctly and the cables hooked up correctly. So how is it possible that a hard drive that has WinXP installed on it can all of a sudden not be a bootable drive just by me moving it to another box (along with all the other components from the old box)

Any ideas?

angryhippy Mar 29, 2004, 03:45pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
David lets start from the first step. Disconnect the power plug, and remove the CMOS Battery, check that it's good and replace it. Use the jumper to clear the bios then reset it to optimalsettings (default). If you still get the same message, Then use the install CD to rebuild your boot files. Here are instructions. Don't worry about which error messages this says the fix is for.

http://support.microsoft.com/default.aspx?scid=kb;en-us;330184...duct=winxp

If that doesn't work you may want to try a repair (upgrade) install. This installs XP over the OS that is already there, and you should not lose any of your files or data, although there is always that chance. You want to use method #2

http://support.microsoft.com/default.aspx?scid=kb;en-us;315341...duct=winxp

Hope you get it going.

Get Hippied out!
http://www.angryhippy.net
Me at work: http://tinyurl.com/3nvncb3
My rig! A Blah blah.With a blah blah! SWEET! http://tinyurl.com/4yujmff
Da Beast! http://tinyurl.com/3sapr2b
i5 3570K 4.6GHz http://snipurl.com/26r3cot
Win7-8 Pro 64bit
on line Mar 29, 2004, 04:08pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
Payton,

I'll try that. Thanks.

You know, I would have just wiped the hard drives clear and started from scratch but I have some important data there that I didn't want to lose. Guess I need to get better about backing data up.

Thanks again Payton and everyone for all the great feedback. I'll keep you posted on the progress

Wildwood Mar 29, 2004, 10:00pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
Never mind, dumb suggestion.


on line Apr 05, 2004, 09:03pm EDT Report Abuse
>> SOLVED...Re: Moved components from one case to another. Now it won't boot. What's that about?
Well, after weeks of trying all kinds of combinations someone suggested I use the Cable Select jumper setting on the hard drives.

Did that and it worked fine. I can't believe it was that simple!!

Thanks everyone for all the feedback. Even when it doesn't specifically solve the problem I'm posting about I always learn something useful from each of the posts.


Marius Janusaitis Aug 12, 2004, 03:00pm EDT Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
Dave,
thanks for that thread you started and maintained.

I faced the same error.
Went throught all the testing/switching crap...

I wouldn't think in hundred years that swithching to cable select would solve the error...
Have no idea why there is such a conflict.
Somebody has an clue?

-m.

bossa ritchie Aug 12, 2004, 03:25pm EDT Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
Yeah I have an asus dvd drive and an asus cd/rw and I need to set my cd/rw as slave and cable select for my DVD drive.

Brian Stewart Aug 12, 2004, 03:41pm EDT Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
Some mobos are bad about that sort of thing.
You're probably using one cable to connect 2 drives, right?
So, you have one master, one slave, it doesn't work.
Sometimes, the master has to be on the top (longer) connector, sometimes it has to be on the bottom.
Cable select means it will decide which is best.

I don't know why exactly, maybe something to do with the physical construction of the cables but that's what I've found to be true

MSI K8N Neo 2 Platinum
1 GB DDR 400
Athlon 64 4600+
6800 GT
Corvus Raven Aug 14, 2004, 11:46pm EDT Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
I am a bit late..

But sounds like you had your C: and D: drives mixed up. :)

--------------------------
ASUS A7N8X Deluxe PCB 2.00 w/ BIOS 1005 (cause? Dunno.. ATM)
AMD XP 2800+ @ 0.0 GHz 0MHz FSB (overheating for no appearent reason)
(2) - Corsair XMS512-3500C2 (5-2-2-2T) @ 0MHz
ATI Radeon 9700 Pro @0
Enermax 500W p/s (ok.
tyler pendleton Feb 03, 2008, 05:42pm EST Report Abuse
>> Re: Moved components from one case to another. Now it won't boot. What's that about?
how do you do what you did to fix it?



 

    
 
 

  Topic Tools 
 
RSS UpdatesRSS Updates
 

  Related Articles 
 
 

  Newsletter 
 
A weekly newsletter featuring an editorial and a roundup of the latest articles, news and other interesting topics.

Please enter your email address below and click Subscribe.