Version: 2008
Advanced Search
advertisement
advertisement

Forum display:

PC hardware: boot problem (inacessable boot device)

by brewdog - 5/19/05 10:22 AM
advertisement
Post 1 of 7

boot problem (inacessable boot device)

by brewdog - 5/19/05 10:22 AM

I've searched the forums and found problems similar to mine but no solutions for my particular problem.

I am attempting to build a computer with a Pcchips M811LU motherboard and a Duron 1.8 G processor. I realize now that this motherboard doesn't have a good track record but at the time I purchased it it looked like an affordable way for a long overdue upgrade.

I am attempting to boot from a Samsung Trigem SV10220/TGE hard drive with Windows 2000 Pro already installed. This drive boots and works fine on the computer I'm presently using. When I try to boot it on the new system it looks like it is going to boot normally. I get a black screen saying Windows 2000 is starting and the progress bar fills up. Then it goes to the Windows 2000 splash screen with a progress bar that fills about 1/3 of the way before going to a blue screen with an error message......stop 0x0000007B (0xED41B84C,0xC0000034,0x00000000,0x00000000) inacessable_boot_device.

I'm not a technician. This is my first attempt at building a computer. There is a great deal I don't understand about them. Why will this hard drive not boot when it is being detected and read from by the motherboard?

Any help would be greatly appreciated.

Post 2 of 7

That's proper.

by R. Proffitt Moderator - 5/19/05 10:27 AM In reply to: boot problem (inacessable boot device) by brewdog

Windows NT, 2000, XP and 2003 do not take to moving to other hardware.

Fix? Install the OS again.

Warning! If you intend on using that hard disk, do not move it to another machine as a drive geometry issue could cause its contents to vanish.

Bob

Post 3 of 7

thanks

by brewdog - 5/19/05 12:03 PM In reply to: That's proper. by R. Proffitt Moderator

Thank you very much for the fast reply.

I installed another drive with Windows 98 on it. It woke up and was very confused by the new environment it found itself in but it does run.

Thanks also for the advice about installing the W2K drive in a different system. I do want to keep the contents of that drive intact for the time being so will not try again to move it to another machine.

Post 4 of 7

Those DOS based OSes often can fix themselves up.

by R. Proffitt Moderator - 5/19/05 1:19 PM In reply to: thanks by brewdog

As you discovered.

Sometimes I wonder if this is progress...

Post 5 of 7

need a little more clarification...help!

by wmadams - 5/30/05 4:35 AM In reply to: That's proper. by R. Proffitt Moderator

Bob -

Your warning has me worried...

"Warning! If you intend on using that hard disk, do not move it to another machine as a drive geometry issue could cause its contents to vanish."

I am attempting to move a Win2K drive into a new system (it will be the only hard drive) and I want to keep the data that is on that Win2K drive. So, if I reload the OS on the Win2K drive, are you saying that I could lose the data? If so, there is really no way of moving the Win2K drive over to any new system without losing the data?

Thanks for any help on this one!!!

Morgan

Post 6 of 7

The move is done all the time.

by R. Proffitt Moderator - 5/30/05 6:56 AM In reply to: need a little more clarification...help! by wmadams

It is the rare issue that some will lose it. Besides this is a non-issue since everyone keeps a backup of what we can't lose on our backups.

I can't write "move the drive" and tell anyone their data will stay due to this issue. 99 will work (the OS will still not boot) and 1 will lose all the hard disk content. Of the 99, 50 to 90 will successfully repair the OS and the remainder will lose the drive contents due to negligance.

Bob

Post 7 of 7

one additional question...maybe two

by wmadams - 5/30/05 7:57 AM In reply to: The move is done all the time. by R. Proffitt Moderator

Bob -

Thanks!

Before I take the step off the edge of the cliff...

1) Would reinstalling the OS on my existing Win2k drive be the correct process that "should" allow me to get to the current data on the drive or
2) Would grabbing another hard drive, loading it with Win2K and then access the old Win2K drive to get to my data be a better solution or
3) Other thoughts?

Backups...yes, have those but still hate to reenter a month or so of data:-(

I am sorry to be bothering you on Memorial Day...what a time to try to do this!!

Morgan

Forum legend:
Locked Locked thread
Moderator Moderator
CNET staff CNET staff
Samsung staff Samsung staff
Norton Authorized Support team Norton Authorized Support team
AVG staff AVG staff
Windows Outreach team Windows Outreach team
Dell staff Dell staff
Intel staff Intel staff
Powered by Jive Software