Windows 95 ---------- With v2.52 we have entered the realm of providing information on the 32bit Windows 95 operating system. Our approach is slow, the features will come as our expertise grows. However this version already ensures that most of InfoSpy's functionality is updated to handle 32bit calls and long filenames. You need to note right away that InfoSpy is still a 16bit program, however it makes 32bit calls when running under Windows 95. In other words, this version is both Windows 3.1 and Windows 95 ready. Not too many other programs can claim that distinction. We have upgraded all our standard features and options so that they are useful under both operating systems, and we have added a new menu group for specific Windows 95 features, such as Processes and Threads. Our goal is to eventually migrate to 32bit completely, but not until the user base of Windows 95 far exceeds the user base of Windows 3.1. In the meantime we will continue to add and improve features, attempting at all time to share the features across both operating systems. Please see the online help for a description of the Windows 95 options and a list of remaining Windows 3.1 options that could not be migrated to Windows 95 in this version. In short, the following features still act up when run under Windows 95: - File Trace Monitoring. - Windows API Message Monitoring. We give you the option of trying them anyways, but be prepared for the worst! If you have comments or suggestions regarding new or updated features please email me at 75240.65@compuserve.com Thanks for making InfoSpy one of the most popular shareware utilities of 1995! Steve Dean NOTE: If you have trouble uninstalling InfoSpy it may be due to an entry that the InfoSpy setup program makes in your SYSTEM.INI. If you delete InfoSpy from your disk without using the uninstaller provided with the setup program you may experience problems or warnings when booting Windows or Windows 95. If so, edit your SYSTEM.INI file and remove the line under the [386ENH] section that contains INFOSPY or INFBOOT.386. Save the SYSTEM.INI file and reboot, the problem should go away.