Tripredacus

If you didn't have the system already in place, it would take a lot of work up front to be able to accomplish it. However, there is another option that I forgot to mention. This falls into the technically possible sector rather into what is supported. What you need is: - a second computer - a WinPE v3 of some sort (from Vista or Win7 WAIK, do not use ADK for 8-10) - a Vista install DVD - a USB or CD/DVD with the USB, storage and LAN drivers (INF type, not installers) Using the second computer, disconnect its HDDs and connect the HDD for the system you want to install the OS on. Install Vista onto it. When the install does the reboot and then boots from the HDD instead of the DVD, the OOBE screen appears. Chosing nothing, you press CTRL+SHIFT+F3. Then the computer will reboot into Audit Mode. When in Audit Mode, you use the sysprep box to check the box for generalize, the choose OOBE and Shutdown. You can choose restart but if you let the OS boot into Windows you have to start the entire process over. Basically, the only system you want to boot into Windows after using Sysprep is on the system the HDD is supposed to be for. Either after the reboot, or after powering on from shutdown, this is the step in which you boot from the WinPE. And here you will use Driver Servicing to add the storage driver, lan and USB drivers for the target system into the offline OS on the HDD. Use diskpart to verify drive letters to make sure you are installing to the correct volume. https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-driver-servicing-command-line-options-s14 After each is added, then you shut down the system. Remove the HDD and put it into the system you want it to be in. If you did it correctly, when you get back to OOBE your mouse and keyboard will work.

Samsung 860 EVO appears to be a SATA SSD. As for whether there is something particular with the disk that will make it so that it will not function properly in the notebook, it is difficult to tell. I can't really find anyone trying to use the two things together. On the surface I would say there would be no issue, but know that saying this isn't an endorement that it will work. The one thing that I can tell you about this is that your notebook's drive bay was specifically designed for whatever size HDD it was sold with. Be aware that some SSDs are actually thinner than HDDs. The difference may be that if there are any pads on the drive chassis (if it uses one) they may not be sufficient to keep the SSD from moving. You may need to use additional padding. You won't know this until you get the drive in hand and try to install it.

We only delete at a user request, a thread OP request or if there is something violating the forum rules. If you look, you can even find it is not against the rules to go OT, or talk about more than just the topic at hand in your post.

Findfast would cause this type of problem with floppy disks. Do not know if it also does it with other removable media types.

You should try to match timing and speed of the memory, and size if you want dual channel. But to be honest, if the purposes you use the computer for are such that you wouldn't notice the memory running at a wrong speed, then it doesn't matter. If you are playing modern games or doing engineering or video editing, then you want to have everything match.

Then there is even more reason to try connecting to a secure site that is also set for a future date. As in my previous post, my personal concern is the ability to connect to routers. A person could, say, set an old router to a future date, enable SSL and then connect to it via an XP computer with the same future date. That should eliminate any issue with the client date being wrong vs the server date. And when I am talking about old routers, pretty much any Wireless B/G router is going to be using the old certificate when SSL is enabled. Also, this is not a task that I am fit to perform. My Win XP system is a custom build and it does not have the updates that are in common amongst users here.

If you had a Vista image, you could image the disk on anything and then put the disk into the system.

Would be interested to know whether this effects trying to log into networking devices that use old TLS. The only reason why I keep an XP system around is to be able to log into "secured" routers, which is something that my modern systems cannot do since they removed the ability to recognise the certificates those devices use.

We already have a topic for this: https://msfn.org/board/topic/174208-windows-10-deeper-impressions/

In my experience, ReadyBoost is great for a day or two, but it always has destroyed the cache media. If you aren't actually going to use it to run cache media, then it should be disabled.

It was a client requirement at the time. Client was using Linux systems in-house to run this particular hardware setup but wanted to introduce a Windows based product. The typical Windows behaviour (even to this day) is to use default outputs. We had tried many different OS to accomplish it, XP Pro x86, XP Ultimate x86, XPe, XPee, Vista Business, Ultimate and even some versions of Server 2003. XP x64 was the only one that allowed for each sound card to have dedicated input and output. Basically, they could output audio on each sound card simultaneously. Whereas the other OS (or even current one) likes to only use 1 "Default" output, no matter how many audio controllers you have. Even on my Win7 PC at home it cannot do this. Despite I have sound controllers on the video card and sound card. If I want to have audio go to my AVR instead of my PC speakers, I have to set the HDMI Audio output as default and then it will work. There is no option for me to output audio through both the video card and sound card.

