Jump to content

tistou77

Member
 View Profile  See their activity

  • Posts

    385

  • Joined

  • Last visited

  • Donations

    0.00 USD 

  • Country

    France

 Content Type 

Posts posted by tistou77

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted

    Is there another topic named "Safe WinSxS Removal With Vlite and RT Lite". Posters complains about same problem with Windows 7 SP1 RTM. But, look at these :

    """http://www.autoitscr...-tools/gimagex/

    download it from there

    choose the apply tab choose the install.wim that already lited with rt lite

    and choose empty dir for destination

    after it done choose capture tab

    use maximum compressing and ultimate edition and fill up it with name """

    you're tested? it's good?

    0

    [Guide] Win7/Server SP1 - Removal With Vlite and RT Lite

    in vLite

    Posted · Edited by bapt

    if I understand

    should be used rt7lite, customize 7 as we want, once the process is complete,

    use Gimagex with the new install.wim done by rt7lite, right?

    thanks you very much ;)

    EDIT: in the Capture tab, I put in destination [7lited win7]\sources\install2.wim and deleted install.wim (original) and replaced by install2.wim is good?

    but once the process install.wim mounted in the empty folder, is not unmounted after... :huh:

    0

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted · Edited by bapt

    I dont understand what you are saying. I got a 6.3GB install with x64 Ultimate and removing languages with vlite. I was asking what his session was because you have to select something as far as I know to get vlite to do something. When I tried a selecting a few things to remove I got an error when installing saying not all components could be installed.

    I was talking about the OS de dead0 ;)

    WAIK 2 is for 7 I thought. 1.1 is for vista. 1.1 was released in 2008, 2 was released in 2009 and 3 this month. WAIK 2 should have the wimmount.sys, that is what I have.

    bapt

    Sorry to say that you are wrong and xpJohnson is right instead. Quoted from Wikipedia:

    1. WAIK 1.0—Released with Vista

    2. WAIK 1.1—v6.0.6001.18000—Released with Vista SP1 and Windows Server 2008

    Filename: 6001.18000.080118-1840-kb3aikl_en.iso

    Version: v936330AIK – Released: 4/9/2008–1375.9 MB

    3. WAIK 2.0 - v6.1.7000.0—Released with Windows 7

    Filename: KB3AIK_en.ISO

    4. WAIK 2.0 RC: 6.1.7100.0—Released with Windows Vista

    Filename: KB3AIK_en.ISO

    5. Win7 WAIK / WAIK 3.0: 6.1.7600.16385 Includes DISM.exe, same version number

    Filename: KB3AIK_en.ISO

    Version: v3.0—Released: 8/6/2009—1706.6 MB

    Windows AIK version 3.0 is the exact same as 2.0. The hash values of the ISO images are exactly the same.

    ok I had seen this for the WAIK 2

    WAIK 2 => 6001.18000.080118-1840-kb3aikl_en.iso (4/9/2008)

    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=94bb6e34-d890-4932-81a5-5b50c657de08

    0

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted · Edited by bapt

    Update: I got it work using dead0 procedure. I only removed the languages so far. For some reason I was getting errors that a component couldn't be installed and I was being very conservative on my vlite removal.

    Dead0, have you tried installing the RegTweak for package removal and remove any packages yet? Also, your procedure of switching back and for the wimfltr and wimmount doesn't make sense. Doesn't the win7 version that we got the wimmount from used with imagex not the wimfltr. I have both in the driver folder. You are just switching the vlite version when you swap them right?

    7 x86 of dead0 take 5GB of disk space, it does not remove many component

    unless it has installed software or other

    0

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted · Edited by bapt

    WAIK 2 is for 7 I thought. 1.1 is for vista. 1.1 was released in 2008, 2 was released in 2009 and 3 this month. WAIK 2 should have the wimmount.sys, that is what I have.

    WAIK 1.1 => WAIK for Windows Vista

    WAIK 2 => WAIK for Windows Vista SP1 et Windows Server 2008

    WAIK3 => WAIK for Windows 7

    not wimmount.sys on WAIK 2 ;)

    0

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted · Edited by bapt

    I tested with Gimagex, and it works not

    after using vLite, there are corrupt files

    when I used Gimagex is the wimfltr.sys (windows\system32\drivers) of Vista I think

    I used Vlite "normal", with wimgapi and wimfltr.sys files (6.0 6001 18000) for Vista

    is not good?

    EDIT: OS of the PC where I'm testing is a 7 x64 (sp1 integrated)

    0

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted

    I've tested with a "take ownership" that works, Monkie53'software (to change the date) does not work for me (error message)

    I used another software, changed the 3 dates "winsxs" folder (and contents) on 13/07/2009 and that's OK with vLite, no problem :thumbup

    I also change the date of the "windows" folder (not contents) on 14/07/2009

    is what to do or not?

    0

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted

    did you get to run the takeown successfully on the winsxs folder?? this maybe the issue if not even with a program changing the folder date ( just guessing here )

    I removed the protection on any files contained in winsxs (and also winsxs) with software to modify the attribute, and I changed the date of winsxs and all content

    I used vLite, reboot and mounted install.wim with gimagex

    winsxs is the date of 13/07/2009 (the 3 dates) and all content winsxs also and I always corrupt files

    0

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted · Edited by bapt

    I tested other software to change the date and time

    I set 13/07/2009 and 20h20mn00s for winsxs and all contents of winsxs

    Some folders in winsxs are to 14/07/2009 (I know not why)

    save the change, and unmount install.wim

    reboot and mount install.wim with gimagex and the .dll, .exe files are still corrupted ...

    I'm testing on a x64...

    after, why changing the date of winsxs, Vlite that will be compatible?

    I tested with Windows 7 and sp1 integrated, "date modified, etc...." are not changed and it works very well

    and the "creation date" is the same (creation date: 14/07/2009) for 7 sp1 MSDN and 7 sp0 and sp1 integrated

    thank you to explain ;)

    EDIT: after I tested on a install.wim where I customize some dll (imageres, etc. ...)

    but no problem with windows 7 and sp1 integrated

    0

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted · Edited by bapt

    Strange : any of the images in kit which i mount with gimagex works fine with take ownership, but try the long way : Folder Properties Security Advanced Owner Edit and select your user from list , confirm the message, etc.

    for winsxs, I can do it, but I receive an error message for all files/folder located in winsxs (it's good and not?)

    and "Change_Folder_Date_Time" how to do, then?

    I can not change the date?

    thanks ;)

    0

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted

    I can not change the date and time ....

    I mounted install.wim, use the "Take Ownership" in the winsxs folder (I did not even have time to see the Windows command prompt :blink: ) and it not work, the file is still locked (delete and rename)

    but I can not change the date with "Change_Folder_Date_Time"

    capturefdk.png

    what do I forget?

    thanks ;)

    0

    [SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

    in vLite

    Posted

    Yes I tested the x86 version and yes issues with the winload.exe is corrupted when using Vlite and x86 MSDN SP1 , do the same thing to the x86 as I stated above in changing date/time for all

    ( Date Created, Date Modified, and Date Accessed ) will fix the issues, it did for me.

    I have fixed my ISO files, they now werk fine with Vlite and are the same files except the date changes were changed to July 13 2009.

    Mounting the install.wim is easy with GimageX, take ownership of the winsxs folder is really a hard issue if you do not know how the "easy" way..

    here is a simple ( source code found in google ) change folder date time I used

    source code included - .exe in main folder to use ( needs Visual Basic 6 application to use the source code, for those that needs to know this :) )

    Change_Folder_Date_Time_Code.7z

    here is my right click take own reg tweak I have been using for over a yr now..

    NOTE: You have to take ownership of the winsxs folder before you can change the date on this folder as You do not have *access rights to modify it*

    NOTE 2: running take ownership of the winsxs folder when mounted will take some time ( 10 ~15 minutes or more *depends on Your PC speed* ) so be patient with this step


    Windows Registry Editor Version 5.00

    ;Add "Take Ownership" to context menu ( This one will do many folders deep unlike the other one )
    [HKEY_CLASSES_ROOT\*\shell\takeownership]
    @="Take Ownership"
    "HasLUAShield"=""
    "NoWorkingDirectory"=""

    [HKEY_CLASSES_ROOT\*\shell\takeownership\command]
    @="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
    "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

    [HKEY_CLASSES_ROOT\exefile\shell\takeownership]
    @="Take Ownership"
    "HasLUAShield"=""
    "NoWorkingDirectory"=""

    [HKEY_CLASSES_ROOT\exefile\shell\takeownership\command]
    @="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
    "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

    [HKEY_CLASSES_ROOT\dllfile\shell\takeownership]
    @="Take Ownership"
    "HasLUAShield"=""
    "NoWorkingDirectory"=""

    [HKEY_CLASSES_ROOT\dllfile\shell\takeownership\command]
    @="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
    "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

    [HKEY_CLASSES_ROOT\Directory\shell\takeownership]
    @="Take Ownership"
    "HasLUAShield"=""
    "NoWorkingDirectory"=""

    [HKEY_CLASSES_ROOT\Directory\shell\takeownership\command]
    @="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"
    "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"

    [HKEY_CLASSES_ROOT\Directory\shell\runas\command]
    @="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"
    "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"

    hello monkie53

    thank you for your great work :thumbup

    if I understand it, take possession on the "windows" and "winsxs" folder (when mounted install.wim with Gimagex example), and apply your patch, right?

    thank you very much ;)

    0
×
×
  • Create New...