![:frusty:](http://reboot.pro/public/style_emoticons/default/frusty.gif)
Ready to change the WimLib / jWim name in multiPE on a daily base
![:suda:](http://reboot.pro/public/style_emoticons/default/suda.gif)
Peter
Posted 22 May 2012 - 03:22 PM
Posted 22 May 2012 - 03:58 PM
Posted 22 May 2012 - 04:06 PM
It is coded in C and wasn't needed.Why the "freelancer" could not use the available 7-zip source as base?
For some developers it is faster/simpler to start from scratch than using a project made by someone else.What was the reason to start (yet-again) from scratch?
The compiled bytecode will run across diverse operative systems and machines. For example, when the new ARM version of Windows 8 comes out we will still be able to use the same old binaries. If we want to run this tool on android, a cloud OS or whatever they invent within the next 50 years, no problem.Why was java chosen as "engine"?
No problem. Let's call this project "reWIM" and get the naming issue solved.
Posted 22 May 2012 - 04:13 PM
I saw that, but as it is a windowmanager implemented in Javascript and has nothing at all to do with images of any sort it should not be an issue especially if you stylize as jWIMhttp://freecode.com/projects/jwim
Ready to change the WimLib / jWim name in multiPE on a daily base
Peter
Posted 22 May 2012 - 04:15 PM
Sim, BossNo problem. Let's call this project "reWIM" and get the naming issue solved.
Posted 22 May 2012 - 05:23 PM
Posted 22 May 2012 - 06:41 PM
Posted 22 May 2012 - 10:26 PM
We had a rule in our company too. Don't reBTW: Developing from scratch does not bind you to any known "Common License" and gives you the ability to use your own / favoured license model.
Posted 23 May 2012 - 12:40 AM
Posted 23 May 2012 - 02:19 AM
3) Java running on any platform? And what are you going to do with your Delphi coded Winbuilder? Are you going to get Delphi for ARM? If I were you I’d rather be trying to run away from Delphi than embracing challenges like coding a WIM library from scratch in Java.
PS: BTW when are you going to release winbuilder 64Bits?
Posted 23 May 2012 - 12:57 PM
Posted 23 May 2012 - 02:48 PM
I did some tests on the compression and it seems that:LZX and XPRESS compression algorithms can be added later. On my tests, the image without compression are faster to load and start.
Posted 23 May 2012 - 02:53 PM
Hi Chris (and Paraglider that reported similar issue),rebuild with original run.bat (wimlib.jar), after creating the folder "Sources". Otherwise we have the message "Capture image failed." without error code or a message more explicit.
after that my building went well (814 Mb) and My Iso seems to start "windows is booting..." before an error.
Posted 23 May 2012 - 03:06 PM
Posted 23 May 2012 - 03:26 PM
Unless your idea, how many seconds fit into a hand, differs greatly from mine, it won't be. I think the description 'a truckload of seconds' would be a better description.but if the use is within a builder like Winbuilder possibly a handful of seconds more won't make a sensible difference,
Posted 23 May 2012 - 04:18 PM
I noted from my tests that increasing the RAM available to the virtual machine might help on this case.
I suspect that the /xpress compression is less symmetrical, i.e. it is slower in compressing and faster in UNcompressing.
This is the "ideal" kind of compressor for PE builds, taken it to a limit it wouldn't be a problem if to compress the image it would take a few hours, IF the actual UNcompressing would be blazingly fast.
Posted 23 May 2012 - 05:23 PM
I see how you are not much familiar with the concept of "understatement"Unless your idea, how many seconds fit into a hand, differs greatly from mine, it won't be. I think the description 'a truckload of seconds' would be a better description.
Posted 23 May 2012 - 06:39 PM
Posted 23 May 2012 - 06:50 PM
Posted 23 May 2012 - 07:08 PM
Posted 23 May 2012 - 07:12 PM
Posted 23 May 2012 - 08:48 PM
Posted 23 May 2012 - 09:21 PM
Posted 24 May 2012 - 01:30 AM
Posted 24 May 2012 - 11:29 PM
you planning WIM compression in Java ;-) you kidding righ?Compression is not a priority for the moment.
First we handle the reported issues before moving to more features.
0 members, 2 guests, 0 anonymous users