open All Channels
seplocked EVE General Discussion
blankseplocked If it's not broken ... (Warning inside!)
 
This thread is older than 90 days and has been locked due to inactivity.


 
Author Topic

Feilamya
Pain Elemental
Posted - 2007.12.06 23:42:00 - [1]
 

Edited by: Feilamya on 07/12/2007 00:37:53
So I downloaded the Trinity patch yesterday, installed it, restarted EVE and played. Then I logged off and shut down my PC. The next day, I booted my PC as usual and started EVE.

-- TO THIS POINT, EVERYTHING WAS FINE! --

Then on the login screen, I was greeted with huge popups telling me "DO NOT REBOOT!! We ****ed up your PC *te he* sorry for that and btw you have to visit THIS thread!!!"

So I visited the boot.ini thread, read the initial post, read it some more and couldn't decide whether I should be ****ed off or laugh about this amazing display of incompetence.

Then I checked my C:\ folder and yeah there was no boot.ini .

OH NOES! I'M DOOMED!! I CAN'T REBOOT ANY MORE!!!

Some hours later (reading the thread, reading Microsoft Knowledge Base articles, annoying ppl in ingame chats and changing my sig to the one you see below) and some more hours of playing EVE and wondering what the difference is (except in fps and lack of anti-aliasing) when I turn on HDR, I decided to fix the problem as described somewhere in the thread, get my Windows XP CD ready (just in case) and reboot.

And now I really had a problem: My Windows XP wouldn't boot any more.

I will spare you the details. It took me about half an hour to fix it, using the information from Microsoft and the CD, then everything was fine again.

Everything, except I still had no boot.ini in C:\. My Windows XP seems to be running just fine without one!

I know how to show hidden system files in explorer. No need to point that out to me, but thanks anyway

Obviously, it was *NOT* the EVE patch that killed my boot.ini - It was myself who broke my system by following the instructions in the thread and creating a bogus boot.ini file that prevented my system from booting.


--- CONCLUSION ---

This whole fuzz created by CCP and the community about the missing boot.ini and how to fix it is a huge load of *******s!

What do we learn from that?

If it's not broken, don't fix it!
Even if some ***** at CCP tells you to.

Thanks for your attention. And now please CCP, TURN OFF THOSE DAMN POPUPS!

Chr0nosX
Habitual Euthanasia
Cry Havoc.
Posted - 2007.12.06 23:52:00 - [2]
 

Edited by: Chr0nosX on 06/12/2007 23:59:31
Originally by: Feilamya

Everything, except I still had no boot.ini in C:\. My Windows XP seems to be running just fine without one!



Or maybe your just a moron and didn't realise you need to check show hidden files and untick hide operating system files.

Crumplecorn
Gallente
Eve Cluster Explorations
Posted - 2007.12.06 23:54:00 - [3]
 

Originally by: Chr0nosX
Edited by: Chr0nosX on 06/12/2007 23:52:23
Originally by: Feilamya

Everything, except I still had no boot.ini in C:\. My Windows XP seems to be running just fine without one!



Or maybe your just a moron and didn't realise you need to check show hidden files and untick hide operating system files.
Or maybe windows was booting using the backup boot.ini which worked because they have a standard setup, then created a proper one which was misconfigured and killed their system.

Cricketz
SMASH Alliance
Posted - 2007.12.06 23:56:00 - [4]
 

Im guessing you missed the "show hidden files" option. =) Thats funny.

Indical
Posted - 2007.12.06 23:56:00 - [5]
 

My own boot.ini has disappeared as well and the system still loads fine. I do however note that I have a backup copy of boot.ini on the system which I presume was created by xp itself at sometime - perhaps on a time when I set my system restore - not sure about that. My understanding of it is that XP will find that backup copy and use that instead.

I have however copied boot.ini to a floppy and have it in reserve should I need to install it into root c at a later date just to be safe lol

