Exec Error when moving project to a new PC

[bellysavalas]

Hi

I just got a new PC and want to move my Delphi projects from my old PC to my new one. I installed RAD Studio 2007 on the new machine and copied my projects over. I then began the process of building each project in turn.

My problem is that some of my projects build (but don't run), but with the following error message:

'[Exec Error] The command "tdspack -e -o -a C:\TPFSoftwareBin\TPFGI\GIDataCollection.exe" exited with code 9009.'

"tdspack" is part of a third party package that seems to build and install without any problems.

All this stuff worked fine on my old machine. The problem only exists on the new machine.

If you are able to point me in the right direction for trying to find out what sort of thing causes this type of error and/or what "code 9009" means, this would be really helpful.

Thanks.

 

[Glenn9999]

All this stuff worked fine on my old machine. The problem only exists on the new machine.

Which means there's something different about the new machine. What's the OS on each one?

----------
Measurement is not management.

 

[bellysavalas]

Both machines are Windows XP Pro, but the new machine has SP3 whereas the old machine has SP2. Do you think that this might have something to do with it?

 

[Griffyn]

Unlikely in my view. Things like DEP and the firewall were already there in SP2.

I'd uninstall and reinstall the tdspack stuff. My guess is that the install of that on the new machine was somehow different - perhaps a component of it didn't get installed.

 

[LucieLastic]

Are there any components/Type libraries that may need installing/registering in Delphi you've missed?

www.radbmx.co.uk

 

[bellysavalas]

Problem solved! Thanks everyone for your input.

There are a lot of components and type libraries involved, so I went through and checked them, making sure that anything that should be registered as servers are etc...

It turned out, however, that the problem was a bit more obscure than that. It's unlikely that anyone will have a similar problem, but I'm posting my solution anyway just in case it is helpful to anyone else.

The problem was that the projects that were giving this error all had a post-build command defined ("tdspack -e -o -a $(OUTPUTPATH)"; defined in Project-->Options-->Build Events). $(OUTPUTPATH) was System32, not the tdspack folder. After building tdspack, I copied the tdspack.exe from the tdspack folder to the System32 folder. This allowed the post-build command to be able to find the executable. This seems to have solved the problem.

Thanks for all your help.