Installation Problem

[PBrennick]

Michael,
It is because the list of DEF files are transitory in nature. The way it has been built allows changes to this list without having to rewrite and recompile the program every time.

Of course, we will 'might' need to rethink this strategy because I do NOT wish to go through this twice. It is to be noted, though, that there has been very few problems with this method. I still am confused why you had a problem at all. That is the real problem here, we do not know what is in your system that is causing this problem. The NT explanation does not hold water or Hutch would have had the same problem. I sure wish I had Windows 2000.

Paul

[jdoe]

Now, that I know that these fancy commands can cause problems, it will take a very convincing story to get me to go back to using 'for' logic again!

Paul and Erol,

Sorry, I never thought that the FOR command was not the same in all Windows version. The idea of a build.bat that don't need to be rewrite was good but it seem to suffer a lack of compatibility. It's just too bad.

jdoe

[Vortex]

No problem Jdoe, we thank you for your support. At the moment, me and Paul, we are working on a method based on using CreateProcess & WaitForSingleObject. We always welcome your contributions.

[MichaelW]

I have now updated the Windows 2000 on my spare system to SP4, installed IE6-SP1, the .NET 1.1 and 2.0 frameworks, and all of the Microsoft security-related updates (~60). So I think I have pretty well duplicated the commonly installed system-level components that are on my primary system, were the GeneSys install is failing, and the GeneSys install on my spare system still works as it should. Whatever the problem is with my primary system I doubt that it's likely to affect very many systems, and so probably not worth trying to fix in the GeneSys install. The installation that I finished up by running setup.bat manually continues to function correctly.