Kirill S. Posted March 30, 2006 Share Posted March 30, 2006 DropTeam exits with I still have the original 0.9.40 release. I did not update it because I could not. This is the DropTeamUpdate.log file: Updating - hold <ESC> to cancel Checking platform 'WIN32' files... Executing: wget.exe http://tbgsoftware.com/DropteamUpdate/WIN32FileList.txt is as far as the updater gets before it crashes. WinXP SP2 Geforce 3 Ti 200 Latest ForceWare I have Cygwin installed on my system. Could that affect the updater? Link to comment Share on other sites More sharing options...
ClaytoniousRex Posted March 30, 2006 Share Posted March 30, 2006 Very strange. Are you willing to try the fix laid out by Microsoft in this knowledge base article? http://support.microsoft.com/default.aspx?scid=kb;en-us;822520 This can also happen if your user account does not have access to some system DLL's. Are you logged into the computer as a user with administrative rights? You can grant all users read access to all system DLL's by doing this at a command prompt: </font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">CACLS %systemroot%\System32\*.dll /E /G BUILTIN\Users:R</pre> Link to comment Share on other sites More sharing options...
Kirill S. Posted March 30, 2006 Author Share Posted March 30, 2006 My login has administrative rights. The fix from Microsoft's website applies to SP1a, but I have SP2. Since I have cygwin on my PC, I decited to go further: GNU gdb 2003-09-20-cvs (cygwin-special) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-cygwin"...(no debugging symbols found)... (gdb) run Starting program: /d/Battlefront/DropTeam Public Test/Update.exe ---Type <return> to continue, or q <return> to quit--- Program received signal SIGILL, Illegal instruction. 0x00402997 in zlib!inflateSetDictionary () (gdb) The zlib in DropTeam's dir is 1.1.3.1 I tried to get zlib 1.1.4 from the same guys, the same error. The zlib 1.2.3 package does not have the same zlib.dll file. My CPU is an Athlon Thunderbird 1.2 GHz OC'd to 1.33 GHz. Regarding DropTeam.exe not running: GNU gdb 2003-09-20-cvs (cygwin-special) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-cygwin"...(no debugging symbols found)... (gdb) run Starting program: /d/Battlefront/DropTeam Public Test/bin/DropTeam.exe ---Type <return> to continue, or q <return> to quit--- Program received signal SIGILL, Illegal instruction. 0x016eac40 in osg!?setDefaults@DisplaySettings@osg@@QAEXXZ () from /d/Battlefront/DropTeam Public Test/bin/osg.dll (gdb) Go Cygwin!!! :cool: :cool: I have Software DEP enabled, if that's any use. Hope this helps. Link to comment Share on other sites More sharing options...
ClaytoniousRex Posted March 31, 2006 Share Posted March 31, 2006 When you get the original "Application failed to initialize" error, are you running it from cygwin there, too? Link to comment Share on other sites More sharing options...
Kirill S. Posted April 1, 2006 Author Share Posted April 1, 2006 No, I run it from windows explorer. I also do not have any Cygwin directories in my PATH. MS Visual Studio also gives the same illegal instruction error for the updater exe Link to comment Share on other sites More sharing options...
ClaytoniousRex Posted April 19, 2006 Share Posted April 19, 2006 Kirill, a guy on the cygwin mailing list had this to say: "The symptom is that I was trying to start a non-Cygwin program that I'd just built, and saw the above-mentioned popup. It didn't occur to me for a long time that the problem had anything to do with Cygwin, since neither the program -- nor the DLLs on which it depended -- used Cygwin. However, I *had* installed those DLLs by using Cygwin's "unzip" to unpack a ZIP file. I then noticed that if I simply did "chmod +x *.dll" on those DLLs, the problem went away. I figure "unzip" set the permissions on those DLLs to 0640, which seems reasonable from Cygwin's point of view ... unfortunately, though, NT requires those DLLs to be executable; hence the infuriatingly obtuse error popup." Sound applicable? Link to comment Share on other sites More sharing options...
Recommended Posts