Here's my summary of what I find is the difference between dosemu 1.2.1 and 1.2.2, in terms of the problems I found with 1.2.2. There are more details here than in my previous posts. I hope they provide clues as to what might be going on ...
I'm running the following when problems occur: 1. WordPerfect Shell 3.1 (used to call DataPerfect and other applications) 2. DPPrint (a TSR that works with DataPerfect) 3. DataPerfect (a fully relational networkable database manager) 4. ZipKey (a TSR that allows me to insert City, State, Zip after simply typing the Zip Code) The problem occurs when I call a DataPerfect application from WordPerfect Shell. Under 1.2.1, with hogthreshold at 1, ZipKey won't work. Everything else works fine. The CPU stays at 0 when not entering data. Under 1.2.1, if I raise hog to 2, everything works fine, including ZipKey, and the CPU stays at about 50%. Under 1.2.2, with hog at 1, ZipKey works fine, and the CPU stays at 0 when I'm not entering data. This is wonderful. But when I decide to print from within a DataPerfect application, DPPrint won't send printing to the printer at all, unless I switch back to Shell. When I switch back to Shell, the print job goes right to the printer. Under 1.2.2, with hog at 2, everything works fine, but the CPU stays at about 86%, even when not entering data. - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
