Search

 
 Join the Community, Create an EVE-ONLINE account or log in.

open All Channels
sepopen Issues, Workarounds & Localization
blankseplocked Be Carefull Installing Premium Upgrades
 
This thread is older than 90 days and has been locked due to inactivity.

New Topic   
 
Pages: [1] 2 3

Author Topic

Lunaz
Posted - 2007.12.06 02:31:00 - [1]
 

Just figured i would warn everyone that installing the premium files can cause serious system errors.

I just recieved the following upon restart after instalation.

Windows could not start because the following file is missing or corupt:
<windows root>\system32\hal/dll

Please re-install a copy of the above file

and sense it cant load in regular mode OR even safe mode no way to go expcept most likely a fresh re-instal of the OS.

so be warned.... please note everything was downloaded correctly and nothing else altered other than the instalation.

Phoenix Allfire
Posted - 2007.12.06 02:35:00 - [2]
 

If you created the system restore point as standard with any installation of any software and hardware, all you need to restore back to that point .... 5 minutes tops, depending on how old the system is.

Lunaz
Posted - 2007.12.06 02:36:00 - [3]
 

cant from the startup that i seen im afraid so system restore aint an option.

atm i am trying to boot from cd to see what i can do

Phoenix Allfire
Posted - 2007.12.06 02:38:00 - [4]
 

F11 or F8? Could always run the administrator from the windows xp cd and do it that way :)

Lunaz
Posted - 2007.12.06 02:39:00 - [5]
 

funny thing is i pop in my windows xp disk and its saying it cant even find a copy of windows on there...... so much for this update. <cries

CCP Mindstar

Posted - 2007.12.06 02:43:00 - [6]
 

This article from Microsoft should be of assistance to those having issues with boot.ini and hal.dll errors when starting Windows.

Lunaz
Posted - 2007.12.06 02:48:00 - [7]
 

thanks for the link checking it out now

Lunaz
Posted - 2007.12.06 02:57:00 - [8]
 

so far its not letting me follow those instructions as its asking for an admin password which i didnt set or if i did none of the passwords i always use work but still trying.... even changed the admin password and it wont acknowledge it /shrug

man i need eve <cries

Lunaz
Posted - 2007.12.06 03:04:00 - [9]
 

YES YES YES its alive ALIIIIIIIVE

thanks so much for your help you 2 and especialy for that link.

Turns out there was no password so i just had to hit enter LOL but ya it fixed it.... again my thanks.

Very Happy

Aaron Sylasta
Posted - 2007.12.06 04:02:00 - [10]
 

Just posting to say I'm getting the boot.ini thing as well. I'd be interested in knowing what this patch is doing to my computer that involves messing up an important system file like that Confused

Lord MuffloN
Caldari
Caldari Provisions
Posted - 2007.12.06 04:09:00 - [11]
 

Originally by: CCP Mindstar
This article from Microsoft should be of assistance to those having issues with boot.ini and hal.dll errors when starting Windows.


Not possible to fix boot.ini when we're still in Windows? (Haven't rebooted yet, oh and, good ****ing going CCP!)

Takitimu
Posted - 2007.12.06 04:10:00 - [12]
 

I've got the same problem as well, fyi

Lunaz
Posted - 2007.12.06 04:21:00 - [13]
 

i was wondering what it was doing in there as well /shrug.

but just follow those instructions and it fixes it NP.

BUT you must use your OS instal disk to get there so if you dont have it then its not good.

Jinli mei
Collegium Mechanicae
Dominus Bellorum
Posted - 2007.12.06 04:29:00 - [14]
 

Edited by: Jinli mei on 06/12/2007 04:55:37
Edited by: Jinli mei on 06/12/2007 04:54:38
Originally by: Lord MuffloN
Originally by: CCP Mindstar
This article from Microsoft should be of assistance to those having issues with boot.ini and hal.dll errors when starting Windows.


Not possible to fix boot.ini when we're still in Windows? (Haven't rebooted yet, oh and, good ****ing going CCP!)


Well, there's a way to toy with it.

edit: apparently there's an obscenely easier way to do this, see this post.

im keeping this here in case the backup happens to be missing for whatever reason.

**** THIS MAY NOT WORK AND IS NOT RECOMMENDED FOR PEOPLE WHO AREN'T FAMILIAR WITH WHERE THE STEPS TAKE YOU ****

Be warned: I am not taking responsibility for further messing up your system. Be careful, be wise! If this seems a little trick to you don't do it.

This will only work for Windows XP Professional as I am using tools only found in XP Professional. In all reality, you should be booting into the repair console for this!


1. Go to start, right click on 'My Computer' and click Manage.
2. Once the management console is open, go to Disk Management. It could take a few seconds to load.

In the disk management you have two parts: A top part indicating all the partitions and driver letters, and a bottom part showing you the partitions and drives ordered by disk number, and then by partition locations.

3. Find what disk number your windows installation is on (for example, mine is on the C: partition, the first partition on disk 0)

Disk 0 Partition 1 should be the typical location where your windows install is. However, I can't possibly guarantee this is it.

