WinSPM

[KellyOConnor]

I'm running WinSPM on an XP Pro box and it has always worked. I can't remember the last time I used it but today it opens and is missing certain areas as you can see in the screenshot. It still works it just looks bad. I have seen stuff like this before and a DLL will get updated or changed and break things. I did reinstall WinSPM and have not patched it up to 9 yet but 9 looked the same before I uninstalled it. I'm going to guess a Microsoft patch has killed it somehow. Windows in general uses certain controls, dll's, etc. to make dialogs have a certain look across the board and it seems like one is missing or changed too much for WinSPM to deal with. Anyone have any ideas?

 

[CarGoSki]

Don't know. Anything funny in the winspm.ini file?

 

[KellyOConnor]

No, I looked at it with notepad and it didn't have any garbage characters in it. So, I uninstalled WinSPM, deleted the folder and reinstalled it. Same :-(

 

[merlinman]

If you only do one site, then Remove DATA and SITE DATA and then re-install and see if that works.

After 10 years of doing this, and suffering MANY BAD CRASHES of WINSPM, I have finally gotten into the habit of making a complete copy of the WINSPM Folder once a week.

That will give me a copy I can "FALL BACK" to, just in case.

http://home.comcast.net/~merlinman

 

[EmuDan]

From the screenshot it looks like you were running version 3 of WinSPM. Maybe the newer copy is in another folder somewhere. Did you check C:\Program Files\Avaya Solutions\WinSPM and see if the Readme file is for version 9?

EmuDan

 

[KellyOConnor]

Thanks merlinman for the reply. You are correct, I only do one site and don't really care to even back it up. I Uninstalled WinSPM and simply deleted any folders related to it which also deleted the site data. Then, Reinstalled, recreated the site and still the same. The funny thing is even the login box looks messed up. I have included a link to a screenshot of the login box. I'm still thinking something in Windows XP Pro SP3 has changed. I keep our computers here patched up with all of the patches. So, if anyone knows of all the dependencies of WinSPM to Windows XP we might figure it out. WinSPM, like many Windows programs, depend on certain standard DLL's to be installed and are typically not included with the program being installed. If one of the standard files are missing or the wrong version then the application goes haywire. I just don't know which files WinSPM relies on.

Kelly

 

[KellyOConnor]

EmuDan, I was runing version 3 just to test whether it would re-install and fix itself. Then I did the patch by patch upgrade all the way to version 9 and it's still messed up. The program still works, it's just hard to read without all the text labels in place. I may just have to live with it. You can see from my second screenshot that even the login box looks odd.

Kelly

 

[TouchToneTommy]

Have you changed the fonts on your computer? In the readme file that pops up on installation or upgrade, there is always a line about "large fonts are not supported".

If you want to try an installation of R9 without doing all the upgraded, contact me through my website.

 

[CarGoSki]

Try right clicking the winspm shortcut and setting it to run in compatability mode.

 

[KellyOConnor]

TouchTone: no font changes, I remember in the readme it mentioning large fonts not being compatible. I'm sure it is something about my work computer that is doing this. I have many, many programs installed for network administration, Server administration, etc. (I'm an IT Manager) As I test sometime today I will try installing WinSPM to another test computer and see how it does. I will report back what I find.
I do have the full install of 9, but the day I tested with 3 simply to see if it would make any difference using an older version. I'm back at 9 now.

CarGoSki: Yep, aleady tried that. In 95 or 98 mode it gets a borland database error but still loads to the broken looking interface. 2000, it loads without complaining but still broken. NT, same.

Kelly

 

[SYQUEST]

Maybe Windoz has a registry problem. You might want to try a utility to check Windoz for problems, then see what happens...

....JIM....

 

[dagwoodsystems]

Do you experience the same Windows "screen repaint" problem when using Standard WinSPM or only when using Quick Access?

Tim Alberstein

http://www.dagwoodsystems.com