Discussion
Running XP and when my PC boots it splashes up Invalid Boot.ini
I get a splash screen with a system configuration utility when I go in, once I cancel that the PC runs fine except I don't want most of the startup programs to run. If I use msconfig and uncheck the boxes of the ones I don't want next time I boot I'm back to square one.
Did someone here post a really cool link to a sort of PC support site/forum ?
I get a splash screen with a system configuration utility when I go in, once I cancel that the PC runs fine except I don't want most of the startup programs to run. If I use msconfig and uncheck the boxes of the ones I don't want next time I boot I'm back to square one.
Did someone here post a really cool link to a sort of PC support site/forum ?
You'll find boot.ini is a text file hidden in the root of the system partition of your machine. If you could post the contents of that file on this thread it should be easy to spot the mistake. As far as running programs on logon, the easiest way to stop it doing that is deleting the keys from the registry.
DJ
DJ
The boot.ini you're interested in is in the root of your system drive (it'll be hidden from view unless you allow system files to be viewed in explorer.exe)
type %systemdrive%\Boot.ini should do it from the command line.
Most startup applications are defined under:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
(one entry per app)
DJ
edited to add: msconfig.exe - new fangled tool which confuses the hell out of me, I always do things the old fashioned way! I believe it specifies an alternative boot.ini to be used but I've no idea of the details..
>> Edited by _DJ_ on Tuesday 27th January 19:00
>> Edited by _DJ_ on Tuesday 27th January 19:01
type %systemdrive%\Boot.ini should do it from the command line.
Most startup applications are defined under:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
(one entry per app)
DJ
edited to add: msconfig.exe - new fangled tool which confuses the hell out of me, I always do things the old fashioned way! I believe it specifies an alternative boot.ini to be used but I've no idea of the details..
>> Edited by _DJ_ on Tuesday 27th January 19:00
>> Edited by _DJ_ on Tuesday 27th January 19:01
Sounds like msconfig.exe is as reliable as it was on Windows 95 then (i.e not at all!).
Chances are you boot.ini file should read:
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP" /fastdetect
However, I wouldn't recommend you change it (because if I've got it wrong it will be difficult to revert back and it ultimately depends on how the OS was installed originally and your disk config). It's not actually doing any harm as it is, I'd just delete those keys from the registry and leave boot.ini well alone!
>> Edited by _DJ_ on Tuesday 27th January 19:47
>> Edited by _DJ_ on Tuesday 27th January 19:48
Chances are you boot.ini file should read:
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP" /fastdetect
However, I wouldn't recommend you change it (because if I've got it wrong it will be difficult to revert back and it ultimately depends on how the OS was installed originally and your disk config). It's not actually doing any harm as it is, I'd just delete those keys from the registry and leave boot.ini well alone!
>> Edited by _DJ_ on Tuesday 27th January 19:47
>> Edited by _DJ_ on Tuesday 27th January 19:48
Still no joy with this one DJ, not all the startup items that reside in the system tray are in that particular registry key and with no working boot.ini I still get the error message on startup, msconfig is a good tool really.....I'm sure someone posted a link to a cool pcsupport forum...anyone remember ??
Preeeciate ya
JC
Preeeciate ya
JC
The App suggested by TJA looks just the ticket; startup items are a result of a number of different registry/disk items and you've only looked at one so far. The chances are the other items are probably in the user's profile (check Start Menu -> Programs -> Startup). If you must fix the boot.ini you can test the boot.ini file I entered above by:
1) Formatting a floppy disk
2) Creating a boot.ini file on that floppy with the contents I posted above
3) Copying NTLDR and NTDETECT.COM from the root of your C: Drive (they are system files so the normal caveats apply about making them visible).
4) Rebooting the machine from the floppy
In my opinion, your issues have been caused by msconfig.exe so I wouldn't rely on it to fix your problem.
DJ
edited to add: If that works you can then copy the boot.ini to your live copy on your HDD and the error msg should nolonger be shown on boot
>> Edited by _DJ_ on Saturday 31st January 21:28
1) Formatting a floppy disk
2) Creating a boot.ini file on that floppy with the contents I posted above
3) Copying NTLDR and NTDETECT.COM from the root of your C: Drive (they are system files so the normal caveats apply about making them visible).
4) Rebooting the machine from the floppy
In my opinion, your issues have been caused by msconfig.exe so I wouldn't rely on it to fix your problem.
DJ
edited to add: If that works you can then copy the boot.ini to your live copy on your HDD and the error msg should nolonger be shown on boot
>> Edited by _DJ_ on Saturday 31st January 21:28
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff