WordPro crashes during initialization if WindowBlinds is active

from Stardock Forums

I have a program, Lotus WordPro (part of the Smart Suite Millenium Edition Version 9.8) that crashes during initialization when WindowBlinds is active.  The program runs fine if either WindowBlinds is unloaded via the taskbar icon unload option or the "default" skin is applied using the WindowBlinds configurator.  Both of these options seem to return the computer to the state where WindowBlinds is not running at all.  In contrast, if WB is up and running with any of the standard skins supplied with the program, then WordPro crashes shortly after initalization (a popup occurs about gathering data to send to Microsoft and the system event log shows that an program error occurred).

Seeing this, I added WordPro to the per-application exception list and specified exclusion of all skinning.  But the crash still occurs.  If WindowBlinds is active, WordPro crashes even if excluded from skinning; if WB is not active then WP runs fine.

Any ideas for a fix or bypass that is amenable to automation?

 

Computer software data:

Windows 10 Enterprise (18362.19h1_release_svc_prod1.190628-1641)
WindowBlinds 10.84 (059 - Windows 10 Edition) - 64 bit OS
Windows 10 Pro 64-bit Version 1903 Build 18362.592   

windowblinds
8,062 views 6 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. But, from what I read online, this "Smart Suite Millenium Edition Version 9.8" is very old and not listed as Windows 10 compatible.

For reference : https://www.cnet.com/products/lotus-smartsuite-millennium-edition-v-9-8-complete-package-series/

Anyway, I have forwarded your questions/problems to the Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate you feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

Quoting basj, reply 1

But, from what I read online, this "Smart Suite Millenium Edition Version 9.8" is very old and not listed as Windows 10 compatible.
End of basj's quote
This might be an apt description for me as well.  But it and I do work and we will see what we get.  My fallback will be to use AutoHotkey to load and run the WindowBlinds configuration program before and after WordPro and manipulate it with automated keystrokes and clicks -- a truly ugly hack but automatable.

SoundPackager - Customize the Windows sound scheme
Reply #3 from Stardock Forums Top

Just a suggestion, if you have a capable system, you can make a Virtual Machine that run without Windowblinds and that VM can run your Lotus WordPro on it. Infact, you can create VM using Windows XP which is certified compatible with it.

Thank you,

Basj
Stardock Community Assistant.

Reply #4 from Stardock Forums Top

Quoting basj, reply 3

Just a suggestion, if you have a capable system, you can make a Virtual Machine
End of basj's quote
Funny you should mention it.  Spent all yesterday trying to get a Hyper-V machine set up and running and then a VMware Player machine set up and running.  Got Win XP going in both.  Failed with Hyper-V to find a reliable way to connect to it from the desktop using Remote Desktop (necessary to have standard shortcuts firing up applications).  Failed in VMware Player to get its Unity mode running (it fails somehow in installation).  Today I will try porting Windows XP Mode.

In passing, last night I did the hackery to get WindowBlinds to go away and come back nicely from a command line.  There are artifacts; at least one program started while WindowBlinds is running does not operate normally after WindowBlinds is disabled, and the taskbar's system tray loses many of its icons when WindwoBlinds is stopped, but I can live with these.  The one program is an AutoHotkey program that hooks lots of things.  These anomalies also occur, by the way, when I use the standard WindowBlinds icon in the task bar to unload it, manually, not using any automation.

Reply #5 from Stardock Forums Top
Quoting Randy31416, reply 2
Quoting basj,
reply 1

But, from what I read online, this "Smart Suite Millenium Edition Version 9.8" is very old and not listed as Windows 10 compatible.

This might be an apt description for me as well.  But it and I do work and we will see what we get.  My fallback will be to use AutoHotkey to load and run the WindowBlinds configuration program before and after WordPro and manipulate it with automated keystrokes and clicks -- a truly ugly hack but automatable.

End of Randy31416's quote

I am wondering if running the dated app in a different compatibility mode - perhaps keeping the WB exclusion - helps:

Sean Drohan
Stardock Support Manager

Reply #6 from Stardock Forums Top

Quoting sdRohan, reply 5

I am wondering if running the dated app in a different compatibility mode
End of sdRohan's quote
Nope.  I tried them all (maybe I missed a service pack level) from Windows 95 up to Windows 8.