5. Open up notepad (start, run, notepad, click ok) and paste in the following:
Quote:
[boot loader]
timeout=30
default=multi(0)disk(YOUR DISK #)partition(YOUR PARTITION #)\WINDOWS
[operating systems]
multi(0)disk(YOUR DISK #)rdisk(0)partition(YOUR PARTITION #)\WINDOWS="Microsoft Windows XP Professional" /fastdetect


There are two things you should notice: disk() and partition(). now set these to what you discovered in step 3, and set them both for the default switch and the operating system entry.

7. Save your boot.ini on the installation drive
8. Click Start, Run, and type in MSCONFIG
9. Select the "BOOT.INI" tab
10. Click "Check all Boot Paths"

If it gives you the OK, you should be in the clear. If it says the boot path is invalid, I recommend taking a few steps back and playing with the boot.ini more.

This is the process I did to get mine back. It will likely differ from yours, so fair warning.

Aaron Sylasta
Posted - 2007.12.06 04:30:00 - [15]
 

Edited by: Aaron Sylasta on 06/12/2007 04:30:31
Originally by: Lord MuffloN
Not possible to fix boot.ini when we're still in Windows? (Haven't rebooted yet, oh and, good ****ing going CCP!)

Looks like it is possible, actually.

http://support.microsoft.com/kb/289022/

Edit: Dang, beaten

Lord MuffloN
Caldari
Caldari Provisions
Posted - 2007.12.06 04:42:00 - [16]
 

Originally by: Jinli mei
Originally by: Lord MuffloN
Originally by: CCP Mindstar
This article from Microsoft should be of assistance to those having issues with boot.ini and hal.dll errors when starting Windows.


Not possible to fix boot.ini when we're still in Windows? (Haven't rebooted yet, oh and, good ****ing going CCP!)


Well, there's a way to toy with it.

**** THIS MAY NOT WORK AND IS NOT RECOMMENDED FOR PEOPLE WHO AREN'T FAMILIAR WITH WHERE THE STEPS TAKE YOU ****

Be warned: I am not taking responsibility for further messing up your system. Be careful, be wise! If this seems a little trick to you don't do it.

This will only work for Windows XP Professional as I am using tools only found in XP Professional. In all reality, you should be booting into the repair console for this!


1. Go to start, right click on 'My Computer' and click Manage.
2. Once the management console is open, go to Disk Management. It could take a few seconds to load.

In the disk management you have two parts: A top part indicating all the partitions and driver letters, and a bottom part showing you the partitions and drives ordered by disk number, and then by partition locations.

3. Find what disk number your windows installation is on (for example, mine is on the C: partition, the first partition on disk 0)

Disk 0 Partition 1 should be the typical location where your windows install is. However, I can't possibly guarantee this is it.

