Post Reply 
 
Thread Rating:
  • 6 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Daz Windows Loader v2.2.2
01-08-2017, 11:25 PM
Post: #131
Smile RE: Daz Windows Loader v2.2.2
Thanks to Daz! It worked like a charm...
Find all posts by this user
Quote this message in a reply
02-10-2017, 08:45 PM
Post: #132
RE: Daz Windows Loader v2.2.2
NEW GUEST DOWNLOAD

https://dropfile.to/H2rrhNy

USE THIS KEY
mYSwctn
Find all posts by this user
Quote this message in a reply
02-11-2017, 08:28 AM
Post: #133
RE: Daz Windows Loader v2.2.2
(04-07-2011 01:09 AM)JimBob Wrote:  I installed Windows 10 Loader 2.0 on my up to date Win7 64 system. It did get rid of the activation warning issue. However, my system properties indicate that Windows is not activated. If I click to activate, the response is that activation is successful . Is this the way it's supposed to work, and will I be able to install updates? Thanks.

Hi
If you are unable to install Windows Updates, first clear up your Temporary Files and Internet Cache, reboot and try again. See if this helps resolve the issue.
Disable your Firewall and Anti-virus software and try again.
Find all posts by this user
Quote this message in a reply
02-27-2017, 07:44 AM
Post: #134
RE: Daz Windows Loader v2.2.2
As of 2/26/2017, the zip files provided in the supposed "mirrors" in the 1st post (OP) are NOT the same as the files hosted on this forum.

Need me to provide the proof? Then read on!

The ORIGINAL (clean) zip file hosted on deioncube has the following:
CRC32: 3ADDF16A
MD5: 9B87C483AE8401ACD1455CAE18214F65
SHA-1: 9FDC0F166AA10087CC49B2952CE9EA3F1412416A


The mirrored files on both Dropbox and MEGA (in the OP's edited "updated links") has the following:
CRC32: D79A454F
MD5: AAC9BD22F58E5B022A92C3DAF92452C3
SHA-1: DC067D8EFCA870349CB836E57DC183C94FA9E2C6

The two differently sourced files DO NOT MATCH.

Additionally, running the extracted loader from the mirrors results in a "Bad" status with a red status icon in the top-right corner of that copy of Daz. It should not be trusted, since it may have been tampered with. You should only use the zip file hosted on deioncube, especially since the GOOD version of the program returns a "Good" status with a green circle icon in the top-right corner. And make sure the MD5 and SHA-1 values match the GOOD version before extracting your downloaded zip!

I would personally like to know why these files do not match.

In the OP (Post #1), the following text is seen next to the timestamp: "(This post was last modified: 02-23-2017 09:10 PM by cw2k.)"

Can cw2k please provide us with info on why the mirror links contain a bad copy of Daz Loader 2.2.2 since he is the one who edited these mirror links on 2-23-2017?
Find all posts by this user
Quote this message in a reply
02-28-2017, 11:51 AM (This post was last modified: 02-28-2017 11:55 AM by cw2k.)
Post: #135
RE: Daz Windows Loader v2.2.2
(02-27-2017 07:44 AM)xyzloader Wrote:  Can cw2k please provide us with info on why the mirror links contain a bad copy of Daz Loader 2.2.2 since he is the one who edited these mirror links on 2-23-2017?
Well giving/comparing the MD5 of the zip is not really appropriate. It's the uncompressed content that counts.

Modified doesn't means bad.
What I did is this:
upx -d "Windows Loader.exe"
Just unpacked the DAZ loader.
That triggered the selfcheck:
Code:
323C0FD51071400B51EEDB1BE90A8188 MD5 of original Windows Loader.exe with UPX
F5E1313C8EA41AC4E9379B9602B30A73 MD5 of unpacked Windows Loader.exe without UPX
However it's still working well.

Reasons for removing UPX:
  • Upxed file got blacklisted in many AV's and filehoster - unpacked it might slip thought the one or other simple check
  • More transparency - well I don't really like packed binaries. New stuff I used to do a quick manually scroll scan with the viewer of the Total Commander.
    And there packed stuff(high entropy data) - is always suspicious.
  • Quicker execution - especially when appling LZMA there'll be a slight delay when you start the exe
  • Better compression ratio when putting it into some zip/7z/rar. That's because already compressed data can't be compressed anymore - sometimes it'll get even slightly bigger when apply compression to it

But well I'll update the MD5 inside "Windows Loader.exe" so that integrity check will work again
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)

Contact Us | Homepage | Return to Top | Return to Content | Lite (Archive) Mode | RSS Syndication