🚀 go-pugleaf

AmC wrote:
> "JAD" <john doe@harvester.addys.for.porn.spam> wrote in message
> news:aemIi.553$Ez7.407@newsfe05.lga...
>>
>> No you didn't,   I'm sorry I missed your first install,,,that was the INF.
>>
>> ""Intel Chip Set Software Installation Utility for Intel Desktop Boards""
>>
>> Did you install in the order in which you posted?
>>
>> What does the device manager say about your hardware currently?
>>
>> If a restore point was made before your first attempt you could go back to
>> that point and install the INF first.or just start over with a reinstall
>> of windows..
>> This shouldn't be a struggle, I have done this hundreds of times on MANY
>> Intel chipset boards, ASUS etc....
>> I haven't found anything directly relating to this yet.
>>
>> What does the event viewer say?
>>
>>
> OK, I got this Intel INF update utility here:
> http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=2529&OSFullName=Windows*+XP+Professional&lang=eng&strOSs=44&submit=Go%21
> 
> I downloaded both zip and exe
> INF Update Utility, for Intel 900 series, version 8.3.0.1013
> infinst_autol.exe
> error:
> This application has failed because the application configuration is 
> incorrect.
> 
> From the unzip INF Update Utility, verison 8.3.0.1013
> setup.exe
> This application has failed to start because the application configuration 
> is incorrect.
> 
> Where can I read the event viewer?
> What is this configuration they keep talking about?
> 

If I go to www.sysinternals.com and get a copy of Process Explorer (procexp.exe)
and run it, then select the Intel "setup.exe" file while it is running, these
are the DLLs that the Intel program loaded. This is what I see when the Intel
colored dialog window eventually shows up. Setup.exe grinds for almost 30 seconds
before showing its window, even though in this case, I'm using the contents of
the ZIP folder (so everything is already unzipped).

Process: Setup.exe Pid: 1892

Name	Description	Company Name	Version
ADVAPI32.DLL	Advanced Windows 32 Base API	Microsoft Corporation	5.00.2195.7038
ChipsetENU.dll	Intel� Chipset Device Software installer	Intel� Corporation	1.01.0006.0000
comctl32.dll	Common Controls Library	Microsoft Corporation	5.81.4968.2500
ctype.nls			
GDI32.DLL	GDI Client DLL	Microsoft Corporation	5.00.2195.7138
KERNEL32.DLL	Windows NT BASE API Client DLL	Microsoft Corporation	5.00.2195.7135
locale.nls			
msvcrt.dll	Microsoft (R) C Runtime Library	Microsoft Corporation	6.01.9844.0000
NTDLL.DLL	NT Layer DLL	Microsoft Corporation	5.00.2195.7006
OLE32.DLL	Microsoft OLE for Windows	Microsoft Corporation	5.00.2195.7059
psapi.dll	Process Status Helper	Microsoft Corporation	5.00.2134.0001
rpcrt4.dll	Remote Procedure Call Runtime	Microsoft Corporation	5.00.2195.7085
Setup.exe	Intel� Chipset Device Software installer	Intel� Corporation	1.01.0009.0000
setupapi.dll	Windows Setup API	Microsoft Corporation	5.00.2195.6622
SHELL32.DLL	Windows Shell Common Dll	Microsoft Corporation	5.00.3900.7105
shim.dll	Shim Engine DLL	Microsoft Corporation	5.00.2195.6717
SHLWAPI.DLL	Shell Light-weight Utility Library	Microsoft Corporation	6.00.2800.1913
sortkey.nls			
sorttbls.nls			
unicode.nls			
USER32.DLL	Windows 2000 USER API Client DLL	Microsoft Corporation	5.00.2195.7133
USERENV.DLL	Userenv	Microsoft Corporation	5.00.2195.7002

When I use a search engine, and look for "application configuration is incorrect", I keep
seeing threads like this, mentioning Visual Studio and the like.

"Re: This application has failed to start because the application configuration is incorrect"
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1667425&SiteID=1&pageid=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=164465&SiteID=1

The msvcrt.dll properties (one of the many DLLs above loaded by Setup.exe), is in
C:\WINNT\system32\msvcrt.dll  . The problem is, I'm using Win2K SP4, so my path
specifications won't be of help to someone debugging a WinXP problem. The thing
is, the majority of things in that list above, that "Setup.exe" is using, are all
in that same system32 folder. Either a particular dependency is missing, or the
entire search path is screwed up. WinXP will have a different name for the system32
folder, but the concept will be similar - many key DLLs will all be staged in the
same folder.

Say, for example, your install didn't "go into the right hole". Say that the path
that the install files were placed in, was incorrect. Then, the part of the system
that loads DLLs, will be royally confused. I wonder if the boot drive is even on C:\ ?

I know you just want a "simple" answer, but unless a search engine turns up such a
simple answer, you're going to have to go about it the hard way. The normal program
dependencies are not being supplied, and because Windows isn't "man enough" to
display a message as to what dependency is not resolved, you are going to have to
compare your broken installation, to another disk that has a working installation on it.

On Unix systems I've used, programs like lddconfig show what versions of dynamically
links libraries are being used by a program, without even running the program. This
is a great feature, that tells you about stuff you may be missing, without any
non-descript error messages.

    Paul