Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

14 Good

About cdob

Profile Information

  • OS
    none specified
  • Country

Recent Profile Visitors

2,477 profile views
  1. https://web.archive.org/web/20070104015133/http://support.microsoft.com/kb/833721/ Try hal at boot.ini: /HAL=filename. Extract a hal.dll from installation media, rename it to hal0.dll. Copy to the hard disk. Edit boot.ini: /HAL=hal0.dll There is no CurrentControlSet at offline registry. HKLM\SYSTEM\Select\Current refers to ControlSet???
  2. MBR, GPT and system backup/image

    Do you boot from the SSD still? Are file \bootmr and \boot\bcd stored at the SSD? Yes, boots up from a MBR partitioned SSD works fine, Windows system and data ciles can be at the GPT partitioned HDD.
  3. Bootable Windows Embedded

    Well, there are ISO9660 names and joliet file names. The ISO9600 names are truncated, the joliet ones not. It's a setulr.bin boot, textmode boot uses short uppercase ISO9600 names, gui mode boot uses long joliet names. It's no clear, which file system this pos ready version uses. I wonder a little bit, Windows NT to Windows 10 boots from a ISO9660:1999. Is posready 2009 a exception? Ecma 119 is the working comitee preparing ISO 9660. https://www.ecma-international.org/publications/standards/Ecma-119.htm There is a 3rd Ecma 119 edition (December 2017). The ISO9660:1999 draft is included now. Acutlly I'm surprised to recognice the development after about 20 years. The previous Ecma 119 2nd Edition December 1987 was released as the international standard ISO 9660:1988 ISO 9660:1988 is the current international standard. https://www.iso.org/standard/17505.html Do we get a ISO 9660:2018 based on 3rd Ecma 119 with long file names? 30 years after the current release? mkisofs.exe -iso-level 4 -no-allow-lowercase -D -b bootsect.bin -hide bootsect.bin -hide boot.catalog -no-emul-boot -o pos2009.iso D:\dl\posr2009 PosReady 2009 installation does boot up to gui mode. Not further tested.
  4. How to install Windows 7 from USB 3.0?

    VIA released Windows 7 drivers Version 5.20a. The newer driver package use the old Kmdf again. http://www.station-drivers.com/index.php?option=com_remository&Itemid=352&func=fileinfo&id=2866&lang=en DriverVer=02/03/2016,6.1.7600.5201 [VIA.NTAMD64] ; DisplayName Section DeviceId ; ----------- ------- -------- %XHC.DRVDESC% = xHC_Inst, PCI\VEN_1106&DEV_9202 %XHC.DRVDESC% = xHC_Inst, PCI\VEN_1106&DEV_9201 %XHC.DRVDESC% = xHC_Inst, PCI\VEN_1106&DEV_3432 %XHC.DRVDESC% = xHC_Inst, PCI\VEN_1106&DEV_3483 %XHC.DRVDESC% = xHC_Inst, PCI\VEN_1106&DEV_3515 [xHC_wdfsect] KmdfLibraryVersion = 1.9 Try the VIA 5.20a USB drivers.
  5. How to install Windows 7 from USB 3.0?

    If the wdf driver is not backward compatible, there had been messages in the meantime. It's safe to assume, works in real world, is backward compatible. I added wdf01000.sys and wdfldr.sys at a BartPE plugin. wdf01000.sys is loaded at boot time. And wdf01000.sys chainloads wdfldr.sys. This boot approach is uesd at Windows 7 still. Poor mans choice: Add a 1.11 wdf01000.sys and wdfldr.sys to boot.wim. . Thanks for the hint. https://support.microsoft.com/en-us/help/2685811/kernel-mode-driver-framework-version-1-11-update-for-windows-vista-win This download works currently: User-Mode Driver Framework version 1.11 update for Windows 7 https://www.microsoft.com/en-us/download/details.aspx?id=38421 Did you used a Fresco or VIA USB3.0 controller in the past? @Mark7ones Do you use a USB keyboard and mouse? Do you use a USB 2.0 port for USB keyboard and mouse?
  6. How to install Windows 7 from USB 3.0?

    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.
  7. How to install Windows 7 from USB 3.0?

    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.
  8. How to install Windows 7 from USB 3.0?

    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.
  9. Good, this shows the HD Audio Bus HardwareID. The driver is installed in the meantime. How did you install the driver? What about the "PCI Simple Communication Controller" ? Run two commands (first the first line, next the second line): devcon.exe hwids * > hwids.txt notepad.exe hwids.txt This opens notepad with a HardwareID list. Search for the "PCI Simple Communication Controller". Do you read a HardwareID? Copy and paste the relating text.
  10. Devcon.exe is a command line tool. https://technet.microsoft.com/en-us/library/bb490890.aspx Did you run cmd.exe first and change the directory?
  11. Where to find DevCon.exe https://blogs.technet.microsoft.com/deploymentguys/2009/12/16/where-to-find-devcon-exe/ https://superuser.com/questions/1002950/quick-method-to-install-devcon-exe/1003435 https://web.archive.org/web/20150219111411/http://support.microsoft.com/kb/311272? https://web.archive.org/web/20150219111411/http://download.microsoft.com/download/1/1/f/11f7dd10-272d-4cd2-896f-9ce67f3e0240/devcon.exe Does Q311272 devcon.exe (the download is a archive, expand it first and use the i386\devcon.exe) devcon.exe hwids *cc_0403* list any device ?
  12. The realtek 0001-WDM_R274.zip expanded. There is a file MSHDQFE\Win2K_XP\us\kb888111w2ksp4.exe I wonder: does kb888111w2ksp4.exe support 2000 Advanced Server SP4? Did you run kb888111w2ksp4.exe? kb888111w2ksp4.exe expanded 0001-WDM_R274\WDM_R274\MSHDQFE\Win2K_XP\us>kb888111w2ksp4.exe /x:. There is a file WDM_R274\MSHDQFE\Win2K_XP\us\commonfiles\hdaudbus.inf %HDAudio.DeviceDesc% = HDAudio_Device, PCI\CC_0403 Does 'devcon hwids *cc_0403' list the 'PCI Device' ? What does list 'devcon driverfiles *cc_0403' ? Does device manager list a system device '* UAA Bus Driver for High Definition Audio' ? If not, then select the 'PCI Device' update drivers and choose the MSHDQFE\Win2K_XP\us\commonfiles directory. Are drivers installed? Then reboot. Do you get new hardware 'Audio Device on High Definition Audio Bus'? WDM_R274\WDM\HDXRT.INF "Realtek High Definition Audio" = IntcAzAudModel, HDAUDIO\FUNC_01&VEN_10EC&DEV_0888 This should match the HD Audio ALC 888 chipset. Does 'devcon hwids *HDAUDIO*' list a new device? Which HardwareId does devcon list? Does match 'HDAUDIO\FUNC_01&VEN_10EC&DEV_0888*' ? Try the WDM_R274\WDM directory anyway. My crystal ball asks for a break
  13. Sorry, then try devcon.exe. Should work at 2000. https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon https://support.microsoft.com/en-us/help/311272/the-devcon-command-line-utility-functions-as-an-alternative-to-device https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon-hwids https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon-driverfiles
  14. Easy over-installation ?

    Well, what about storage space? Most WinSxS files are hard linked by default. However there are double files at the hard disk now. The WinSxS files are not hard linked anymore. They require more space at the hard disk now. https://blogs.msdn.microsoft.com/e7/2008/11/19/disk-space/ The files can be hard linked again. http://reboot.pro/topic/19643-winsxs-hardlinked-files/ To select the double WinSxS files: finddupe.exe -bat hl.txt -hardlink f:\ findstr.exe /I "winsxs" hl.txt > hl.cmd
  15. Windows 7 x64 Intel USB 3.0 slipstreaming?

    Get WAIK Either full WAIK https://www.microsoft.com/en-us/download/details.aspx?id=5753 Or small WAIK tools and Dism for Windows 7 https://1drv.ms/u/s!AnNmc1rU9VMAhGfaGtiigOc0BUlV Install \Waik_3\x86\wimmount.inf at a XP x86 machine, mouse right button install. Use dism.exe to mount, add drivers and unmount the USB 3.0 drivers. Target: Boot.wim index=2. And install.wim, used index https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-and-remove-drivers-to-an-offline-windows-image https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-7/dd744355(v=ws.10)