Jump to content

Mark7ones

Member
  • Posts

    18
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Italy

Posts posted by Mark7ones

  1. 1 hour ago, cdob said:

    VIA USB 3.0 driver xhcdrv.sys calls windows driver wdfldr.sys.
    If you use a historic VIA USB 3.0 driver , it's calling a wdfldr.sys 1.9. This wdfldr.sys is integrated in Windows 7.
    The xhcdrv.sys driver works.

    Dism includes the VIA USB 3.0 driver only, not the WdfCoInstaller.
    The OS default wdfldr.sys is used still.

    If you use a current VIA USB 3.0 driver, then xhcdrv.sys calls a newer wdfldr.sys. This is not included in Windows 7.
    The xhcdrv.sys driver dosn't works. The system is calling for a missing driver. It's a driver version conflict.

    If you install the drivers at windows, then WdfCoInstaller is installed too. There is a current wdfldr.sys installed.
    The xhcdrv.sys driver works.

    If  a user use historic hardware, the historic VIA driver works.
    If a user use more recent hardware, the historic VIA driver dosn't support the hardware and fails.

    Setup:

    1) Working driver:

    [xHC_wdfsect]
    KmdfLibraryVersion = 1.9

    2) Not working driver (downloaded from Gigabyte):

    [xHC_wdfsect]
    KmdfLibraryVersion = 1.11

    The second driver is for Windows 8, also compatible with Windows 7 but not usable during setup.
    Of course I did not know...

  2. 2 hours ago, cdob said:

    This is a historic VIA driver with WdfCoInstaller01009.dll. Yes, Windows 7 supports this WDF 1.9 version out of the box.
    Congratulations, the old drivers works at given hardware.

    I don't know... according to the date in the .inf file, the driver I have integrated is more recent.
    But I still do not understand why the drivers I use for the system. for the same controller. are not good for setup. :unsure:

  3. 2 hours ago, cdob said:

    VIA USB 3.0 is  a WDF driver model.
    The culprit is the Wdf driver version. At 4.50 it was a WdfCoInstaller01011.dll. Which version uses 4.90A?
    Windows 7 supports WDF 1.9 out of the box.
    https://docs.microsoft.com/en-us/windows-hardware/drivers/wdf/kmdf-version-history

    If you like to install from USB, there is no need to set start mode.
    Booting from USB is another case.

    What about post #7? http://reboot.pro/topic/21231-can-w7-be-booted-from-usb30-port/#entry200513
    Be aware, there are CPU requirements.
    A Win 8.1 install ISO may be useful. There is 'dism /apply-image' and 'bcdboot' out ot the box.

    Solved.

    I have slipstreamed the drivers from this pack: https://pcorakel.stackstorage.com/s/TZ47bLjfLs2M9wv.

    These VIA drivers work, the ones I downloaded from Gigabyte no.

  4. 35 minutes ago, Tripredacus said:

    For USB 3.0 there are usually 2 drivers you need to add. For intel, they have a driver for the controller and also for the hub. VIA may be similar (edit as cdob says in that thread). Also, if you are using a stock boot.wim, make sure you are injecting your drivers into Image Index 2. Also make sure to use a Windows 7 SP1 source.

    Right, my VIA controller has two drivers (ViaHub3.inf and xhcdrv.inf) integrated in both boot.wim images (winpe and setup) and install.wim.

    There's something I cannot understand, because even if I load drivers manually it doesn't work...

  5. 3 hours ago, jaclaz said:

    Well, the EXACT hardware you have, the EXACT drivers you added and rhe EXACT  way you have integated it (and the EXACT Registry changes you made) may make a difference, anyway try this:

    http://reboot.pro/topic/21231-can-w7-be-booted-from-usb30-port/

    jaclaz

     

     

    Sorry ... :) I'm sure I've integrated the right drivers (VIA_XHCI_Driver_V4.90A_AP).
    I'm not really a newbie.
    Also, I tried on a different pc with all the USB 3.0 drivers available (Etron, AMD).
    The problem is not the drivers, the problem is Microsoft.
    I'll read that thread, let's see if there's anything interesting...

  6. Did anyone succeed to install Windows 7 from USB 3.0?
    Because I have integrated the drivers in boot.wim and install.wim, but I always get the same error (missing driver).
    I also tried to load them from a folder or to install in UEFI mode ... no way!
    It's quite frustrating...

  7. Sorry for the late...

    It's been years I don't use RT7Lite or vLite, but WinReducer is still full of bugs and DISM is a nightmare.

    So, for the guys, like me, who will never upgrade to W10, this is the tip of the year...

    You're installations have crashed not for this or that component... but simply because you removed the screensavers... lol

    Just a little bug from RT7Lite...

    For those who still use vLite, well I don't have any problem (even if this app is for Vista).

    It's fairly simple, you have less things to remove and it works well when it has to clean WinSxS folder.

    Basically, I removed all the components marked as to keep in the first post and the setup was fine.

    ; vLite preset file
    ;
    ;#Environment:
    ; vLite v1.2
    ; Framework 2.0.50727.5420
    ; Microsoft Windows NT 6.1.7601 Service Pack 1 64-bit
    ;
    ;#Target:
    ; Windows 7 HOMEPREMIUM 64-bit Service Pack 1
    ; Version 6.1 English (United States)
    ;
    [Compatibility]
    
    [CustomHide]
    
    [Components]
    ;# Accessories #
    Accessibility
    Disk Cleanup
    Games-Game Explorer
    Games-Inbox Games
    Games-Premium Inbox Games
    Mobility Center
    Notepad
    Paint
    Snipping Tool
    Speech Support
    System Information
    Welcome Center
    Windows Sidebar and Gadgets
    Wordpad
    ;# Drivers #
    Diva Server
    Modems
    QLogic Fibre Channel Adapter
    Scanners
    TV Tuners-ADS Technologies
    TV Tuners-ASUSTeK Computer Inc.
    TV Tuners-AVerMedia Technologies, Inc.
    TV Tuners-Compro Technology Inc.
    TV Tuners-Conexant Systems, Inc.
    TV Tuners-Creatix
    TV Tuners-Hauppauge
    TV Tuners-KNC ONE GmbH
    TV Tuners-KWorld
    TV Tuners-Lumanate, Inc.
    TV Tuners-Philips Semiconductors
    TV Tuners-Pinnacle Systems
    TV Tuners-TerraTec Electronic GmbH
    TV Tuners-VidzMedia Pte Ltd.
    ;# Hardware Support #
    Floppy Disk Support
    Internet Small Computer System Interface (iSCSI)
    Modem Support
    Smartcards
    ;# Languages #
    Arabic
    Brazillian
    Bulgarian
    Croatian
    Czech
    Danish
    Dutch
    Estonian
    Finnish
    French
    German
    Greek
    Hebrew
    Hungarian
    Italian
    Japanese
    Korean
    Latvian
    Lithuanian
    Norwegian
    Polish
    Portuguese
    Romanian
    Russian
    Serbian
    Simplified Chinese
    Slovak
    Slovenian
    Spanish
    Swedish
    Table Driven Text Input Processor
    Thai
    Traditional Chinese
    Turkish
    Ukrainian
    ;# Multimedia #
    Media Center
    Media Metadata Handler
    Music and Video samples
    Sample Pictures
    Screensavers
    Shell event sounds
    Sound Recorder
    Windows Media Player
    ;# Network #
    Distributed File System (DFS)
    Internet Explorer
    Internet Information Services (IIS)
    Quality of Service (QoS)
    Simple Network Management Protocol (SNMP)
    Simple TCPIP services
    Telnet Client
    Telnet Server
    TFTP Client
    Windows Collaboration
    ;# System #
    Component Cache (winsxs)
    Digital Rights Management (DRM)
    Disk Quota
    IMAPIv2 Burning Support
    Jet Database Engine
    Manual Install (Setup.exe)
    MDAC
    Microsoft Client For NFS
    Microsoft Message Queue (MSMQ)
    Parental Controls
    Performance Counters
    Reliability and Performance Monitor
    Security Center
    Software Quality Management (SQM)
    Subsystem for UNIX-based Applications (SUA)
    Sync Center
    System Restore
    Tablet PC
    Windows Defender
    Windows Easy Transfer
    Windows SAT (Performance Index)
    Zip Folder
    
    [Options]
    DEP (Data Execution Prevention) = Default
    User Account Control (UAC) = Disabled
    AntiSpyware Realtime Protection = Default
    AutoPlay = Enabled
    Paging Executive = Enabled
    Power scheme = High performance
    Power button = Default
    Sleep button = Default
    Control Panel - Classic View = Default
    Show hidden files and folders = No
    Show protected operating system files = No
    Show extensions for known file types = No
    IE Phishing Filter = Default
    IE Phishing Verification Ballon Tips = Default
    
    [Services]
    
    [Protection]
    
    [Drivers]
    
    [Unattended]
    
    [Hotfixes]
    
    [LanguagePacks]

    Ah... just another tip for you... the WinSxS cleanup doesn't break Windows Update as it says... (if you keep Windows Update component naturally).

    ;)

  8. Ok I did some tests, as I did some months ago (this is not the first time I try to use this tool).

    So here are the conclusions:

    -It DOES NOT remove anything in OFFLINE MODE.

    -Use DISM instead (after you have unhided the packages) or use the tool in ONLINE mode.

    -These packages (removed with DISM) break Windows Setup:

    Windows Client Language Pack

    Windows Client Drivers

    Windows Common Drivers

    -Internet Explorer package removal breaks MMC (you can remove optional and troubleshooter packages).

    -Some packages cannot be removed in DISM (error 0x800F0805), but they can be removed with install_wim_tweak in Online Mode.

    ;)

  9. Hi guys,

    Does this tool remove registry keys or packages?

    Because, I still see the removed packges (/c /r) inside the image.

     

    I did the same question 8 months ago... no answer.

    So let's do some spam.

    Does this tool remove registry keys or packages?

    How does it work?

    Does it work?

    No errors and no packages removed.

    No errors and no packages removed.

    No errors and no packages removed.

    No tv and no beer make Homer go crazy.

    No tv and no beer make Homer go crazy.

    No tv and no beer make Homer go crazy.

     

    It works only if quotation marks are used (eg. "SystemRestore").

    Lol...

    I tried to remove System Restore in online mode and it worked, now I try in offline...

     

    Completely useless...

    It removes nothing in offline mode.

    I don't need it.

  10. Anyone knows why this tool says it removed the packages but actually it didn't remove anything?
    I'm trying to remove some stuff from Windows 7 x64 in offline mode; I didn't get any error message, but the image size is identical and if I install the system the packages are still present.

    I also tried the latest version, no way.

  11. Your image has IE10 integrated. I already said on TechNet you need to remove the IEWelcomeMessage object from your answer file or else you will get this error.

     

    See here for reference:

    http://social.technet.microsoft.com/Forums/windows/en-US/f1978c86-3639-489f-b105-5591e59325f7/setup-offlineservicing-error-windows-7-homepremium-sp1-64bit#8edd3366-26e9-4be6-9486-690cf1dfa0d2

    It didn't work even without IE10 integration.

    Making unattended installation with Microsoft is a nightmare.

    There's a problem for every pass...

    For example, I wanted to disable some features or packages and it didn't work.

    Now I know that I have to apply unattend.xml to install.wim to make it works.

    For updates it seems unattend switch (Sysprep) is required...

    What can I say?

    Microsoft f**k off!

  12. As many of you know, Theme Resource Changer is a utility that allows to change Windows Explorer icons (e.g. Navigation buttons),

    without replacing .dll files. Now it seems that sometimes this program fails to work (I still have default icons even after patched Windows with all apps I can find:

    Universal Theme Patcher, UltraUXThemePatcher, UxStyle_Core_Jul13_x64).

    Did anyone find a solution?

  13. I had successfully installed Win7 from usbdrive using Autounattend.xml file and installed Win7 with integrated updates

    following standard procedure.

    If I try to deploy unattended installation of a Windows copy with integrated updates I get this error.

    It seems like Windows cannot handle integrated updates in unattended mode.

    Maybe some istruction in xml file's needed.

    Autounattend.xml

×
×
  • Create New...