The Journalist Dilemma

By | November 22, 2011

Jeff Jarvis over at BuzzMachine says there are too many journalists and newspapers would do well to cut back on reporters and reinvest digital interaction on the local level — in other words, to build connections with communities and have them report. Cheap/free local citizen Journalists, in other words, replace jet-setting, expensive correspondents:

So maybe the problem with journalism today isn’t that there are too few reporters and and editors but too many. I’ve talked before about the foolishness of sending 15,000 reporters to the political conventions, about papers sending TV critics to junkets or golf writers to tournaments. Inside the newsroom, too, there are overwrought processes. Meanwhile, of course, revenue is sinking and staff will follow.

But rather than treating this as an endless retrenchment, the ballsy editor would take this bull by the horns and undertake an aggressive reinvestment strategy. Why not cut that staff today? Find your essence — hint: it’s local, local, local. Streamline now to put out a better focused and better print product.

I definitely agree with the absurdity of having thousands of journalists all covering one single-dateline story, whether it’s a convention or a Michael Jackson trial. But I wonder, too, how this obsession with new approaches to media — citizen journalism, community interaction, local coverage vs non-local — is going to look a few years down the track. For sure, there’s a lot to be said for breaking down the barriers between newspaper and community between professional and amateur reporter/photographer/editor. But this movement will also have some heavy long term effects that aren’t really discussed in this blogocratic world.

  • “Going local” is nearly always going to mean narrowing horizons. Newspapers and their portals (and their successors) with thinner or nonexistent foreign pages, what coverage there is based on wire reports. Is this what we want?
  • I’m all for interactivity and respect for active reader/contributor participation. But to me it’s somewhat shortsighted an argument that goes “newspapers are less profitable so fire the people who actually differentiate, or should differentiate your product from everything else out there”. Surely we should be talking about how journalists might raise/alter their game to match this challenge? Since when was responding to a change in the market a question of throwing the value overboard and investing in fewer skills, not more?
  • The issue closest to my heart is international coverage. Baltimore Sun, LA Times etc are cutting back on international staff. Fine, people say, replace them with bloggers. No question bloggers are good, and have good things to say, but who is going to do the legwork to explain, in an objective and engaging style, the complexities of issues such as terrorism (al Qaeda, Jemaah Islamiyah), disaster relief (earthquakes, tsunamis) to an international audience? There may be no interest in these issues right now, but when another disaster happens, who is going to do the coverage? 9/11, anyone?
  • Foreign coverage is only a “worthy” (rather than profitable) investment because it’s seen that way, not because it need be. I certainly agree with one commenter that journalists tend to hunt in packs, not because they lack imagination but because they tend to be rewarded by nervous editors looking for “matching” copy. The result is a foreign news page that tends to look similar from publication to publication. This needs to change; most foreign correspondents work their socks off satisfying editors’ hunger for matching copy (“Java Earthquake Kills Hundreds; Briton Forced to Cut Short Holiday”) and then, when everyone else goes home for the weekend, traipse off to the jungle to weave a telling story about environmental destruction/global warming/species extinction.

In short, I think we need to explore ways of reinvigorating coverage of news beyond our own local niche and recognise that the idea of the foreign correspondent, while dated and definitely in need of updating, has been around since the Boer War because it works. For sure there’s plenty of room for amateurs (some of my favorite writers about Indonesia aren’t journalists) but there’s also room, nay a need, for professional reporters to explore and report back on what they see. In an increasingly complicated world we need them more than ever.

How To Fix A Broken Installation File

By | November 22, 2011

This is another public service announcement of interest only to a few people, but if you experience a problem under Win2K/WinXP installing a driver, with the folllowing error message:

The required section was not found in the INF

this might save you hours of fiddling around. In this case it happened with my vodafone/Globe Trotter 3G PCM card but I’ve seen people with scanners, printers etc experience the same problem. Basically the drivers won’t install, and that’s that.

I couldn’t find any solution on its own that fixed the problem, and I don’t know whether this works in all cases, but this is what I did, and it worked for me:

Open your C:WindowsSetupapi.log file, and look around for the “INF” reference. You should see something like

#E067 Could not locate section [ClassInstall32].
#E142 Class: {4D36E971-E325-11CE-BFC1-08002BE10318}. Install failed. Error 0xe0000101: The required section was not found in the INF.

This tells you the section that is missing in the installation file. So now you need to find that file.

Go back up the log and see what INF file (a file with the last three letters, after the period, as inf, like c:windowsinfoem126.inf.

That’s the file that’s causing the problems. Open the file in notepad (in some cases you can do this simply by pasting the full path and file name into Start/Run. Sometimes this won’t work.

Save a backup of the file in question.

Then in the original, add a section with the name of the missing section. In my case, [ClassInstall32].

Save the INF file. Close it, remove the hardware and connect it again. Keep your fingers crossed. Now the installation should proceed normally.

At least it did for me. How dumb can installation software be that this basic problem cannot self-heal?

(Here’s where I got some information for this from.)