Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bweiß]

So on and off for years I've used IL2-Mat Manager v2.36. For the last year or so, I've used it with IL2 1946 BAT 4.2.1.

System uses Win 8.1/64 bit.

IL2FB.exe is installed on drive G.

Well I messed it up with custom mat files, and upon uninstalling it and reinstalling it, it no longer recognizes (IL2.exe).

I've used IL2fb.exe SAS version 5.0.0.3 (01/2019), copied it to another folder, renamed it IL2.exe. Nada. (Both IL2.exe and IL2FB.exe are both in the IL2 1946 root for all of these attempts as directed).

IL2fb.exe SAS/UP version 5.0.0.2 (05/2013), copied it to another folder, renamed it IL2.exe. Nada.

I even tried to use IL2fb.exe (Sept 5, 2006), copied it to another folder, renamed it IL2.exe. Nada.

I tried installing IL2-Mat Manager in drive G, and in it's default location in C:/Program Files (x86). Nada.

...and yes I have ClearCache=0 in the [game] section of the Conf.ini, and even tried renaming IL2FB.exe as IL2 with no ".exe", and also tried to installed IL2-MM folder inside the IL2 1946 root folder of the "G" drive where IL2 1946 resides. No change.

I've tried running it in compatibility mode, but it comes up with an error. Will not run in compatibility mode or in administrator mode. (Both or either of those (compatibility mode or as administrator), get the following

error: /Run-time error '339':
Component 'mscomctl.ocx' or one of it's dependencies not correctly registered: a file is missing or invalid

(I believe I first encountered this mscomctl.ocx error many times before when I tried to use IL2-MM in administrator mode - never needed to run it as admin before though as it worked just fine out of the box). But in fiddling with it in the past, I remember that error so I have to
think it is not the issue, though it keeps me from running it in admin or compat modes at this juncture.

Which I thought/believe, is an error for Windows 10 on 32 bit programs (which IL2-MM) is. But should that take place in Windows 8.1/64?

I tried the DEP trick, telling the system not to use on IL2-Mat Manager, IL2.exe, and IL2FB.exe. Nada.

I've told my anti-virus not to monitor either IL2-MM, or IL2 1946 folders and processes. In fact, I shut the anti-virus down when using the game or game apps.

I've uninstalled it, carefully removing all files associated with IL2-MM, in the IL2 1946 root, and Coop/Regiments folders, and reinstalled it more times now than I can remember. And of course, I have to use the task manager to shut it down when it can't find IL2.exe.

So, what I'm looking for is the "secret sauce". Something that I'm unaware of.

The IL2-MM worked like a charm before I tried using my custom mat files, which due to BAT 4.2.1., may, obviously were, not compatible as I created them many, many versions back in time. Up to that point however, no issues nor any problems with either IL2 1946, or IL2-MM prior to the uninstall of IL2-MM. Issue began upon uninstall/reinstall. Nothing else was moved, deleted, or modified. In all this time of using IL2-MM I've only encountered this when I "forgot" to copy IL2FB.exe and rename it to IL2.exe. And then it would work. Not this time?!?

So then, anyone have any ideas? Is there something I'm not seeing here? Gremlins?

For whatever reason, IL2-MM is not recognizing il2.exe. Period. What outside the normal things listed above that should always work, could be causing this seemingly out of the blue?

Appreciate anyone giving me any assistance.