Something definitely happened with the way WB handles those parameters between 7.0 Build 80 & 7.01 Build 83.  I have 7.0/B80 running on two other rigs & it still respects/enforces/remembers the maxbordercut settings on those; 7.01/B83 on the one remaining rig (my daily user) does not.

Perhaps if we keep bumping this, Neil will take a look.

He has...just waiting to see what he comes up with...he has many issues to deal with...doubt if this one is first...or even next.

How could any of those be more important than this?

Did you play for the 'Boys, BTW?

I just roots fer em

Updated to the 7.09 version today but doesn't seem to have fixed it.  However, the About WB dialog says this:

Is this just the time-honored/traditional Stardock failed-to-update-version-info-with-app-update thing or did my install get borked?  FWIW, it did hang for about a half hour at the 'verifying' stage & I had to cancel/restart the update.

I'm no expert on those file versions but that sure looks wrong.

They're all newer than the 7.0 files on my rig at home except for tray.exe which shares the same date.  Just don't know if they're the correct ones for 7.09 (& the '7.01' in the About WB dialog is just an 'Oops, forgot!').  I know longer have a 'known good' 7.01 version to compare to.

The XP version did not get any updates with the 7.1 beta.

There should be some XP updates with the next beta update which I.R. Brainiac has actually seen.

Thanks, Neil.  I'll come in off the ledge & put the gun away.

Here's what I currently have for WB:

WindowBlinds version : WindowBlinds 7.1 (build 90 x86)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.

(Plug and Play Monitor) 1 is attached to NVIDIA GeForce 8600M GT   

Wblind.dll         2010/06/07 15:10:20
Wbsrv.dll         2010/02/03 16:11:56
SevenConfig.exe         2010/06/07 15:10:02
Wbload.exe         2010/02/02 14:33:18
Wbhelp.dll         2008/04/28 11:35:07
Wbui.dll         2008/04/28 11:35:05
Tray.dll              2009/10/21 07:13:19
Screen.exe         2010/06/07 15:10:43

Still not respecting the maxbordercut settings for any windows (Windows Explorer was the only window so affected before).  Once any window is 'cycled' (minimized/restored -> maximized) the maxed window 'sets' properly.

I havnt tested this lately...I'm on 7 at the moment and not running a non perpixel blind.