Tripredacus

Name changed

Which version of Windows, or WinPE? The only real difference I know is that in the WinPE based on Win11, it won't assign a drive letter to an OS volume. This effects both ADK built WinPE as well as the PE that Setup uses from the install media. For which WinPE to use in general, I had typically stuck with whatever the most recent one that was needed for whatever purpose and typically that would work with previous versions of Windows but I would keep old builds around for legacy purposes. If you are referring to OS option on my profile card, that is just reflective of the computer I tend to post on the forum from. My regular internet usage computer is Win7 x64 but my gaming/streaming computer and my dev notebook run a Windows 10 equivalent, my security notebook runs Linux and I believe my imaging server runs Server 2019 Standard. I manage a Windows 11 computer also but you can only put 1 thing into the profile card. Not currently possible to circumvent enumeration. I don't even want to think about what would be required to change it. I don't think that it is impossible to do but it probably wouldn't be worth the effort unless you were really bored. Usually you just have to make the best with what you have and apply workarounds if you need to use them. Some of those workarounds that I have had to do in the past include: - always changing C volume to another letter on first boot into WinPE because it will assign USB drives and some unpopulated card readers to letter C which can interfere with some deployment scenarios. - having to make alternate deploy profiles for situations where WinPE enumerated Disk 0 as something other than the disk the OS is supposed to be deployed to. Methods of controlling drive letters include: - Using PXE to boot WinPE instead of from USB. - Using mapped network drives to be the places where OS images and applications would be stored.

WinPE reassigns all volume letters based on the order in which the volumes are enumerated. Typically it goes in ascending order from Volume 0, but there are some instances (on real hardware) where a volume (or disk) is not made available at the same time every time and those letters can change. Because of this, I usually recommend that only the disk that is meant to be imaged (or worked) is connected when booting to WinPE.

It seems to differ from Android version to version. I remember having a previous phone that I could set custom sound alerts for SMS for specific contacts, but then a later phone didn't have this option. There are apps that can do it but trying to find a simple clean app (especially these days) can be a real task. I had used apps to manage this before and they do work but not reliably. For example one phone I used an app for that, it would play the custom sound half the time and others it wouldn't before eventually it just stopped working. My current phone just has a default "Notification Sound" that is system wide, and the app I use for SMS doesn't have an option to use anything other than the system notification sound. I had a previous app that did but I never bothered to change it before it stopped letting me open it.

I only enabled the one custom theme. I will put making a new theme onto my worklog. Probably won't get to it until Monday at the earliest. If you have a wish about what kind of colors you are looking for, post in the Complaint Department.

I have not tried to do an installation the way you are thinking about. I would use a solution where the drive letter doesn't matter, which typically means to include the files I need to be installed (including the .cmd file) in the image itself, so that all paths are relative aka on C:\ already.

First of all, people typically don't respond well to demands to give answers or do all of the work for you. Second, it would be good for you to explain how exactly you are designing your deployment workflow. Since you mention using both XML types (one for install, one for sysprep) it leads me to believe that you are making a deployment image. I have never personally found it useful to add any scripting into Autounattend.xml to begin with because that is only for creating the base installation. It is different if you also intend to use it for a recovery scenario, but in that case you wouldn't end up using two XML files anyways. I've only operated in a structured deployment environment where the need for determining drive letters or scanning for volumes wasn't needed. Nevertheless, for post deployment customizations I would use FirstLogonCommands in the oobeSystem phase to specify a single .cmd file. Then within that .cmd file that would be where I would include the scripts. But as I said, I never would need to have to scan for volumes and if I did have to do something like that, I would likely end up writing a program to handle that type of task so that I can leverage WMI and Win32 API calls.

Bring back the Azure Screen of Indifference! Wasn't there a red screen of death in a Vista beta?

I don't really care about it personally. I have to deal with it here and the other thing I mentioned but MSFN is based in Europe so we have to follow those rules. If MSFN wasn't an official fallback location that line wouldn't be there. It is only because MSFN has many EU members that I mention it. It seems standard practice that US sites don't care about those things, even if the forum software supports it.

What do they mean by apps? Are they only referring to stuff that comes from the Store and not traditional executable programs?

The alternative forum is now available. It is located here: https://tripredacus.net/forum/index.php This forum is actively managed by myself and has public status sections for the three websites that I am providing temporary forums for. The fallback boards are not visible to the public and are not segregated, meaning if you can see a board, you can post in it if you want. The sections will always be open, even if the hosted site has an Up status such as MSFN currently does. This forum is not intended to, nor can it replace MSFN. It is also not meant to be a replacement for other unmanaged or unofficial meatup destinations such as any Discord channels, Steam or Facebook groups. It simple is a place to go in case there is a problem or you want to get info about whatever might be happening. This is not an indication that there is any longevity issue with MSFN. The forum rules are not MSFN's rules, with the exception that discussion about circumventing MSFN rules 1 are not allowed. UK/EU members make sure you read the end of the Registration Agreement. Whether you decide to register on it or not is up to you. This post is just to make you aware that it exists. You choose your own level of involvement. If you decide to register, you should edit your profile to put your MSFN name as it explains in the appropriate profile field. Doing so will cause a MSFN icon appear on your info card if you post in a thread.

I don't think the Discord is official. You can use whatever you want. The site has been running good lately, so hopefully no one will ever need to use it.

Websites can be weird at times, idk why. I got banned on Venmo just by registering an account. And I got banned on Whatsapp by opening the app on my phone after I took the sim card out.

An alternate/emergency forum is in the process of being completed and I will post more once it is ready.

I only go there while logged in but they could really use a better search overall. Besides shorts, it often gives results for things other people have watched which are never relevant to what I typed in. I wish all sites that had a search even Google or Ebay had an advanced option you could set where it would just give you results based on what you typed and not all that fluff they want to make money with.