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. 



cdob

Member
  • Content count

    1,118
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

13 Good

About cdob

Profile Information

  • OS
    none specified
  • Country

Recent Profile Visitors

2,176 profile views
  1. Ntoskrnl and Ntkrnpa are fixed names (Ntldr reads fixed names). Depending on the hardware this are renamed files. Can you read the orignial names from a backup? The original ntoskrnl.exe () won't work at a current multiprocessor machine : black screen At a ACPI multiprocessor machine ntkrnlmp.exe is remaned to ntoskrnl.exe. And ntkrpamp.exe is remaned to ntkrnlpa.exe. (used at boot.ini /PAE) Hints: http://support.microsoft.com/kb/299340 http://support.microsoft.com/kb/309283 Curious: ntkrnlmp.exe 5.1.2600.7392 is one month old
  2. Installing W10 from 16 GB USB.

    Yes, you contributed to both articles. And no doubt you can add drivers at dism, I understand, you like to use 3x NVMe Samsung SSD 960 EVO at RAID mode. The registry keys are a documentation, how does dism integrate the *.inf files? Are there any clitches at first glance? A possbile driver stack is included, but I doub't some details. However I've no hardware to test. The suggestion was to run regedit.exe or reg.exe after dism run. And edit the file system32\config\system. Integrating working drivers would be nice. Did you finish installation with the 8 GB USB? Do you use a running Windows 10 already? Run device manager, change view per connection, search the raid disk, go some steps up to AMD-RAID Bottom View details, select HardwareID. Or boot a PE, run regedit.exe, search for data "PCI\CC_01". Goto HardwareID. Or run devcon to list mass storage controllers devcon.exe hwids *cc_01* https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon https://networchestration.wordpress.com/2016/07/11/how-to-obtain-device-console-utility-devcon-exe-without-downloading-and-installing-the-entire-windows-driver-kit-100-working-method/ What about boot the 8 GB USB, read drivers from the 8 GB USB and apply windows files from the 16 GB USB? Or install to a SATA WD disk. Build a NVMe RAID at UEFI. Install RAID drivers. Clone windows to the NVMe RAID. Another approach: X399 NVMe RAID is a new feature, get some time to rest. Wait half a year, try current BIOS, drivers, 960 firmware updates again.
  3. Installing W10 from 16 GB USB.

    Let's see. md c:\mount dism /Mount-Wim /WimFile:U:\sources\boot.wim /index:2 /MountDir=c:\mount dism /image=c:\mount /add-driver:C:\driver\WTx64 /recurse dism /UnMount-Wim /MountDir=c:\mount /commit Do you use SATA RAID or NVMe RAID? Wich HardwareID matches your mass storage controller? rcbottom.sys is a storport.sys and wdfldr.sys child driver. The "PCI\CC_010802" may conflict with stornvme.sys. https://msdn.microsoft.com/en-us/library/windows/desktop/mt718131.aspx Which driver get's the higher PNP priority, the in-box stornvme or the third party rcbottom? In doubt I would delete DriverDatabase\DeviceIds\PCI\CC_010802\stornvme.inf. The demand start Services\rccfg\Start=3 is curious too. I would try the default Start=3 first. And if it fails, Start=2, Start=1, Start=0 next. X399 NVMe RAID seem sot be a new feature. https://community.amd.com/community/gaming/blog/2017/10/02/now-available-free-nvme-raid-upgrade-for-amd-x399-chipset http://support.amd.com/en-us/kb-articles/Pages/NVMe-RAID-Support-for-the-AMD-Ryzen-Threadripper-platform.aspx http://forum.asrock.com/forum_posts.asp?TID=6453&PN=4&title=taichi-x399-cannot-install-windows-in-raid-mode http://forum.asrock.com/forum_posts.asp?TID=6751&PN=2&title=x399hd-not-showing-in-uefi-boot-list-in-raid-mode
  4. Installing W10 from 16 GB USB.

    It's a rather curious behaviour. One driver difference: Asrock AMD RAID driver ver:9.00.00.088 rcbottom.inf uses WdfCoInstaller01011.dll. Injecting this driver to boot.wim is difficult. If I recall correctly, Windows 7 dism didn't set service load because of a WdfCoInstaller. No Idea about 1709 dism.exe. The AMD 9.1.0.18 rcbottom.inf does not use WdfCoInstaller. Injecting this driver to boot.wim should be simpler. https://www2.ati.com/drivers/raid-windows-driver-9_01_00_018.zip
  5. Installing W10 from 16 GB USB.

    This is a nice miracle. Can you clarify? Do you use a X399 Taichi? X399 Taichi Did you update the BIOS (UEFI firmware)? Which RAID driver version do you use? Do you use BIOS or UEFI mode at the 8 GB USB stick? Do you use BIOS or UEFI mode at the 16 GB USB stick? Which Windows version do you use? 1709 supports several partitions at a removable device. The removable bit is not importand anymore. Which max file size do you use? Does it fit at FAT32? As far as I know, Rufus use a special MBR code. Or a special Efi NTFS driver. May this interfere with RAID? I don't know. Just to crosscheck: what happens if you build the USB stick with diskpart and xcopy?
  6. Drive Converion Question

    In addition, there is integrated tool nowadays: MBR2GPT https://docs.microsoft.com/en-gb/windows/deployment/mbr-to-gpt
  7. BSOD x00000007b during install

    Can you clarify: Which mass storage was included initially? Which mass storage did you add? Does another OS list this disk? Which disks list the BIOS? Can change the boot order? Can you boot a Windows 10 DVD or relating USB key? Press shift F10, diskpart.exe, list disk Wich disks are listed? PCI\VEN_8086&DEV_22A3&CC_0106 is SATA AHCI mode, not legacy mode.
  8. X64\Sources and X86\Sources: The Windows 8.1 and Windows 10 setup.exe supports this. The Windows 7 <DVD:>\setup.exe dosn't support X64\Sources and X86\Sources, the path x86 or x64 is unkown. The file install.wim is not found. However windows 7 setup.exe supports .\Sources. A relative path is supported. Run <DVD:>\x86\sources\setup.exe or <DVD:>\x64\sources\setup.exe at start up. Hence at boot.wim. What about adding a text file setup.vbs? How to read topic 26064: Dual Boot BIOS/UEFI Windows 7 AIO https://web.archive.org/web/20160505013612/http://www.911cd.net:80/forums/index.php?showforum=3
  9. BSOD x00000007b during install

    It's a eMMC disk. There is nothing connected to the SATA controller. SATA controller drivers dosn't matter. Include eMMC drivers. However: Windows 7 does not include any driver support for eMMC devices https://www.intel.co.uk/content/www/uk/en/support/articles/000006602/mini-pcs.html It's a Braswell CPU N3050. https://www.acer.com/ac/en/IL/content/model/NX.MYGET.009 The Embedded Drivers for Windows 7 may work or fail. The N2930 is supported, but not the N3050. https://downloadcenter.intel.com/download/24548/ Which hardware ID matches your eMMC Host Controller? Does matches PCI\VEN_8086&DEV_2294? Compare iaiosd.inf http://www.msfn.org/board/topic/175652-desperate-to-installuse-windows-7-help/
  10. Which USB disk do you use? Can you name the manufactuer and model? Do you have a Windows 7 arround? Do you get a 'Bytes Per Physical Sector'? fsutil fsinfo ntfsinfo U: https://support.microsoft.com/en-us/help/982018/ Can you disassemble the USB case? And connect the hard disk internally? Do you get the same 'Bytes Per Physical Sector'? The next step is a 20 TB USB disk. How does the USB firmware translate this disk? Does Windows understand this? To be done in future, let's wait.
  11. Does the USB bridge offers 512 byte or 4 k sectors? Which MBR partition data are available out of the box? Backup the first several sectors. In case of 512 byte sectors: Can you try a 3TB floppy? Hence no MBR (sorry for of topic), a partition sector only. usbstor.sys reads this. XP should work with the 3TB USB drive. No idea about 2000. Can you use a live linux DVD? https://wiki.archlinux.org/index.php/NTFS-3G mkfs.ntfs --force -Q -L "3TB_floppy" /dev/sdX
  12. There was a Memory Remap Feature at previous Motherboard / BIOS. Unfortunately not at current UEFI versions. https://forum-en.msi.com/index.php?topic=260794.0 The motherboard seems to map physical RAM 2 to 4 GB above 4 GB address space: available at 64 bit and 32 bit PAE versions. There is no relating hint at the motherboard manual. Strange, the manufacturer offers Vista 32 bit and later OS 32 bit drivers. Try a BIOS update anyway. And as a last hope, try the BIOS setting 'Windows 8/ 8.1 Configuration'. If you are lucky, this set RAM remapping too. Do not rely on that.
  13. @E-66 The motherboard provides UEFI only at inital boot, hence the USB mouse is working. If you enter the firmware settings, the mobo works at UEFI mode. The motherboard speaks to the hardware at UEFI mode only. On top of UEFI, the motherboard provides CSM emulation mode. This goes to the operating system. The operatin system may detect a BIOS hardware, but it's a emulated one. The hardware itself works at UEFI mode still, the firmware emulates this. CSM mode is enabled at certain conditions. The hardware manufactuer offers Windows 7 drivers, Windows 7 is supported. http://asrock.com/mb/AMD/AB350M Pro4/index.asp#osW764Most likely the motherboard choose UEFI/CSM automatic currently. If you boot a old MBR USB disk (no Windows 7 UEFI files added) , the motherboard switch to CSM mode. I understand so far: there are no UEFI boot filles at the USB disk currently. Windows 7 setup is launched a BIOS mode and installaion to a old MBR disk does work. If you boot the same USB disk, the motherboard switch to CSM mode in future too. Windows 7 setup is launched a BIOS mode and installaion to a new empty SSD disk does work. Windows 7 setup creates a MBR disk. If you add a UEFI boot environment to this USB disk, the firmware may provide UEFI mode at USB boot. Windows 8 & 10 can't access the UEFI options from within Windows, contrary you may configure next boot. At reboot the machine boots to firmware settings automatically. What do you wan't to get: Windows 7 at BIOS or UEFI mode at the SSD? As for Windows 7 allone: use UEFI, if you use a 3 TB SSD. Well, not very likely. Keep BIOS mode: SSD at MBR and HDD at GPT. What about the year 2020, Windows 7 end of life support? Do you like to upgrade then or keep Windows 7? As for a multi boot environment, validate other operating systems too. Choose BIOS or UEFI mode. To get UEFI boot choose, you may have to update your USB disk.
  14. Unable to access list of installed updates

    What about http://update.microsoft.com/windowsupdate ?
  15. As for USB controller and USB hub: Dism does a good job, the driver files are copied to driverstore and to system32\drivers. In addition there are included to the registry CriticalDeviceDatabase. And to Services, marked to demand Start=3. The drivers are working at next boot. However a existing ENUM entry has a higher priority. If a relating ENUM entry exist, but without a service entry, then the drivers are not connected to the hardware, they are not used. Delete the half broken ENUM entry. Or try to add iusb3xhci und iusb3hub to the ENUM entry. Dism and regedit are sufficient to adjust Hardware in machine to new machine.
×