Edit Boot.ini whitout logging in

[Frejoh466]

Can I edit the Boot.ini in the recovery tool?

I don't know why but I wasn't able to start my computer so I fooled around and fund that the Boot.ini was corrupted. So can I edit it somehow? I was trying whit this is in the recovery tool

bootcfg /rebuild
Y
[Random name]
/fastdetect

But it wont work, I just get more errors instead of the Hal.dll error, I have been here and there to find a way to restore the boot.ini but I can't get it to work. But I found out why I got the error in the first place, I had partition(1) whit 2 partition and the first one was just dummy data, and the second one was the real one...

So can I increase the number of partition showing or add the C: drive to the boot.ini, I ain't the god over the recovery tool or the things need to make XP to run...

So any help would be good.

[patio]

Did you save a copy of the Boot.ini ? ?

[Frejoh466]

yea I have a backup on my desktop. It is old but I think it will still work

[patio]

Rename the current boot.ini to boot.old....

Then copy the 1 from the desktop to the appropiate directory and re-boot.

[Frejoh466]

Whit the text who say "Edit Boot.ini without logging in" you can guess that I can't login to my computer. I might should have been clearer on that point.

[dahlarbear]

Can I edit the Boot.ini in the recovery tool?

Can you "currently" boot to the Windows XP Recovery Console?

Do you have a "working" floppy or CD drive?

[patio]

Well you would need to have pretty decent command-line skills to do it and need to know the exact location of the files you want to edit...

Recovery Console Commands...

This would entail booting to the XP CD and choosing the 1st option to load the RC.

The other option would be to pull the drive and hook it up as a slave drive in another working machine.

[Frejoh466]

Can you "currently" boot to the Windows XP Recovery Console?

Do you have a "working" floppy or CD drive?

If I wasn't able to boot whit Windows XP Recovery Console, how would I be able to get in to the recovery tool?

@patio
I really don't need to make the ini file exact as before just so I can login to the computer would be good. Then I can fix the problem easy

[patio]

If I wasn't able to boot whit Windows XP Recovery Console, how would I be able to get in to the recovery tool?

This doesn't make sense...when booting to the XP CD and loading off the RC the HDD is not initialised...

[Frejoh466]

Edit:
Ok lets start over.

1.Can I login some how when the boot.ini is corrupted?
2.Can I fix the Boot.ini in the Windows recovery console?
3.Can I fix the problem somehow or do I need to reinstall Windows?

Would be glad if someone answer this  and tell me the solution.

[BC_Programmer]

Edit:
Ok lets start over.

1.Can I login some how when the boot.ini is corrupted?
2.Can I fix the Boot.ini in the Windows recovery console?
3.Can I fix the problem somehow or do I need to reinstall Windows?

Would be glad if someone answer this  and tell me the solution.

1. No.
2. maybe
3. no.

as a last resort you could delete boot.ini. this you can do from the recovery console. I don't think you can edit it, though, but you can rebuild boot.ini as well using recovery console commands.

[patio]

Boot to the Recovery Console and make the neccessary changes suggested above...

[Geek-9pm]

Re: Edit Boot.ini whiteout logging in

Simple answer is no.
But if you have another way of starting another OS, or another copy of the same OS, yes you can.

Some Linux versions can run off of a 'Live CD' and require no installation on the HDD. Using that , you can edit the BOOT.INI, if you know where it is and know how to mount the volume.

As for me, I find it easier to just swap another  HDD with the OS into the master position and slave the other. Then it is rather easy to do.

BTW. If you know the OS is on the first partition, and you know it is active, you maybe able to just delete the BOOT.INI  and it may  boot anyway.

[patio]

Boot to the Recovery Console and make the neccessary changes suggested above...

[Frejoh466]

Ok how can I delete the boot.ini when I just get acnes deny?

[dahlarbear]

Use the Recovery Console "attrib" command to modify whichever file attributes are preventing you from deleting it.

