WordStar for Windows
Introduction
After installing Adobe Acrobat 4, printing a WordStar for Windows document to the Acrobat Distiller causes a Windows general protection Fault (GPF).
This is caused because the default installation directory for Adobe Acrobat 4 uses Windows 9x long file names. WordStar for Windows doesn't understand these and crashes.
Introduction
WordStar for Windows Mail Merge Doesn't Retain Special Characters (accents, true apostrophes, em dashes, etc.).
Using mail merge addresses, or other data, looses true apostrophes, em dashes, and accents from characters, etc. This is because, by default, WordStar for Windows uses the DOS OEM character set for mail merge imports and this character set does not support these characters.
Introduction
Some wheel mouse drivers don't provide all the signals necessary for older software to recognise the wheel function.
Solution
One solution is to try different brands of wheel-mice. Reports indicate that the problem only occurs with Microsoft wheel-mice and that Logitech versions work correctly.
Introduction
When first starting WordStar for Windows, or creating a new document the default font is incorrect.
Cause
This can happen if the file paths and names for the WordStar for Windows default document template have become corrupted. This can happen after a reinstallation of Microsoft Windows, restoring WordStar for Windows from a backup but forgetting to also restore the files held in the Windows directory (folder), or following a program crash or disk corruption.
Introduction
Problems that can occur if the wsw.ini file is missing or damaged include the wrong default font or template being used by WordStar for Windows.
There is a 'template' for this file in the WordStar for Windows installation directory (usually C:\WSWIN) called WSWINI.TXT.
More Articles …
Page 3 of 7