MCSX not fully loading, anyone else?

[boroko]

Just tried to run Micro Code Studio v.5 (MCSX) and it is locking up before completely loading.
I have been running it on this machine for quite a while (XP sp3). I removed it, went into the PGP3 directory and got a fresh install, rebooted the machine, and it is still the same!?!?.
When it starts loading I get an error window "CodeStudio.exe- entry point not found" "The procedure entry point ThunkConnect32 could not be located in the dynamic link library KERNEL32.dll"

I have been getting the error about thunkConnect32 for ever and was told it's not a problem.
I get the program icon in the lower task bar, but nothing else.

I am at a bit of a loss here. Anyone had this problem or have any ideas?
Thanks
Mark

[boroko]

I see that a number of you have looked at this and there are no ideas as of yet.
I am beginning to believe it is more of a machine problem than a program problem. I have down loaded a new copy from Mechanique and loaded it with the same symptoms. If I boot in safe mode, it still will not run, and if I open the task manager, PBPX.exe locks up 50% of my core 2 Duo processor until i kill it even after closing an unresponsive program. I have once seen an error that stated ; WSAStartup not yet determined, but I have not been able to go any further.
Still fishing for suggestions, short of rebuilding my system.
Thanks.
Bo

[boroko]

BTW, MCS v3 still runs fine. it just makes it hard to work with PBP3 without MCS v5.

[prstein]

I've no particular insight for you, but I can confirm I'm running it on a very similar system without issues.

System properties says:
Intel(R) Core(TM)2 Duo CPU
P9600 @ 2.66GHz

I assume you've tried a clean install of MCSPX?

Best Regards,
Paul

[Dave]

Try a search on the web for "ThunkConnect32". From what I have read it's a corrupt windows problem and there are some automated fixes available for it.

[boroko]

Thanks for the replys. I have found that there are corrections for the ThunkConnect32 problem and will work on them, but I have been running with that error for years and Jeff S has told me in the past that it was not a problem. If it does correct anything, I will post it here.