rloew, on Yesterday, 03:36 PM, said:
It appears also when starting and stopping the second pass.
rloew, on Yesterday, 03:36 PM, said:
Doing Main Updates first separately from the rest worked, but there are no instructions to do so.
I know about the CHM because you told me. There is no reference to it that I can see.
The Installer goes to the selection menu without the user being able to read the CHM beforehand even if he knows about it.
Your target audience will mostly be NEWBIES. Experinced users will have less need for this SP.
The Instructions should be plainly displayed before the selection window.
Website instructions will quickly be separated from a downloaded package, so you can't depend on people reading the Website for Installation instructions.
I know about the CHM because you told me. There is no reference to it that I can see.
The Installer goes to the selection menu without the user being able to read the CHM beforehand even if he knows about it.
Your target audience will mostly be NEWBIES. Experinced users will have less need for this SP.
The Instructions should be plainly displayed before the selection window.
Website instructions will quickly be separated from a downloaded package, so you can't depend on people reading the Website for Installation instructions.
rloew, on Yesterday, 03:36 PM, said:
You may want to add this to your documentation.
rloew, on Yesterday, 03:36 PM, said:
I did not use DLLHOOK or WDMEX in these tests.
WDMEX replaces WDMSTUB, so the INF files would have to be purged of WDMSTUB references.
DLLHOOK issues were related to KernelEX not U98SESP3. I don't see any reason for problems with DLLHOOK or FILE64.
WDMEX replaces WDMSTUB, so the INF files would have to be purged of WDMSTUB references.
DLLHOOK issues were related to KernelEX not U98SESP3. I don't see any reason for problems with DLLHOOK or FILE64.



Help


Back to top








