[HOME] [DOWNLOAD] [DOCS] [BLOG] [SUPPORT] [TIPS] [ISSUES] [Priority Support]

Testing Whonix-Installer for Windows


#182

@Razor12911 Thank you for stopping by, I have a few questions, is the pZlib_source.7z file the source for this version: pzlib_1210.7z? It doesn’t include win64 object files, if we add them, would it compile the 64 bit binary as well? Do you think it is easy to compile the zlib object files from source? DelphiZLib 1.2.7 includes C++ Builder project files whereas 1.2.8 does not


#183

Well you could get the already object files for x64 from here.

http://www.base2ti.com/

The reason I didn’t include them is because I’m a developer based on Delphi, anything other than that is just not my thing so the problem with x64 obj files was that they were 2 times slower than the x86 which is totally weird, but there is source as well in the attachment from the site, you can generate new obj files if you know how to do it because certainly, I have no clue how it’s done. I don’t they may not be slower for you but do check, I have been constantly changing obj files, it may or may not have been these ones that had this problem.

Goodluck.


#184

Good day,

First of all, thank you very much for joining our Forum and being willing to Support us in such a Major way. That is incredibly nice of you.

Furthermore, you may take a look at the current source Code and compilation methodology here and here.

Secondly, thank you very much for Clearing up the licensing question. Just for legal reasons, may I ask whether it would be ok to use your source Code, obviously with proper Attribution under the MIT license?

Thirdly, the x86 vs x64 Speed inconsistencies are likely caused by the requirements for extending the string lenght when running AMD64 based Systems in 64-Bit mode while the string lenght doesn’t fully utilize more then 32bits causing an increased requirment in using Cache which doesn’t yield any improvements while limiting the small amount of low Level Cache available on most consumer CPUs. That though is only a hypothesis. Maybe I simply misunderstood something my CS teacher told me, though that’s how I recall his reasoning on certain aspects of x64 being slower then x86.

Again, thank you very much for your help, if you have any questions or require anything, don’t hesitate to ask and have a great day,

Ego


#185

As I know for Linux and Mac there is only 32bits versions and for Qubes only 64bits. For Windows what versions there are ?


#186

Good day,

The installer includes both the 32 and 64bit version of VirtualBox. Whonix itself is currently being distributed in 32bit, which may run on any system, see also: https://www.whonix.org/wiki/Dev/64bit#Current_Situation

Have a nice day,

Ego


#187

Good day,

Adding to that, in the comming days, I shall release a completley new version of the Installer. It will be based on Inno Setup, increasing compatibility, decreasing size and optimizing stability. Furthermore, it has been designed in such a way as to make the compilation as easy as possible. After all the required files are in the same folder, you’ll only have to launch a batch file and everything will be handled automatically.

You may already compile it yourself: https://github.com/EgoBits1/Whonix-Windows-Installer

Have a nice day,

Ego


#188

Are you sure,

  • 7zSD.sfx
  • 7za.exe

should be shipped since these are binary executable files?


#189

Good day,

Problem is, the only way to currently utilize 7-Zip SFX in combination with a custom logo is by having these premodified via Resource Hacker. We can of course exclude them, though the installer would then carry the “7z” icon.

Have a nice day,

Ego


#190

The binary package can have them, but I don’t think we should have binary executable files within the source package.


#191

Good day,

I’ll adjust the process then, as to keep the checksum between the binary and the compilation comparable.

Have a nice day,

Ego


#192

You mean referencing and checking the checksums of 7z before executing these? That would be good.


#193

Good day,

I was actually refering to the compiled binaries checksum. What I meant was that I shall change the entire process in a way that is not going to necessitate the inclusion of these binaries while still allowing for both the premade and the self-compiled installer to be the exact same including the icon.

Have a nice day,

Ego