New Beta Not Working

Umm, this latest beta isn't working for me. Not at all. The program freezes whenever I try to open an image, requiring Ctrl/Alt/Del and making it unusable.

Same here. File --> Open Image --> Select any image file.

Program just freezes.

I don't understand why a new update has to be forced upon the user, as opposed to just letting the user choose if they want to install it or not. And if you are going to force the user to update, you could at least check that the update is actually working.

This is not some obscure bug we're talking about, the program can't even open an image.

I can't open the new beta at all and can't put back the old one because it will not work.

Now I can't use Filter Forge 3 at all.

also, if you're using any version of windows to download and install tthe new version, make sure that your file size is what the website says the file size is supposed to be. windows downloaders are notorious for NOT downloading the entire file.

It doesn't freeze for me, it abort before finish to load

File size is correct, i try to reinstall avoiding overwriting, so with a clean install no joy

I tought could be a win 7 lock (you know 7 place locks on everything on Program Files to "raise the security level" ) so i reistalled again in a different directory, again it abort at start up

PS

here the bug log, i already send automatically but since i would not mind a free copy and automatic report don't count here it is

Operating system: x64 Edition (6.1 build 7601) Service Pack 1
Physical memory: 8182 MB
Number of processors: 4, available: 4
Processor info: Intel® Core™ i5 CPU M 430 @ 2.27GHz, ~2253 MHz

Filter Forge x86-SSE2 3.004.22135.32562 Release-SSE2, September 30, 2011 15:34 [02/10/2011 14:17:57 ora legale Europa occidentale]
[Controls::Control] Exception occured while processing window message 0x00000201(WM_LBUTTONDOWN) (0x00000001 0x007600D2) for window 000E040C/000E040C, control: <class Controls::SplashControl>@017B9450.
Exception caught at thread 00000D04 'Application':
<class XFW::OSCallError> form.GetThemeMetric failed failed.

<unknown file>(0) : <unknown function>()+0 at 005B22F0 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00DBD224 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 0047D082 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 005556A2 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00555F45 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 005B160C in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 005C228E in Filter Forge x86-SSE2.exe
<unknown file>(0) : gapfnScSendMessage()+818 at 75AA62FA in C:\Windows\syswow64\user32.dll
<unknown file>(0) : GetThreadDesktop()+215 at 75AA6D3A in C:\Windows\syswow64\user32.dll
<unknown file>(0) : CharPrevW()+312 at 75AA77C4 in C:\Windows\syswow64\user32.dll
<unknown file>(0) : DispatchMessageW()+15 at 75AA788A in C:\Windows\syswow64\user32.dll
<unknown file>(0) : <unknown function>()+0 at 005AE532 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 006D1320 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 006D0EDC in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 005AEC7B in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 0057B966 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00550D11 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 0040F81B in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 006CEEFF in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 00788077 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 006CDD00 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 006CECDA in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 0081EEE4 in Filter Forge x86-SSE2.exe
<unknown file>(0) : <unknown function>()+0 at 008ADE83 in Filter Forge x86-SSE2.exe
<unknown file>(0) : BaseThreadInitThunk()+18 at 75DC339A in C:\Windows\syswow64\kernel32.dll
<unknown file>(0) : RtlInitializeExceptionChain()+99 at 77E49ED2 in C:\Windows\SysWOW64\ntdll.dll
<unknown file>(0) : RtlInitializeExceptionChain()+54 at 77E49EA5 in C:\Windows\SysWOW64\ntdll.dll
CONTEXT_CONTROL: CS:EIP 0023:755CB9BC, SS:ESP 002B:00184268, EBP 001842B8, FLAGS 00200212
CONTEXT_INTEGER: EAX 00184268, EBX 0000000B, ECX 00000003, EDX 00000000, ESI 00B03704, EDI 001842F8
CONTEXT_SEGMENTS: DS 002B, ES 002B, FS 0053, GS 002B

Please CFandM let me borrow your text and change it a little

Stupid things happen to Beta Software for stupid reasons at stupid times!

I do not know how is possible that they have released the new beta on friday which is a stupid time because the FF team is not working on weekend.

I was working in a interesting test with FF 3.0 Beta version 2 and have been waiting ALL the week for the weekend to be able to continue with it and then surprise, surprise on friday FF releases and NEW version that block version 2 BUT the new version is really dysfunctional, impracticable, inoperative, nonfunctional, unfunctional, unproductive, unusuable, unworkable, worthless.

