03.12.2009, 01:58
I'm horrified to hear about this Trojan Horse infection.
I have accepted few days ago an overwrite of my wrapper to assure
the very best install of I don't remember exactly what. It most probably
was the SAS mod activator 2.01 ( allows upgrade 4,09m over 4,08m...
without lost of older mods)(also Mig15bis installed W/O Uni1.2.)
Not to say that I dont have problems: my open-GL lately has been working poorly
in certain areas of the game. It returned to almost normal after freeing more space
on my hardrive, but I'm still having that video issue in my FMB. However that has been
going on for couple of months, long before nany of my new installs.
Simply an old computer, my video card may be on the way out. Starving for more Gigs.
I want to point out that IF your problem is an Anti-Virus issue where the Anti-Virus
causes false alarms, then oubviously it will cause these same false allarms with
all the same files (wrapper) anywhere, on old saves, old backups and that
even if they where isolated from potential infetcs by been completly inactive.
The reason is that if nothing has infected them, then they will all react the same
to the troublesome virus-scan, since they ALL are actually free of the virus !!!
In other words, if protected backups are ALL responding identicly to
your infected one, then that is more reason to believe there is no infection at all.
Otherwise this infect must had happen a very very long time ago. So
why would it wait for your specific virus-scan to pop-out-just now ???
I think your situation may be better then you think.
As for the russian-bug there are lot of solutions offered everywhere. There was
for instance a small issue of russian even in the SASmod-act. (I think about the
English Awards) They identified the file.ru that the IL2 was reading and transferred
the text content of the english fille into the .ru file: so now the .ru file is read as
being the english one. An IL2 in russian is an issue there since the very beginning
of all mods. Just go back and search old posting on the suject, or just take the
advice from people here who have resolved that issue and still rember how.
I have accepted few days ago an overwrite of my wrapper to assure
the very best install of I don't remember exactly what. It most probably
was the SAS mod activator 2.01 ( allows upgrade 4,09m over 4,08m...
without lost of older mods)(also Mig15bis installed W/O Uni1.2.)
Not to say that I dont have problems: my open-GL lately has been working poorly
in certain areas of the game. It returned to almost normal after freeing more space
on my hardrive, but I'm still having that video issue in my FMB. However that has been
going on for couple of months, long before nany of my new installs.
Simply an old computer, my video card may be on the way out. Starving for more Gigs.
I want to point out that IF your problem is an Anti-Virus issue where the Anti-Virus
causes false alarms, then oubviously it will cause these same false allarms with
all the same files (wrapper) anywhere, on old saves, old backups and that
even if they where isolated from potential infetcs by been completly inactive.
The reason is that if nothing has infected them, then they will all react the same
to the troublesome virus-scan, since they ALL are actually free of the virus !!!
In other words, if protected backups are ALL responding identicly to
your infected one, then that is more reason to believe there is no infection at all.
Otherwise this infect must had happen a very very long time ago. So
why would it wait for your specific virus-scan to pop-out-just now ???
I think your situation may be better then you think.
As for the russian-bug there are lot of solutions offered everywhere. There was
for instance a small issue of russian even in the SASmod-act. (I think about the
English Awards) They identified the file.ru that the IL2 was reading and transferred
the text content of the english fille into the .ru file: so now the .ru file is read as
being the english one. An IL2 in russian is an issue there since the very beginning
of all mods. Just go back and search old posting on the suject, or just take the
advice from people here who have resolved that issue and still rember how.