.NET Framework 2.0 files are required in order to install LW4.5. If you do not have them installed you can go to Windows Update and download them.

If you are using Buckmaster, you need to make sure you have the correct dll file. LW was crashing every 15 QSOs on my system. When I searched for all hamcal32.dll files, I found one in MixW, one in system32 and one in the LW Bin. The LW Bin dll for some reason was different in size than the others, so I simply made sure the correct latest Buckmaster dll was in each place. Note, after calling Buckmaster back, they recommended NOT DELETING ALL BUT ONE, as shown below, but rather replace each one with the latest version. A download link to it is provided below. The LW dll was the only one that was not the new dll, so I replaced it. BINGO, LW does not crash now when you enter the 15th call in a row!

Anyway, FWIW, you have to stop installing your DLL's (any files) in the System32 directory. Microsoft is locking it down now with Vista. MS has given up on the concept of "Shared DLL's" due to poor versioning control on vendors end. .NET Assemblies sort of address this, but still, no more shared binaries in a Microsoft directory. MS wants you to put ALL of your binaries and ActiveX components in your own directory. If you need a "common" directory you should create your own common directory and list it in the registry. If you put your common DLL's into a common directory, and publish the registry key to locate them you'll be Vista compliant and save a future headache. ActiveX controls just need to be registered (regsvr32.exe) in their directory and the system will find them when needed. If you put your DLL's in the directory with your EXE then you won't have to PATH to load them. So, it's a simple setup change for you. As for users of your DLL, they should 1) Check for your registry key and load from there, 2) if that fails, then allow the system to try to PATH to it. FWIW. -Bob Flickinger KI4PQV BeCubed Software for Sco, Inc. (Log Window)