5. Open up notepad (start, run, notepad, click ok) and paste in the following:
Quote:
[boot loader]
timeout=30
default=multi(0)disk(YOUR DISK #)partition(YOUR PARTITION #)\WINDOWS
[operating systems]
multi(0)disk(YOUR DISK #)rdisk(0)partition(YOUR PARTITION #)\WINDOWS="Microsoft Windows XP Professional" /fastdetect


There are two things you should notice: disk() and partition(). now set these to what you discovered in step 3, and set them both for the default switch and the operating system entry.

7. Save your boot.ini on the installation drive
8. Click Start, Run, and type in MSCONFIG
9. Select the "BOOT.INI" tab
10. Click "Check all Boot Paths"

If it gives you the OK, you should be in the clear. If it says the boot path is invalid, I recommend taking a few steps back and playing with the boot.ini more.

This is the process I did to get mine back. It will likely differ from yours, so fair warning.


It works under WinXP Home as well

Coniglietta Magica
Posted - 2007.12.06 04:52:00 - [17]
 

c:\windows\pss\boot.ini.backup

copy this to c:\boot.ini

if it says access denied. edit the boot.ini and copy the content of boot.ini.backup to it.

Kasheem Cetanes
Optimus Crime.
Triumvirate.
Posted - 2007.12.06 05:02:00 - [18]
 

Or Use msconfig >.>

Preston FateForger
Caldari
Cutting Edge Incorporated
RAZOR Alliance
Posted - 2007.12.06 05:08:00 - [19]
 

Edited by: Preston FateForger on 06/12/2007 05:09:38

This is a serious error.

Fixes had better work.

Aperion Madante
GoonFleet
GoonSwarm
Posted - 2007.12.06 05:11:00 - [20]
 

Edited by: Aperion Madante on 06/12/2007 05:19:57
The straightforward way to get Windows to create a new boot.ini file is as follows:

Go to control panel -> system -> advanced -> and click on settings under startup and recovery. If it pops up with an error saying it can't find boot.ini you need to fix it.

Copy and paste the boot.ini files as shown several posts above, taking into account your version of Windows (Home/Professional) and what drive/partition it's on.

Taraq Zell
Posted - 2007.12.06 05:15:00 - [21]
 

It's my understanding that this is only an issue that is affecting people who have Windows installed in a non-standard way? Because I have the premium content patch installed, and I turned off my laptop and everything afterwards. Booted it up a few minutes ago, no error greeted me like everyone is saying...

Maybe it's because I don't have EVE installed to C:/Program Files, but rather to C:/Games?

Shar'Tuk TheHated
Posted - 2007.12.06 05:16:00 - [22]
 

Does this only apply to people with XP or Vista as well?

Epoch
Earth A.D.
Posted - 2007.12.06 05:25:00 - [23]
 

Edited by: Epoch on 06/12/2007 05:25:20
Originally by: Taraq Zell
It's my understanding that this is only an issue that is affecting people who have Windows installed in a non-standard way? Because I have the premium content patch installed, and I turned off my laptop and everything afterwards. Booted it up a few minutes ago, no error greeted me like everyone is saying...

Maybe it's because I don't have EVE installed to C:/Program Files, but rather to C:/Games?


no. it's affecting everyone. the eve file boot.ini is replacing the system file. to check if you have it. either start -> search -> all files and folders (select more advanced options and choose to search for hidden files & folders) -> search for "boot.ini". it should be on the c: drive. just because it affecting you does not neccesarily mean you're going to have reboot/boot problems.

other way is start -> run -> msconfig. there should be a boot.ini tab.

ccp - you guys should call attention to this. this is a big foul up.

other than that, trinity is awesome. Wink

Ayane Shardmoor
Minmatar
Tribal Liberation Force
Posted - 2007.12.06 05:25:00 - [24]
 

Originally by: Aaron Sylasta
Just posting to say I'm getting the boot.ini thing as well. I'd be interested in knowing what this patch is doing to my computer that involves messing up an important system file like that Confused


When I installed the graphics upgrade, the first thing the patcher did was "Delete file: \boot.ini". This image shows specifically what I mean.

I got the missing boot.ini startup error after mucking about with the test server build a couple days ago. Put 2 and 2 together and figured the test patch must've done something. So this time around, I kept an explorer window open watching the C:\ root, while running the content upgrade patch, and voila! C:\boot.ini went bye-bye before my very eyes.

Perhaps CCP's QA team is in need of a little time out. Razz

Simon Monkoto
Evolution
IT Alliance
Posted - 2007.12.06 05:37:00 - [25]
 

Edited by: Simon Monkoto on 06/12/2007 05:41:47
I would think that running EVE (or at least the patcher) as a non administrative user should prevent this issue from happening. By default the boot.ini file is read only & hidden so unless EVE is somehow managing to run as a system process it shouldn't be able to touch the file.

Gralatus
Death Smiles
Posted - 2007.12.06 05:37:00 - [26]
 

I want to give a warm thank you for making my computer go totally fubar.

Thanks CCP. you're the best!!!!!!

Quarc
Copia-WarRages Armaments
Legion of xXDEATHXx
Posted - 2007.12.06 05:54:00 - [27]
 

Originally by: Ayane Shardmoor
Originally by: Aaron Sylasta
Just posting to say I'm getting the boot.ini thing as well. I'd be interested in knowing what this patch is doing to my computer that involves messing up an important system file like that Confused


When I installed the graphics upgrade, the first thing the patcher did was "Delete file: \boot.ini". This image shows specifically what I mean.

I got the missing boot.ini startup error after mucking about with the test server build a couple days ago. Put 2 and 2 together and figured the test patch must've done something. So this time around, I kept an explorer window open watching the C:\ root, while running the content upgrade patch, and voila! C:\boot.ini went bye-bye before my very eyes.

Perhaps CCP's QA team is in need of a little time out. Razz


Hum, while, not exactly afraid of it, I really do wodner how exactly did this "little" Messup happen?
I can jsut see a bunch of the non-techie people with only one comptuer wodnering why their comptuer won't start after the eve patch (althought not exactly is it often that people, certanly people not exactly knowing much about computers, won't connect game patch to sudden comptuer death) And, the ammount of poeple who are just wondering what to do...

:/
How did it happen? O.o

Zenara Merric
Posted - 2007.12.06 06:07:00 - [28]
 

im getting the same <windows root> \system32\hal.dll. file missing. This is ridiculous. I wonder how many ppl this has just happened to that cant access the forums to get this issue addressed. How much damage did this update do? I cannot boot windows XP from disk, and it wont let me do "copy C:\windows\pss\boot.ini.backup C:\boot.ini" it says path not found. I really dont want to have to reinstal everything cause i cant launch windows. CCP needs to adress this issue and not screw us over


SheriffFruitfly
Caldari
Posted - 2007.12.06 06:10:00 - [29]
 

Hah - this is nuthin. Just wait til the next patch when they put "format c:\" in the install script.

proclaimed HERETIC
Posted - 2007.12.06 06:14:00 - [30]
 

Edited by: proclaimed HERETIC on 06/12/2007 06:43:23
I put up a script on one of my domains that checks your boot.ini to see if it's still intact. Source to script is provided.

www.gamingassist.com

Put it right on the front page so no one can miss it.

-proclaimed HERETIC


Pages: [1] 2 3

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

New Topic