Author: Ash Nallawalla

About Ash Nallawalla

Ash Nallawalla is a consultant enterprise SEO with a long background in large companies with complex websites. He is a published author of several books and thousands of magazine articles.

Losing a Corrupted Word 2021 Document

Reading Time: 3 minutes

I suffered a major setback by way of a book manuscript I was writing. It is lost beyond repair. I know what I should have done, but I am documenting this to help others. I use an offline copy of Word 2021, not the online Office 365.

Possible Causes of Word Doc Corruption

The book manuscript was about 283 pages from memory and I had not backed it up for over a month, and the backup copy was 30 pages shorter. I was finding that Word and Excel documents were taking longer than usual to open and I wondered if my hard drive was on its way out. I decided to back up the folder to my backup drive (a separate physical drive) and that was a clue that something was wrong, as the copy failed.

I used O&O Software Disk Defragmenter to defrag my data drive D but it was taking very long, so I thought I should stop it.

I tried to open the manuscript to add some content and found that it would not open. I had last used it last night, so I was puzzled. I remembered that I had done an online repair of Office and wondered if I had installed the 32-bit version of Office instead of the 64-bit version. I had an ISO of the original download, so I reinstalled Office, but it made no improvement. The Word doc refused to open.

The doc would not open.
The doc would not open.
Still no luck.
Still no luck.

Things Tried on the File

chkdsk /f reported no errors.

chkdsk was happy with the drive.
chkdsk was happy with the drive.
chkdsk was happy with the drive.
chkdsk was still happy with the drive.

Error checking via File Manager > Properties showed no file errors. (image above)

Open and Repair did not work.

Text recovery tool did not recover any text.

Recover Text from Any File did not work.

Opening in Notepad is a crazy suggestion, as seen in some articles. The contents are not plain text – other than some file names. See below the older, working copy and the corrupted file below.

Corrupt and clean versions viewed in Notepad.
Corrupt and clean versions viewed in Notepad.

There are no previous versions or unsaved versions.

Importing into Google Docs did not work.

Inserting into an empty document as an object did not work. “Word has encountered a problem.”

The recovery tips in https://docs.microsoft.com/en-us/office/troubleshoot/word/damaged-documents-in-word were tried but none worked.

Trying to link the corrupt file to a clean doc did not work.
Trying to link the corrupt file to a clean doc did not work.

Tools Used

There are many articles with suggestions, but they are rehashes of the things I tried above and sometimes have affiliate links to tools.

Libre Office could not open it.

LibreOffice failed to open it.
LibreOffice could not open the corrupt file.

OpenOffice also failed to load it. Its help text says “The most recent versions of OpenOffice can load, but not save, the Microsoft Office Open XML document formats with the extensions docx, xlsx, and pptx.” Note: Both LibreOffice and OpenOffice did open the working copy – but not this corrupt copy.

OpenOffice failed.
OpenOffice failed.

Stellar Repair for Word crashed on the file.

Stellar Data Recovery was useful to undelete an earlier version, but 30 pages shorter.

GetData Word Repair couldn’t open it.

Remo Repair announced that it had recovered it, but the file vanished

https://word.recoverytoolbox.com/online/

https://onlinefile.repair/rtf

https://online.officerecovery.com/word/ took ages to upload, but at least it was uploading.

Conclusion (See update)

At the moment I am stumped. The disk and data are fine. The file is difficult to select – clicking it sends File Explorer into a long delay before I can get control, but the file just does not open. Sending it to an online service times out for this reason and downloaded trial tools cannot process it.

If you have any suggestions and have personally solved this problem, please leave a comment. (Comments are moderated)

Update

I managed to open the copy with a paid version of the file recovery tool – Remo Repair Word – but it turned out to be an older version too. In the end, I used a recent PDF copy and exported it to RTF. This has some scrambled tables and some missing images, but it will get me back to sanity, with fewer than 10 lost pages. Many of the lost pages have images, which are safe, so the lost text won’t be too hard to re-create.

The Mythical Bombay Back Bay Station

Reading Time: 3 minutes

I administer an unlisted Facebook group known as “Bombay, I Remember”. It is a group for reminiscences of its members in the pre-1995 Bombay (when the city was renamed to Mumbai), but nowadays it is kept alive with a lot of historic content about Bombay. Several posts have covered the railway line of the former Bombay, Baroda and Central India (BB&CI) line, particularly the stations at the start of the line.

I have not found any old document that mentions this “Bombay Back Bay” station.

The Bombay Builder

Today, I found an archive of the Bombay Builder covering 1867 at the Asiatic Library’s online archive known as Granth Sanjeevani. The specific page below is dated 5 April 1867. Note that date.

Note the stations in the Locality column.
Note the stations in the Locality column.

Two things stood out for me. The terminus at Colaba was there in April 1867. The second station is called Esplanade Station. This is an added mystery, as the Esplanade in those days was too far from this train line to deserve the title. As this is a journal for engineers, they were interested in girders and overbridges, in addition to stations.

Western Railway

The Western Railway (WR) has been the name of the former BB&CI since 1951, so it should know its own history. Its website is very flaky, so here is a screenshot of its About Us > Milestones page.

WR milestones.
WR milestones.

Notice that the WR timeline says the line to Colaba was extended in 1873. How can the earlier reference in the Bombay Builder mention a Colaba Terminus before 5 April 1867? The entry for 1867 mentions the start of a local service between Back Bay and Virar (then spelt Veraur) on 12 April 1867.

