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. 


Tripredacus

Supervisor
  • Content Count

    12,097
  • Donations

    $50.00 
  • Joined

  • Last visited

  • Days Won

    6

Tripredacus last won the day on March 14

Tripredacus had the most liked content!

Community Reputation

466 Excellent

5 Followers

About Tripredacus

  • Rank
    K-Mart-ian Legend
  • Birthday September 29

Contact Methods

  • AIM
    atrbludgeon
  • Website URL
    http://tripredacus.net/

Profile Information

  • OS
    Windows 7 x64
  • Country

Flags

  • Country Flag

Recent Profile Visitors

18,325 profile views
  1. I sort of miss the days of using funny names for computers. Now everything is so serious or boring.
  2. Outside of a software hiccup, there are two things that come to mind. 1. the ISP deleted the items on the server for whatever reason. 2. You had connected to this same email account using another client that was configured as POP3. By client, it can mean something like an email app on your phone, or perhaps even the webmail interface. Since the response you got from your ISP seems generic (although you did not provide an exact quote) I would imagine they did not actually verify the folder contents on the mail server. Having previous experience at ISP, I do know this is possible, but also that ISP did eventually phase this ability out for edge reps. In an IMAP situation, the response would be that what you see on your end is what is on the server. That can be confirmed however, by connecting to your mail account using another client set up as IMAP. Something like Thunderbird or another client that supports IMAP. Then you can verify that the folder is empty on the server, or perhaps it isn't actually empty but there is a problem with Outlook.
  3. I did a compare to the three main WinPEs, the 14393 prod, 14393 local and the 17763 prod to figure out which drivers were in each and which were unique. It brought me back to the AMD drivers again. It would seem logical to do that after the end of the last post, however I had to check all of the drivers specifically because I was seeing the issue on non-AMD boards. The logic would be that Windows would not load an AMD storage driver on a non-AMD storage controller, right? I did a compare on the working and non-working driver set. 9.2.0.87 Working (all NVMe is Disk 0 on any controller) seems to be the newest, also tested 8.1.0.26 (which does not load the AMD driver onto the NVMe) 9.2.0.127 Not working (all NVMe is Disk 1 on any controller) Looking specifically at rcbottom.inf, the meat of the three drivers in my experience... (AMD RAID drivers have 3 infs, rcbottom, rccfg and rcraid) Ok some difference. My first thought it to look at that yellow line that I have clicked on. It has a Hardware ID of CC_010802. I did a recheck of the device properties again using new injections and only with the v17763 of WinPE using the 8.1.0.26 vs 9.2.0.127 drivers.... but that data is similar to what is in the end of the last post. I did a search and NirSoft's DevManView does not have any record of CC_010802. This is a compat? flag. But look at that driver data, you can see rcbottom.inf is loaded on a non-AMD vendor ID. AMD is VEN_1022, what is VEN_144D? It is Samsung. So rcbottom.inf is loaded on the physical hardware device for the NVMe, and then the NVMe (as a disk that can have volumes) is loaded under disk.inf. So here is the proof that Windows will load the AMD RAID driver onto a non-AMD controller because it is loading it for the storage device and not the controller. This is why an NVME can be seen as an AMD RAID device on non-AMD boards. Since we already know that DevManView won't show the whole slew of additional HwID or compat IDs that is actually tied to the device (from WMI), we can boot into the OS and use Device Manager. In this scenario, the PC has Windows 10 Pro but does not have the AMD drivers installed. Hence it appears as "Standard NVM Express Controller" in the Storage Controllers section. And there it is.
  4. Great area, maybe some day I can live there.
  5. Welcome to the MSFN!
  6. What about Windows for Workgroups and Windows NT?
  7. Getting somewhere, maybe.... This could have been a perfect storm, a situation where something else was changed besides the WinPE version and caused this issue to appear... The SK1200KP with a RAID 1 and spindle disks is the same in both WinPE versions. And then these results using 14393 on a PRIME B450M-A, since the NUC would not boot on that PE version. As seen here, it is the same as 17763! But certainly NVMes were definately being detected as disk 0... how could that be? Well I am testing with local PEs not production PEs. They are mostly the same, but obviously there is something different. Production PEs have always detected NVMe as Disk 0 like all other disk types, and it was only the "local" PE that would detect NVMe as Disk 1... UNTIL 17763 came out, and then either build detected an NVMe as Disk 1. Here is the NVMe on the B450M-A using the production PE v14393 where it is detected as Disk 0: I can't put the OCs into the production PE, so I can't run the wmic command. I can do this comparison between B450M-A with NVMe using Production 14393 (detected as disk 0) AMD-RAID Bottom Device Advanced Micro Devices, Inc. rcbottom SCSIAdapter PCI\VEN_144D&DEV_A802&SUBSYS_A801144D&REV_01\4&2074c63f&0&000E @System32\drivers\pci.sys,#65536;PCI bus %1, device %2, function %3;(8,0,0) 0x00000000 0x00000000 No Yes 5/14/2020 3:28:57 AM 5/14/2020 3:28:54 AM AMD-RAID Bottom Device 9.2.0.87 oem17.inf rcbottom_Inst.NT 9/21/2018 5/14/2020 3:28:53 AM AMD-RAID Controller [storport] Advanced Micro Devices, Inc. rcraid SCSIAdapter {54cb850d-a731-8590-0628-1992592bd448}\rcbottom\5&d1e0a6&0&131071 0x00000000 0x00000000 No Yes 5/14/2020 3:28:56 AM 5/14/2020 3:28:54 AM AMD-RAID Controller [storport] 9.2.0.87 oem19.inf rcraid_Inst 9/21/2018 5/14/2020 3:28:54 AM AMD-RAID Samsung SSD 950 SCSI Disk Device (Standard disk drives) disk DiskDrive SCSI\Disk&Ven_AMD-RAID&Prod_Samsung_SSD_950\6&10c8e623&0&080200 Bus Number 8, Target Id 2, LUN 0 0x00000060 0x00000000 No Yes 5/14/2020 3:28:57 AM 5/14/2020 3:28:57 AM N:\ Disk drive 10.0.14393.0 disk.inf disk_install.NT 6/21/2006 5/14/2020 3:28:56 AM and same but with local PE 14393 (detected as disk 1) AMD-RAID Bottom Device Advanced Micro Devices, Inc. rcbottom SCSIAdapter PCI\VEN_144D&DEV_A802&SUBSYS_A801144D&REV_01\4&2074c63f&0&000E @System32\drivers\pci.sys,#65536;PCI bus %1, device %2, function %3;(8,0,0) 0x00000000 0x00000000 No Yes 5/14/2020 3:39:23 AM 5/14/2020 3:39:22 AM AMD-RAID Bottom Device 9.2.0.127 oem11.inf rcbottom_Inst.NT 7/5/2019 5/14/2020 3:39:21 AM AMD-RAID Controller [storport] Advanced Micro Devices, Inc. rcraid SCSIAdapter {54cb850d-a731-8590-0628-1992592bd448}\rcbottom\5&d1e0a6&0&131071 0x00000000 0x00000000 No Yes 5/14/2020 3:39:22 AM 5/14/2020 3:39:22 AM AMD-RAID Controller [storport] 9.2.0.127 oem13.inf rcraid_Inst 7/5/2019 5/14/2020 3:39:22 AM AMD-RAID Samsung SSD 950 SCSI Disk Device (Standard disk drives) disk DiskDrive SCSI\Disk&Ven_AMD-RAID&Prod_Samsung_SSD_950\6&10c8e623&0&080200 Bus Number 8, Target Id 2, LUN 0 0x00000060 0x00000000 No Yes 5/14/2020 3:39:26 AM 5/14/2020 3:39:26 AM D:\ Disk drive 10.0.14393.0 disk.inf disk_install.NT 6/21/2006 5/14/2020 3:39:26 AM Any M.2 shows up as a RAID device on AMD boards, since it does not use the SATA controller, rather to be able to detect the disk you set NVME mode to RAID. A comparison of just the driver info (from Nirsoft's Devmanview) shows that two different RAID driver versions are being used. I could see that as being related to this issue happening on an AMD board, but not the Intel based boards. I will have to do some tests with those AMD drivers removed and see if it makes any difference.
  8. The license requirements are for System Builders, integrators or OEMs. It related directly to fulfillment scenarios, aka selling the OS and a computer. That edition is designed not for retail sale, but for sale along with a full computer system. The OS has to be installed onto the hard drive, the COA put onto the case and the Pack itself included as an accessory. It is basically a restriction from selling the kit on its own in the Retail Channel. For an end user, you can use it to install to a computer without a problem. You do not need to use the OPK. For Windows 7, only OEMs were able to use the OPK and for System Builders and end users they could use the WAIK. All of that was replaced by the ADK. For those wondering, there is no mistique about the OPK, the only difference between it and the WAIK for Windows 7 (from what I can tell) is one .chm file that has additional license requirements for OEMs and System Builders. With the ADK, MS had made one kit for everyone and now the OEM specific documentation is paywalled and separate from the kit. A situation you may find is that storage or USB drivers are missing from the DVD. You would need to use the WAIK or ADK to add USB drivers into the image and then rebuild the install CD. But this process is not different than with other versions of Windows 7. If you do run into this USB issue, if your computer has PS2 ports you can get around it (instead of rebulding the DVD) by using PS2 Keyboard/mouse for the initial setup, install the USB drivers and then switch to your USB devices.
  9. Welcome to the MSFN!
  10. It is in IoT as well and has some issues. The UWF does not support full disk or volume. For example, it will not work properly if you are using single read-only disk. Look in the requirements for the feature, Pro is not there.
  11. The Rules and Donate links in your signature are broken.
  12. This is answered earlier in the thread. https://msfn.org/board/topic/181489-cpi-error-messages-other/?tab=comments#comment-1181520
  13. You'd have to test if that works. I always run things through cmd.
  14. What I get from here: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh825129(v=win.10)?redirectedfrom=MSDN Is that the enable/disable of optional packages inside of the Foundation Package must be done with an /apply-unattend, and that branch should be in Offline Servicing and not just Servicing branch. The image must then be installed using Setup, using your XML that does not have the offlineservicing object in it. Onedrive can be uninstalled, I usually do it with first run commands. Here is the cmd: c:\windows\syswow64\OneDriveSetup.exe /Uninstall
×
×
  • Create New...