Drugwash, on Sep 15 2006, 11:58 AM, said:
It appears that it calls PEiD 3 times (in this particular case; for other files it only calls it once or twice). After that, the error message box appears. Most likely it's a Win9x issue, as the Dependency Walker log reveals missing functions in some modules (log attached below).
PEiD is supposed to be called 3 times if the filetype isn't obvious. UniExtract runs PEiD in three different modes (deep, hardcore, and external), and then takes action based on the results of the three scans (each scan can return different results). This is new behavior in 1.3.
I agree, it's most likely a Windows 98 issue. I have two statements here (please read both fully):
1. I do not and really can not support Windows 9x. I haven't done anything that should explicitely prevent it from working, but I don't have access to any system running Windows 9x, and vendor support for all Windows 9x systems (including security fixes) ended on 06/30/2006. Because of this, any system running Windows 9x really should be upgraded (or migrated to another OS, such as Linux), and as a security professional I cannot justify officially supporting an end-of-life'd OS.
2. With that said, I do understand that some people simple cannot upgrade or migrate to a newer OS, and I have no intention of simply ignoring them. I'll look into this issue when I have the time, and will try to fix the problem if possible. I'll post back once I've had a chance to investigate this further.
Galactical, on Sep 16 2006, 04:03 AM, said:
The error log location is 'hard coded' to the root of C:\, but different users will have different preferences and disk layouts. Could you include a means for us to change that location, perhaps to any/all of: the Universal Extractor installation directory; or the starting location for the extraction; or the target location for the extraction; or just anywhere the user prefers?
Actually, it's not harcoded to C:, it's hardcoded to the root of your %SYSTEMDRIVE%. This will ensure that the file always gets written, even if Windows is installed on your G: drive. I chose %SYSTEMDRIVE% because out of all of the other possible locations (installation directory, temp directory, etc.) it's the quickest and easiest to get to if you need to view that file. The only other place I can think of that would be even easier would be your desktop, but I hate
desktop clutter, so that's not going to happen.
Now, I do intend on reworking this in some way during the next major upgrade. I'm not sure what I want to do with it just yet, but making the location user-selectable seems reasonable. I'll keep it in mind.
the_guy, on Sep 16 2006, 08:29 AM, said:
I have no idea why, but the issue on 98SE is also on ME.
Yeah, I'd expect as much. I'm sure most of the people on this message board already knows this, but there are substantial difference between 9x-based systems (95, 98, and ME) and NT-based systems (NT, 2000, XP). Most likely either UniExtract or one of its components is calling some function that's only available on NT, so the same error message would appaer regardless of 98 or ME.
Drugwash, on Sep 16 2006, 11:28 AM, said:
That's bad news.
Maybe actually building the main exe on a 9x system could fix things. No idea if AutoIt does work on 9x and currently I have no free HDD space to install and test. Could you test it, nitro322, maybe in a virtual machine or something?
AutoIt does work under Windows 9x, but simply compiling it under 9x wouldn't make a difference. As I mentioned previously, there's probably some function call that requires NT, and I'll have to troubleshoot when I get some time.
justwanna, on Sep 16 2006, 03:38 PM, said:
Universal Extractor fails to extract the installer exe of the new version of yEnc32 (v1.0.7).
I can't get it to work, either. NSIS support is not at all complete; this looks like one of the unsupported types.
Hanschke, on Sep 17 2006, 10:07 AM, said:
here i got an error message:
Based on the description (CAB SFX), this file looks like it should be supported, but I can't say for sure without testing the actual file. Can you provide a download link?
This post has been edited by nitro322: 17 September 2006 - 09:16 PM