Jump to content

Thiersee

Ultimate Sponsor
  • Posts

    2,075
  • Joined

  • Last visited

  • Days Won

    65

Posts posted by Thiersee

  1. .....

    Not compatible with SP1 (7601): 'G:\Updates\McRip Windows 7 x64\Additional\Not integratable to Offline image\Windows6.1-KB2533552-x64.msu'

    Doesn't seem to be a valid update file: 'G:\Updates\McRip Windows 7 x64\Additional\Integrate to installation media\KB2649909-v2\Windows6.1-KB2649909-v2-x64.cab'

    ............

    Not compatible with SP1 (7601): 'G:\Updates\McRip Windows 7 x64\Additional\BallotScreen\Windows6.1-KB976002-x64.msu'

    are these to be integrated Differently!

    KB2533552 will be downloaded from win-update, no matter if you installed it or not.

    KB976002 is the browser-choice, it will be also dowdnloaded from win-update.

  2. I don't see the issue, everything worked how it should. What was you expecting?

    This is, what I wanted to say with my post:

    acycqex19j3w.jpg

    mrhy983tmhc.jpg

    Do you see the difference ;) ?

    v52 is working for my perfect: no problems, no issues, nothing!

    All features I need are working.

    P.S.: can you mark the topic as "solved"? Thanks!

  3. When I removed the code that verified that installer matched the posted MD5, I also removed the ability to reuse a previously downloaded installer. I didn't and don't have the time, right now, to properly fix it.

    As to the Shockwave installers, other than file size, I really don't know. If you go the the Adobe Shockwave site and download it, it will automatically give you the slim version.

    That's the best that I can do for now.

    ~jonnyboy

    BTW: Very few people even use this anymore, or ever really did.

    It's OK, thank you for your answer.

    Regards, Thiersee

  4. Hi Jonnyboy,

    just one issue in v1.02.11 I "discovered" and tested yesterday:

    everytime I start to create an installer, the tool doesn't find the FF-Installer and downloads it every time,

    even if the FF have been downloaded during the "create" before and it is still present in the "temp/files"-folder.

    BTW: I use FF 14.0.1 , german version.

    One question: what is the difference between Shockwave "slim" and "full"?

    Regards, Thiersee

  5. Hi,

    Virtual PC has moved to Silent Install+SFX as "not needed" (together with two optional updates for VPC), but it has been integrated (and the two updates too) only because XP-Mode was still present in the prerequisite list; have a look to the first screenshot: the status line shows "integrating VirtualPC".

  6. I tried an integration, after I have read the post from McRip, but I forgot to cancel the XP-Mode-File from the update-list;

    the result was that WinToolkit integrated VirtualPC and the two updates, even if WinToolkit moved this three items to the Silents+SFX (see screenshots); please, have a look to the status-line.

    Run integration

    pojb3s67shc2.jpg

    Updates before integration

    as9wjzxwxfa1.jpg

    Updates after integration

    pglrid6e56.jpg

    Silent Installs + SFX before integration

    bjq2be9d672n.jpg

    Silent Installs + SFX after integration

    qwkv6brgkqq1.jpg

    And what I want to say with allt his stuff?

    XP-Mode must in the exceptions-list too.

    Regards, Thiersee

    P.S.: if you mean, this post is better in a new thread, please feel free to move it ;)

  7. Hi,

    sorry for posting in this thread, but I found Test2 here...

    This Test2 does NOT integrate the VirtualPC (XP-Mode); instead it moves the newest VirtualPC Windows6.1-KB958559-x64-RefreshPkg.msu to the Silents+SFX and marks it there as N/A

    (about this KB see my thread, where I informed you about).

    Version.50 and Test1 DOES NOT have this issue!

    BTW, MS published this "new" VirtualPC to get it installed on system with SP1 and it contains a patch (KB977206) necessary for processors, that not support virtualization;

    if you have the possibility to read or translate from German, here an info.

    Regards, Thiersee

  8. Just another "Little Thing":

    If I want to change the Temp- and Mount-Path, I can't edit the surface with the current path: I have only a possibility with the "browse"-button to choose a path, that already exists.

    I.e. I must create the path first, even if WinToolkit can create a path (OK, a default-path).

    It would be nice to edit the path field.

    Regards, Thiersee

×
×
  • Create New...