I decided to check the newspapers of the day, as scanned by Granth Sanjeevani.

The Bombay Gazette of 12 April 1867.
The Bombay Gazette of 12 April 1867.

I checked the date of this new service, the next day and a few days on either side. Not a single mention. Surely a service covering the length of Bombay was worth a mention? BB&CI used to advertise almost daily, but no mention of a new service?

The Wikipedia Entry

The Wikipedia entry for Churchgate railway station says:

“By 1867, a track along the foreshore, further than Grant Road station was constructed, up to the station named as “Bombay Backbay” near Marine Lines. On 12 April 1867, the first suburban train was started with one train each way from Virar to Bombay Back Bay. The stations were then named, “Viraur, Neela, Bassein, Panje, Borewla, Pahadee, Andaru, Santa Cruz, Bandora, Mahim, Dadur, Grant Road and Bombay Backbay”. In year 1870, Churchgate was first time mentioned as the station. The line further extended towards Colaba in 1872, and goods shed was built there.”

The spellings in those days were quite fluid, so they are a little different from the ones in the Bombay Builder. The unknown Wikipedia contributor has a different date (1872) for the extension of the line to Colaba compared to the WR date of 1873. They mention this mythical “Backbay” (actually two words, Back Bay) station as being “near Marine Lines.

A letter to the editor

The Times of India, 2 September 1868
Letter to the Editor, The Times of India, 2 September 1868

Where does this leave me? I have not found any old document that mentions this Back Bay station. Until I do so, I will treat Back Bay Station as a colloquial reference to Church Gate Station (whose name slowly became one word). If you go to that Wikipedia page for Church Gate Station, you will see that it was opened in 1867!

Wikipedia entry for Church Gate station.
Wikipedia entry for Church Gate station.

Here is another modern reference to Church Gate being called Back Bay.

Church Gate being called "Bombay Backbay".
Church Gate being called “Bombay Backbay”.

As for the other mystery of an Esplanade Station between Colaba Terminus and Churnee Road (now spelt Charni Road), I think it too is a colloquial reference. Perhaps the engineer who wrote that entry was a brief visitor and wrote it up when back in the UK?

Colaba Station Dates

I found this document “Things of India Made Plain, or A Journalist’s Retrospect” by W Martin Wood in the more navigable archive – the Wayback Machine. It mentions in an entry dated 29 September 1873 that the Colaba station was well towards completion that year, after a period of seven years, suggesting that it was started in 1866.

Colaba station took 7 years to be built.
Colaba station took 7 years to be built.

The previous page has an entry dated 9 October 1872, mentioning the procurement of the land for the station.

1872 entry.
1872 entry.

Those words from 1872 suggest that there were railway tracks to Colaba in 1867 (also mentioned by the Bombay Builder), but the grand station was not completed until seven years later. Those tracks carried the cotton to the docks there during the US Civil War and to the Cotton Green. There is a plaque at Bombay Central station that acknowledges a Colaba Causeway station built in 1870 and another reference that the line used to go to Arthur Bunder.

Control Malahit DSP2 with SDRUno-Extio and Omni-Rig

Reading Time: 2 minutes

You might want to try connecting your Windows PC with your Malahit DSP2 receiver using SDRUno-Extio (not the regular SDRUno, but the other one you will find that was installed at the same time) and Omni-Rig 1.9. Now why would you want to do this? One reason is that you are a geek like me and want to see if it works and is worth the trouble.

What You Need

In addition to the receiver, you need a USB cable, but as a geek you have already hooked that up to update your firmware. You need Omni-Rig 1.9 (other versions might work, but you need one that shows the TS-480.)

Manage sound settings
Manage Sound Settings

Once you have enabled the two disabled items above, you should see the “spectre” option in SDRUno-Extio, but after you have set up Omni-Rig correctly.

Omni-Rig settings
Omni-Rig settings

The Rig type should be TS-480 and the Port is the one you see in Control Panel Device Manager. When you unplug the receiver, a COM port will disappear and will return when you plug it in – that is your Malahit’s COM port – COM 7 in my case.

Find the COM port used by the Malahit.
Find the COM port used by the Malahit.

The baud rate should be the same as the CAT settings in SDRUno (The Sett. button in the SDRUno Rx Control).

Start SDRUno-Extio. A tiny window opens up.

Start SDRUno-Extio

Click Sett. to open the main settings. Choose Malahit spectre as the WME Input Device.

Select Malahit spectre.
Select Malahit spectre.

Click RX in the main window to open a receiver instance. Note the three buttons at the top: RSYN1, MCTR and TCTR. The labels are white text.

A receiver instance is opened.
A receiver instance is opened.

Click each of the three buttons: RSYN1, MCTR and TCTR. They will turn to orange text.

The three buttons are clicked.
The three buttons are clicked.

Click Sett. and go to the CAT tab. Choose the Malahit’s COM port and baud rate.

Set COM and Baud Rate.
Set COM and Baud Rate.

I am not sure why the status says “Not connected” but once you click Play on the main window, the PC speaker should come to life and relay the Malahit’s audio and mirror the frequency in SDRUno.

Click SP1 in the main window to display the spectrum and waterfall in SDRUno-Extio.

Spectrum and Waterfall in SDRUno.
Spectrum and Waterfall in SDRUno.

You can now control the receiver from your PC. Enjoy!

Thanks to Alexander DL5VZ for his help in clarifying these steps.

Mastodon