I am sorry FF but this gives me a very high deception.

A whole weekend lost without FF 3 that was hoping to work with.

Also lost much time trying to get FF 3 beta 3 to work with no luck, making a clean install, cleaning registry, and amking test to see if it could work, but nothing can make FF 3 work right.

Quote
SpaceRay wrote: Please CFandM let me borrow your text and change it a little Stupid things happen to Beta Software for stupid reasons at stupid times!

By all means please do...Oh wait you just did..

Quote
SpaceRay wrote: Also lost much time trying to get FF 3 beta 3 to work with no luck, making a clean install, cleaning registry, and amking test to see if it could work, but nothing can make FF 3 work right. smile:evil:

Thats why I make it need to download every installer (especially alpha and beta versions) that was ever posted...Its been a long practice and seems like a trivial and hoarder practice but if something every was to arise such as this, I would have a way to install an older working version of that software that was tested or used....

CFandM - I downloaded all the installers and tried to put the one before this one back. It says that it needs to be updating, so I can't use FF3 at all now. I always keep older versions when there are a number of new I went back to FF2, but all of my changes made recently were in FF3 so I basically was going back about 6 months.

I hope this problem is solved on Monday.

Quote
Paula Sanders wrote: but all of my changes made recently were in FF3 so I basically was going back about 6 months.

Yep I know what you are saying there.. I have to go back about 2 months to get the previous version to work..
Have some version3 filters still unfinished..

Quote
KirkDunne wrote: This will also teach me NOT to build/edit new filters in a beta, lol. (filters that I might end up really needing, anyways). Build those in version 2...THEN take it over to version 3 beta.

Yes it is true, you can not trust anymore in FF releasing betas that work as they have done before, and work building new filters on these betas because you do not know when they are going to release a new beta by surprise and then block the previous beta and you will not know if the new beta will be working or not as before.

The problem building them before in version 2.0 and THEN taking it over to beta 3 is that you willnot be able to use any of the new features for this filter construction.

Or begin building using the features that are from 2.0 and then when you reach the point that you will need the 3.0 features transfer it to beta 3.0, but know that any day this beta can be blocked and locked out and you will not know if the new beta works in the same way as the previous beta.

Quote
Paula Sanders wrote: I always keep older versions when there are a number of new I went back to FF2, but all of my changes made recently were in FF3 so I basically was going back about 6 months.

I too also keep always the old version until the final new official version is released, and also had the FF 3.0 more actualized and configured BECAUSE FF 3.0 takes over the activation of filter loading from Browser and FF 3.0 beta is the default when starting from filter download from browser, but now I do not have it anymore since the beta 3.0 version 3 is released and blocks any previous.

Although I learnt from the previous beta 2 that you can´t trust in this and you can open FF 2.0 BEFORE trying to download any filter that is important and you need and so the FF 3.0 will not be activated, and now with the great Beta 3.0 version 3 freeze unusable can´t trust anymore in the beta as main program, just only as a test as they release a new beta by surprise and blocks the previous beta and can´t be used anymore and if there is some problem like now you are without FF.

With this new freezing Beta 3.0 version 3 they have frozen my trust in FF and do not know how is possible that they have not tested and released a working version like Beta 3.0 version 2.

If one just could go back in time.. hmm I wonder how

This is very painful, and it didn't need to be.

Forced to update - never good
Bad update - never good
Friday update - beware
No support for days after update - never good

For those of us that are trying to work and need FF this is a very nasty episode.

BTW Rod, there is no way system restore works when the update is FORCED.

Yikes!

We've updated the beta, please redownload from our beta page.

PhotoComix was the first to post a full bug report on GetThemeMetric failed — that's one bug point for you.

Quote
Sphinx. wrote: If one just could go back in time.. hmm I wonder how smile;-)

All you need is a DeLorean and some plutonium to keep that Flux Capacitor fluxing.....

Quote
CFandM wrote: All you need is a DeLorean and some plutonium to keep that Flux Capacitor fluxing.....

Actually a few mouse clicks in the lower right screen region will do

Quote
And yes system restore does take your computer back in time.

Well I guess in some sense, but you know what - the system time is still up to date after restore (hint hint)