LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 05-19-2009, 06:25 PM   #1
stevewm
LQ Newbie
 
Registered: May 2009
Posts: 5

Rep: Reputation: 0
fixing boot/mbr via linux


I recently got wiped out by a virus/trojan in windows xp. When i try to reinstall all i get is a bluescreen with error code 0x00000078 (0xf78d663c,0xc0000034,0x00000000, 0x00000000). I assumed this meant a bad mbr and or boot.ini. I've managed to fix the mbr but no clue how to create a new boot.ini. I do not have a linux live cd so had to install full version of slackware to try and remedy this issue. Any help would be greatly appreciated.
 
Old 05-19-2009, 06:53 PM   #2
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
fixboot and fixmbr are proprietary programs used by the NT version of the M$ systems, meaning they are used only in Win2k and Xp. Therefore they cannot be provided by an OpenSource Linux.

You can use the bootcfg command available in a Win2k/Xp installation disc. Try run it with bootcfg /? to see what you have to do. The end product is a boot.ini.

The file can be "copy & paste" over hundreds of Internet sites if you just Google it.

I hate taking people by their hand but when I Google "boot.ini AND microsoft" I got this which is directly from the horse's mouth!

Last edited by saikee; 05-19-2009 at 06:56 PM.
 
Old 05-19-2009, 07:03 PM   #3
stevewm
LQ Newbie
 
Registered: May 2009
Posts: 5

Original Poster
Rep: Reputation: 0
I happen to know that fixboot and fixmbr are commands used in windows recovery..if you would read my post you would see i cannot get to recovery to run those commands..that error is a blue screen error. I wouldn't have ask here if i could've gotten to recovery console.Oh and there is no ntfs partition on my sata hard drive period now, just slackware...odd how slack installs with out a hitch and windows will not

Last edited by stevewm; 05-19-2009 at 07:13 PM.
 
Old 05-19-2009, 07:33 PM   #4
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 6,976

Rep: Reputation: 1283Reputation: 1283Reputation: 1283Reputation: 1283Reputation: 1283Reputation: 1283Reputation: 1283Reputation: 1283Reputation: 1283
You've installed Slackware and are now trying to re-install xp? What does "I've managed to fix the mbr" mean? Creating a boot.ini shouldn't be hard and as saikee indicated, you can find any number of sites describing how to do tha. I don't see the point if you can't install xp, creating a boot.ini won't help as it is only one of several files needed to boot xp.

Did you try googling that error or go to support.microsoft and do a search?
 
Old 05-19-2009, 07:56 PM   #5
stevewm
LQ Newbie
 
Registered: May 2009
Posts: 5

Original Poster
Rep: Reputation: 0
yes i did..and i used a command in linux to wipe out the mbr and was hoping there was something i could do for boot.ini as well..i have spent hours googling trying to find a fix to no avail...i came here as a last resort before buying a new hard drive..microsoft gives no reference to fixing anything via linux as you well know so that is pointless as i cannot do anything with windows xp installation cd due to the blue screen...i'm fairly sure the boot.ini was infected by the virus which is causing the bluescreen..everything i've read up to now points to an infected boot.ini but no fix for it
 
Old 05-19-2009, 08:02 PM   #6
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
The boot.ini is a configuration file inside a booting volume (or partition) for telling Win2k/XP's boot loader NTLDR where to load a Xp or Win2k which can be in any of the primary and logical partition. I have used it to boot Xp from 1st to 126th partition with it.

The boot.ini has absolute no use if you have not got a partition with

NTLDR
NTDETECT.COM

and its sole purpose is to boot an "installed" Xp or Win2k. It doesn't help your case if you can't even load a Xp installation disc and have no installed Xp to boot to.

You are making an assumption the blue screen is cause by the lack of boot.ini. That is your assumption only! You specifically asked for it so we tailor our help accordingly but it doesn't seem to be the cure for you.

You have confused us because you claimed to have fixed the fixmbr. In such a case it would boot you to an active M$ partition of Fat16, Fat32 or NTFS. Since you stated no ntfs partition how do you know your fixmbr works? Slackware or any Linux has no use of fixmbr.

You will find many cases of blue screen of death can be avoided if you have the latest Service Pack 3 which you can download and slipstream into your current installation disc.

The SP3 is intended for Xp to cope with the new development in hardware which causes the BSOD. Since M$ can't take the already-sold installation disc back it only allows you to download it for free. How to incorporate it into your installation disc is your problem. However there are many Internet howtos to teach you how to slipstream sp3 into the installation disc. It is a 15 minutes job but most of them are written for M$ users using a M$ Windows. The short cut is to buy a Xp with SP3.

Last edited by saikee; 05-19-2009 at 08:09 PM.
 
Old 05-19-2009, 08:22 PM   #7
stevewm
LQ Newbie
 
Registered: May 2009
Posts: 5

Original Poster
Rep: Reputation: 0
let me try to make this as simple as possible so as to not confuse you further.

Is there a way I can fix my hard drive? If no please say so and i'll be on my way. Oh and i did not fix fixmbr I wiped mbr clean the same thing i want to do with boot.ini if possible.
 
Old 05-19-2009, 08:43 PM   #8
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
Look you are confusing yourself. A blue screen got nothing to do with the hard drive. The blue screen is caused by loading an old Xp installation disc to a computer that since has some new hardware added or not using the original installation disc.

If you could installed a Slackware into your hard disk then there is nothing to be fixed. The disk has to be healthy in order to be able to store and run an operating system. Got it ?

If your Slackware is loaded with ntfs-3g you can use the "mkntfs /dev/sda?" command (?=partition No) to format it into a ntfs partition, open "kwrite" the editor, browse the Internet, copy and paste the content of the "boot.ini" and save it under the name of boot.ini. There you have boot.ini inside your hard disk if you think this could cure it.

I am bending backward to paste the content of the Microsoft site boot.ini here so that you save one less click
Code:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
I even highlight it red to show you it is intended for partition 1 so you can change it to suit your case.

Edited------------

boot.ini can be inside a fat32 partition that you can always created in any Linux like Slackware by command
Code:
mkdosfs -F32 /dev/sda?
. Therefore you don't need to have inside Slackware "ntfs-3g" with which you can write on a ntfs partition.

Last edited by saikee; 05-19-2009 at 08:48 PM.
 
Old 05-19-2009, 09:15 PM   #9
stevewm
LQ Newbie
 
Registered: May 2009
Posts: 5

Original Poster
Rep: Reputation: 0
actaualy it has nothing to do with xp period....i'm needing the sata drivers which i don't have of course
 
Old 05-20-2009, 03:03 AM   #10
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
Typical. Never honest about the real problem or do not understand it. Changing position all the time.

Sata drivers are supplied by the motherboard manufacturers and always available at their sites.

Also the sympton of no Sata driver is the Xp installer will report "No disk found" when being asked to install. Modern Linux are always preloaded with Sata drivers.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
How To:fixing Grub Re-install After Mbr Recovery In A Fedora/windows Multiple Boot DOTT.EVARISTI Fedora 8 06-01-2008 05:36 AM
fixing mbr on usb i_s Linux - Newbie 4 12-20-2007 05:50 PM
Attempted Dual Boot of XP and Fedora. Now MBR will boot straight to Linux.How to fix? mdorries Fedora 7 05-27-2007 07:22 AM
Fixing Windows MBR with Knoppix dbough Linux - Newbie 5 04-22-2007 06:53 AM
fixing my mbr bernstein Linux - General 7 06-30-2005 11:24 PM


All times are GMT -5. The time now is 09:56 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration