[Missing] boot.ini?

When my system has been off for a few hours or over night and I start it up it comes to the black screen that gives choices to start windows normally, safe mode, etc. rather than just loading Windows XP. When I choose to start Windows normally it continues and goes right into XP and will continue this going directly to Windows XP ever time when I either shut down or re-boot with no problem unitl the system is off for a few hours.

Due to this problem I have just reformatted my hard drive and re-installed Windows XP and thought I had the problem under control? Next morning when I started the computer it came back to the same black screen with the choises as I mentioned above.

I spoke to a technician locally and he told me to do a search for "boot.ini" (I made sure to check "Show hidden files and folders" in View.) I find no evidence of my system having this "boot.ini" file on my system.

Is there any workaround for my problem which I would bet is not having the boot.ini present?

Thanks so much,

 

It can’t be a missing boot.ini as you quite simply could not get in to Windows without it. You have to untick "Hide protected operating system files" before you can see it.

Can’t at this moment think what your problem might be, but if it only ever happens when the computer is cold, then I doubt its a Windows problem, more likely hardware.

 

John, we can easily verify/clear your boot.ini file.

Right click on My Computer > Properties > Advanced > Settings button in the Startup and Recovery area > Edit button. That will open the boot.ini file in Notepad. Copy the contents and paste them in your next post.

I doubt that the boot.ini file is your trouble since XP will actually boot without it. The XP MBR code is written so that if the boot.ini file is missing, it will search for the other necessary bootloader files (ntldr and ntdetect.com) on the root of the Primary HD.

Post back what you find and perhaps it will point the way.

 

Knock me down with a feather.

I can’t believe after all these years I didn’t know that! Had to just try it and sure enough "““Invalid boot.ini file "“ booting from C:\Windows\â€

It can’t be the MBR Surferdude, has to be ntldr itself. Mmm I wonder if this will work in Vista if the BCD is missing?

Huh, no…..â€an error occurred while attempting to read the boot configuration dat.â€

 

You're quite right McTavish, it's the MBR > NTLDR > boot.ini > et al...

Generally if the NTLDR is missing or corrupt, a specific error message appears that identifies it as the culprit. Therefore, I doubt the NTLDR is the culprit this time. I doubt the boot.ini is either. The absolute proof would be to make a "Quickboot" floppy that would use its own MBR, NTLDR, Boot.ini and NTDETECT.COM files. You can make one by running the XP Quick file. You'll need a floppy drive for or else download and WinImage it to a boot CD.

I suspect in John's case, there is something happening in the shutdown process that isn't sociable and causes the "Improper Shutdown" flag to be set. That's speculation though since he didn't report what I would expect to see at boot when that happens. The very fact that he can finally boot into Windows proves the bootloader files are there.

Perhaps he will post back with some more info.

 

boot.ini

First of all thanks so much to both of you for jumping on my problem so quickly.

I do had previously unchecked (unticked) the box that would block seeing the hidden operating system files.

I tried once more for a using M$ Search to find boot.ini and also boot*.* and boot.ini didn't surface. I then just checked in the root and there it was but it points to a printing type file application? But again it is labeled as boot.ini and here are the contents of this boot.ini. Still concerned about the M$ Search not finding this file?

