Showing posts with label error code 39. Show all posts
Showing posts with label error code 39. Show all posts

Friday, January 15, 2010

iTunes Error 2131

Contacted by a client who suddenly found he couldn't burn CDs from iTunes. When he tried he just got an error message - the code was error 2131. How can that be fixed?

Reasonably on getting Error Code 2131 as he ran iTunes he naturally assumed that the cause of the problem was something within iTunes. Of course any single software application relies completely on interaction with the operating system which in this case was Microsoft Windows. iTunes does some things, Windows handles thousands of other tasks. For an exercise to be completed correctly, such as burning a humble CD, both iTunes and Windows need to play their part.

It is difficult to quickly see where the source of any error might lie, but my immediate thought was that this stems from Microsoft who offer a wide range of Error Codes. When we've been ripping CDs I think we've seen most of them but this one was new to me.

First stop - Google the error code. Wow, aren't there a lot of people hit by Error Code 2131 was my first thought. Looking at their posts to forums and blogs this has been going on for years. One common complaint - why doesn't Apple fix this? In my experience Apple does so having seen the age of the issue my suspicious eye turned to Microsoft.

Reading through the posts I felt that the majority of users complaining were laptop users. Next, why doesn't Microsoft fix this? Reading deeper into the messages from those who had beaten error 2131 they had done so either through an edit in Windows Registry or by downloading firmware for their drives. If you're not familiar with the term firmware its a small program a device such as a DVD or CD writer needs to function. Logically it sits "under" the operating system and therefore out of Microsoft's remit; physically it is stored on a small microchip on the logic board driving the writer.

Dell, Fujitsu and Toshiba owners were all hit, odd in itself as these are better quality manufacturers. I can't prove it but my suspicion is that they have all sourced CD / DVD drives as components from the same manufacturer. At some point something has happened resulting in a clash between Windows and the drive. Indeed this is what the error code is trying to say.

If my analysis is correct this really is the responsibility of the manufacturer and indeed several Dell users have downloaded a new version of firmware for their writers which has put an end to 2131. Owners of other makes have said this has worked for them too.

What should you do if iTunes stalls with Error 2131? Try Googling 2131 with the name of your PC manufacturer and that might give you access to a firmware update. Try your suppliers support website too, and log this as a fault with them. If you purchased your machine recently from a decent supplier think about contacting them and maybe even rejecting the machine. In my opinion far too few people do this.

Beyond these comments and suggestions I'm sorry to have to say if you get both iTunes and Error 2131 I'm sorry, I don't have an instant solution.

Monday, March 30, 2009

Error Code 39 - Vista - Lost DVD & CD Drives

If I ever get famous I shall use my position to publicise what will become known as Underwood's Second Law of Computing - never start a quick job on a Friday afternoon.

Client rings up, he wants some music put onto his iPod from the backup DVDs we supplied when we ripped his CD collection last summer. As he's off on holiday he wants it done quickly, and his PC has broken. Can we help? Yes, this is one for our great standby program XPlay 3 which enables you to move digital music files onto (or off) an iPod without using iTunes. "Great" says client (who lives in Chelsea) "I'm on the A12, about 10 minutes away, can you do it while I wait?"

Of course, we did, and client went away to his cottage in Suffolk very happy. But afterwards I couldn't use either of the DVD drives on the PC. They were there in the System properties boxes but with a yellow warning triangle next to them. Looking into properties it said something about Code 39, a driver being out of date. I fiddled and fiddled, by which time it was 18:00 and I had to be somewhere else. But it nagged at me all weekend, I put in an hour on Saturday and a couple of hours on Sunday, but no joy.

Today, Monday, I just had to get the DVD Reader / Writers back so I sat down to crack the problem. Which I eventually did. I won't bore you with how but I will tell you why it went wrong.

Connecting an iPod to a computer incurs the risk that it will be grabbed by iTunes and automatically synchronised. Client's iPod should be linked to his PC, even though that's broken. So I didn't want to run the risk that all his music would be lost, specially as he was sitting in my kitchen reading The Times. So to be absolutely safe and sure I deleted iTunes from that PC.

Now I find that a consequence of deleting iTunes in Vista (plus a few other programs according to Microsoft's website) is that the uninstall program deletes key values in Registry. It is Registry that lets your operating system know what is attached, so the computer thought the DVD devices were corrupted.

The fix was achieved by running a downloadable fix from Microsoft, equally it would probably have been fixed when I re-install iTunes for the project that begins tomorrow. So there you have it - if you lose your ROM drives, if you get the yellow triangle and driver error code 39, you know what to do - but most of all, if you plan to attempt a quick computer job, don't do it on Friday afternoon.