rustweaver

Is anyone here having issues with firefox 4 portable? I just can't get it to run properly. It keeps freezing and crashing on basically every site i try to visit. The only two web pages that work (i.e. manage to load) are "welcome to firefox" page, and firefox homepage (google). I tried various combinations of JIT compilation, even turning it completely off for both chrome and content, i disabled flash plugin, out of process plugins, hardware acceleration (just in case). What's funny is that firefox 4 consumes less memory on startup (according to wintop), and its UI feels more responsive than that of firefox 3.6, it's just that web pages are not loading and then whole application becomes unresponsive. It might be due to seriously underpowered system i'm trying to run it on, (p3 500, 128mb ram), but still on that same system firefox 3.6 runs just fine. Any ideas? p.s Win98 SE with KernelEx 4.5 final.

Yes, i finally got 32 bit icons working following these steps. Thank you. For Tihiy if he wishes to investigate: Windows 98 SE KernelEX 4.5 RC4 Revolutions Pack 9.6.5 Nvidia Detonator 45.23 drwatson_snapshot.zip

That solved the RPConfig issue, but not the Code::Blocks issue. Although they appeared to be related i guess they are not related after all. But still, thanks a lot.

I have an issue to report related to KernelEx 4.5 RC 1. I am unable to switch revolution pack skins when firefox (3.6.8) is running (RPConfig just does what appears to be initial resizing of controls before applying skin, and then just stops at that point and becomes unresponsive. I have to kill it in task manager). I tried to change skins in old fashion way using Appearance tab, but same thing happens. When I close firefox, both ways of switching skins are working properly. There is also one other related thing. My own nightly ansi build of Code::Blocks refuses to start and it's entry in task manager just sits there indefinitely doing nothing until i kill it. This is also firefox related, as when i close firefox it can start just fine. That behaviour did not happen in KernelEx 4.0 final2.