Try "attrib -H -S -A -R boot.ini".

[Frejoh466]

I keep getting that it's not a valid kommand.

and after (or if) I delete it, I just do

Bootcfg /rebuild
Y
[Random name]
/Fastdetect

and restart? or dose the computer generate a new .ini file?

[dahlarbear]

1.  Attrib command.  Yeah...  I'm also getting "invalid" message when attempting to modify multiple attributes on same command.  Changing one attribute at a time seems to work however.

2.  Bootcfg /rebuild.  I assume it generates a new "boot.ini".  I don't know if you need to "delete" the old one first.  You can use Recovery Console "copy" or "rename" command to back it up first.  For example:  "copy boot.ini boot.old" or "rename boot.ini boot.old".

Note:  If your "Windows" installation is at the default directory "Windows" on the default partition "partition1" on the default boot drive "\Device\Harddisk0"; you don't need a "boot.ini".  NTLDR should default to that location for the operating system files.

3.  Restart.  You don't "restart", you type "exit" command from Recovery Console and the system should automatically reboot.

4.  Map command.  The Recovery Console "map" command shows the device letter assignment it uses.  This may differ from the letter assignment of a "normal" boot.

How many partitions does it show on "Device\Harddisk0"?

5.  Alternate Boot Device.  You can place the Windows XP boot files:  NTLDR, NTDetect.com, and boot.ini on an alternate device and still boot to the hard drive operating system (if boot.ini points to appropriate location on hard drive).  You need a Windows XP volume boot record on that device that points to NTLDR as the bootloader program.  For a floppy disk, you "format" the floppy on a Windows XP system which places the appropriate volume boot record on it; then copy the NTLDR, NTDetect.com, and boot.ini files to it.  This is not an MS-DOS boot floppy; it's a Windows XP boot floppy (if done correctly).

[Frejoh466]

3.  Restart.  You don't "restart", you type "exit" command from Recovery Console and the system should automatically reboot.

Translations

Present participle
restarting

to restart (third-person singular simple present restarts, present participle restarting, simple past and past participle restarted)

   1. To start again.

   2. (computing) to reboot.



now when we know what restart mean you can try to clear out what you did just say.

Or if you for some strange reason you thought I would under stand what you did just say, Imagen that you are in windows recovery console tell me what exactly you do to restore the boot.ini

Thanks

[BC_Programmer]

Translations

Present participle
restarting

to restart (third-person singular simple present restarts, present participle restarting, simple past and past participle restarted)

   1. To start again.

   2. (computing) to reboot.



now when we know what restart mean you can try to clear out what you did just say, becuase that you said did not help a bit.

Or if you for some strange reason you thought I would under stand what you did just say, Imagen that you are in windows recovery console tell me what exactly you do to restore the boot.ini

Thanks

you have plenty of information to do that. read the posts.
the quote you mentioned was stating that you typed exit to restart. that's it.

[Frejoh466]

yea I forgot to and "and then I restart?

But still whit all the information you guys have posted none of them have helped on my problem well

Edit:
Ok lets start over.

1.Can I login some how when the boot.ini is corrupted?
2.Can I fix the Boot.ini in the Windows recovery console?
3.Can I fix the problem somehow or do I need to reinstall Windows?

Would be glad if someone answer this  and tell me the solution.

1. No.
2. maybe
3. no.

as a last resort you could delete boot.ini. this you can do from the recovery console. I don't think you can edit it, though, but you can rebuild boot.ini as well using recovery console commands.

is the only who have cleared up things but still...

Btw sorry if I seem to be a little rude, I am very grateful for the help. I have some work on the computer and I am a little frustrated for that.


Edit:
Unbelievable I made some progress. I did

cd C:\
attriv -h-s-a-r  boot.ini 
del boot.ini

so the boot.ini is gone but I can't rebuild it.

bootcfg /rebuild
Y
[Random name]
/fastdetect
fixboot

