On Wed, 17 Nov 2004, Bart Oldeman wrote: Thanks, Bart.
The other problem I alluded to still remains. The following line in .dosemurc $_X_vesamode = "1024,740" elicits no response to a query which lists the available VESA modes. Changing the $_X_vgaemu_memsize has the expected result; going from one megabyte to 2 brings the 1280x1024 and 1600x1280 modes into existence, but the custom modes do not show up. This worked fine in 1.0.2.1. Stas suggested that I do some debugging and file a bug report, which I have not done yet, but there is no debugging output from either -D9+v or -D9+X. thanks --jim > On Tue, 16 Nov 2004, jegunn wrote: > > > Thanks. I tried this a little while before I got your reply; the > > performance is *very* sensitive to the setting; 3 is more-or-less > > OK, but better with zero. I was using 1 before with 1.0.2.1. Did > > the priority code change between these versions? > > yes, certainly. You may even want to try 1.2.1 and see how that behaves, > since there were a few changes between 1.2.1 and 1.2.2 that can be > regressions in certain cases (we'll have to look at this more closely). > > There's a big difference between hogthreshold 1 and 2, then to 3 4 5 etc > it goes more gradually. > > With "0" you pretty much have dosemu using 100% CPU all the time; with say > "10" it will still sleep most of the time at the DOS prompt for instance. > > Bart > - 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
