File->Capture->Area locks box Options

[asavage]

Hello, Peter:

Long ago, perhaps two years ago, I found that using "Area of Screen" for screen captures would sometimes or often lock up my box, so I stopped using it. Instead, I used "Screen", then after capture I'd crop.

Today, I decided to try "Area of Screen" again, and after displaying crosshairs, it locked the box -- the WarpCentre clock stopped, crosshairs would not move, and no obvious response from the keyboard. C-A-D worked OK.

I let it reboot, and repeated the same experiment: same results.

This is quite probably a Matrox video driver issue, but I though that I'd report it anyway. I have several older Matrox drivers, but I've been using the 2.58.144 for several years and it has worked OK for me in most ways.

I do NOT expect you to work around a video driver issue, and I can work around this problem easily by reverting to capturing the entire Screen + crop. My purpose in posting this is to either confirm that this is a Matrox driver issue (so it can be added to the README or Help system), or to pin it down to being only applicable to this particular box.

W4 FP17, 1GHz, 1GB
Later kernel (14.096-something)
Matrox G400 AGP 16MB, v2.1 BIOS, 2.58.144 driver

Help->System Info:
[code:1:post_uid0]Application
 Product name     : PMView Pro for OS/2
 Version          : 3.05
 Build            : 22638
Graphics
 Screen size      : 1152x864 pixels
 Bit depth        : 24 bits
 Plane count      : 1 plane
 Number of colors : 16777216 colors
 Palette manager  : No
 Raster caps      : 0075
Screen
 Physical size    : 283x212 mm
 Resolution       : 103x104 dpi
Processor & memory
 Number of CPUs   : 1
 CPU family       : 6
 CPU model        : 4
 CPU stepping     : 2
 Page size        : 4096 bytes
 Physical RAM     : 1024 MB
 High memory supp.: Yes
Operating system
 Operating system : OS/2 Warp
 Version          : 4.5
 Build            : 14.096
 Boot drive       : E: HPFS[/code:1:post_uid0]

Here are the Matrox drivers I have available to test:
[code:1:post_uid0]1696_213                  .zip    1,315,353   7-07-97
1696_221                  .zip    1,374,406   7-02-98
1696_222                  .zip    1,028,768   1-14-99
os2_223                   .zip    1,043,832   2-19-99
os2_236                   .zip    1,117,953  11-18-99
os2_254                   .zip    1,267,298  12-14-00
os2_258                   .zip    1,310,938  12-27-01[/code:1:post_uid0]

Regards,
Al S.

[Peter]

I don't think it is the Matrox driver. I'm using the matrox drivers 236 and 258 on a daily basis, and can't repeat the problem.

FWIW, PMView 2000 and Pro were both *developed* on a Matrox G200.

Probably something else in your system is triggering the problem...

Did you ever try to check out if anything gets logged with:

pmview /log=pmview.log

Usually if PMView locks up, it's because of an IBM OCL bug and in this case the problem should clearly show up in the log.

Oh, but you say the clock stops. Then you're right! It IS a driver bug. An application can not lock the system that hard. So PMView obviously triggers a driver bug in your system for some reason...

Have you tried to upgrade to the 2004 kernel?

Thanks,



Edited By Peter on 1077110963

[asavage]

I don't think it is the Matrox driver. I'm using the matrox drivers 236 and 258 on a daily basis, and can't repeat the problem.  

FWIW, PMView 2000 and Pro were both *developed* on a Matrox G200.

Probably something else in your system is triggering the problem...

Did you ever try to check out if anything gets logged with:

pmview /log=pmview.log

Usually if PMView locks up, it's because of an IBM OCL bug and in this case the problem should clearly show up in the log.

Oh, but you say the clock stops. Then you're right! It IS a driver bug. An application can not lock the system that hard. So PMView obviously triggers a driver bug in your system for some reason...

Have you tried to upgrade to the 2004 kernel?

Thanks,

Did you ever try to check out if anything gets logged with:

pmview /log=pmview.log

I always run PMView with that parameter. Unfortunately, nothing gets logged:

[code:1:post_uid0]
PMView Pro v3.05 build 22638  Jan 23 2004
OS/2 20.45 build 14.096 @ 1152x864, 24 bits
Started Tue Feb 17 19:48:32 2004
[/code:1:post_uid0]
And that's it, nothing more.

Have you tried to upgrade to the 2004 kernel?

I am running the 20031113d kernel. When I tried the 20040206d kernel, I lost much of the use of both COM ports, which really bites because I'm on dialup. And I also lost a bunch of PN/2's files in a lockup with that kernel -- so I'm taking a small vacation from Usenet, currently. I'm not really inclined to fool with 2004 kernels right now

Any [u:post_uid0]other[/u:post_uid0] suggestions?