(#1)
|
(#2)
|
|
Zeropaid Regular
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,825
Join Date: Apr 2002
Location: Florida
Reputation Power: 279
|
October 9th, 2003, 07:07 AM
go into dos prompt or command prompt and type FDISK /MBR
which was posted here: http://support.microsoft.com/default...b;en-us;171611 Then reboot if you get any trouble which you shouldnt then run fixmbr on the recovery console of your windows install disk and it should fix it. Ive done it before and didnt get any problems so you shouldnt. |
|
|
|
(#3)
|
|
Registered User
![]() Posts: 3
Join Date: Oct 2003
Location: in the uplink truck
Age: 53
Reputation Power: 0
|
October 9th, 2003, 07:57 AM
Having tried linux a few times I have a tip that may help you avoid this situation in the future.
If you are using windows 2k or XP (probably also older NT versions too) there is a way to use the NT loader that comes with windows to boot into linux without having to worry about lilo messing up your MBR try taking a look at this the next time you install linux http://www.poopoccurs.com/linux/dualboot.html if you use this method and keep a linux boot disk around in case of emergency I've found recovering from problems becomes much easier and the risk of damaging your current windows install is minimized. I hope this isnt over your head (it took me a few times to figure it out myself) and helps..... good luck |
|
|
|












Linear Mode