but it wont work... anyone know?

Edit2:
If I don't get the computer to run in 24h I reinstall the whole thing.

Edit3:
Ok how can I move my file in "C:\Documents and Settings\***\Skrivbord\boot.ini" to "C:\boot.ini" ?
copy "C:\Documents and Settings\***\Skrivbord\boot.ini" dose not work get a error that it's a invalid command

also can I move a huge important file from C:\ to a USB or something in windows recovery console?

Edit4:
Can I see what driver my USB are on?

Edit5:
I found http://support.microsoft.com/default.aspx?scid=kb;en-us;305595&sd=tech so,

Edit:
Ok lets start over.

1.Can I login some how when the boot.ini is corrupted?
2.Can I fix the Boot.ini in the Windows recovery console?
3.Can I fix the problem somehow or do I need to reinstall Windows?

Would be glad if someone answer this  and tell me the solution.

1. No.
2. maybe
3. no.

as a last resort you could delete boot.ini. this you can do from the recovery console. I don't think you can edit it, though, but you can rebuild boot.ini as well using recovery console commands.

so the right should be

1.Yes, If you have a exact copy on a working boot.ini for your computer.
2.probably, but no one knows how.
3.You could be able to fix it, but it will probably end whit your Windows CD in your computer and reinstall the whole thing.

[patio]

Rename the current boot.ini to boot.old....

Then copy the 1 from the desktop to the appropiate directory and re-boot.

[Frejoh466]

and how can I do that?

It's like telling your pet to go and get you a drink. I'm 99% sure nothing will happen

[Geek-9pm]

Example:
Here is an invalid BOOT.INI  file.

[boot loader]
timeout=8

This will give error message because the rest of the file was blank.

Invalid BOOT.INI file
Booting from C:\WINDOWS\

Then it will start the OS on the active partition.
If your configuration is typical.

VERY  IMPORTANT: BOOT.INI must not be changed to BOOT.INI.txt or it will not work.

[Frejoh466]

You do still know I can't get in to my computer to Change, edit, move files. I am still stuck, so I can't login to the computer.

Edit:
Btw can you change a boot.ini to use partition2 and or 1?

I found that E: is my main and not C: so my Windows folder is on partition2, anyone say a boot.ini who will start whit partition2

both

Code: [Select]

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

and

Code: [Select]

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect


Code: [Select]

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

dose not work

[dahlarbear]

1.  Recovery Console Restrictions.  From Description of the Windows XP Recovery Console:

Restrictions and limitations of the Recovery Console
When you use the Windows Recovery Console, you can use only the following items:
     •   The root folder
     •   The %SystemRoot% folder and the subfolders of the Windows installation that you are currently logged on to
     •   The Cmdcons folder
     •   The removable media drives such as the CD-ROM drive or the DVD-ROM drive

Note If you try to obtain access to other folders, you may receive an "Access Denied" error message. Also, when you are using the Windows Recovery Console, you cannot copy a file from the local hard disk to a floppy disk. However, you can copy a file from a floppy disk or from a CD-ROM to a hard disk, and you can copy a file from one hard disk to another hard disk.

Note:
     a.  You don't have access to "C:\Documents and Settings\***\Skrivbord\boot.ini".
     b.  You aren't permitted to write to "removable" drives (floppy, CD, USB), but you may read from them.

2.  Map Command.  Use the recovery console "map" command to determine what devices are known to it and how the drive "letters" are assigned.  The assignment may differ from that of a normal boot, so check it.

3.  Boot.ini.  If the "Windows" directory for your operating system is on the second partition, I believe the following code is correct:

Code: [Select]

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect


Note:
     a.  For test purposes, you may add additional lines under [operating systems] with different invocations or boot options.  See Custom Boot Menu in Windows XP.  For example:

Code: [Select]

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="WinXP - Part_1" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="WinXP - Part_3" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="WinXP - Part_4" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Safe Mode" /safeboot:minimal /sos /bootlog /noguiboot