[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 Home Edition" /fastdetect /NoExecute=OptIn

I hope perhaps the contents in the above might give you fellows some hint as to what is going on?

The local technician I spoke with told me that sometimes even though the hard drive is formatted it can still be corrupt? He mentioned that Gateway has a small file that would write the drive to 0's. He also did mention the "LDR" file you speak of and said that it might be corrupt and something about unpluging the hard drive? This conversation was on a street corner and I didn't have anything to write all this down so I am doing pertty well consdering my "senior moments "

As I mentioned in my origional post I am experiencing the same problem with this new install of Win XP Home as I was getting before I made the decision to strike the drive and reload XP

I have three hard drives in my computer Drive C, D, & E only drive E is partitoned into two eaqual partitions E & F. I have also check them to for possibly having something to do with this boot.ini

I am leaning more twards hardware problems with hard drive C -- I do allot of preventative daily maintenance to keep my equipment running tight. Drive sounds healthy but again that really doesn't mean that much -- I guess?

Again thanks so much to both of you fellows for your input and if you come up with anything else please respond.

 

John, Your boot.ini file is fine, no problem there. The fact that the MS Search tool doesn't find it is probably not significant either since that tool is famous for its shortcomings. I suggest you get AgentRansack for you future use, its free and widely used.

I suspect there is something amiss with your hardware that is confusing XP's NTLDR at startup. That would render the Windows Advanced Options Menu that you are getting. Try disconnecting all peripheral devices except the mouse and keyboard for a test. If no joy there, power down and disconnect all HD except the Primary and reboot for effect.

It'll take some process of elimination with a problem like this.

I doubt you have any bootloader problem but you can check that also by making a QuickBoot disk for your system. They're nice to have around anyway. Make an XP Quick Boot disk.

 

Yeah, nothing wrong with your boot.ini and agree it may be hard to find the cause.

Your MBR (Master Boot Record) is not actually a part of Windows and not a file John. It’s the boot code and partition table located on the very first sector of the hard drive and is hidden to you without special software to access it. When you reinstalled XP it would have been replaced anyway, so I don’t suspect a problem here. As you managed to reinstall XP ok then I also doubt any problems in your hard drive configuration or with file system errors or bad sectors on any of your drives. Such problems would most likely show on every boot and not just when the computer was cold "“ but worth checking for anyway. Right click on the drive in My Computer and select Properties>Tools and click the Error Checking button, put a tick in both boxes and click start. When you do the C: drive you will have to reboot for the checks to be carried out. Depending of the size of your hard drives it may take a little while.

 

On further thought, it wouldn't hurt to check the BIOS settings for anything out of the ordinary. Maybe replace the battery and reset to default settings. It might be that simple but if not, we have to eliminate all the easy stuff along the way. Since powering down overnight brings on the problem, it makes the battery suspect. Then it may also be some intermittent keyboard or controller problem since it's acting like you're pressing f8 on startup. It would seem that the problem is either thermally or time related.

Then there's the FIXMBR and FIXBOOT commands that XP provides if booted to a Recovery Console. I just throw that into the mix to cover all bases. They may not help you but it's chicken soup anyway.

Now you've got lots of tests to make so post back any results and perhaps someone can hit the nail more squarely.

 

missing boot.ini

Well fellows I am still at it but the problem presists. I have noticed that I don't have to wait till overnight for this situation to occur. I just shut down the system less than an hour ago and when I turned it on it came to the some black screen where start windows normally was highlighted.

Here is what I have done thus far. I decided to re-formatt both my D & E Drives from within Windows -- No Joy

I did as you suggested this morning and unplugged everything from the computer except for the Monitor, Mouse, & Keyboard - No Joy

I unplugged power from both drives D&E - No Joy

I insaalled another CR-2032 Battery which I am not sure of it's age so I am going out and buy another one today and then I am sure it will be fresh.

I downloaded the quick boot files but don't understand how to create a boot disk with what you gave me? A little help on this would be appreciated.

Surerdude2 I sure want to thank you for the link to Agent Ransack boy that program walks all over what Microsoft offers. I found the boot.ini and NTLDR files right off the bat.

My thought are leaning twards the battery situation the last time I bought a couple of these CR-2032 batteriss was about eight years ago.

Being that the computer looses it's mind in less than an hour this gets me wondering about the battery?

Keep you posted

 

Realised I haven't asked if shutting completly off and restarting within a few seconds is ok. Just rebooting from within Windows skips the early part of the POST process.

 

Just double click the downloaded file and it will ask you to put a blank floppy in your drive bay. The rest is automatic. Then use that floppy for a boot test. It should boot you into Windows and makes a fine diagnostic tool to clear any doubts about the normal HD contained bootloader files. It uses the MBR, NTLDR, NTDETECT, and Boot.ini contained on the floppy. If your problem persists when boot with this floppy, you can be sure that your HD bootloader files are not responsible.

Amen! Good luck.

 

missing boot.ini

McTavish (what a great name) to answer your question which I missed when checking the forum is that when I am up and running and I choose to re-boot the system it comes back into Windows just fine. Also if I shut it down after I have been in Windows it also again comes back just fine.

From what I am keeping track of when there is a time span of 30 minutes to an hour of being completely turned off and I boot up the system it comes into the "Windows Advanced Options" menu.

Superdude2 Well I installed a brand new fresh CR2032 - No Joy.

Thanks for the instructions in creating the boot disk -- I'm batting 100% -- I put a floppy in my drive and discovered that the blasted thing isn't even hooked up to power or cable. I found a cable and a power lead that fit but when I restated the system the floppy disk drive light was on constantly so I disconnected power and data cables from the drive. I am a clutz on the hardware end even though I retired from he computer business -- (thank God they never let me too close to the shop

I'm going to call a tech tomorrow to and have him set up the floppy correctly and then proceed on from that point.

While on this subject I have noticed that when this problem happens on posting I hear two soft clicks which sound to me like you might hear when a monitor is setting the timeing? I use a flat panel Samsung 172T which is hooked up both Analog and Digital into a ATI Radeon 9800 Pro.

Thanks again to both of you fellows for all you input -- although the problem isn't nailed down yet I have learned much from you both.

 

The floppy drive light staying on all the time is a sure sign that you have the ribbon cable plugged in backwards (classic symptom). They can be plugged on either way so reverse it (either end but not both )and it'll likely do fine.

There is an outside chance that you've got the wrong cable, since you say you "found" one. The proper one must have a twist in it. A straight point to point cable won't work.

 

So it’s definitely a temperature problem and the most common by far that occurs when a machine is cold is the many contacts of the graphics card "“ next would be the memory cards. Try removing and refitting the graphics card, or alternatively just wiggle it and make sure it is fully home. I’ve never seen it cause your problem, but you never know. If it makes no difference then do the memory cards. Is the clicking sound coming from the monitor or PC?

The common hard drive thermal errors occur once the drive warms up, so not applicable in your case. But it may still be worth downloading the drive manufacturer’s diagnostic utility "“ what make of drive is it?

 

John:

I've been following your thread with interest and have also been learning from two of the best on this board. In conjunction with what has been recommended, there are a couple of things that you might want to try while you are in that case - along with re-seating your 9800 Pro and your memory, you would be well advised to pull the memory and video card and clean the contacts with a clean pencil eraser by wiping downward in line (not across) with the contacts. Follow that with a little rubbing alcohol on a Q-tip and once dry, reseat them. This can help clean up oxidation that might interfere with connectivity. Your 9800 Pro also has a molex connector and you can connect/disconnect this a few times (machine unplugged and all power off) to clean or scratch up those contacts.

Stick with SD2 & McTavish - they'll get you squared way if anyone can. Should you bail out and go to your local shop, take a copy of this thread with you as it will help the technician tremendously.

Good Luck.

 

missing boot.ini

Hi guys,

Well I managed to get the floppy working and as you mentioned superdude2 I had the floppy cable on incorrectly. I use the braided round copper cables throughout my system for better air circulation (so couldn't see any twist but guess my guess that it was a floppy cable was correct)

Ran the quickxp.exe and copied both files to a freshly formatted floppy and changed the boot device to floppy and the compurter posted into a menu very briefly and then went right into Windows.

I wish my stardard boot off the hard drive was so quick to get into Windows? As I recall everything looked good on the information before it loaded Windows but I don't recall it seeing any of the hard drives twards the bottom of the screen?

Perhaps if you can advise me what to look for I can get you better feedback?

 

You're doing fine John.

The next logical step would be to shut the system down for a period of time that would normally cause your problem to occur. Boot with this floppy to see if you still have the problem. That could give us some further info and help point the way.

I hate to be pessimistic but I think you'll still have the problem. If it's a thermal intermittent hardware problem, you'll probably have to get it bench serviced by a sharp tech that knows how to use a heat gun and a can of chill blast.

Post back any results and I'll check in periodically. Others may have some ideas on this as well and are welcome.

 

missing boot.ini

Well fellows I'm still at it. I did in fact pull the video card and used a pencil eraser to clean the contacts but I did go from side to side rather than up and down on them with the eraser -- I then followed with Isopropal Alcohol and then when dry I reseated the video card.

I have not as yet snapped out the (2) 512 mb Crucial memory modules but will do that tomorrow. Checking the memory modules makes sense as the way this machine is behaving it almost acts like while it's up and running everything is fine but when powered down for even 30 minutes somthing seems to drain from it where it looses it's settings? That is why I changed out the CMOS battery right away here-to-fore.

I have per your suggestions also reset the CMOS to defaults using F5 again no joy doing this.

Boy the machine starts and goes right into Windows rock solid with when using the quickXP boot disk.

I wish my hardware knowledge were better but I am also wondering if the problem might lay in the hard drive controller? My M.B is the ASUS A7V-333 - Processor is AMD Athelon 2.1 Ghz running at 1733mhz

You might have noticed in my earlier post that the tech I did speak with told me that even though a hard drive is formatted the corruption can still be present and he told me about a small utility that Gateway has to write the drive to Zero's? I dread the thoutht of having to reformatt again an reinstall XP as I have so much information that I have to put back on the system once XP is installed and it turns into a 3 day episode for me -- my health isn't all the good and it really drains me down.

I sincerely hope I am not wearing out my welcome with you folks but all your feedback has really helped me allot and which ever way it turns out I think we will nail the problem.

 

Are you saying John that you don’t get the problem when booting from the floppy? It’s also definitely curious if as you say it boots better than it does on its own. If you hadn’t just reinstalled I would have been wondering about the boot records on the hard drive. I’m starting to wonder if it’s a partition problem. Can you take a screenshot of your drives in Disk Management and post it on the board or email it to me and I’ll post it.

Writing zeros to the drive (a zerofill) will remove everything, including Windows file errors and all the partition details and so any partition problems. It won’t repair bad sector problems. The error repair tests in Windows that I suggested earlier will take care of file errors and bad sectors, so a zerofill now will only remove partition errors.There are plenty of free zerofill apps around. If you want to test the hard drive/s you should download the manufacturer’s own diagnostic utilities. What make are they?

If we do get to the point where you want to zerofill or try another hard drive then you should copy or ‘clone’ Windows to one of your other drives, or at least make an image so you don’t have to reinstall XP and all your apps, but just restore the image.


Cheers Rockster