Don't have a FP1 device to test with. Possibly due to some new APIs being called in post-002 that might not have been present in FP1. Don't have suitable SDK to check that either.
Submitter: (btw please log in so I know who is submitting stuff...) can you try running "chkdeps c:\sys\bin\swi.exe" and attach the output here? Or get in touch so I can send you a test build.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Number of dependencies checked = 29
1: euser.dll Uid3:100039e5 - No import data
2: iocli.dll Uid3:00000000 - File was found, Uid3 is supported
3: efsrv.dll Uid3:100039e4 - No import data
4: ltkutils-tcb.dll Uid3:10286f57 - File was found, Uid3 is supported
5: hal.dll Uid3:100039e8 - No import data
6: dfpaeabi.dll Uid3:00000000 - No import data
7: drtaeabi.dll Uid3:00000000 - No import data
8: scppnwdl.dll Uid3:00000000 - No import data
9: drtrvct2_2.dll Uid3:00000000 - No import data
10: lineeditor.dll Uid3:10285c66 - File was found, Uid3 is supported
11: ltkutils.dll Uid3:10286a06 - File was found, Uid3 is supported
12: bafl.dll Uid3:10003a0f - No import data
13: estor.dll Uid3:10003b0d - No import data
14: ws32.dll Uid3:10003b21 - No import data
15: sishelper.dll Uid3:101f7293 - File was found, Uid3 is supported
16: uiss.dll Uid3:10202dc8 - File was found, Uid3 is supported
17: sisregistryclient.dll Uid3:10202dcb - No import data
18: uissclient.dll Uid3:10203521 - No import data
19: sisxfile.dll Uid3:10202dc6 - No import data
20: fbscli.dll Uid3:10003a15 - No import data
21: apgrfx.dll Uid3:10003a3c - No import data
22: plpvariant.dll Uid3:10009b13 - No import data
23: imageconversion.dll Uid3:101f45ad - No import data
24: securitymanager.dll Uid3:10202614 - No import data
25: cafdataprovider.dll Uid3:1020685d - File was found, Uid3 is supported
26: caf.dll Uid3:00000000 - No import data
27: swidataprovider.dll Uid3:1020362d - No import data
28: ecom.dll Uid3:10009d8e - No import data
29: charconv.dll Uid3:10003b11 - No import data
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the log. Not a dependency issue then... Does the --verbose option give you any more info about what's going wrong? I assume you were seeing the problem with installing - does "swi list" work for you?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It gets weirder... my 3rd FP2 device (N96) only lists 16 DLL dependencies, as does my N8. So there must have been some refactoring of software install between FP1 and FP2. I guess it's due to that, so I'm surprised that chkdeps didn't find any problems. Looking further at the diffs of v002 and v004, there's almost nothing different in the code when doing a "swi list" unless you specify --verbose, so I'm running out of ideas. I'm pretty sure all the SIS were built on the exact same baseline so I can't see why v002 would have worked for you but not v004.
One thing I forgot to ask, does "swi --help" work?
Also, what device are you seeing the problems on? It's a production device presumably, and you're self-signing the SIS file?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Don't have a FP1 device to test with. Possibly due to some new APIs being called in post-002 that might not have been present in FP1. Don't have suitable SDK to check that either.
Submitter: (btw please log in so I know who is submitting stuff...) can you try running "chkdeps c:\sys\bin\swi.exe" and attach the output here? Or get in touch so I can send you a test build.
Number of dependencies checked = 29
1: euser.dll Uid3:100039e5 - No import data
2: iocli.dll Uid3:00000000 - File was found, Uid3 is supported
3: efsrv.dll Uid3:100039e4 - No import data
4: ltkutils-tcb.dll Uid3:10286f57 - File was found, Uid3 is supported
5: hal.dll Uid3:100039e8 - No import data
6: dfpaeabi.dll Uid3:00000000 - No import data
7: drtaeabi.dll Uid3:00000000 - No import data
8: scppnwdl.dll Uid3:00000000 - No import data
9: drtrvct2_2.dll Uid3:00000000 - No import data
10: lineeditor.dll Uid3:10285c66 - File was found, Uid3 is supported
11: ltkutils.dll Uid3:10286a06 - File was found, Uid3 is supported
12: bafl.dll Uid3:10003a0f - No import data
13: estor.dll Uid3:10003b0d - No import data
14: ws32.dll Uid3:10003b21 - No import data
15: sishelper.dll Uid3:101f7293 - File was found, Uid3 is supported
16: uiss.dll Uid3:10202dc8 - File was found, Uid3 is supported
17: sisregistryclient.dll Uid3:10202dcb - No import data
18: uissclient.dll Uid3:10203521 - No import data
19: sisxfile.dll Uid3:10202dc6 - No import data
20: fbscli.dll Uid3:10003a15 - No import data
21: apgrfx.dll Uid3:10003a3c - No import data
22: plpvariant.dll Uid3:10009b13 - No import data
23: imageconversion.dll Uid3:101f45ad - No import data
24: securitymanager.dll Uid3:10202614 - No import data
25: cafdataprovider.dll Uid3:1020685d - File was found, Uid3 is supported
26: caf.dll Uid3:00000000 - No import data
27: swidataprovider.dll Uid3:1020362d - No import data
28: ecom.dll Uid3:10009d8e - No import data
29: charconv.dll Uid3:10003b11 - No import data
Thanks for the log. Not a dependency issue then... Does the --verbose option give you any more info about what's going wrong? I assume you were seeing the problem with installing - does "swi list" work for you?
"swi list" causes the same error.
It gets weirder... my 3rd FP2 device (N96) only lists 16 DLL dependencies, as does my N8. So there must have been some refactoring of software install between FP1 and FP2. I guess it's due to that, so I'm surprised that chkdeps didn't find any problems. Looking further at the diffs of v002 and v004, there's almost nothing different in the code when doing a "swi list" unless you specify --verbose, so I'm running out of ideas. I'm pretty sure all the SIS were built on the exact same baseline so I can't see why v002 would have worked for you but not v004.
One thing I forgot to ask, does "swi --help" work?
Also, what device are you seeing the problems on? It's a production device presumably, and you're self-signing the SIS file?
`swi --help` doesn't work too.