Print

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

[Plowshare]

It’s been a long time since I’ve been here – I hope I’m still welcome as I need some help.

I have Il-2 DBW 1.71 heavily modified to 31+GB on an NVMe drive and three other copies on three other HDDs.

I used Il-2 DBW 1.71 offline several times a week and once a week online with a friend until November of 2020. Since that point it’s only been once a week online with him over the past 4 years; I haven't added any mods or even made any missions in this past four years.

Both the Selector and il2fb.exe are running as Windows XP (Service Pack 3) compatibility as they always have been.

My hardware is two-and-a-half years old with no changes since the rebuild at that time.

Then "The Problem" started....

I went to start Il-2 through the Selector 2.2.2 as always on a Wednesday just over a month ago. The Selector came up but, after choosing the “Start IL-2 now!” button, the game wouldn’t start.

I tried the il2fb.exe direct running as administrator – no start.
I tried the il2fb.exe direct running as administrator on each of the other copies – no start.

Since that night here's what I've tried:

I disabled all 8 Avast shields – no start.
I uninstalled Avast – no start.
I disabled Windows Defender – no start.
I disabled Windows Data Execution Prevention (DEP) – no start.
I disconnected the internet cable and disabled Avast, Defender and DEP – no start.
I made a new Windows account – no start.

On the “S” drive I scanned both the IL-2 Selector.exe and the il2fb.exe with Avast. No issues.

I checked the registry for possible changes in the executable file parameters:

I first went to “HKEY_CLASSES_ROOT\.exe” – it had the “Value Data” set for the proper “exefile”.

I then went over to “HKEY_CLASSES_ROOT\exefile\shell\open\command” and the “Value Data” field was the correct “%1” %*”.

Ran the DISM “Dism.exe /online /cleanup-image /restorehealth” through the Administrator Command Prompt - “The restore operation completed successfully. The operation completed successfully.”

Ran the “sfc / scannow” through the Command Prompt - “Windows Resource Protection did not find any integrity violations.”

I realize all the registry repair attempts had to do with the “C” drive while the DBW is on the “S” drive but I’m running out of ideas!

My friend brought his DBW over on an external HDD and I tried running directly from that – no start.

I’ll say again: In all the above I ran the Selector then, when that didn’t work, I ran the il2fb.exe directly as admin.

I tried to reset default app through “Settings>Apps>Default Apps>Choose default applications by file type” – couldn’t find .exe on the list.

Today, October 20, 2024 I tried to run the Selector. I then went into the Il2 root file and checked for the latest file that has been changed. I found the "initlog.lst" file with this text:

2024-10-20 20:36:26:349 : JVM Parameters injector activated
2024-10-20 20:36:26:350 : Applying JVM Memory Settings from IL-2 Selector...
2024-10-20 20:36:26:350 : Adding JVM Option: -Xms1520M
2024-10-20 20:36:26:350 : Adding JVM Option: -Xmx1520M
2024-10-20 20:36:26:350 : Adding JVM Option: -Xss14024K
2024-10-20 20:36:26:351 : Adding JVM Option: -XX:PermSize=219M
2024-10-20 20:36:26:351 : Adding JVM Option: -XX:MaxPermSize=219M
2024-10-20 20:36:26:351 : Checking duplicate JVM Options...
2024-10-20 20:36:26:351 : Checking mandatory JVM Options...
2024-10-20 20:36:26:351 : Adding JVM Option: -Djava.class.path=.
2024-10-20 20:36:26:351 : Adding JVM Option: -Xincgc
2024-10-20 20:36:26:352 : Adding JVM Option: -Xverify:none
2024-10-20 20:36:26:352 : Adding JVM Option: -Xcomp
2024-10-20 20:36:26:352 : Final JVM Option List:
2024-10-20 20:36:26:352 : -Xms1520M
2024-10-20 20:36:26:352 : -Xmx1520M
2024-10-20 20:36:26:352 : -Xss14024K
2024-10-20 20:36:26:353 : -XX:PermSize=219M
2024-10-20 20:36:26:353 : -XX:MaxPermSize=219M
2024-10-20 20:36:26:353 : -Djava.class.path=.
2024-10-20 20:36:26:353 : -Xincgc
2024-10-20 20:36:26:353 : -Xverify:none
2024-10-20 20:36:26:353 : -Xcomp
2024-10-20 20:36:26:378 : Hooked "SAS_CreateJavaVM" function activated, injecting JVM Parameters
2024-10-20 20:36:27:853 : JVM Parameters injector deactivated

The next file, "il2fb.ini", has a "Date modified" as 09/05/2024 19:37. Here's the text:

