🚀 go-pugleaf

AmC wrote:
> "JAD" <john doe@harvester.addys.for.porn.spam> wrote in message
> news:yGjIi.595$nc7.132@newsfe12.lga...
>> "AmC" <spam.no.more@spam.no.more.com> wrote in message
>> news:jkjIi.624$6p6.188@newssvr25.news.prodigy.net...
>>> Installed Windows XP Professional on my Intel DP965LT mb. I have 2GB
>>> memory.
>>> I download the Intel programs and utility.
>>>
>>> I am unable to execute the following downloaded programs:
>>>
>>> Intel Chip Set Softeware Installation Utility for Intel Desktop Boards
>>> INF_AllOS_8.4.0.1016_PV_Intel.exe -
>>> The Application has failed to start because the application configuration
>>> is incorrect. Restalling the application may fix the problem.
>>>
>>> The Intell Desktop Utility
>>> IDU_3.0.14.19.exe
>>> The Intel SM Bus drivers could not be installed. This is a required
>>> driver. The installation will now abort.
>>>
>>> Intel Integrator Toolkit
>>> iTK_FE_3.2.1.146.exe unzip to toolkit_3.2.1.146.exe
>>> Component Transfer Error
>>> The Parameter is incorrect.
>>>
>>> Intel Management Engine Interface Drivers
>>> HECI_Win2K_allXP_Vista32.2.1.22.1026_.exe
>>> Error executing the specific program
>>> c:\program files\Intel Desktop Board\HECI_2.1.22.1026_PV\setup.exe
>>> unable to execute the specific command line.
>>>
>>> Thank you for your help.
>>>
>>
>> When installing a Windows OS for the first time, always install the INF
>> drivers before installing any other drivers. See the INF readme for
>> details.
>>
>>
> 
> Can you please show me the link to download INF drivers for this Intel mb?
> I cannot not find it here:
> http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=2374&OSFullName=Windows*+XP+Professional&lang=eng&strOSs=44&submit=Go%21
> 
> I must have missed it somewhere?
> 
> 

It is the second item on the Intel page, called "Chipset".

When you click the download link, you'll be downloading
INF_AllOS_8.4.0.1016_PV_Intel.exe , which you've already got.

I can run the Intel utility, and if run in GUI mode, it uses
a temporary folder for its files. I found a help file in there,
which indicates the executable can be run from a DOS window
via a command line syntax.

*******
Help for Setup Command-Line Options

      -?			displays this help dialog
      -a			extracts all driver files
      -aonly		extracts driver files that match the system hardware
      -b			reboots the system after setup is complete
      -f2 <path>		changes the default log path
      -l <number>		specifies the language of the setup dialogs
      -nowel		does not display the welcome dialog
      -nolic		does not display the license agreement dialog
      -noread		does not display the readme dialog
      -overide		overwrites the IDE driver
      -overall		overwrites all drivers
      -overwrite		ignores the overwrite warning
      -p <path>		changes the default install path
      -s			does not display any setup dialogs
*******

I tried a DOS command box and due to the long name of the file, it
wouldn't run there immediately. I renamed the file to "dumb.exe" and
then executed the following in the DOS command window. (Note - first
you have to CD to the directory containing the file, so I'm missing
some steps here...)

    dumb.exe -a

The result was, that the Intel program decided to dump the INF files into
C:\Program Files\Intel\INFInst

The raw INF files are there, if you wish to update chipset drivers.

In the past, Intel has offered a ZIP version of the INF files, and if you
absolutely must be guaranteed of getting something for your trouble, that is
the thing to get. But I don't see a ZIP version offered in this case. They
could easily do it, if they wanted to, because the -a option is doing
exactly that - unzip and quit.

I'm not going to say anything more about what to do next, because
this is not addressing the real problem, whatever it is. Chipset drivers
are not preventing executable software from executing. Missing libraries
and the like, are.

For better or worse, installer packages rely on things outside themselves.
(They really shouldn't - only an idiot would do that...)
My suspicion is, that if you were to run Windows Update, some of these
things may be filled in for you. Microsoft has a .NET library for example.
Microsoft also has some "Windows Installer" software that I keep seeing
when I use Windows Update.

What I'd recommend, is take the error messages you got from your attempts
at installation and run the text of the error message through a search
engine (copy the whole sentence and put quotes around it). You may find
mention of .NET or the Windows Installer software or maybe even some
crufty old Visual Basic files. Maybe something like that is what is
preventing them from executing. If there was a problem with part
of the registry being locked, the error messages would be different
ones. It could be, that a visit to Windows Update, will fill in some
of those gaps.

    Paul