Problems with FaK 3.5 and WMM, Shell32.dll

I have loved using FaK -- first of all.

Recently I've encountered a couple of problems that have compelled me to uninstall FaK 3.5 for a while:

Windows Movie Maker can't find files required for doing transitions between movie files in a project -- I read about this problem on a WMM website -- see the second page of this thread (http://www.windowsmoviemakers.net/Forums/S...spx?PostID=2014)
Because of the size of Shell32.dll under FaK (presumably from all the icons? It reached 27Mb in size) I got an error when opening some apps (Calculator for example): "The system DLL user32.dll was relocated in memory. The application will not run properly..." and after uninstalling FaK the problem has of course disappeared.

Does anyone have fixes for one or both of these problems? Using XP's regular interface is a sad way to live.

Windows Movie Maker: Uninstall it using the Flyakite uninstall option. If that doesn't work, go to Start-> Run and type in

%systemroot%/inf

Navigate down to moviemk.inf. Right click the file and select "Install". Insert your Windows XP install disc and clock Ok.

#451493

Ciao,

I had the same problem, on 2 computers, I guess it is the Windows update from the first days of April, one of those countless security updates from Microsoft. I restored to a prior point, last day of March and everything works well again with FaK..

Tray

#451652

Yes, it's the "mouse cursor" security update. I don't think uninstaling it is a good solution, it contains many critical security patches.

#451721

I "solved !?" the problem in two steps: 1st using a Microsoft hotfix and 2nd not allowing FaK to update the system files. Herewith the systems operates properly again. However some icons turned to be "windows-like" again. Expecting a better solution of the problem........

#452144

Has anyone found a solution?!?!

#452581

I had the same problem when trying to load Calculator, a Gimp XCF directly from the file and also when trying to load Acronis True Image.

The only thing I can think of is uninstalling the shell32.dll that came with FaKOSX. Either that, or uninstalling the security patches, but that isn't going to be a good solution in the long term.

#455312

I reported this to Chris a week or two ago using PM here and to his email address but so far have not received a reply indicating he received either. He mentioned he would be working on a new version but not to hold him to a time table (if I remember correctly.) I think he'll do something eventually, we just need to sit tight and be a little patient.

for the time being, i just haven't installed security update: 925902 (MS07-017) on my computers while employing reasonable intuition and security of other means.

here is the gist of my email:

recent security updates by microsoft: 925902 (MS07-017) and 928843 (MS07-008) and running Windows XP Sp2 has caused an interaction with FlyakiteOSX3.5 to throw up this error (close approximation,) on windows Startup:

"The system DLL user32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL C:WindowsSystem32[application name here] occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL."

I've tested this on 3 machines running 3.5 prior to the security updates, all with the same result. Additionally used system restore in testing to isolate suspected issue.

Excerpt:

Cause of the problem

The Hhctrl.ocx file that is included in security update 928843 and the User32.dll file that is included in security update 925902 have conflicting base addresses. This problem occurs if a program loads the Hhctrl.ocx file before the program loads the User32.dll file. Microsoft has confirmed that this problem affects the following third-party applications.

Microsoft Bulletin:

http://support.microsoft.com/kb/935448

it indicates BricoPack Vista Inspirat as also affected by the update.

also, welcome, the new users who are posting for clarification/fix to this issue

#455313

I uninstalled FaK and reinstalled it -- the shell32.dll problem is gone; presumably Windoze after the most recent update ensures that modifications to shell32 don't make it unusable.

Reinstalling WMM using the tip above worked fine...

#455466

i solved the problem by editing the DLL's base address. I found the instruction at another forum and followed that. It works!

This link is: http://forum.crystalxp.net/index.php?showtopic=18709

#456498