The only way to "edit" boot.ini from within recovery console is to use the "bootcfg" command with the appropriate option switches.  Otherwise you need to import new version of file from a "removable" device (floppy, CD, USB).  I don't know if you could access it from a "mapped" network drive.

4.  bootcfg /rebuild.  I don't know why you're having problems with this recovery console command.  Perhaps there's an underlying problem with your system that prevents it from working correctly.  See If you can’t boot windows or recovery console after you edit the boot.ini.

5.  Data Recovery.  Standard operating procedure (SOP) to recover data files is to slave the hard drive to working computer system and attempt to "read" and backup the files from there.  You shouldn't write to partition (or hard drive) if you need to preserve the data.  Another option is to boot to a Live CD (e.g. Ubuntu 9.10 or various rescue disks) and use that operating system to read and backup the data you need (to floppy, CD, DVD, USB, another hard drive).

[Frejoh466]

Thanks for the replay, but nothing did help.

But can you see if the file exist on the hard drive? Because I thing the boot.ini dose not longer exist on the C: drive.

Code: [Select]

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="WinXP - Part_1" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="WinXP - Part_3" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="WinXP - Part_4" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Safe Mode" /safeboot:minimal /sos /bootlog /noguiboot

on "multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect" I got a Hal.dll error, and the other I got that Windows didn't exist... So would it somehow be a Hal.dll error, and not the boot.ini?

Edit:
I saw that I got C: and E: drive, there E: is main whit 10gig, and C: is second whit 790gig, can I install Windows in E: and then login whit E: and have acnes to the C: drive? or will I just get massive error's?

Edit2:
Whit

Note:
     a.  You don't have access to "C:\Documents and Settings\***\Skrivbord\boot.ini".

dose that mean I can't even read it?

[dahlarbear]

1.  Boot.ini File.  Normally, the "active" primary partition (system) is the "C:" drive and this file would be at "c:\boot.ini".  I think it's there and any (or all) of the following should verify this if done at "C:\>" prompt:
     a.  dir boot.ini
     b.  type boot.ini
     c.  bootcfg /list

To navigate to "C:" drive or its root directory, just enter "C:" from wherever you are.  To return to Windows installation directory, you may use "systemroot" command.

Not sure if you may access from "C:\Windows>" prompt using:
     d.  dir c:\boot.ini
     e.  type c:\boot.ini

2.  Hal.dll File.  My guess is it's not the "boot.ini".  Not sure about the "Hal.dll" file.  Have you modified or replaced this file recently?  If not, don't...  There are seven different versions of this file (all with different external file names).  When the system is first installed, the correct one for your hardware configuration is selected from the installation source and renamed to "hal.dll".  If you've replaced this file, we'll have to figure which one it should have been.

3.  "systemroot" Command.  This recovery console command takes you to the Windows installation directory.  If you enter "systemroot" command, what does the command prompt look like; e.g. "C:\Windows>"?

4.  Partitions.
     a.  With "map" command, can you verify this is what you have?
          E:       10 GB   Device\Harddisk0\Partition1
          C:    790 GB    Device\Harddisk0\Partition2

     b.  Is this a brand name computer; e.g. Dell, HP, Gateway, Acer; or a custom build?  Brand name computers frequently ship with preinstalled operating system and a separate restore/recovery partition.

     c.  The "E:" drive might be a "Restore/Recovery" partition.  Until we know what it is and why it's there, I think you should leave it alone.

5.  Chkdsk.  I'm not clear on how we got to the "boot.ini" file.  Normally, when you have a system boot problem, one of the first things you try is to verify and attempt to fix/repair the integrity of the file system.  This may be done from recovery console using the "chkdsk" command.  It can take a long time to run.  If problems are found, it can take even longer.  This program was not designed to be interrupted - so don't (or you could corrupt the file system).  Let it run to completion, possibly overnight.  Execute the following command:  "chkdsk c: /p /r"

