Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows NT / Setup / September 2003

Tip: Looking for answers? Try searching our database.

PC is not start after hard disk change:  BMLite corrupted. Boot from BMLite disk.

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Dmitry N.Ananyev - 26 Sep 2003 08:45 GMT
I am change hard disk to its copy from 3G to 20G.

But PC is not start:

BMLite corrupted. Boot from BMLite disk.

What it means?

266MGz, 196 RAM, NT4.0

Thanks.

Dmitry.
Jiri Tuma - 26 Sep 2003 11:38 GMT
Seems you have (or should to have - there are machines, for ex some Compaq
models,  depending on small service partition located on begin of primary
disk) any MBR level boot manager installed. What method did you used to copy
your files?

Is this 20GB disk new one or it was used elsewhere before?

Are you able to boot using NT boot floppy? Try this:
Plug in old disk, launch NT, create NT boot floppy  (format floppy under NT
operating system and copy files NTLDR., NTDETECT.COM and BOOT.INI from root
of your C: drive to this floppy, if there is optional NTBOOTDD.SYS file copy
it too), plug in new disk and try to boot from floppy.

luck

George

Dmitry N.Ananyev <dtc.98@relcom.ru> p??e v diskusn?m
p??sp?vku:eRR60IAhDHA.3276@tk2msftngp13.phx.gbl...
> I am change hard disk to its copy from 3G to 20G.
>
[quoted text clipped - 9 lines]
>
> Dmitry.
Dmitry N.Ananyev - 29 Sep 2003 11:45 GMT
DOS\  fdisk /mbr  - is a good idea.
Jiri Tuma - 30 Sep 2003 11:15 GMT
not always.

If you are 100% sure you have IBM compatible machine, this command is safe
and helpfull.

But if your machine is using proprietary design (good example are some
Compaq machines) you need to be more careful because this command will
replace code in MBR by industry standard code and if machine depends on
proprietary code here your machine can reject booting at all. Also some disk
crypting systems need to have proprietary code in MBR to be fully
functional. Using  manufacturer emergency utilities is much better than
"fdisk /mbr" in such case.

It is better to save previous content of MBR to file before you try "fdisk
/mbr" command (you can use disksave.exe from NT resource kit if you have not
any better tool).

Dmitry N.Ananyev <dtc.98@relcom.ru> p??e v diskusn?m
p??sp?vku:eIkcJbnhDHA.1172@TK2MSFTNGP09.phx.gbl...
> DOS\  fdisk /mbr  - is a good idea.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.