CCW = Connected Components Workbench, for those who don't know.Īfter scanning Process Explorer (from Windows Sysinternals) for a while, I found one file that turned out to be the issue - DT元2.dll I had upgraded from CCW 10.01 to CCW 11.00, which forces RSLinx 4.00 to be installed (so installing RSLinx 3.90 or less is not an option for me). After I do, I'll downgrade RSLinx to v3.9 and see if that fixes the problem. I'm going to have to re-image this machine soon. I've had hellish experience with Windows XP mode so I'm going to stick to a VMWare virtual machine. Or Roach would have figured out a way to do it. KEN ROACH WHERE ARE YOU?!?!?!īack in the good old days, say around the time RSLinx was coming out to replace Interchange (actually it was Wintelligent Linx first, wasn't it), Rockwell have made some utility that would just cause RSLinx to lie about it's version number to PB32. There has to be some combinations of these fixes that will work. Run RSLinx itself in compatability mode for XP. Right click on PBWin32.exe and run it in compatability mode for Windows XP. Right click on WinPFTv2.exe and run it in compatability mode for Windows XP. I'm surprised you got it working at all in Windows 7". I too called Tech Support and just got "PanelBuilder32 is not supported after XP. What bothers me is that I had it working fine on Win 7 64-bit and it just doesn't work on Win 10, but I think I was running RSLinx v3.9 on Win 7 and now I'm at v4.00.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |