Jump to content

matidio

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Italy

About matidio

matidio's Achievements

0

Reputation

  1. I used the archive as I wrote and you're right when you say I have an invalid path of Universal Extractor in the path variable. I didn't remember its existence otherwise I would have deleted it. Ok, problem resolved. Although I think this is a bug. As I assume UE tries to find the extracting binaries in its path, can't find them but then uses PEID.exe in the current path (the one from which I launched it), is this right? Ok, it's a rare case ... anyway. As I said in my comments some week ago. A very nice application, thanks for it. Saluti
  2. I verified at work and it happens definitely with the new version 1.1 as you can see on the screenshot. I'm verifying what could be the difference between home and work. Here at work nothing special is installed. As you can see on the second screenshot the message "Nothing found [Overlay] is delivered from PEid.exe. I will report if I find something. Saluti
  3. It's unbelievable. I tried it now at home with same universalextracter binary which I ported from work (the bin rar) at home and here it works ... I swear it's the same bin. At work I started it directly from the extracted directory (It can't be the 1.0 because I did uninstall it some week before) and it didn't work and showed this message. So I don't know what it could be. I hate this kind of mysteries I doubt it has something to do with the environment. Both standard XPSP2 (at home a little bit cleaner). Wednesday I will do another test at work (tomorrow is a holiday for us) and I will report. Sorry for this mess.
  4. Seems that sometimes it has difficulties to recognize the archive format. If you take for example the original Trialversion for winzip 10 - a zipexe archive - UniversalExtracter responds with a message: winzip100.exe cannot be extracted. Filetype returned was: Nothing found [Overlay] If you try to extract it with Winrar or 7-zip there are no problems. This problem existed since the first version of Universalextractor Saluti
  5. Hi, oftenly I have problems to read the forum feeds with my feed reader. This is independent of the reader (it occurs with a few ones) therefore I exclude a reader problem. This time I had for example the following problem: XML Parsing Error: not well-formed Location: http://www.msfn.org/board/index.php?act=rssout&id=7 Line Number 61, Column 976: <description><![CDATA[Runing nlite in a windows XP sp2, updated up to date, no .net framework. .... etc. This is an example where someone used code snippets which confused the parser. Unfortunally these kind of problems accumulate in the last weeks. Maybe it is possible to configure the feed creator in a way that it produces a more standard/syntax compatible format? Thanks
×
×
  • Create New...