[Frejoh466]

1.  Boot.ini File.  Normally, the "active" primary partition (system) is the "C:" drive and this file would be at "c:\boot.ini".  I think it's there and any (or all) of the following should verify this if done at "C:\>" prompt:
     a.  dir boot.ini
     b.  type boot.ini
     c.  bootcfg /list

a. the file is in C:\Windows\boot.ini
b. did not work
c. No start alternative could show

and I have to login to the C: drive when I get to the console

2.  Hal.dll File.  My guess is it's not the "boot.ini".  Not sure about the "Hal.dll" file.  Have you modified or replaced this file recently?  If not, don't...  There are seven different versions of this file (all with different external file names).  When the system is first installed, the correct one for your hardware configuration is selected from the installation source and renamed to "hal.dll".  If you've replaced this file, we'll have to figure which one it should have been.

I did not change the boot.ini so... I don't know

3.  "systemroot" Command.  This recovery console command takes you to the Windows installation directory.  If you enter "systemroot" command, what does the command prompt look like; e.g. "C:\Windows>"?

It say "C:\Windows>"

I know all the commands for the console, just so you know.

4.  Partitions.
     a.  With "map" command, can you verify this is what you have?
          E:       10 GB   Device\Harddisk0\Partition1
          C:    790 GB    Device\Harddisk0\Partition2

     b.  Is this a brand name computer; e.g. Dell, HP, Gateway, Acer; or a custom build?  Brand name computers frequently ship with preinstalled operating system and a separate restore/recovery partition.

     c.  The "E:" drive might be a "Restore/Recovery" partition.  Until we know what it is and why it's there, I think you should leave it alone.

Yes, the E: was installation thingy, but it was for Vista, but dose no longer exist. So I bought this crap to computer.

5.  Chkdsk.  I'm not clear on how we got to the "boot.ini" file.  Normally, when you have a system boot problem, one of the first things you try is to verify and attempt to fix/repair the integrity of the file system.  This may be done from recovery console using the "chkdsk" command.  It can take a long time to run.  If problems are found, it can take even longer.  This program was not designed to be interrupted - so don't (or you could corrupt the file system).  Let it run to completion, possibly overnight.  Execute the following command:  "chkdsk c: /p /r"

When I do "chkdsk c: /p /r" I need to tell the computer where the file is I did type "C:\Windows\system32\autochk.exe" is that right/normal or is it just one more strange thing?

Edit:
Well it said it fixed something but don't know what. and it is the boot.ini that is not working, I get a boot.ini error in 0.2sec before I get the Hal.dll error

[BC_Programmer]

and I have to login to the C: drive when I get to the console

And this is a problem because?

[patio]

I know all the commands for the console, just so you know.

If so where is the hangup ? ?

The other option would be to pull the drive and hook it up as a slave drive in another working machine.

This was also suggested...

[Frejoh466]

and I have to login to the C: drive when I get to the console

And this is a problem because?

I didn't say it was a problem, when I get to the windows recovery console  it tell me what drive I need to login and I only have Windows on C: so I can only login to C:

If so where is the hangup ? ?

Ok that's not a valid Command

attrib    del        fixboot   more     set
batch     delete     fixmbr    mkdir    systemroot
bootcfg   dir        format    more     type
cd        disable    help      net          
chdir     diskpart   listsvc   rd           
chkdsk    enable     logon     ren          
cls       exit       map       rename 
copy      expand     md        rmdir

I don't have time to say what they do, becuase I still have the problem.

[BC_Programmer]

it tell me what drive I need to login and I only have Windows on C: so I can only login to C:

OK... and why is that bad? boot.ini is on C:.

[Frejoh466]

OK... and why is that bad? boot.ini is on C:.

And when did I say it was bad? and please if you don't want to help stop posting here, Thanks!

[BC_Programmer]

And when did I say it was bad? and please if you don't want to help stop posting here, Thanks!

