Ok here's an update. I did not upgrade to 7600, I am still using 7100 RC.
NOTE: this is the x64 bit version. There was no problems with the 32bit version of windows 7, this issue in my Oringinal topic, is 64bit specific.
And, at 4gb of ram, CS4 at least for my machine, doesn't feel like it's lacking ram at all, now that I got in working. The problem after all had nothing to do with the build of Windows 7 x64 that I was using. It was Flash CS4. After reinstalling it, it still didn't work. So since I didn't have a copy of 7600 to try, I went and got Adobe CS4 Master Collection. Since that was the other difference between myself and Reaper.
That did the trick. My original copy of Flash CS4 stand alone would not run, but after installing it from the Master Collection, it works like a charm. There are obviously some differences between THOSE builds. It wasn't windows 7 causing the issue at all.
I have been running Flash CS4 after installing the masters collection for about a week now, without a reboot, or even shutting down Flash CS4 at all. And it's blazing fast.
Shiffsratte, your problem with slowness is not your RAM, it's your Athalon1 cpu, it's not really worth the material it's made out of anymore. Upgrade to a half decent dual core cpu and you'll be fine. And using an original Athalon cpu, then you must also be using an old motherboard, which takes older, slower style ram, probley not even DDR2. The amount of RAM you have doesn't make a big difference if the RAM is slow.
I'll take 1gb of DDR3 over 4+gb of DDR1 anyday. Your machine needs upgrades
Fabinho, I wasn't getting a JavaScript error. Whatever your issue was, it wasn't the same as I was having. I program in JavaScript, doesn't mean I know everything, but I'll know if I'm getting JS errors, and usually how to fix them. And I always make sure I'm fully updated and patched on my Adobe products. It was the first thing I did when I installed Flash CS4 on windows 7, just incase there were any windows 7 specific fixes or updates available from adobe.
So thats my story. If you have Adobe Masters Collection, it works, even without patching, if you have the stand alone copy (which is SUPPOSED to be the exact same program) then it won't work. Why i dunno, but it's something Adobe runtime side.
Hope this helps some people out there. Chow!