I create package definitions for admins to import for our tools, in .sms format.
In this format, you have to specify the environment requirements which include OSPlatform.
There is a hotfix that when run, inserts the X64 options into the database, and therefore they are vissible in the manual program properties for selection.
However, when creating the package definition, specifying the versions for x64 XP Pro, when you view the program properties, the x64 XP Pro option isn't selected, and instead it has inserted a string WinNT (x64). When i advertise this program. The program fails saying that it is not compatible. However, if i select the built in X64 Windows XP Professional option manually, the program runs correctly.
When specifying version numbers of all other versions in the package definitions. The versions are grabbed, and tied to the database display version, so when you look at the program environment requirements, the standard options are selected depending on which vers you specified. This is not the case for x64. Which not only does it not show the standard x64 object selected in the GUI, but it doesn't even validate correctly at execution time, even though the version numbers are the same between my specified .sms file, and the GUI wizard selected one.
Does that even make sense to anybody? If so, anybody any ideas?
Hope this Helps.
Neil J Cotton
njc Information Systems
Systems Consultant
In this format, you have to specify the environment requirements which include OSPlatform.
There is a hotfix that when run, inserts the X64 options into the database, and therefore they are vissible in the manual program properties for selection.
However, when creating the package definition, specifying the versions for x64 XP Pro, when you view the program properties, the x64 XP Pro option isn't selected, and instead it has inserted a string WinNT (x64). When i advertise this program. The program fails saying that it is not compatible. However, if i select the built in X64 Windows XP Professional option manually, the program runs correctly.
When specifying version numbers of all other versions in the package definitions. The versions are grabbed, and tied to the database display version, so when you look at the program environment requirements, the standard options are selected depending on which vers you specified. This is not the case for x64. Which not only does it not show the standard x64 object selected in the GUI, but it doesn't even validate correctly at execution time, even though the version numbers are the same between my specified .sms file, and the GUI wizard selected one.
Does that even make sense to anybody? If so, anybody any ideas?
Hope this Helps.
Neil J Cotton
njc Information Systems
Systems Consultant