Forum Home
Press F1
 
Thread ID: 56747 2005-04-14 03:38:00 Nero 5.5 wont reinstall after XP reinstall dob (7890) Press F1
Post ID Timestamp Content User
344741 2005-04-14 03:38:00 My CDRW/DVD combo (Dick Smith) has run quite happily for the past year on the OEM install of Nero 5 . 5 that came with it . - OS = Win XP Pro .

After installing a new hard drive and doing a clean install of XP pro - any attempt to install Nero comes up with the following message - "an older version of Nero-Burning Rom was found on your computer" , "Click to remove Nero . . . . etc" .

Needless to say - clicking "Remove" achieves nothing

A Registry search for "Nero" natually yields nothing - as expected

Is it possible that the Nero detects XPs inbuilt CDR drivers ?

Attempted to install Nero after reinstalling most of our previous programs first - certainly nothing related to the CD drive

Most grateful if anyone could shed some light on this mystery .
dob (7890)
344742 2005-04-14 03:52:00 Download the latest version (6 . 6 . 0 . 8) of Nero .

It might be a bit old the version u have, thats what it's saying .

I dont think Nero worries about what CDR drivers XP has . (Altho XP builtin cd burning isnt that great anyway) .

The version of Nero may not be compatible with your version of XP (If u have SP1 or SP2 installed) .
Speedy Gonzales (78)
344743 2005-04-14 04:07:00 Havn't got round to reinstalling SP1 yet , although it was on the PC when I installed Nero the 1st time

dob
dob (7890)
344744 2005-04-14 04:14:00 I would still get the latest version . It's much better .

The only reason why cd burners wont work with Nero or any version of Nero, is if u changed the burner (if the burner u had died), or the OEM version of Nero u had/have didnt come with the original burner .

BUT this would let u install Nero, BUT the burner wouldnt work / be recognised, coz the burner wasnt the original burner, the OEM version came with .

The only thing is, if u do update Nero, it may remain a demo as the OEM version serial may not / wont work with v6 of Nero .
Speedy Gonzales (78)
344745 2005-04-14 04:15:00 Hi dob, Welcome to PressF1

Have a look at this Nero FAQ on your error message - here (ww2.nero.com). They offer a General Clean tool which may be of benefit.
Jen (38)
344746 2005-04-14 05:06:00 Tried Nero Clean Tool

No luck - thanks
dob (7890)
344747 2005-04-14 05:26:00 try regcleaner or registrar lite to search for and remove any mention of nero, I just did a quick search with registrar lite thru my registry and came up with 589 mentions of nero......... drcspy (146)
344748 2005-04-14 05:33:00 I had this problem a while back. I had a long back and forth email conversation with Nero tech support, following all their recommended steps and using their clean tool. In the end I tracked it down to a corrupt dll file (sorry can't remember which one). The clean tool would remove everything else but not this file and it prevented Nero from running or successfully or re-installing. I couldn't delete it manually -- used assorted disk tools to try and kill it, the lot.

In the end I decided it was time to reformat my disk and re-install Windows, which I did. Haven't had a problem since.

Run the Nero Clean Tool to find out which DLLs are involved. Then locate them and just try renaming them (.bak instead of .dll, for example). If you have the same problem I did, you'll get to one that you can't rename - it's the sick puppy.
Biggles (121)
344749 2005-04-14 05:49:00 this was a clean install of XP a few weeks ago on a new HD with just a few basic programs - norton AV, Winzip & some utilities installed (ones that I have used for years) . Same CDRW drive, same PC, same Nero 5.5 - only this time it wont install - can't be any references to Nero in the registry, though I did check just in case (stranger things have happened) dob (7890)
344750 2005-04-14 06:04:00 If it's the same issue I had it has nothing to do with registry, it is simply a file corruption. The file won't do it's job (it's corrupt). I had the same error message about an "older version". Try what I suggest and I suspect you will find a single DLL fiule that has gone bad. Biggles (121)
1 2