I find it hard to believe that the system does not support hibernate. I would suspect there is something wrong with the system or that the BIOS isn't set properly. None of the notebooks I work with have this type of issue. If I were to come across a notebook that did not suspend properly, I would contact the manufacturer support and/or issue an RMA.

Post the most recent memory.dmp or minidump file.

Microsoft does not fix bugs unless it is forcasted to have an impact to their bottom line. It doesn't matter if it is related to a currently supported product or not. I have submitted bug reports including PoC for current MS Office and with the ADK and they do nothing about it, not even acknowledge it. The typical reaction goes something like this: If I do a specific thing, I get an error. How should I fix it? Let me ask you a bunch of irrelevant questions ... (a lot of back and forth) I found what makes the error. Here are the commands I run, what happens, the logs and traces, and how to fix it = Sometimes it comes down to who you talk to. If the person you are interacting with is a support person and not a tech or engineer, then they may see a "resolution" of using a workaround and never pass it up. Once they think they have "solved" the issue, it is over. Nothing is ever done, not even make a KB or a post about it.

The only thing I can add about XP x64 is that it is the only OS I have used that allowed 4 separate sound cards to work using dedicated and separate channels. Obviously this is a very specific requirement that most people aren't going to run into.

Here is the error [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Any time I attempt to count computers, I certainly count the GRiD Systems 1520, which is literally a brick since it went underwater and ended up becoming completely destroyed with corrosion and dirt. It is too special of a computer to have thrown away. I didn't consider counting the micros. That is 1 C64, 2 VIC-20, and if they count a TI-99/4A and a Timex Sinclair 1000.

For your particular error: Error: Package_for_RollupFix Error: 0x80073712 Unless another solution presents itself, the DISM log doesn't usually pass failures caused by the OS into the DISM log, but it does reflect this in the file you uploaded. Now CBS log is going to be quite large, so you'll want to look at (or post only) the portion around the same timestamp as the error below. 2021-04-23 10:44:58, Info DISM DISM Package Manager: PID=2404 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

I am watching season 2 of Arrow.

OK that part number matches what you put in the first post. If your computer has an N license/OS on it now, the key from the SBK probably isn't going to work. You can attempt to change the product key in the OS and/or even trying to activate it but knowing a couple things: - The OS installed may or may not access the new key but beyond that, it may not have the additional stuff inside of the OS to change to Pro. - If it happens to take the key and does actually activate but doesn't change the edition (or worse, changes winver but not the actual features) then you might need to use the telephone activation when you reinstall using the SBK. I have not had to deal with N, at least in this type of scenario, there is no production or support scenario where changing a product key to change editions is viable. So I do not know whether or not N would accept the key or not. My gut tells me that the OS would just say the key is wrong. No such thing as overkill for backup drives, sometimes it is just what happens to be available. For my main computer which has maybe 400 GB total space among 4 HDDs, I have a 4 TB backup drive. Why so big? Well it is simple, I went to the store to buy a USB HDD for backup and that was the size for the cheapest one.

People just repeat what they are told and this is especially true if they do not fully understand how something works. The root of this comes from sales pitches from companies from years ago. Even old versions of Windows have had advertisements like "most secure ever" which implies the predecessor is not secure once the new version comes out. Also people conflate installing updates or the ability to get new updates with security. They know some bad thing happened to someone online and there is an update, and if you have the update you will be protected from that thing. But people do not actually look at what the update is, or the CVE or anything like that. They have no idea whether or not the update even has anything to do with their operating environment or how they use their system. This is why I never understand people who just go an install all of the updates, or worse, brag about installing all of the updates. No one needs all those updates, but people will just put them all in there anyways because it is easier than learning how their computer or OS actually works and being able to determine which updates they actually need.

N editions and typical System Builder (OEI DSP, which is in the retail channel) are not in the same channel and the keys are not compatible with each other. There is no shared upgrade path between the two editions. You will need to buy the media kit and will need to reinstall the OS entirely. But, what is the kit number on your existing media pack? Because the name you put in bold does not look to be for an N edition, but we can know for sure with the part number. This is the "End Item PN" above the first barcode on the pack.

Played Just Cause 2 for the first time since 2017, according to the save game.

The drivers at that link appear for me, showing XP to Win 10.

No.