View Single Post
Old 30-04-2004, 18:17   #24
TheBlueRaja
cf.mega poster
 
Join Date: Dec 2003
Location: Baw deep in a munter
Age: 50
Services: Initiations, rep rigging and orgies!
Posts: 5,750
TheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny star
TheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny starTheBlueRaja has a nice shiny star
Re: windows xp major problem

Quote:
Originally Posted by Kronas
it told me my current boot record is 'invalid or unrecognizable' and if i continued my current partition may be unreadable.
Ok - I took this from the Microsoft Website (check the bit in bold)

Fixmbr Repairs the master boot record of the boot disk. The fixmbr command is only available when you are using the Recovery Console

fixmbr [device_name]

Parameter

device_name

The device (drive) on which you want to write a new master boot record. The name can be obtained from the output of the map command. An example of a device name is:

\Device\HardDisk0.

Example

The following example writes a new master boot record to the device specified:

fixmbr \Device\HardDisk0

Note

If you do not specify a device_name, a new master boot record will be written to the boot device, which is the drive on which your primary system is loaded.

If an invalid or nonstandard partition table signature is detected, you will be prompted whether you want to continue. If you are not having problems accessing your drives, you should not continue. Writing a new master boot record to your system partition could damage your partition tables and cause your partitions to become inaccessible.

---------------------

So what that means is that it has detected a problem, as this CAN cause you to loose ALL data in the event of failure, use this ONLY as a last option, but i think this will fix your issue. If it doesn't and it all goes wrong though, sorry - but i cant think of anything else.

Incidentally, i have used this command before and it did fix an issue and did not erase all my data - but - i cant guarantee it.
TheBlueRaja is offline   Reply With Quote