Com Files Msjavx86 Exeter
Optional Offer for WinThruster by Solvusoft Overview of MSJAVX86.EXE What Is MSJAVX86.EXE?MSJAVX86.EXE is a type of EXE file associated with MSDN Disc 4 developed by Microsoft for the Windows Operating System. The latest known version of MSJAVX86.EXE is 1.0.0.0, which was produced for Windows. This EXE file carries a popularity rating of 1 stars and a security rating of 'UNKNOWN'. What Are EXE Files?EXE ('executable') files, such as MSJAVX86.EXE, are files that contain step-by-step instructions that a computer follows to carry out a function. When you 'double-click' an EXE file, your computer automatically executes these instructions designed by a software developer (eg. Microsoft) to run a program (eg. MSDN Disc 4) on your PC.Every software application on your PC uses an executable file - your web browser, word processor, spreadsheet program, etc.
making it one of the most useful kinds of files in the Windows operating system. Without executable files like MSJAVX86.EXE, you wouldn't be able to use any programs on your PC. Why Do I Have EXE Errors?Because of their usefulness and ubiquity, EXE files are commonly used as a method of delivery for virus / malware infection. Often, viruses will be disguised as a benign EXE file (such as MSJAVX86.EXE) and distributed through SPAM email or malicious websites, which can then infect your computer when executed (eg. When you double-click the EXE file).In addition, viruses can infect, replace, or corrupt existing EXE files, which can then lead to error messages when MSDN Disc 4 or related programs are executed. Thus, any executable files that you download to your PC should be scanned for viruses before opening - even if you think it is from a reputable source.
When Do EXE Errors Occur?EXE errors, such as those associated with MSJAVX86.EXE, most often occur during computer startup, program startup, or while trying to use a specific function in your program (eg. Common MSJAVX86.EXE Error MessagesThe most common MSJAVX86.EXE errors that can appear on a Windows-based computer are:. 'MSJAVX86.EXE Application Error.'
. 'MSJAVX86.EXE is not a valid Win32 application.' .
'MSJAVX86.EXE has encountered a problem and needs to close. We are sorry for the inconvenience.'
. 'Cannot find MSJAVX86.EXE.' .
'MSJAVX86.EXE not found.' . 'Error starting program: MSJAVX86.EXE.'
. 'MSJAVX86.EXE is not running.' . 'MSJAVX86.EXE failed.' . 'Faulting Application Path: MSJAVX86.EXE.' These EXE error messages can appear during program installation, while a MSJAVX86.EXE-related software program (eg.
MSDN Disc 4) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your MSJAVX86.EXE error occurs is a critical piece of information in troubleshooting the problem. Caution: We do not recommend downloading MSJAVX86.EXE from 'EXE download' sites. These sites distribute EXE files that are unapproved by the official MSJAVX86.EXE file developer, and can often be bundled with virus-infected or other malicious files. If you require a copy of MSJAVX86.EXE, it is recommended that you obtain it directly from Microsoft.Below is a list of troubleshooting steps to resolve your MSJAVX86.EXE problems.
These troubleshooting steps get progressively more difficult and time consuming, so we strongly recommend attempting them in ascending order to avoid unnecessary time and effort. Please Note: Click the image to expand the troubleshooting instructions for each step below. You can also click the image to hide the instructions as you proceed through each step.Sometimes MSJAVX86.EXE and other EXE system errors can be related to problems in the Windows registry. Several programs can share the same MSJAVX86.EXE file, but when these programs are uninstalled or changed, sometimes 'orphaned' (invalid) EXE registry entries are left behind.Basically, what this means is that while the actual file path may have changed, its incorrect former location is still recorded in the Windows registry. When Windows tries looking up these incorrect file references (file locations on your PC), MSJAVX86.EXE errors can occur. In addition, malware infection may have corrupted the registry entries associated with MSDN Disc 4.
Thus, these invalid EXE registry entries need to be repaired to fix the root of the problem.Manually editing the Windows registry to remove invalid MSJAVX86.EXE keys is not recommended unless you are PC service professional. Incorrectly editing your registry can stop your PC from functioning and create irreversible damage to your operating system.
In fact, one misplaced comma can prevent your PC from booting entirely!Because of this risk, we highly recommend using a trusted registry cleaner such as (Developed by Microsoft Gold Certified Partner) to scan and repair any MSJAVX86.EXE-related registry problems. Using a automates the process of finding invalid registry entries, missing file references (like the one causing your MSJAVX86.EXE error), and broken links within the registry. A backup is automatically created before each scan, with the ability to undo any changes in a single click, protecting you against the possibility of PC damage. The best part is that can also dramatically improve system speed and performance. Caution: Unless you an advanced PC user, we DO NOT recommend editing the Windows registry manually. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. We do not guarantee that problems resulting from the incorrect use of Registry Editor can be solved.
Use Registry Editor at your own risk.To manually repair your Windows registry, first you need to create a backup by exporting a portion of the registry related to MSJAVX86.EXE (eg. MSDN Disc 4):. Click the Start button. Type ' command' in the search box.
DO NOT hit ENTER yet!. While holding CTRL-Shift on your keyboard, hit ENTER.
You will be prompted with a permission dialog box. Click Yes. A black box will open with a blinking cursor. Type ' regedit' and hit ENTER. In the Registry Editor, select the MSJAVX86.EXE-related key (eg. MSDN Disc 4) you want to back up.
From the File menu, choose Export. In the Save In list, select the folder where you want to save the MSDN Disc 4 backup key. In the File Name box, type a name for your backup file, such as 'MSDN Disc 4 Backup'. In the Export Range box, be sure that ' Selected branch' is selected. Click Save.
The file is then saved with a.reg file extension. You now have a backup of your MSJAVX86.EXE-related registry entry.The next steps in manually editing your registry will not be discussed in this article due to the high risk of damaging your system. If you would like to learn more about manual registry editing, please see the links below. Tip: If you do not already have a malware protection program installed, we highly recommend using Emsisoft Anti-Malware. They offer a malware removal guarantee that is not offered by other security software.Over time, your computer accumulates junk files from normal web surfing and computer use. If this junk isn't occasionally cleaned out, it can cause MSDN Disc 4 to respond slowly or provides an MSJAVX86.EXE error, possibly due to file conflicts or an overloaded hard drive.
Cleaning up these temporary files with Disk Cleanup might not only solve your MSJAVX86.EXE error, but can also dramatically speed up the performance of your PC. Tip: Although Disk Cleanup is a wonderful built-in tool, it will not completely clean up all of the temporary files on your computer. Other programs that you frequently use such Microsoft Office, Firefox, Chrome, Live Messenger, and hundreds of other programs are not cleaned up with Disk Cleanup (including some Microsoft programs).Because of the shortcomings of the Windows Disk Cleanup (cleanmgr) tool, we highly recommend using a specialized hard drive cleanup / privacy protection software such as (Developed by Microsoft Gold Partner) to clean up your entire computer. Running once per day (using automatic scanning) will ensure that your computer is always clean, running fast, and free of MSJAVX86.EXE errors related to temporary files.How to run Disk Cleanup (cleanmgr) (Windows XP, Vista, 7, 8, and 10):. Click the Start button. Type ' command' in the search box.
DO NOT hit ENTER yet!. While holding CTRL-Shift on your keyboard, hit ENTER. You will be prompted with a permission dialog box. Click Yes. A black box will open with a blinking cursor. Type ' cleanmgr' and hit ENTER. Disk Cleanup will begin calculating how much occupied disk space you can reclaim.
The Disk Cleanup dialog box will appear with series of checkboxes you can select. In most cases, the 'Temporary Files' category will occupy the most disk space. Check the boxes of the categories you want to clean and click OK.MSJAVX86.EXE errors can be related to corrupt or outdated device drivers. Drivers can work one day, and suddenly stop working the next day, for a variety of reasons. The good news is that you can often update the device driver to fix the EXE problem.Finding the exact driver for your MSJAVX86.EXE-related hardware device can be extremely difficult, even directly on the Microsoft or related manufacturer's website. Even if you are experienced at finding, downloading, and manually updating drivers, the process can still be very time consuming and extremely irritating. Installing the wrong driver, or simply an incompatible version of the right driver, can make your problems even worse.Because of the time and complexity involved in updating drivers, we highly recommend using a such as (Developed by Microsoft Gold Partner) to automate the process.updates all of your PC device drivers, not just those associated with your EXE error.
Proprietary One-Click Update™ technology not only ensures that you have correct driver versions for your hardware, but it also creates a backup of your current drivers before making any changes. Maintaining a driver backup provides you with the security of knowing that you can rollback any driver to a previous version if necessary. With updated device drivers, you can finally unlock new hardware features and improve the speed and performance of your PC. Tip: If you are positive that your EXE error is related to a specific Microsoft program, uninstalling and reinstalling your MSJAVX86.EXE-related program will likely be the solution to your problem.System File Checker is a handy tool included with Windows that allows you scan for and restore corruptions in Windows system files (including those related to MSJAVX86.EXE). If System File Checker finds a problem with your EXE or other critical system file, it will attempt to replace the problematic files automatically.To run System File Checker ( Windows XP, Vista, 7, 8, and 10):.
Click the Start button. Type ' command' in the search box. DO NOT hit ENTER yet!. While holding CTRL-Shift on your keyboard, hit ENTER. You will be prompted with a permission dialog box.
Click Yes. A black box will open with a blinking cursor. Type ' sfc /scannow' and hit ENTER.
System File Checker will begin scanning for MSJAVX86.EXE and other system file problems (be patient - the system scan may take a while). Follow the on-screen commands.Microsoft is constantly updating and improving Windows system files that could be associated with MSJAVX86.EXE.
Sometimes resolving your EXE problems may be as simple as updating Windows with the latest Service Pack or other patch that Microsoft releases on an ongoing basis.To check for Windows Updates (Windows XP, Vista, 7, 8, and 10):. Click the Start button. Type ' update' into the search box and hit ENTER. The Windows Update dialog box will appear. If updates are available, click the Install Updates button. Caution: We must emphasize that reinstalling Windows will be a very time-consuming and advanced task to resolve MSJAVX86.EXE problems. To avoid data loss, you must be sure that you have backed-up all of your important documents, pictures, software installers, and other personal data before beginning the process.
If you are not currently backing up your data, you need to do so immediately to protect yourself from permanent data loss.This step is your final option in trying to resolve your MSJAVX86.EXE issue. Reinstalling Windows will erase everything from your hard drive, allowing you to start again with a fresh system. Furthermore, a clean install of Windows will also quickly clean out any and all 'junk' that has accumulated over the normal usage of your computer. Filename: MSJAVX86.EXELatest Known Version: 1.0.0.0Developer:File Size (Bytes): 6507256Software:Operating System: WindowsDescription: October 1998MD5: 2FC04539C7DBFEEC34AF4289CD557F86SHA1: 01E4711FC5257280CC737329500A09F4B78E8F32Operating System InformationMSJAVX86.EXE error messages can occur in any of the following Microsoft Windows operating systems:. Windows 10.
Windows 8. Windows 7. Windows Vista. Windows XP.
Windows ME. Windows 2000Are You Still Experiencing MSJAVX86.EXE Issues?Please reach out to us anytime on social media for more help.
Oblique aerial view of Exeter at anchor with awnings rigged, 24 April 1934Exeter was ordered two years after her and her design incorporated improvements in the light of experience with the latter. Her was increased by one foot (30 cm) to compensate for increases in topweight, and her boiler uptakes were trunked backwards from the boiler rooms, allowing for straight further removed from the rather than the raked funnels on York to ensure adequate dispersal of the flue gases. As the eight-inch (203 mm) had proved not strong enough to accommodate the originally intended, Exeter was given a pair of fixed catapults angled out from amidships in a 'V' shape, with the associated placed to starboard. Consequently, the bridge was lowered (that of York being tall to give a view over the intended aircraft), and was of a, enclosed design that was incorporated into later cruisers.Exeter was slightly lighter than expected and displaced 8,390 (8,520 ) at and 10,620 long tons (10,790 t) at.
The ship had an of 575 feet 1 inch (175.3 m), a beam of 58 feet (17.7 m) and a of 17 feet (5.2 m) light load and 20 feet 3 inches (6.2 m) deep load. She was powered by four geared sets, each driving one shaft, using provided by eight. The turbines developed a total of 80,000 (60,000 ) and gave a maximum speed of 32 (59 km/h; 37 mph). The ship could carry 1,900 long tons (1,930 t) of which gave her a range of 10,000 (18,520 km; 11,510 mi) at 14 knots (26 km/h; 16 mph).
The ship's complement was 628 officers and.The main armament of the York-class ships consisted of six in three twin-, designated 'A', 'B', and 'Y' from fore to aft. 'A' and 'B' were forward of the superstructure and 'Y' was aft of it. Defence against aircraft was provided by four in single mounts and a pair of light AA guns ('pom-poms') in single mounts. The ships also fitted with two triple above-water mounts for torpedoes.The cruisers lacked a full-length.
The sides of Exeter 's and the sides of the were protected by 3 inches (76 mm) of armour. The transverse at the end of her propulsion machinery rooms were 3.5 inches (89 mm) thick. The top of the magazines were protected by 5.5 inches (140 mm) of armour and their ends were 4.375 inches (111 mm) thick. The lower deck over the machinery spaces and steering gear had a thickness of 1.5 inches (38 mm). Modifications In 1932 Exeter had her side plating extended to enclose her open main deck as far back as the fore funnel. During that same refit, her pair of fixed catapults were finally installed for her.
In 1934–1935, two quadruple mounts for replaced the pair of two-pounder 'pom-poms' originally installed. Exeter at anchor, early 1941While under repair in 1940–1941 after her battle with the Admiral Graf Spee, the Royal Navy decided to upgrade her armament and fire-control systems. The was rebuilt and enlarged to accommodate a second aft of the (DCT) on top of the bridge, her single four-inch AA guns were replaced with twin-gun mounts for and a pair of octuple mounts for two-pounder 'pom-poms' were added abreast her aft. Enclosures ('tubs') for single were added to the roof of both 'B' and 'Y' turrets, but these weapons were never installed, because of shortages in production, and lighter tripod-mounted machine guns were substituted. The pole were replaced by stronger because the had separate transmitting and receiving, one at each masthead. In addition, a Type 284 was fitted to the DCT.
Construction and career Exeter, the fourth ship of her name to serve in the Royal Navy, was on 1 August 1928, on 18 July 1929 and completed on 27 July 1931. The ship was then assigned to the of the, where she served between 1931 and 1933. In 1934 she was assigned to the and remained there, aside from a temporary deployment to the Mediterranean during the of 1935–1936, until 1939. Second World War Battle of the River Plate.
Damage received by Exeter during the Battle of the River PlateAt the outbreak of the, she formed part of the South American with the heavy cruiser, under. The ship, commanded by, was assigned to Force G to hunt for German commerce raiders off the eastern coast of South America on 6 October 1939. Two months later, Harwood ordered Exeter and the to rendezvous with his own off the mouth of the, while HMS Cumberland was refitting in the. The two other ships arrived on 12 December, and then the Admiral Graf Spee spotted the Exeter during the following morning.Captain decided to engage the British and closed at full speed. The British doctrine on how to engage ships like the Admiral Graf Spee had been developed by Harwood in 1936 and specified that the British force act as two divisions. Following this procedure, Exeter operated as a division on her own while Achilles and Ajax formed the other, splitting the fire of the German ship.
They were only partially successful as the German ship concentrated her main armament of six 283-millimetre (11.1 in) guns on Exeter, and her secondary armament of eight 149-millimetre (5.9 in) guns on the light cruisers. Langsdorff opened fire on Exeter at 06:18 with shells and she returned fire two minutes later at a range of 18,700 yards (17,100 m). The German ship the British cruiser with her third; shrapnel from the near misses killed the crew of the starboard torpedo tubes, started fires amidships and damaged both seaplanes. After eight salvos from Exeter, Admiral Graf Spee scored a direct hit on 'B' turret that knocked it out of action and shrapnel from the hit killed all of the bridge personnel except three. Bell, wounded in the face, transferred to the aft conning position to continue the battle. His ship was hit twice more shortly afterwards, but her powerplant was not damaged and she remained seaworthy, although her aircraft had to be jettisoned.At 06:30, Langsdorff switched his fire to the light cruisers, but only inflicted shrapnel damage on them before some of Exeter 's torpedoes forced him to turn away at 06:37 to evade them.
Her second torpedo attack at 06:43 was also unsuccessful. In the meanwhile, Langsdorff had switched his main guns back to the heavy cruiser and scored several more hits. They knocked out 'A' turret, started a fire amidships that damaged the ship's fire-control and navigation circuits, and caused a seven-degree with flooding. After 'Y' turret had temporarily been disabled, Bell said, 'I'm going to ram the -.
It will be the end of us but it will sink him too'. The turret was repaired and she remained in action until flooding disabled the machinery for 'Y' turret at 07:30.
At 11:07, Bell informed Harwood that Exeter had a single eight-inch and a four-inch gun available in local control, and that she could make 18 knots (33 km/h; 21 mph). Harwood ordered Bell to head to the Falklands for repair.The ship was hit by a total of seven 283 mm shells that killed 61 of her crew and wounded another 23. In return, the cruiser had hit Admiral Graf Spee three times; one shell penetrated her main armour belt and narrowly missed detonating in one of her engine rooms, but the most important one disabled her oil-purification equipment. Without it, the ship was unlikely to be able to reach Germany. Several days later, unable to be repaired and apparently confronted by powerful Royal Navy reinforcements (including HMS Cumberland), the Admiral Graf Spee was scuttled by her captain in the harbour of.Exeter made for for emergency repairs which took until January 1940. She was repaired and modernised at between 14 February 1940 and 10 March 1941; Captain was appointed to relieve Bell on 12 December 1940. Then, on 10 March 1941, the very day that Exeter was due to be recommissioned, Beckett died at Saltash Hospital from complications following exploratory surgery to repair poison gas injuries that he had received earlier in his career.
His replacement was Captain. To the Far East Upon returning to the fleet, Exeter primarily spent time on ‘working up' exercises, however she also conducted several patrols in northern waters, one on which she stopped in Iceland to refuel. On 22 May she departed from Britain (for the last time as it would turn out), escorting Convoy WS-8B to Aden (Yemen) via Freetown and Durban, South Africa (the beginning of which occurred at the very same time as the hunt for the. Was taking place). Exeter henceforth became attached to the East Indies Squadron (later redesignated as the ).Exeter then stayed on escort duty in the Indian Ocean (primarily off the coast of Africa) and the northern Arabian Sea (where she visited Bombay, India) until 13 October. On that day Exeter departed Aden for, ) via, arriving on 24 October.
Exeter then spent several days in a graving dock and after undocking (on the 29th) conducted exercises off Colombo and visited the.Upon return to Trincomalee (Ceylon) from the Maldives on 14 November, Exeter then departed for Calcutta on the 16th to cover a small two-ship convoy that left Calcutta for Rangoon (Burma) on the 26th and 27th. After the successful completion of that duty she was then tasked to escort another ship from Calcutta to Rangoon on 6 December. However, during that convoy, on 8 December, Exeter was ordered to urgently proceed to Singapore to reinforce, as the had just begun. Exeter arrived at Singapore during the afternoon of 10 December, too late to support and as they had both been sunk earlier that day, but some of the survivors from these two ships were treated in Exeter 's.Exeter thus returned to Colombo the next day (11 December) and spent the next two months – until almost mid-February 1942 – escorting convoys (primarily from Bombay and Colombo) bound for Singapore – which fell to the Japanese on 15 February.
During this time, in early 1942, Exeter was attached to the newly formed ABDA Commandwhich came into being in early January in Singapore, but soon shifted its headquarters to Java in the Dutch East Indies (present day Indonesia).The Gaspar Strait sortie. Exeter under air attack on 15 February 1942On 13 February, Allied reconnaissance aircraft spotted Japanese invasion convoys north of and the new commander of ABDA naval forces, of the, was ordered to assemble the Allied Striking Force of Exeter and three Dutch and one Australian light cruisers at on the morning of 14 February. Escorted by six American and three Dutch, the force departed that afternoon. The Dutch, commanding the force, took his ships through the and then northwest towards Bangka Island. While passing through the strait, the Dutch destroyer struck a rock in poor visibility and another Dutch destroyer was tasked to take off her crew. The Japanese spotted the Allied ships around 08:00 and repeatedly attacked them.
The first was a group of seven 'Kate' from the that attacked Exeter with bombs around 10:30. The blast from a near miss badly damaged her, but the ship was only damaged by shrapnel. They were followed shortly afterwards by a group of 23 'Nell' bombers from the that inflicted no damage as they dropped their bombs from high altitude. Another group of six B5Ns attacked without effect at 11:30.The repeated aerial attacks persuaded Doorman that further progress was unwise in the face of Japanese aerial supremacy and he ordered his ships to reverse course and head for at 12:42. The attacks continued as 27 G3Ms of the then bombed from high altitude. Seven more B5Ns attacked fruitlessly at 14:30; a half-dozen more followed an hour later.
The final attack was made by 17 'Betty' bombers of the shortly before dark. The Japanese attacks were almost entirely ineffectual, with no ship reporting anything more than shrapnel damage.
In return, allied anti-aircraft fire was moderately effective with most of the attacking bombers damaged by shrapnel. In addition, one G4M crashed while attempting to land, and another was badly damaged upon landing. First Battle of the Java Sea. Main article:On 25 February, Helfrich ordered all available warships to join Doorman's Eastern Striking Force at.
Com Files Msjavx86 Exeter Pa
The Exeter and the Australian light cruiser, escorted by three British destroyers, and, set sail at once, leaving behind one Australian cruiser and two destroyers that were short of fuel. After they had arrived the following day, Doorman's entire force of five cruisers and nine destroyers departed Surabaya at 18:30 to patrol off Eastern Java in hopes of intercepting the oncoming invasion convoy which had been spotted earlier that morning. The Japanese were further north than he anticipated and his ships found nothing. His own ships were located at 09:35 on the following morning, 27 February, and were continuously tracked by the Japanese. Doorman ordered a return to Surabaya at 10:30, and his ships were attacked by eight bombers from the Kanoya Air Group at 14:37. They claimed to have made two hits on the Jupiter, but actually they missed the British destroyer. Just as his leading ships were entering harbour, he received reports of enemy ships 90 miles (140 km) to the north and Doorman ordered his ships to turn about to intercept them.Aware of Doorman's movements, the Japanese commander, Rear Admiral, detached the convoy's two escorting destroyer, each consisting of a light cruiser and seven destroyers, to intercept the Allied ships in conjunction with his own pair of heavy cruisers ( and ) which were escorted by a pair of destroyers.
His heavy cruisers opened fire at long range at 15:47 with little effect. The light cruisers and destroyers closed to ranges between 13,000 and 15,000 yards (12,000 and 14,000 m) and began firing beginning at 16:03. All of these torpedoes failed to damage their targets, although one torpedo hit Exeter and failed to detonate at 16:35. Three minutes later, Haguro changed the course of the battle when one of her shells penetrated the British ship's aft twin four-inch gun mount before detonating in the aft, knocking six of her boilers off-line and killing 14 of her crew. The ship out of line to avoid another torpedo and slowed, followed by all of the trailing cruisers.
Perth laid a to protect Exeter and the Allied ships sorted themselves into separate groups as they attempted to disengage. Exeter was escorted by one Dutch and all three British destroyers in one group and the other cruisers and the American destroyers formed the other group. The Japanese did not initially press their pursuit as they manoeuvered to use their torpedoes against the crippled Exeter, which could only make 5 knots (9.3 km/h; 5.8 mph), and her escorts.The Japanese began launching torpedoes beginning at 17:20 at ranges of 10,000 to 18,500 yards (9,100 to 16,900 m), but they all missed. For some reason, two Japanese destroyers continued to close before firing their torpedoes at 6,500 yards (5,900 m) and Encounter and Electra pulled out of line to counter-attack.
They engaged and at close range as they closed. Asagumo was damaged by Electra, but the Japanese ship sank the British destroyer at 17:46. Meanwhile, the Exeter continued south to Surabaya, escorted by Encounter and the Dutch destroyer. Doorman's repeated, unsuccessful, and ultimately fatal attempts to reach the transports concentrated the Japanese on the task of protecting the transports and allowed the damaged British cruiser to reach harbour.
Com Files Msjavx86 Exeter Va
Second Battle of the Java Sea. Exeter sinking after the Second Battle of the Java SeaThe following day, after making temporary repairs and refuelling, the Exeter, escorted by Encounter and the American destroyer, was ordered to steam to, via the. They departed on the evening of 28 February, but they were intercepted by the Japanese heavy cruisers Nachi, Haguro, and, and by the destroyers, and on the morning of 1 March.At about 0800, the British ships spotted two of the Japanese cruisers, one of which launched its spotting floatplanes. Two others were seen closing in, and both launched their aircraft before opening fire at about 09:30. The Allied ships laid smoke and turned away to the east with the Japanese to their north and south. Exeter was able to reach a speed of 26 knots (48 km/h; 30 mph) before the first hit on her again detonated in a boiler room and knocked out all power around 11:20.
The Japanese destroyers closed in and fired a total of 18 torpedoes, of which only two, fired by the destroyer hit the ship – starboard amidships, and starboard just forward of A Turret – (as confirmed when the wreck was first discovered in 2007 ). Exeter then quickly and sank. Encounter and Pope were also lost; Pope temporarily survived the initial melee, only to be sunk by several B5Ns a few hours later.The Japanese rescued 652 men of the crew of the Exeter, including her captain, who became prisoners of war.
Of these men, 152 died in Japanese captivity. Wreck site The wreck was located and positively identified on 21 February 2007, lying in Indonesian waters at a depth of about 200 feet (61 m), 90 miles (140 km) north-west of – some 60 miles (97 km) from the estimated sinking position given by Gordon after the war. Her wreck, a British war grave, had been destroyed by illegal salvagers when an expedition surveyed the site in 2016. Footnotes.