I am at a loss as to why it will not load -- I have run the program on several machines and I never had a problem with it running. Perhaps it requires updated runtime files?
Philip, what program was used to build the Optimizer? Is it VB? Do users need to have updated vb6runtime files? Or was some other program used (C++, etc.)?
By the way, you can modify simple text lines like that with a binary file editor -- as long as you simply substitute one letter for another. You don't have to recompile the whole program again. So the version I am using has "time" in it now.
__________________________________
All the MaxMTU and Latency tests I have run are working perfectly on every machine. The new rewrite seems to be a winner.
You have also done an excellent job with the adapters. Everything is almost perfect, except...
1) You are still trying to read the MTU for for the Dial-Up Apapter in the \NetTrans\000n\MaxMTU value. You will not find the MTU there. Instead, it is in the \Net\000n\IPMTU value.
2) You are starting from the \Class\Net\ keys instead of the \Enum keys. Because of this, it appears that two problems can arise:
..... a) Adapters that aren't bound to TCP-IP seem to still appear in the drop-down list. This is becase they still exist in the \Class\Net key even if they are not bound to TCP-IP.
..... b) The Optimizer is also assuming a linear relationship between the \Class\Net\000n subkeys and the \Network\MSTCP\000n subkeys -- which does not exist. If you unbind TCP-IP from your Dial-Up Adapter (usually 0000 in both of these subkeys), the relationships are no longer linear. All Adapter/IP Address/MTU listings in the Optimizer will be off by one.
Since many users seem to follow the security gospel according to Gibson, many users may have their Dial-Up Adapters unbound to TCP-IP -- therefore rendering the Optimizer incapable of reading the correct MTU settings.
_______________________________________
The Optimizer goes: \Class\Net\000n -> \Network\MSTCP\Driver -> \Class\NetTrans\000n. It assumes the first \Class\Net subkey is related to the first \MSTCP subkey. This will not always be the case -- as above.
Then, the Optimizer only looks in the NetTrans subkeys for MaxMTU -- the Net\IPMTU values are never queried. While I did not try to set the IPMTU with the Optimizer (time is limited), even reading these incorrectly will be a disservice to PPPoE-DSL and Dial-up users.
You do not appear to be using the data in the Enum\Root\Net or Enum\PCI keys. These are the *only* keys that tie together the multiple other subkeys. Without using that data early on, you can never truly link all the keys together correctly.
Just my humble opinion. Good luck.
]
