Author Topic: The file is a decompression bomb (42110)  (Read 7124 times)

0 Members and 1 Guest are viewing this topic.

Offline sludge7051-x

  • sludge7051-x
  • Jr. Member
  • **
  • Posts: 88
The file is a decompression bomb (42110)
« on: November 28, 2014, 11:13:23 PM »
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

There are two errors, actually, but the above is a good one, LOL:

Error:  The file is a decompression bomb (42110)

Error:  An attempt was made to move the file pointer before the beginning of the file (131)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The error I see:

File D:\1\05 software hardware\05  OFFICE\window blinds\Window Blinds - setup.exe|>%AppFolder%\sdactivate.exe Error 42145 {Installer archive is corrupted.}
File D:\1\05 software hardware\05  OFFICE\window blinds\Window Blinds - Skin Studio - setup.exe|>%AppFolder%\DeElevate.exe Error 42145 {Installer archive is corrupted.}


Window Blinds - setup.exe

Window Blinds - Skin Studio - setup.exe

Please see screenshots
« Last Edit: November 28, 2014, 11:36:53 PM by sludge7051-x »

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: The file is a decompression bomb (42110)
« Reply #1 on: November 28, 2014, 11:21:29 PM »
A decompression bomb just means that the file is highly compressed so Avast will not open it during a scan however, if it is opened by another programme it will be monitored

Offline sludge7051-x

  • sludge7051-x
  • Jr. Member
  • **
  • Posts: 88
Re: The file is a decompression bomb (42110)
« Reply #2 on: November 29, 2014, 04:20:24 PM »
Thanks!

The second error must be from trying to open it?  Here's what I see:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Dynamics NAV Error: The operating system returned the error (131): An attempt was made to move the file pointer before the beginning of the file.

http://navisionary.com/2011/10/dynamics-nav-error-the-operating-system-returned-the-error-131-an-attempt-was-made-to-move-the-file-pointer-before-the-beginning-of-the-file/

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The operating system returned the error (131):

http://www.mibuso.com/forum/viewtopic.php?p=127780&sid=56402f4f8557e3b369ef984272759f1d#p127780

The clientmonitor saves all data into a temptable. A temptable is first kept in memory, but if it gets to big, it is saved on the local disk.
Because of historical reasons, a file created or opened by Navision CANNOT supperate 2GB. If it superates these 2GB, you get that error.

To solve it, you might try to let the client monitor take less data (untoggle some things you don't need) or try to let your report calculate less data.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Error message when you run a report or a dataport in Microsoft Dynamics NAV 4.0 or in Microsoft Business Solutions - Navision 3.7: "Operating System Returned the Error (131). An attempt was made to move the file pointer before the beginning of the...

http://support.microsoft.com/kb/933984

Offline sludge7051-x

  • sludge7051-x
  • Jr. Member
  • **
  • Posts: 88
Re: The file is a decompression bomb (42110)
« Reply #3 on: November 29, 2014, 04:28:08 PM »
These are not huge programs though:

Window Blinds - setup.exe is 47.6 MB
Window Blinds - Skin Studio - setup.exe is 13.7 MB

How highly compressed could they be?  A lot less than 2 GB.  Why would Avast be flagging it?

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: The file is a decompression bomb (42110)
« Reply #4 on: November 29, 2014, 04:57:08 PM »
It depends on the compression ratio

Offline MikeBCda

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 2246
Re: The file is a decompression bomb (42110)
« Reply #5 on: November 30, 2014, 12:05:39 AM »
If I may add to essexboy's remarks ... a so-called decompression bomb is (or at least used to be) typically compressed in several sequential stages, each stage using a different compression method to allow further compression.  Therefore the end result could be as much as several orders of magnitude smaller than the original file, as compared with, e.g., a common self-extracting exe, which might be a few dozen times smaller than its contents.

While we haven't seen much news about such "bombs" lately, we used to get lots of complaints about the worst-case scenario when trying to re-expand one, where in some cases the user would run out of disk space with one or more stages of decompression still to go.
« Last Edit: November 30, 2014, 12:18:48 AM by MikeBCda »
Intel Atom D2700, 2 gig RAM, Win 7 x64 SP1 & IE-11, Firefox 51.0
(default). 320 gig HD, 15Mb DSL, Win firewall, Avast 12.3.2280 free, SpywareBlaster, MBAM Prem., Crypto-Prevent

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37698