Question about Computers & Internet

1 Answer

I can 't open file extension .ini in windowes xp

We have problem when open file extension .ini in windows xp
give me error the filenamem , directory name , or volume label syntax is incorrect gave

Posted by on

  • ehabpob70 Jan 14, 2009

    I need More Solution

×

1 Answer

  • Level 2:

    An expert who has achieved level 2 by getting 100 points

    Hot-Shot:

    An expert who has answered 20 questions.

    Corporal:

    An expert that hasĀ over 10 points.

    Mayor:

    An expert whose answer gotĀ voted for 2 times.

  • Expert
  • 55 Answers

Here is a link to someone with the same problem and the solution: http://www.windowsbbs.com/windows-xp/70739-ini-extension-files-does-not-open-notepad.html

You can start by clicking start, then click run, and type regedit and press enter. Then expand the HKEY_Classes_Root folder and look for .ini, Click on .ini and make sure it is the following:

Default REG_SZ inifile
PerceivedType REG_SZ text

Let me know if you need more help. If this was helpful please rate, thanks!
Shawn

Posted on Jan 13, 2009

  • Shawn McGuire
    Shawn McGuire Jan 14, 2009

    Well, what was inappropriate in my answer. Inappropriate is used for
    answers that are abusive or out of contest. I think I gave you a
    solution. Please remove the rating. Thanks

×

1 Suggested Answer

6ya6ya
  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi,
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
goodluck!

Posted on Jan 02, 2017

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

I have 2 HDD's in my PC - both with Win XP Prop


Boot.ini is correct, but looks default is booting from Disk2 and partition 1 which is your G:\ 500 GB.

Try Copying boot.ini from c:\boot.ini to g:\boot.ini It might help

In your example I see missing "\" after partition(1), may be typing mistake, but in real time can generate error.

You boot.ini looks exactly same in both drive c:\ & G:\

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

Note: boot.ini will be hidden and readonly file. You need to unhide the file and remote the read only option and then only you will be able to save the boot.ini file

Hope this helps

May 22, 2010 | Microsoft Windows XP Professional SP2

1 Answer

MY pc does not start anymore. I have a Seagate hard drive ST380011A. I got the message: The following fail is missingC:/windows rootsystem32hal.dll