[Settings]
ModType=4
RamSize=1753
TIR=0
ExpertMode=1
LAA=0
UseCachedFileLists=0
MultipleInstances=0
ExitWithIL2=1
[JVM]

The next logs with the nearest changed date go back to when my friend and I last flew. These files are:

sound.log
conf.ini
console.cmd
logfile.lst
eventlog.lst

All the above have the "Date modified" as 08/28/2024 22:49 when we signed off Il2 for the night.

This is the ONLY program that has stopped working. I cannot find any other program that won’t start.

If there is any more information needed ask and I'll see if I can come up with what is needed.

I hope I can get this running as my friend and I miss our Wednesday night Flight Nights!

Bob

[Frankiek]

have a look here https://www.sas1946.com/main/index.php/topic,71235.msg775749.html#msg775749

[Plowshare]

Hi Frankiek:

Thanks for the link. However, the DEP setting was already set for "Turn on DEP for essential Windows...." It had no effect.

Something I noticed in both the picture from the link and on my DEP window was, at the bottom, the line "Your computer's processor supports hardware-based DEP. Could this have an effect?

Thanks you.

Bob

[SAS~Storebror]

Ancient Selector version with critical RAM settings.
What could go wrong? 

Updating to the most recent Selector version is definitely in order.
Using safe RAM settings likewise.
Don't run in compatibility mode (no need to).
And if it still doesn't work (and only then), Windows Event Log ("Application" section) might shed some light on this.


Mike

[Plowshare]

Ancient Selector version with critical RAM settings.
What could go wrong? 

Updating to the most recent Selector version is definitely in order.
Using safe RAM settings likewise.
Don't run in compatibility mode (no need to).
And if it still doesn't work (and only then), Windows Event Log ("Application" section) might shed some light on this.


Mike

Hi Mike:

Sorry, it's been such a long time since I've been away from Il-2 (as seen by me using DBW!) that I can't remember what to do here.

Where do I get the latest Selector and how do I change the RAM? I unset the compatibility and still no startup.

I went into Event Viewer and found this on the General page from 10/21/2024 09:50:54:
Faulting application name: il2fb.exe, version: 3.0.6.10, time stamp: 0x44fe754b
Faulting module name: jvm.dll, version: 0.0.0.0, time stamp: 0x3af53001
Exception code: 0xc0000005
Fault offset: 0x000495ba
Faulting process ID: 0x4f8c
Faulting application start time: 0x01db23c03fb08b1a
Faulting application path: S:\DBW 1.7  Static\il2fb.exe
Faulting module path: S:\DBW 1.7  Static\bin\hotspot\jvm.dll
Report ID: f0bb02b0-5073-4411-8b09-8589d311282b
Faulting package full name:
Faulting package-relative application ID:

And this from the Details page:
- System
  - Provider
   [ Name]  Application Error
   - EventID 1000
   [ Qualifiers]  0
    Version 0
    Level 2
    Task 100
    Opcode 0
    Keywords 0x80000000000000
   - TimeCreated
   [ SystemTime]  2024-10-21T13:50:54.8395394Z
    EventRecordID 277979
    Correlation
   - Execution
   [ ProcessID]  0
   [ ThreadID]  0
    Channel Application
    Computer DESKTOP-7NLK99E
    Security
 
- EventData

   il2fb.exe
   3.0.6.10
   44fe754b
   jvm.dll
   0.0.0.0
   3af53001
   c0000005
   000495ba
   4f8c
   01db23c03fb08b1a
   S:\DBW 1.7 Static\il2fb.exe
   S:\DBW 1.7 Static\bin\hotspot\jvm.dll
   f0bb02b0-5073-4411-8b09-8589d311282b


Edit:

I found the new Selector but haven't installed it yet. I did view the Selector Manual and found how to change the RAM and did that on the current Selector - the game still didn't start.

Edit 2: Stand by!!! I just made a change and got DBW to launch - once. I'm going to restart the computer and see if the change fixed things. I'll get back to you.

Thanks for the help.

Bob

[Plowshare]

Hoorah!! It works!!!

What I did:

I hit the Selector button on the task bar (as I've done for decades now). When the Selector opened I went to "Change Settings". I unticked "Expert Mode (I know what I'm doing!)". I had set the RAM down to 1021 but now it got set to 1024. I saved the setting and launched the game. It launched! I then restarted the computer just to make sure and yes, it started.

What I didn't do:

I didn't install the latest Selector and the other related files and folders.

Now, a question:

Will reducing the RAM make the game stutter or worse?

Thank you for your time Frankiek and Mike.

Have a great day.

Bob

[SAS~Storebror]

Will reducing the RAM make the game stutter or worse?

Nope, you are safe now.


Mike