Installing DiRT

[iplatt]

Hello, i have a Unity version 3.1(2). I am trying to install Dirt ver 1.0.115 but keep getting the error message below when running setup

*** ERROR: Old format or invalid type library.

*** ERROR: An unexpected setup error has occurred!

Does anyone know how to cure this please?

I have another Unity running exactly the same version and DiRT installed OK

Many thanks

Regards

Iain

[lindborg]

hmmm... I haven't seen anything like that error message before - what OS/SP are you running on that box?

[amylinit]

This post reminded me I've run into an installation problem with installing DiRT Backup 1.0.115 as well.

Platform is Unity 4.0.4SP1 on Windows 2000 SP4. Same problem occurs on two different Unity installations (also Win2KSP4, w/Unity 4.0.4SP1).

While running setup the following dialog box appears:

Setup (in title bar of dialog box)

Setup cannot continue because some system files are out of date on your system. Click Ok if you would like setup to update these files for you now. You will need to restart Windows before you can run setup again. Click Cancel to exit setup without updating system files.

The installation window remains in the background, and shows the current progress:"Copying file please stand by. Processing MSVBVM60.DLL (1 of 1))"

If I click Ok in the Setup dialog box I'm prompted to reboot. Rebooting and reinitiating the installation just brings up the same dialog again in an endless cycle. Clicking Cancel aborts the install.

No problems with installing the last couple versions of DiRT Restore. Only happening with Backup.

Happy to email screenshots if it would be helpful.

Any ideas?

Cameron

[lindborg]

This sounds like a seperate problem than the one that started this thread.

Someone reported something similiar with the FullDBExport install on an older NT install a couple weeks ago - unfortunately I need that Virtual Machine file on there and it needs to be the correct version (i.e. the one that comes with Visual Studio 6 SP6) - so I can't just remove it from the install. I'm unsure why the OS is not allowing it to be updated (NT has this fab little habit of restoring files it considers "system" if they've been updated against its will).

for the folks having problems with the FullDBExport I bundled up an Install Shield version of the setup which worked - it's apparently smarter about dancing with the OS mechanisms for replacing system files that are in use than the build in Visual Studio installer. Unfortunately this requires I bundle the MSI 2.0 install, a setup.exe wrapper and some rather large merge modules into the setup which bloats them to 15+ megs a pop instead of the 2 or 3 meg they are now.

If you want to ping me directly: lindborg at cisco dot com, I can drop an IS version of the install for DiRT backup and have you try it out on that box to see if it works around it.

[lindborg · Accepted solution]

I went ahead and generated and tested an Install Shield version of the DiRT backup setup - it's bigger than the old style CAB setup but more robust and may address the problem you're having here. Ping me at "lindborg at cisco dot com" and I'll shoot you a copy to try out. I'll have to wait for QA to test and approve it before posting it to www.CiscoUnityTools.com for general consumption.