<windows root>system32hal.dll. is missing or corrupt. â How to fix it?â The Hal.dll file is the first file that boot.ini tells the system to look for at boot. â Looking at it this way, this error message can be rather misleading. In fact the reason could be a number of things, such as: â The boot.ini file is actually corrupt or damaged, â or it is pointing the Startup to look in the wrong place. The Hal.dll file is located in the System32 directory of your %SystemRoot% which in a default XP setup is:â C:WindowsSystem32.â You can use the Dos boot disk (or NTFS Reader above) to quickly determine if the file is missing.â If it is, then you should extract it from your XP CDrom and place it in its proper location.Boot to your XP CDrom, and then choose 'r' to go to the Recovery Console.â With your XP Cdrom in the drive, issue this command:Expand D:i386hal.dl_ C:Windowssystem32â â (This assumes the CDrom is D and your System Partition is C) â If this does not cure your issue this may be due to issues in your boot.ini file.â â The boot.ini file is actually corrupt or damaged, or it is pointing the Startup to look in the wrong place. Resolution:â The easiest way to fix this is to boot to the Recovery Console and replace the old boot.ini with a new one.â Once you have booted to the Recovery Console run these commands at the prompt:Attrib -H -R -S C:boot.iniâ â â (This removes the attributes and allows deletion). DEL C:boot.iniâ â â â â â â â â â â â â â â â â â (Deletes the corrupted boot.ini file)â â â â â â â â â â â â â â â â â â â â â â â â â â â â BootCfg /Rebuildâ â â â â â â â â â â â â â â â (Recreates the new boot.ini file)If you would like to view the boot.ini file, you will need a boot disk to get to the DOS prompt.â If you have formatted with FAT32, then you may use a Windows boot disk (such as a W98 disk), but if you are running NTFS, you will need a NTFS reader boot disk, such as NTFS Reader For DOS which is available for download here.â To diagnose the problem, copy the boot.ini file from the hard drive (C:boot.ini) and open it with Notepad.â You will want to verify that the "Default=" line as well as the ARC path line are pointing to the right location.â Here is two examples of boot.ini files (ARC paths start with multi): [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 Professional" /fastdetect This is a sample of the above Boot.ini file after adding another partition running Windows 2000 Professional. [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS [operating systems] multi(0)disk(1)rdisk(0)partition(1)WINDOWS="Windows XP Professional" /fastdetect multi(0)disk(0)rdisk(0)partition(2)WINNT="Windows 2000 Professional" /fastdetect â â

Nov 20, 2009 | Seagate Barracuda 7200.7 ST380011A 80 GB...

3 Answers

C:\windows\system32\hauurjab.dll is missing on my


Just google the error msg and you'll find the solution for it. At most times, ppl recommend you to delete this particular registry file that is associated with this dll file. But if I were you, i would better reinstall the operating system. Just google the error and give a try. Best o'luck.

Hope this helps, If so, rate me.. ,thanks - billa

Sep 05, 2009 | Microsoft Windows XP Home Edition

3 Answers

What is *.ini files ? how can i create it ? what is the use of it ?


.INI files are plain-text files that contain configuration information. These files are used by Windows and Windows-based applications to save information about your preferences and operating environment. "INI" stands for initialization.
Format of .INI Files.INI files contain one or more sections. Each section begins with a section name, which is followed by zero or more entries. An entry associates a keyname with a value. The general format is:

[section]
keyname=value

Comments can also be included in the file by prefacing the comment with a semicolon (;).

Windows and Windows for Workgroups use several standard .INI files for storing configuration information. These files are WIN.INI, SYSTEM.INI, PROTOCOL.INI, PROGMAN.INI, CONTROL.INI, WINFILE.INI, MSMAIL.INI, SHARED.INI, and SCHDPLUS.INI. Windows-based programs may also add sections and entries to WIN.INI, and they may add .INI files in the Windows directory.

Editing .INI FilesBecause .INI files use only plain text, they can be edited using any text editor or word processor. .INI Master also has a built-in text editor for making corrections in the .INI files you are diagnosing.

To create a custom Setup.ini file:
  1. Start the Setup INI Customization Wizard.
  2. Type the path to your Office XP administrative installation point, and then click Next. The wizard searches the specified network share for a Setup.ini file.
  3. From the administrative installation point, select an INI file on which to base your custom INI file. Or, click Browse to go to a different location and select a file. Click Next.
  4. Under Logging, select a logging mode, and then type a name for the log file or template. Click Default to use the logging mode that is specified in the INI file. Click Verbose to use all logging options. Note that verbose logging creates very large log files.
  5. Under Display, select a default display setting, and then click Next. The wizard searches the administrative installation point for additional packages (MSI files) that you can chain to the Office installation.
  6. Select the check boxes next to the packages that you want to include in your custom INI file, add packages or programs (EXE files) that are stored in another location, and then click Next.
  7. Use the arrow keys to determine the order in which you want Setup.exe to install the chained packages. The System Files Update package is always installed first (if required), followed by the Office XP package. You can change the order in which subsequent chained packages are installed.
  8. Select each package, specify the options that you want for that package, and then click Next. For each package, you can specify an MST file and a unique display setting, as well as additional property values.
  9. To add additional property-value pairs to your custom INI file, select a package, click Advanced Properties, type the properties and values that you want, and then click Next. The wizard displays a summary of the changes to save in the custom INI file.
  10. Click Save As, and then type a name and path for your INI file. The wizard supplies a sample Setup command line that specifies your custom INI file with the /settings option.
  11. Click Finish to quit the wizard.

May 12, 2009 | Microsoft Windows XP Professional

1 Answer

Need file asms to complete installation


The problem is some files in your installation cd cannot be read anymore.

Options:

1. When the error appears try to redirect the wizzard to the directory of your CD ROM and locate the file.

2. If you have back up copy of your xp cd use it to replace the xp cd you are installing when the error appears.

3. If you have a copy of your xp installer on your hard disk re direct the wizzard to that directory.



Apr 27, 2009 | Microsoft Windows XP Professional

3 Answers

I keep getting an error message when I start up my laptop. the 2 wire gives me a "corruption has been detected in feature manager, backup file has been loaded", and it will not connect. All other programs...


If the machine is a Dell with DellControlPoint, open start, run then type msconfig and hit enter. Choose the Startup tab and find the startup item named "Dell" with the Command from "C:\Program Files\Dell\Dell Control Point\Connection Manager\Dell.UCM.exe" and uncheck the box. Hit Ok, then reboot your computer.

Jan 16, 2009 | Computers & Internet

1 Answer

BOOT.INI deleted. How to re-create this file?


type in run "cmd" then presss enter then type "bootcfg /?" it gives u some help .

Dec 28, 2008 | Microsoft Windows XP Professional for PC

2 Answers

How do I...


NTOSKRNL.EXE is missing or corrupt.

Related errors:

Below is a listing of the full error message that may be related to this error.

Windows NT could not start because the below file is missing or corrupt:
C:\Winnt\System32\Ntoskrnl.exe

Cause:
Keyboard issue
Miscellaneous corruption
Corrupt boot.ini file.
Missing boot.ini file.
Missing or corrupt ntoskrnl.exe file.
Windows NT installed on a partition bigger then 7.8GB
Corrupted hard disk drive or severely corrupted Windows.
Solution:
Keyboard issue
This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.

Miscellaneous corruption
Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626.

Corrupt boot.ini file
This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer.
Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492.

Missing boot.ini file
Microsoft Windows XP users:
If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648.

Microsoft Windows NT and Windows 2000 users:

To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.
Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
In the setup menu, type R to start the repair.
When prompted for the ERD diskette insert the diskette and inspect the startup environment.
Missing or corrupt ntoskrnl.exe file
If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.
Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
Select the operating system you wish to fix, and then enter the administrator password.
Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
Type exit to reboot the computer.
Windows NT installed on a partition bigger then 7.8GB
If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the

error message as shown below.

OS Loader v4.01
Disk I/O error status=00000001
Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe
Please reinstall a copy of the above file.

If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.

Corrupted hard disk drive or severely corrupted Windows
Attempt to check the hard disk drive for any errors by running the chkdsk error. To do this follow the below steps.

Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
Select the operating system you wish to fix, and then enter the administrator password.
Once at the recovery console type chkdsk /r
Once completed type exit and see if issue is resolved.
If after trying all of the above steps you are still encountering the same issue it's likely that Windows is severely corrupted and it is recommended you attempt to reinstall Windows. Additional information about erasing the computer and starting over can be found on document CH000186.
Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.

Oct 09, 2008 | Dell OptiPlex GX110 PC Desktop

1 Answer

ACER DESKTOP COMPUTER


Issue: NTOSKRNL.EXE is missing or corrupt.
Related errors:
Below is a listing of the full error message that may be related to this error.
Windows NT could not start because the below file is missing or corrupt:
C:\Winnt\System32\Ntoskrnl.exe
Cause:
  1. Keyboard issue
  2. Miscellaneous corruption
  3. Corrupt boot.ini file.
  4. Missing boot.ini file.
  5. Missing or corrupt ntoskrnl.exe file.
  6. Windows NT installed on a partition bigger then 7.8GB
  7. Corrupted hard disk drive or severely corrupted Windows.
Solution: Keyboard issue This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.
Miscellaneous corruption Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626.
Corrupt boot.ini file This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer. Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492.
Missing boot.ini file Microsoft Windows XP users: If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648. Microsoft Windows NT and Windows 2000 users: To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.
  1. Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
  2. In the setup menu, type R to start the repair.
  3. When prompted for the ERD diskette insert the diskette and inspect the startup environment.
Missing or corrupt ntoskrnl.exe file If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.
  1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
  2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
  6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
  7. Type exit to reboot the computer.
Windows NT installed on a partition bigger then 7.8GB If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the error message as shown below. OS Loader v4.01
Disk I/O error status=00000001
Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe
Please reinstall a copy of the above file. If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.
Corrupted hard disk drive or severely corrupted Windows Attempt to check the hard disk drive for any errors by running the chkdsk error. To do this follow the below steps.
  1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
  2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Once at the recovery console type chkdsk /r
  6. Once completed type exit and see if issue is resolved.
If after trying all of the above steps you are still encountering the same issue it's likely that Windows is severely corrupted and it is recommended you attempt to reinstall Windows. Additional information about erasing the computer and starting over can be found on document CH000186. Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.

best regards wish u give me a good rate ^^

Aug 15, 2008 | Acer Computers & Internet

2 Answers

Problem with opening ini files...


from each computer:
right click on a .ini file,
select 'open with...'
choose notepad and select the box that says 'always use the selected program to ope this kind of file'
click 'ok'

Apr 07, 2008 | Microsoft Windows XP Professional

Not finding what you are looking for?
Computers & Internet Logo

Related Topics:

114 people viewed this question

Ask a Question

Usually answered in minutes!

Top Computers & Internet Experts

Brian Sullivan
Brian Sullivan

Level 3 Expert

27725 Answers

kakima

Level 3 Expert

102366 Answers

David Payne
David Payne

Level 3 Expert

14161 Answers

Are you a Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...