WHY is it a problem when you can only log in to drive C:? if it's not a problem/issue, why bother mentioning random facts that are completely meaningless? Unless of course your simply unfamilar with how to change the current drive in recovery console? <drive letter>: (for example D: to change to drive D: )

You have been given ALL the available methods to "edit" boot.ini without starting windows.

-Use the recovery console bootcfg command with the /rebuild switch.

-Delete boot.ini from C:\ in recovery console.

-Slave the drive and edit the file directly.

-Boot into a Live CD of some description (Ubuntu, Knoppix, or Windows PE, for example).

I have absolutely no idea what your Problem is anymore, but the fact is you've either ignored every proposed solution or complained of some trivial barrier you encounter while trying it.

[Frejoh466]

well no one have told me what exactly what to write in the console, so far I have guessed it should be

attrib -H-S-A-R boot.ini
del boot.ini
bootcfg /rebuild
Y
Windows
/fastdetect
bootfix
exit

but I still get the same error, it's ether the Hal.dll error or a other error

anyone can tell me if I can install Windows in E: and be able to get into C:

Edit:
and I can't get the hard drive out from my laptop.

[Geek-9pm]

Hello folks,
The board moderator and many others have been very patient with this original poster. It seems he has a hard time understanding what other people are trying to tell him. He doesn't grasp that the information others are giving him is the right information, but he has his own idea as to what the problem is. Below is a small  a screenshot of my system. I have worked with the BoOONT.INI file, even as most of you have worked with it.

The original poster is perhaps confused by the terms  active, system, boot, and how partitions are identified. To see a larger view of my disk manager click on the link below.
http://geek9pm.com/pix/boot-drive.png                           
Notice that in this case the the file that needs to be edited is on the C.: drive of disk 0. I took this screen shot while operating on my XP Pro system. As you can see in the screen shot it is on a different partition. In fact, it is a logical partition inside the extended partition. And besides that, there is a corrupted Windows 7 partition. So this is a rather convulsed odd llayout for this disk manager. But the point is that it actually works! And if I want to make any changes to the boot loader, I have to find the file that is on the C.: drive. And of course, it is called BOOT.INI and is a text file. At an earlier point in time I removed the hide and read only attributes for this file. As others have noted, you can always do this inside the recovery console. Now if a picture is worth 1000 words, then it's time for me to shut up. 

[Frejoh466]

I do what I thought I would do at the start

Edit:
Ok lets start over.

1.Can I login some how when the boot.ini is corrupted?
2.Can I fix the Boot.ini in the Windows recovery console?
3.Can I fix the problem somehow or do I need to reinstall Windows?

Would be glad if someone answer this  and tell me the solution.

so the right should be

1.Yes, If you have a exact copy on a working boot.ini for your computer.
2.probably, but no one knows how.
3.You could be able to fix it, but it will probably end whit your Windows CD in your computer and reinstall the whole thing.

So I reinstall C: and get everything to work again.

[dahlarbear]

So I reinstall C: and get everything to work again.

1.  So...  Are we done here...  Computer working OK now?

2.  For your information:
     a.  "boot.ini" should be within "C:\" directory; not "C:\Windows".
     b.   Yes, you could install Windows XP to "E:" partition; but why destroy what may be a "legitimate" Vista restore/recovery partition just to run Windows XP.  For all I know, Vista may be the only Windows operating system supported on that computer (laptop?).

[Frejoh466]

1.  So...  Are we done here...  Computer working OK now?

2.  For your information:
     a.  "boot.ini" should be within "C:\" directory; not "C:\Windows".
     b.   Yes, you could install Windows XP to "E:" partition; but why destroy what may be a "legitimate" Vista restore/recovery partition just to run Windows XP.  For all I know, Vista may be the only Windows operating system supported on that computer (laptop?).

1. well dunno it take 6h to get everything working again. (but yea things should be running good)