Jonny JoJo
Amarr
The Imperial Guards
Posted - 2007.12.06 23:57:00 - [6]
 

Originally by: Crumplecorn
Originally by: Chr0nosX
Edited by: Chr0nosX on 06/12/2007 23:52:23
Originally by: Feilamya

Everything, except I still had no boot.ini in C:\. My Windows XP seems to be running just fine without one!



Or maybe your just a moron and didn't realise you need to check show hidden files and untick hide operating system files.
Or maybe windows was booting using the backup boot.ini which worked because they have a standard setup, then created a proper one which was misconfigured and killed their system.


That sounds about right, since I know a lot of anti-virus software do that. Oh well, the irony!

umop 3pisdn
Minmatar
Fnck the blob.
Posted - 2007.12.07 00:02:00 - [7]
 

Originally by: Chr0nosX
Edited by: Chr0nosX on 06/12/2007 23:59:31
Originally by: Feilamya

Everything, except I still had no boot.ini in C:\. My Windows XP seems to be running just fine without one!



Or maybe your just a moron and didn't realise you need to check show hidden files and untick hide operating system files.


This post is correct post op is ******

Feilamya
Pain Elemental
Posted - 2007.12.07 00:02:00 - [8]
 

Edited by: Feilamya on 07/12/2007 00:14:17
Originally by: Chr0nosX
Edited by: Chr0nosX on 06/12/2007 23:52:23
Or maybe your just a moron and didn't realise you need to check show hidden files and untick hide operating system files.

No sir, you are a moron for not thinking before posting.

I said I created a boot.ini. If there had been a hidden one, I would have noticed it at that point, even if "Show hidden files" was disabled, and of course it wasn't.

There is no boot.ini on my system, there probably has never been one, and as long as there isn't one, everything is fine.

-----

Okay, maybe there really is a backup boot.ini file hidden (as in "buried", not "[x] hidden") somewhere in C:\WINNT that works.

And I'm fine with that, because I know this boot config will survive the next EVE patch.
Unless, of course, something unexpected happens. But who would expect such a thing from a company that cares more and works harder? ...

RetributionBitch01
Posted - 2007.12.07 00:10:00 - [9]
 

Back in the darks ages before Windows 1.0 ppl used batch files to switch programs using a menu.
Boot.ini is just the menu file for the ntloader program which switches to a partition and loads the boot sector of the partition which has the operating system you wish to run.
If boot.ini is not there ntloader will not know which partition boot sector to load.
However when windows installs it makes a copy of the original boot.ini in the install folder.
My system starts with the linux loader GRUB then I switch to boot.ini and ntloader,btw I have had no problems.

Kerfira
Kerfira Corp
Posted - 2007.12.07 00:15:00 - [10]
 

The boot.ini file is not only hidden, its also marked as a system file. Thus it's most likely not visible even if you turn 'show hidden files' on.

One way of checking it is starting a Command Prompt, and type the command:
type c:\boot.ini

This'll type out to the command prompt the contents of boot.ini if it's there, to say 'The system cannot find the file specified.' it it's not.

Katana Seiko
Gallente
Posted - 2007.12.07 00:16:00 - [11]
 

I totally agree with the popup. The first five times were funny. The other 99995 times it was annoying.

Oh, and I don't have a boot.ini anymore. I have 150$ spare and invested into Windows Vista Ultimate x64 Very Happy

Tortun Nahme
Minmatar
Umbra Synergy
Posted - 2007.12.07 00:17:00 - [12]
 

Don't worry people

Experts have diagnosed the OP with epic fail, medical technicians are enroute for euthanising procedures

Feilamya
Pain Elemental
Posted - 2007.12.07 00:19:00 - [13]
 

I have GRUB installed too and had no problems ...
However, I don't see how GRUB could make a difference (you didn't claim it would, I know). GRUB invokes ntloader and then ntloader does the usual thing ... or am I wrong?


 

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only