|
Post Number: 1
|
mionica 

Group: Members
Posts: 49
Joined: Apr. 2005
|
 |
Posted on: May 31 2006,14:04 |
|
 |
I don't know how you do duplicates search, but I assume you use the good old (fileSize+fileMD5) mapping technique.
The problem is, if I add a file to an image in which it already exists (in a different folder, or by another name), 'Optimize' won't work. This is surely understandable, since 'Optimize' only 'looks' at the after-last-save added file.
Options to use an associated file list containing (lba, size, md5) would be really nice, since it would allow for real, full-scale optimization. That would be, 'generate'/'import'.
However, in this case, the 'import' thing may lead to really unfortunate mistakes on users' behalf, tough it may be a powerful function for powerful optimization-addicted users (as I am).
There would be another aproach though, however applicable only if the image should reside on an NTFS partition (but, btw, this is really common): use an ADS to store/retrieve this (meta)data, say D:/ISO/myImage:md5sums. This would be a failsafe technique, unless the user would hexedit files in the image by hand (which the average user doesn't); as a protective measure, you could store in the :md5sums stream the MD5 of the image's header (of everything except the data) and only use it if valid.
In practical terms, you could drop somewhere a checkbox saying 'Use image layout file' (though, given my previous post, 'layout' would be a conflicting term), and if the user checked it: image.Open { ... if (!isLayoutFileValid ()) { warnUser (); generateLayoutFile (); } } image.Save { ... generateLayoutFile (); }
Regards, Mircea.
|
 |
|
|
Post Number: 2
|
|
Post Number: 3
|
mionica 

Group: Members
Posts: 49
Joined: Apr. 2005
|
 |
Posted on: Jun. 02 2006,22:23 |
|
 |
Yes, I am sure. Please see the attached case study.
Reagards, Mircea.
Download attachment [ ZIP File ]
Number of downloads: 1263
|
 |
|
|
Post Number: 4
|
xoben 

Group: Super Administrators
Posts: 2200
Joined: Nov. 2004
|
 |
Posted on: Jun. 04 2006,19:49 |
|
 |
This is a normal case. UltraISO will disable 'Optimize' when you save directly. To avoid this limitation, please use 'Save As' or check 'Recompile ISO when saving directly'.
|
 |
|
|
Post Number: 5
|
mionica 

Group: Members
Posts: 49
Joined: Apr. 2005
|
 |
Posted on: Jun. 05 2006,03:16 |
|
 |
Lol. It desn't 
I mean, I tried simply saving (optimize checked) the same file twice to an already existing image and - guess what - optimization did work (same LBA for both added files, just as I hoped it to be).
Anyway, my point was that you could (not should) optimize the optimization procedure further, i.e. make it a great deal faster. And, because I don't believe in criticising without providing a solution, I suggested the ADS approach.
|
 |
|
|
|
|