2.
     a. Well thats obvious that I know where the dam boot.ini is
     b. Well the Vista OS is 3-4gig? and the rest of the space 6-7gig there is loads of crap, and it is thing that's only work for 1h to 7 days then they become useless. It would take me a week to remove all programmes, and still every thing wouldn't be gone, so no thank you.

[dahlarbear]

Okay.  Clearly you prefer Windows XP over Vista.  Good luck with the reinstall.  It's been an experience.  Almost as if a "squall" blew through.

[Frejoh466]

Well you are right that I prefer Windows XP, but if Vista hadn't spammed the whole computer whit programs I would properly use Vista on that computer.

And yea... Hope I didn't <Censured> to many people off whit this.

[Geek-9pm]

Please clarify the following:
1. This is a recent Dell laptop?
2. It had Vista on the primary partition, and a recovery partition?
3. You installed a "downgrade" XP on the recovery partition?
4. At first it was working fine and then it went bad?

All of the above will make a big difference in the answers you get here.

I once said  nobody can not install XP on a Vista laptop. Then the experts here on CH showed me how it is done.

[BC_Programmer]

but if Vista hadn't spammed the whole computer whit programs I would properly use Vista on that computer.

Do you mean the software the PC came with? most of that is from those danged manufacturers. First thing I do with any PC I get that I don't build myself is to do a clean install of some version of windows. And I delete the recovery partition.

[Frejoh466]

Please clarify the following:
1. This is a recent Dell laptop?
2. It had Vista on the primary partition, and a recovery partition?
3. You installed a "downgrade" XP on the recovery partition?
4. At first it was working fine and then it went bad?

All of the above will make a big difference in the answers you get here.

I once said  nobody can not install XP on a Vista laptop. Then the experts here on CH showed me how it is done.

1. It's a Netbook > Aspire > One AO751h
2. In E: it was Vista and first time I started the computer it installed it automatic. That's all I know for that.
3. I installed a what in a what? I installed XP in C: after a time I removed the data on E: That's the answer you where looking for?
4. I dunno what happen but the boot.ini did not work when I started my computer. I thought it was a virus or something...

Do you mean the software the PC came with? most of that is from those danged manufacturers. First thing I do with any PC I get that I don't build myself is to do a clean install of some version of windows. And I delete the recovery partition.

when I install the OS the computer came whit I get loads of game demo who work for 1hour, I got a virus protection software who work for 7 days, I got free ware for loads of crap that did only work for a time.

Tho I got the computer working now. just so every one know. I reinstalled it.

[BC_Programmer]

when I install the OS the computer came whit I get loads of game demo who work for 1hour, I got a virus protection software who work for 7 days, I got free ware for loads of crap that did only work for a time.

Yep, that's the crapware the manufacturer's (in my case, it was Toshiba) decide we all need. my laptop ran so much better when I did a clean install of Vista Ultimate then it did with the "factory" condition, which had a lot of crap on it (like trialware games and programs, and worst of all Norton)

[Frejoh466]

Yep, that's the crapware the manufacturer's (in my case, it was Toshiba) decide we all need. my laptop ran so much better when I did a clean install of Vista Ultimate then it did with the "factory" condition, which had a lot of crap on it (like trialware games and programs, and worst of all Norton)

Off topic:
You hate norton? I think it's kinda good, except that it's really slow, but else it's good. Well it's Norton or Avast for me, I will get Avast after X-mas, I got it as a X-mas present for 3 years ago. So I will try to find a good Virus program, I don't thrust those free ware.   

[patio]

3 pages of advice...and a re-installl.


All is well with the World.

[Geek-9pm]

All is well with the World.

All the World Needs Now....
is a full re-install

[killerb255]

3 pages of advice...and a re-installl.


All is well with the World.

It was probably for the best, considering that there were too many communication issues, both with the TC (his own frustrations, bias, and inability to understand the advice given) and with everyone trying to help him (too many cooks in the kitchen).