Jump to content

Francesco

Member
  • Posts

    414
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Italy

Posts posted by Francesco

  1. Any hope for a nice smooth progress bar in the install dialog? It requires just a timer that slowly increases the percentbar position to reach the current percentage (the update frequency in milliseconds should be calculated from the difference between the current percentbar position and the real position it should have).

  2. Please if you find bugs on vista try to report them on MS forums: we risk that those bugs will end up in the final version. As everybody can realize the current builds are still full of pesky bugs everywhere and unless they're security bugs it's very hard that MS will fix them after vista release.

  3. Ok, so let me see if I got the gist of this thread correctly..... (so far, it's been a bit vague)

    PerfectDisk is crapola.....Diskkeeper is written by the same company that wrote Windows Defrag (a fact, not rumor) and they support the Church of Scientology. How am I doing so far?

    Well, I'm so glad to know all that, but I quit using Defrag a long time ago to keep my HD in order.

    All the defrag programs 'wet the bed' as far as this tech is concerned. The last decent Defrag was in Windows ME. I still share that will all my Win-98 customers.

    I found that if I just do a Ghost Restore after I've done a Ghost backup, all my files are rewritten in perfect order, with no spaces and NO fragmentation. And it only takes five minutes, not the long times that defrag programs are noted for. When seen from MS XP's Defrag Analysis, right after a Restore, it looks like this:

    mydrive.jpg

    Now, if any of yous have a Defrag program that can do any better'n that.....I'll buy it. :thumbup:lol::lol::lol:

    Cheers!

    Andromeda43 :thumbup

    Yes there is and it's SpeedDisk from the Norton Systemworks. However it's quite old (they never updated it since 2001).

  4. I think that's because the newbies don't see the guide in the homepage. Usually people look at the navigation bar or check out the downloads section on the website and can't see the guide because it's in the homepage (and you have to scroll down to see it).

  5. you should read carefully...

    "other programs" means not "windows hotfixes"

    "other programs" means "all the wide variety of programs you can find anywhere"

    don't be so stubborn... stupid me, you may have interest in MS ?

    But In my first post I was talking about system files. I don't care about extra applications at all: when you integrate XPize in the DVD it surely doesn't patch 3rd party applications.

    1/ that's only a detail, but CRC/CRC32 is an unreliable algo ; and MD4/MD5 are known to create collisions also. For safety, another algo needs to be used (SHA for example was never broken AFAIK).

    2/ all you say here is right... You presume "there aren't localized resources images". That's true. But adding an image as a resource in an executable is not enough to display this image. There is also (localized or not) "code" (mainly DIALOG(EX) or UIFILE resources) that have references to those images (by their ID).

    One can easily change this reference, and XPize-like shell packs are blind to this (they update a resource ID that is no more used by the binary file).

    This is not a "possible (theorical) bug case", since some shell packs does this sort of modifications. Another example : i were talking about sysdm.cpl 'coz there's here on msfn a thread on how to have a "vista-like" one : if you use it, xpize is no more able to reload sysdm.cpl, with or without your resources integrity checks (you will get the dialog layout of the "vistaized" one, with images from both xpize and vista-ized one, and it looks weird, defeating the "reloader" purpose)

    The way XPize replace the resources is already flawed: I just made some easy suggestions about implementing my idea surely there are plenty others but since XPero is just using a nsis setup using reshacker.exe and FC.exe seemed the simplest idea to me.

    At least extracting the resources and comparing them would make XPize safer (less system files replacements).

  6. -> adding a tag doesn't mean other programs are able to see it, thus they can update resources leaving the tag intact, letting "xpize_modded_with_your_idea" think its xpized when it is not (same issue if using the fileversion)

    As long as I know windows the hotfixes replace the entire files.

    -> comparing the resources themselves can be done only by predefined IDs, since xpize updates only the graphics and not the dialogs codes (for example), one can modify a dialog to make it use another resource ID, letting xpize updates a blind resource. This issue is present in the actual xpize, and in some other shell packs, your idea will just slow things without solving that (thus my "will also work"). (if you don't understand this point, just look around for sysdm.cpl customisations, for run box customisations and for logonui.exe customisation -- but all dialog boxes are concerned)

    Yes I already know that XPize already updates the resources without knowing if the file is the same it is meant to be patched I just made my suggestion considering that such a practice won't change. However XPero could save correct CRCs of the resources and compare then when they're extracted (there aren't localized resources images as long as I know). So XPize can extract them, compare the extracted resource image files' crc with one stored internaly in the application and be sure the resource it's going to patch is correct. That is probably the best workaround because with CRCs check there won't be messes if the dll is different (another version).

  7. stop brainstorming and implement your idea in a real program of your choice (or find someone to do it).

    Where's the problem XPize can just extract the resources with reshacker and it can use FC.exe windows utility to compare them. There's no need of a magician to do such a simple task.

    you should be aware that i've already wrote a bug report for it :}

    But this is not a bug it's a feature suggestion

    :lol::no:

    it was referring to "Log slipstreamed resources, slipstream the log, read back this log after windows setup."

    It does some other thing too, like actually slipstreaming the resources or extracting them back (it's in fact @T-13 before any hotfix can be applied, not after setup).

    i'm still debugging the "backup before hack" and "reloader" parts.

    ++

    Ehm what application are you talking about? XPize? Isn't that programmed only by XPero?

  8. Francesco, that's great news, ah well it's easiest to blame nLite so we do it ;)

    I'm pretty sure it has to do with something nLite changes: surely it's not an nLite fault it's a MS bug however I think there's something nlite does that triggers that bug.

    I have clean XP installs that never presented that problem and I also have nLited XP install and all of them had that problem so I suppose that it is a problem caused by an integrated update.

    The important thing for now however is that we have the patch.

  9. i have got the hotfix would it be agaisnt the rules to share it?

    if not where could i upload it to

    i have got the hotfix would it be agaisnt the rules to share it?

    if not where could i upload it to

    You can upload it on RARhost or RapidShare however the first one is better.

    it also solved the problem for me with the svchost.exe CPU Usage Poll at 100% the detation went alot faster, and on here the sfc is disabled.

    also the fix will be included in sp3 and happrently acording to the guy at ms tech support sp3 is due ou late jan 07??

    It should come out 2-3 months after vista however it will just be a collection of hotfixes like the old service packs.

  10. Like you said in the other thread, adding "tags" inside the files(*2), or extracting-then-compare resources will also work, but checking each binary is slower than reading a single log.

    It is slower but it's more accurate. If it's just a version string then the check will be pretty fast: XPize doesn't patch a big number of files.

    (*2): this should be considered as a bad technique, since the updated resources themselves can act like "tags"

    But it's the most accurate way to do that job because XPize can know if each file has been patched.

    (*1): i have a working batch that does it flawlessly, sorry for this egocentrism

    That does what? altering the version strings of the files?

  11. I'm almost sure that the patch I posted in the first post is the only way to fix this mess.

    There is a bad and a good news: the good news is that I think the problem is caused only by the buggy MSI.dll, the bad is that it could be that a wrong version of MSI.dll integrated by nLite. I'll check this out and report later.

  12. I always have SFC disabled, and have never experienced the 100% cpu bug. I've also never used automatic updates, but I do use Microsoft Update.

    Is your OS nlited?

    BTW if you have a very fast cpu the 100% cpu usage goes away almost immediately: you should try opening the task manager and visiting MS update to see how much cpu it uses during the check to be sure that you don't have that problem..

  13. Yes, but XPize is an install and forget app. You dont have to think about uninstalling it after 2 months. If you dont like it, you will realize in a couple of days maximum, right? Anyway, this is fixed for next one.

    It may even be an install and forget app however since people are forced to uninstall it before installing new versions don't patch some files anymore it's an enormous security risk if old versions of the files are restored: it makes the system vulnerable. Also it breaks applications like WMP that do an heavy check on all the files versions.

    You shouldn't backup the files: you should backup the replaced resources and put them back if the files is still the same you patched when you uninstall xpize. That way you save hd space and also you avoid all security risks because the system files dll/exe code remains the same and only resources are changed.

    You're wrong. New XPize versions can be installed on top of old ones. No need to uninstall.

    But you told me in another post that if a newer XPize version doesn't patch a certain system file anymore it won't restore it! If I want the file restored I have to uninstall the old xpize and then install the newer version.

    For example I install an older XPize that patches a file that doesn't like being patched and starts giving problems: in the new xpize version you may fix that problem by having xpize not patching that file anymore.

    But users using an older version of XPize if they install the newer version over the previous one will still leave that file patched and the problem will persist: the ony solution is uninstall the old version and install the newer one.

  14. Yes, but XPize is an install and forget app. You dont have to think about uninstalling it after 2 months. If you dont like it, you will realize in a couple of days maximum, right? Anyway, this is fixed for next one.

    It may even be an install and forget app however since people are forced to uninstall it before installing new versions don't patch some files anymore it's an enormous security risk if old versions of the files are restored: it makes the system vulnerable. Also it breaks applications like WMP that do an heavy check on all the files versions.

    You shouldn't backup the files: you should backup the replaced resources and put them back if the files is still the same you patched when you uninstall xpize. That way you save hd space and also you avoid all security risks because the system files dll/exe code remains the same and only resources are changed.

  15. Actually XPize ONLY saves and patches the resources so even when uninstalled you would still keep the newest files you have on your systems i.e. any hotfixes you have installed before uninstalling xpize will still be installed.

    What's the "C:\windows\xpize\Backup" dir used for then? Aren't those files restored?

    You're right. That's a XPize flaw that I've just fixed. XPize Reloader will backup newest files, so when uninstalling you will have latest version of files restored. Coming in next version ;)

    What happens to those who don't use xpize reloader when they uninstall xpize? Will they still get old versions of the files restored?

  16. 1 easy option... is a commandlike option like...

    xpize /fix filename.dl

    I think that a better idea would be to skip all the files that XPize usually integrates in the cd. It won't be the same thing (because it will require XPize to be installed before the hotfixes) but at least it it will make things faster.

  17. I dont see how it can be done. Anyway, this is not an intersting feature for the average user IMO, sorry :)

    Un, dos, tres :

    Log slipstreamed resources, slipstream the log, read back this log after windows setup.

    :angel

    ++

    That isn't a good idea because there are some MCE hotfixes that should be applied after windows installation.

    XPize should be run after the hotfixes and as you can imagine at that point the log won't be accurate anymore.

    The best idea is to extract the resources and compare them or let XPize change the file version structure adding it's own signature (so it doesn't need to extract all the resources but just the signature to find out if the file is patched or not.

  18. Ive seen the 100% usage on machines with sfc enabled both xp and 2000, shouldnt there be a poll option for that ?

    Yes there should be a poll for that but I didn't create the poll well so I can't edit it anymore :( . Let's hope that the forums admin will re-enable poll editing.

    I had the same issue but I remove almost all and I got there just to check something, never expected it to work. I think if you have Autoupdate service (which gets reinstalled by the WU site anyway) and you removed BITS service or something it needs you may experience that problem.

    I didn't remove any component on the installs where I had those problems. There's something wrong with MU and I got problems with it on all the unattended PCs.

    **** there must be a way to find out what creates this problem. There's a patch for that so it's a MS bug but there should surely be something triggering all this mess.

    Lets first start with a question did you use Windows Update compatibility option?

    I didn't need it I didn't remove any component or service.

×
×
  • Create New...