Winfeed for Windows 95/98/ME/2K/XP/Vista/7

Some of the things that are not in the Windows 3.1 version: long filenames, background colors (in some windows), and enhanced metafile support. The individual windows have not been changed, but I have tried to improve the user interface in most of the modules, so you will notice differences.

A version number is now displayed in the Help|About box. From time to time, it is necessary to increase this number, because something has been added to a winfeed file that older versions of the program will not be able to handle. The program will never attempt to open a file whose version number is greater than that of the program.

Details of other changes can be found in the updated Help files.

If you use Windows XP and want Winfeed controls (buttons, scroll bars, etc) to have the Windows XP “look”, download this file (right-click and Save Target As). From this zipfile, extract the file whose name matches the program version you are using (there is one for each language), sending it to the same folder where the program itself is found.

There will of course be occasional bugs. If you find things that I have missed, please tell me about them. Also send along any suggestions.

It occasionally happens that initialization files (*.ini) become defective (in the event of a crash, for example). Opening a bad ini file can cause the program to act strangely, or not work at all (this is the source of many problems). For example, if the Btns menu does not display a check mark that indicates the current mouse function, this is a sure sign that the ini file has been corrupted. To tell the program not to use a suspicious ini file when it opens a window, check the menu item called “Use defaults”. (This is easier than finding and deleting the files bif.ini, colseq.ini, dyc.ini, dyr.ini, grtab.ini, ifc.ini, ifr.ini, jul.ini, mandel.ini, par.ini, srf.ini, slide.ini, web.ini, wf.ini) When windows close normally, their ini files are restored to health.

Winfeed normally places its initialization files in the “Windows” directory, and looks for them there. There are two other versions that might be preferable. The first one places its initialization files in the directory from which the application is launched. If you launch the program by double-clicking the program icon, the resulting “home” directory is where the executable is kept. If you launch the program by double-clicking a file icon, however, the home directory is where that file is kept. If you launch the program by double-clicking the program icon, the resulting “home” directory is where the executable is kept. If you launch the program by double-clicking a file icon, however, the home directory is where that file is kept. The second one places initialization files in the current working directory. If you would like either of these versions in one of the available foreign languages, just let me know — my e-mail address can be found in the Help|About dialog box.