Grey Ghost wrote:So it switches to 20% trans. and static minimap on it's own.
Come on, that's just weird. Still potentially fits with "BF1942 has trouble reading, but not writing, the configuration file", since the results you see on-screen don't match what's in the configuration file. But it is a bit odd that what you see on screen doesn't match what the /configuration dialog/ is showing, either. So maybe we're just fighting something else entirely, and still very far off of the true root cause.
But a Process Monitor log still seems worth the time, at least to me. If we do the Process Monitor log and analysis still doesn't show what the cause of the issue is, I think the next step should be an uninstall and re-install of Battlefield, the 1.6 and 1.61b patches, DesertCombat and DC_Final, etc. On the off chance we're fighting an issue which is actually a corrupted file / code module failing to load in relation to processing the configuration, which is why it doesn't honor the saved configuration.
You might be apprehensive about re-installing, which is fine and we can do the Process Monitor log first to try and diagnose what's happening "without changing anything." Or if you would prefer to just re-install as something you already know exactly how to accomplish it, doing the re-install first is fine too, and we could proceed with Process Monitor if the issue still persisted.
The steps for using Process Monitor in this case are:
1. Download Microsoft's Process Monitor from
http://technet.microsoft.com/en-us/sysi ... 96645.aspx, using one of the "Download Process Monitor" links. This will download a "ProcessMonitor.zip" file which you can temporarily save on your desktop.
2. Right-click the ProcessMonitor.zip and select "Extract All...", which will default to extracting (de-compressing) the contained files to a "ProcessMonitor" folder on your desktop (or where ever you actually saved the file).
3. Open the "ProcessMonitor" folder and double-click the "Procmon.exe" program in that folder. Accept the license agreement that will show up the first time you run the program.
4. Process Monitor will immediately begin capturing events, which is distracting because we haven't actually configured anything yes. Click the "magnifying glass" icon in the Process Monitor toolbar to stop capturing. (Or select "Capture Events" from the "File" menu to toggle the state and cease capturing events.) Either way, note it can take even up to 60 seconds for Process Monitor to actually cease is capturing, so give it a minute and wait for the "magnifying glass" icon to show a red 'X' through it to confirm it has stopped.
5. Process Monitor will capture a shit-ton of data about every process on the system, and we're only interested in BF1942.EXE. From the "Filter" menu, select "Filter...". In the filter dialog, use the drop-down list to change the condition from it's default of "Architecture" to "Process Name". Leave the condition as "is", and in the empty data field right beside it type in "bf1942.exe". Then press the "Add" button to add this condition to the filter list, and then press OK to save the filter list.
6. Again from the "Filter" menu, select the "Drop filter events" item to toggle its state to being checked/enabled. This makes it so the non-BF1942 events will literally not be captured, as opposed to just not being shown.
7. From the "Edit" menu, select "Clear Display" to dispose of the unwanted events Process Monitor started capturing by default.
8. Now click the "magnifying glass" icon in the Process Monitor toolbar to begin capturing events again. (Or toggle the state of the "Capture Events" item in the "File" menu.) Nothing will start showing up immediately, because BF1942.EXE is not running yet.
9. Now minimize the running Process Monitor window, and launch Battlefield 1942 as you normally would.
10. Before joining a game, first visit the options menu and set the crosshair to the "pink" color you prefer (and any other mini-map options you need to change) and use the "Save" button to save these options.
11. Now join a game, and confirm that once you're in-game, the saved "pink" crosshair is not set. Once you have confirm this, simply quit the game all the way back to the Windows desktop.
12. In the Process Monitor window, click on the "magnifying glass" icon to stop the capture. In the "File" menu, select "Save...". In the Save To File dialog that appears, ensure "All events" is selected, and "Native Process Monitor Format (PML)" is selected. Then use the "..." button beside the file path to browse to your desktop and then save the LogFile.pml to your desktop (or where ever you need to save it).
13. The .PML file will likely be rather huge. To make the size slightly more manageable, right-click the saved .PML file and use the "Send To" -> "Compressed Folder" to compress the file down to a LogFile.zip file.
I'm assuming the LogFile.zip should end up being under 100MB, and if so I'll just have you email it to me. (Don't try and attach it as a PM here on the EA117 board.) If it's larger than I'm expecting, then we'll work out a place to upload it, unless you happen to already have a way to make it available for me to download (Google Drive, etc.). PM me once you have the log and know the .ZIP file size, and we'll decide where to go from there.
You can just close the Process Monitor program completely at this point, and there is nothing to "uninstall" or "undo" other than deleting the "Process Monitor" folder and ProcessMonitor.zip file off your desktop.
-Trench