Afteryou come out of the Ancient Ruins, pop a Gale Seed and warp back to Horon Village to save yourself the long walk back. Go about any business you need to do, but then head out of Horon Village via the eastern exit towards the windmill. Instead of heading towards the windmill though, immediately head south after you leave. This will put you out on the beach.
An interesting case. I got the full game as well, and to be sure also the available patches: the game always shows the same behaviour: while DxWnd doesn't log any sort of error, the program, when asked to start a combat mission, gracefully terminates because of some internal control that doesn't find everything ok.
Either analizing the assembly or by trials and sheer luck I'd find what the program doesn't like and fix it.
Yes, I noticed that. I believe that beachhead15/16.exe don't start in windowed mode, but simply it expects that the screen mode was already set by its father BH2000.exe or brother Bh.exe.
By the way, Avast found beachhead15.exe (and not beachhead16.exe) infected by malware gen on Win7 and not on Win10. Likely it is a false positive, but I'm just telling you.
The problem with this game is its splitted logic: if you check the running processes or simply look at the calls within each module, Iyou can see the folllowing:
- bh2000.exe is an invisible and mute frontend. Its purpose is to run, in turn either BH.exe or one of the twin programs beachhead\beachhead15.exe or beachhead\beachhead16.exe
- bh.exe is the program that show the game main menu and some intro stuff, options and everything is NOT 3D. It also checks the video modes and sets a 640x480 resolution with either 15 or 16 BPP color depth. When it terminates, it tells its father bh2000.exe the chosen action through the exit code
- beachhead15.exe and beachhead16.exe are the actual 3D gun engines for 15BPP and 16BPP video modes respectively.
So, the current situation is that I got a valid DxWnd configuration for bh2000.exe and beachhead\beachhead16.exe, so that I can separately run a useless menu and a new game. All these configurations, though, require DLL injection.
To make the whole stuff working there is the need to hook the invisible bh2000.exe and make it propagate the DLL injection to its son, a thing that in theory should work, but so far the hooked bh2000.exe refuses to work.
Somehow the DLL injection never worked properly for me. And if you want something even more nasty and similar case for testing purpose, search for the game named "Deer Hunt Challenge", the product of EA Sport say it all..
Actually it doesn't always work correctly for me as well, and Beach Head 2000 is a nasty enough case!
That's why I added the logging "Separated" option to last release, so that I can now have logs from more than one process at a time, even if running in same folder.
I'll have a look to Deer Unt Challenge as well, whenever possible....
@cloudstr: now that I have all the logs, I can see that the extended DLL injection doesn't work at all, and I need it to make BH2000 working. There is a work in progress, at the end the situation should be quite better than now!
Here is the necessary stuff: dxwnd.exe+dll, plus 4 (FOUR!!!) exported files that must ALL be present in the dxwnd configuration, because one task is executing the others. Maybe you could just avoid the 15 BPP engine configuration that doesn't get used, but you neve know.
Even more, when you haveall of them imported, you should set the logging flag to "Separated" (it's a recent update, not yet releases) so that each damn'd task will make a log of its own.
One sad news: the equivalent of BH.exe for Beach Head 2002, that is BH2.exe, is irremediably obfuscated! Look at it through CFF Explorer, It exposes one single kernel32 imported function! It's incredible how much fuss people dedicated to protect such a silly game.
One of therse days I'd like to check if I'm able to hook such a heavily obfuscated program, but so far that one is out of reach!
On Win10 and setting the "Limit resolution" to 640x480 the game positioning works with no problems as well. Are you sure you need the 400x300 value? That does not correspond (AFAIK) to the game native resolution, unless it may depend on the game detail level settings (I set it to the maximum, that is also the default)....
About the BH2.exe game, this time the Evo-Gen is reported by the Win10 up-to-date antivirus too, so I'll save the exe, but skip to Beach Head Desert War. BTW, that game has a BH2.exe as well, but it is not identical to the Beach Head 2002 file and can't be used in substitution.
Well, prudence is never too much.
But I was not mistrusting you (though I'd better have to!), my point was simply that BH2002 and BH Desert War were so similar each other that there was no point in starting with the risky one while there was a safe one to begin with.
Anyway, I never run that exe, so I believe I'm safe. I'll take the new gift, thank's again .....
Strangely (but not too much!) here on Win7 the situation is the other way round : I could not make the 3D engine BH2.exe to work, either alone or together with the other two programs. Would you be so kind to lend me your exported files? I'm pretty sure there shouldn't be anything too strange, but you never know.
About CPU efficiency, CPU limit is kind of a stupid "brute force" way, stopping and starting the thread no matter what it does. There are other options that may work better or for nothing at all depending on the case:
Since we're not all military types, it's probably good to explain what a beachhead is before we talk about one. A beachhead is not where the beach begins, or a guy who just thinks about getting to the beach all the time. In wartime, a beachhead is very serious business. It's a small piece of ground you try to take as your first step in taking all the ground that your enemy holds. For example, during World War II, two of the world's greatest generals went against each other when the Allies set out to take North Africa back from the Germans. General Dwight Eisenhower, the commander of the Allied forces, planned to land and take three important beachheads. German general Rommel - the famous "Desert Fox" - basically said, "We must stop Eisenhower within 48 hours of his landing - or we won't stop him." They didn't stop him. And five months after Eisenhower successfully captured that first beachhead, Rommel had to flee and surrender everything, including 250,000 soldiers. But he lost it at that first beachhead.
Satan, the commander of hell's forces, is determined to stop you from ever becoming what Jesus died for you to be. And like any smart general, he knows he has to stop you at that first breakthrough - before you gain any more ground. His strategy is revealed in our word for today from the Word of God, found in Mark 4:15, "Some people are like seed along the path," Jesus said, "where the seed is sown." Some people are like the seed along the path, where the Word is sown. "As soon as they hear it, Satan comes and takes away the word that was sown in them." God's Word has landed in your heart, you're starting to gain some ground spiritually, and your enemy is alarmed. He comes immediately to try to take away the ground you just gained through God's Word.
It's important to understand that. It helps explain why things have suddenly gotten so tough, why things are going wrong, why you don't have the spiritual enthusiasm you did before. Your logical reaction is - "I've really been trying to do what God wants. What's wrong here?" The answer may be, "Nothing's wrong! It's because something's right!"
You have started to take a beachhead for God and the enemy is worried. So suddenly he's interested in you. He didn't have to bother you when you weren't a threat. But now he's got to get in there and make it hard, he's got to stop your forward progress fast, or there's no telling how much ground he's going to lose!
Satan gets busy whenever God has made a major landing in your life - he's got to stop the beachhead. Maybe you've recently made a new surrender of your life to Jesus, or you've said yes to His call on your life, or you've stepped up to leadership. Or it could be you've begun a new work for the Lord, made a new commitment to be the marriage partner or parent you should be, to give more to the Lord's work, to live by new priorities. And alarms are going off in hell.
But don't get discouraged; don't go back to the old ways. This is just your old enemy trying to stop this progress while it's new and fragile. If you keep going this way, he's going to lose big time - and he knows it. Just step up and launch a Biblical counterattack. In the words of James 4:7, "Submit yourselves to God. Resist the devil and he will flee from you. Come near to God and He will come near to you."
The battle for the beachhead may be raging around you right now. Hold your ground, soldier. You're not losing - or the enemy wouldn't bother with you. You're on your way to some of the greatest victories of your life!
The trail begins at the far end of Sand Beach with granite steps. A right at the top of the steps leads to an open ledge ascent that provide excellent views of Sand Beach and The Beehive. The trail continues along the headland with dramatic views of the coastline and ocean. The trail is rocky with uneven footing. Good foot wear is recommended. It is a gradual grade to reach the highest point at 145 feet above sea level. At this point the ruins of a 1915 tea house can be seen. The trail turns away from the shore and descends through the forest. A cedar post marks a junction in the trail. For a shorter loop (1.3 miles) , take the trail to the left. It climbs steeply before leveling out and leading back to Sand Beach. For a longer loop (1.9 miles) continue straight. The trail angles back toward the ocean with occasional views. At the next junction, turn left for a easy walk back to the top of the steps where the hike began. Descend the steps to Sand Beach.
3a8082e126