MSDATGRD. OCX files associated with the DEPENDENCY version 1.0 and version 2.2 parse out the associated files why is not the same as

Version 1.0 file parsing out, is not missing files, and the associated files not many, only ten, as shown in the figure below:


Version 2.2 parsing, dozens of related documents, and lack of two files, as shown in the figure below:



Above, please in the scarlet letter marked by 1 and 2 icon, add icon on the left side of the funnel is what meaning? What's the meaning icon on the right side with red

Add the missing file from above, tip missing files, as shown in the figure below:



Add the missing file from above, tip missing files, as shown in the figure below:



Add the missing file from above, tip missing files, as shown in the figure below:



Add the missing file from above, a hints file error, as shown in the figure below:



Excuse me: 1, why two versions of parsing out the related documents,
2, what is the last error message? I'm looking for the last two files doesn't seem to be XP version, the download file, there are two versions of WINDOWS 7 X86 and 7, 64, I choose is the placement of X86 to C: \ WINDOWS \ SYSTEM32 directory, why error drawings is 64?

CodePudding user response:

The "funnel" icon on the left, probably should be called "lazy loading module",
"Red" logo and icon, said that module is a problem with the "import analysis",
In this instance, you because the MPR. DLLS needed to find two other DLL, so "parse has a problem,"

1. The analytical results are different:
From the top left corner you can see, the tree list 1.0 parse only "shallow level,"
And high version is "layers of in-depth" parsing, so, the phenomenon of the "involving files a lot",
2. The DLL is a mixture of different systems, even with the same name, you use it to "fake", is certainly going to have a problem,

CodePudding user response:

reference 1st floor Chen8013 response:

the "funnel" icon on the left, probably should be called "lazy loading module",
"Red" logo and icon, said that module is a problem with the "import analysis",
In this instance, you because the MPR. DLLS needed to find two other DLL, so "parse has a problem,"

1. The analytical results are different:
From the top left corner you can see, the tree list 1.0 parse only "shallow level,"
And high version is "layers of in-depth" parsing, so, the phenomenon of the "involving files a lot",
2. The DLL is a mixture of different systems, even with the same name, you use it to "fake", is certainly going to have a problem,

Thank you very much, I thought the last two DLL without XP version, now find the XP version, however, after the update, if still not normal, as shown in the figure below, please help to have a look at, thank you,

CodePudding user response:

Your system has a problem!
I have downloaded a version 2.2 (2.2.6000) to open MSDATGRD. OCX, put all the nodes,
Check the entirely, there is only one node id "there is a problem,"
This node "path" is:
MSDATGRD. OCX - ADVAPI32. DLL - SECUR32. DLL - NETAPI32. DLL - DNSAPI. DLL
-> IPHLPAPI. DLL - MPRAPI. DLL - SETUPAPI. DLL - SHLWAPI. DLL - MPR. DLL
I don't know it the "question" what is going on,
On this node "a", and SHLWAPI. DLL coordinate, actually also has a node is MPR. DLL, but the node does not show "abnormal",
The difference is:
Selected the "normal nodes", the top right of the list is three export function, the front is "green C" mark;
But select the "abnormal node", listed in the list above is 7 export function, is one of the "C" red tag, the other six "green C" tag,


Directly open the MPR. DLL to view, but also from "ADVAPI32. DLL" down the "path" to MPR. DLL logo "problems";
But the inside is a little difference, with SHLWAPI. DLL "parallel" MPR. DLL nodes have no "child nodes, node icon is a" return "symbol?
But the "node" on the three export function is the same,

CodePudding user response:

Look at the, as if our MSDATGRD. OCX different?
You is 1998, I was in 2004,


You compare the pictures in the list below, MSDATGRD. OCX information...

CodePudding user response:

The

reference 4 floor Chen8013 reply:

, as if our MSDATGRD. OCX different?
You is 1998, I was in 2004,


You compare the pictures in the list below, MSDATGRD. OCX information...

Thank you very much, my MSDATGRD. OCX version is 6.1.97.82, my environment is XP

CodePudding user response: