Re: Catastrophic X graphics slowdown going from 1.0.2.1 to 1.2.2.0

2004-11-17 Thread Bart Oldeman
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,

Re: Catastrophic X graphics slowdown going from 1.0.2.1 to 1.2.2.0

2004-11-17 Thread jegunn
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

Re: Catastrophic X graphics slowdown going from 1.0.2.1 to 1.2.2.0

2004-11-17 Thread jegunn
Many apologies--I thought the debugging output came on stdout/stderr, but it is clearly put into boot.log. Running with -D9+c elicits the output X_fullscreen 0 vgaemu_memsize 0x600 vesamode_list (nil) X_lfb 1 X_pm_interface 1 when parsing the .dosemurc lines in the vicinity of # size (in

Re: Catastrophic X graphics slowdown going from 1.0.2.1 to 1.2.2.0

2004-11-17 Thread Bart Oldeman
On Wed, 17 Nov 2004, jegunn wrote: in .dosemurc. So the memory size is recognized, but the vesamode line is not. Has the syntax changed? The documentation has not. No, it's a typo. in dosemu's etc/global.conf replace foreach $yyy ( , $X_vesamode) by foreach $yyy ( , $_X_vesamode)

Re: Catastrophic X graphics slowdown going from 1.0.2.1 to 1.2.2.0

2004-11-17 Thread Bart Oldeman
Thanks much, Bart. I am running from the binary distribution, so I took the chicken's way out and changed dosemu.users to read the fixed global.conf file. Ok, that's fine, it just overrides the builtin one then. quilla:SDSSPrettypicsxdosemu [1] 3541 quilla:SDSSPrettypicsERROR: Unable to