Windows XP SP1, 2000 and older FlashGot.exe error

[Giorgio Maone]

If you're an user of Windows XP SP1 or older (e.g. Windows 2000) you'll probably receive an error message from FlashGot.exe as soon as you upgrade to FlashGot 1.4.

This is due to an incompatibility between Visual C++ 10 (which FlashGot.exe has been rebuilt with to add FlashGet 3.7 compatibility) and older Windows version, introduced (intentionally?) by Microsoft.

This is tentatively fixed in latest development build 1.4.1rc1, but I can't test by myself and it's not confirmed yet.

Please install the aforementioned latest development build and let me know if it works by replying to this thread.
If it doesn't, please consider downgrading to 1.3.9 until a solution is found.

[strawbeard]

Confirmation: latest development build works with Windows 2000 SP4.

[landrieu]

Still receive error msg in XPSP1. Reverting to 1.3.9 fixes, but auto update keeps pushing 1.4

[Giorgio Maone]

Still receive error msg in XPSP1. Reverting to 1.3.9 fixes, but auto update keeps pushing 1.4

Do you mean you receive it with 1.4.1rc3 (I wonder why Windows 2000 users report it working then)?!
BTW, is there any reason not to upgrade to SP2 (genuine curiosity)?

[Tom T.]

.... BTW, is there any reason not to upgrade to SP2 (genuine curiosity)?

None whatsoever. FYI only, my OEM, Toshiba, urged customers who had the original XP (I didn't) NOT to install SP1, because they were getting numerous issues from it -- sometimes, crashes; sometimes, required a complete reinstall. Searching the web will result in numerous other reports of same from various sources.

They *did* urge customers to install SP2, and provided it with OEM technical support.
(My present machine came preloaded with XP SP2, in 2005.)

Apparently, OP was either one of those for whom update to SP1 was problem-free, or the machine came preloaded with that version.

If OP doesn't want IE 7+ or .NET or whatever, those should either be subject to de-selection during the update process, or removable afterwards, depending on the OEM or a retail Windows disk, etc. However, once you get to a certain level of .NET, I think it becomes uninstallable. I've never missed that resource-hog, personally. IMHO. YMMV.

But yes, update to SP2. Lots of security and stability improvements.

[Fulvio B.]

Another confirmation: 1.4.1rc2, on Windows 2000 SP4, FF 3.6.27, tested a lot, works fine. Thank you Giorgio!