Don't confuse the two builds. Also, XBO is x86_64, not ARM.Don't forget they went through a period of optimisation so they could run it on Arm, that was after Windows 7.
Microsoft phones and the xbox one run Windows 10.
Don't confuse the two builds. Also, XBO is x86_64, not ARM.Don't forget they went through a period of optimisation so they could run it on Arm, that was after Windows 7.
Microsoft phones and the xbox one run Windows 10.
Don't confuse the two builds. Also, XBO is x86_64, not ARM.
I'm not confused, I know they use different cpus. You understand it's mostly written in C & C++ and the same code is compiled for each platform right?
https://techcommunity.microsoft.com/t5/Windows-Kernel-Internals/One-Windows-Kernel/ba-p/267142
Most times old machines will run into trouble with hardware accelerated UI elements, but those can be easily (and permanently) disabled, although personally I also trim useless services a particular user is unlikely to need in their use case which boost performance even further.
Sure. Do you understand that your results vary greatly depending on the platform, especially on a unified kernel? The more platforms you support simultaneously the less specialised the final product is. That's neither here nor there, I chose to stop engaging bleh on the 7 vs. 10 meme because it's a fairly popular myth among power users. Windows 10 had a lot of the fat trimmed off specifically because it was intended to run on lower power platforms going forward and in most daily uses has a smaller footprint and better performance compared to 7, and by a reasonable margin. In fact, many hailed it as the saviour of old machines that would otherwise fall into obscurity, although I am sure that its initial stellar results have diminished with subsequent quality of life updates.
That's neither here nor there though, it was merely a good chuckle. He does have a point, 10 was not designed with the NetBurst architecture in mind (he said Prescott, which was incorrect, but I gathered what he was trying to say), so your mileage may vary depending on the workload and the bloat. I'm not one to take people off their chosen path, I can run a benchmark and see the difference myself.
EDIT: I see that you've changed your post to encompass that information as I was typing, which is fair. Most times old machines will run into trouble with hardware accelerated UI elements, but those can be easily (and permanently) disabled, although personally I also trim useless services a particular user is unlikely to need in their use case which boost performance even further.
I'm not being funny, I've seen Windows 10 run on Pentium II machines with no HW acceleration, so where there's a will, there's a way. Naturally it's hard to advise you without actually seeing the machine in question.The EEE PC struggles to play youtube videos with windows 10, possibly a desktop composition issue. I looked into killing dwm but at the time it looked complicated.
It's always been something I only used for holidays, so sorting it out was never a high priority. But if you have any hints, I might try it out.
The "Prescott family" consists of Pentium 4 and Celeron D chips. The laptop in question (Latitude D630) is equipped with a Core2Duo T7250 which belongs to the Merom family.I wasn't referring to Netburst, I was referring to a specific 'family' of chips. I wanted to be clear that I was referring to the Prescott specifically and not the older Netburst chips.
I'm not being funny, I've seen Windows 10 run on Pentium II machines with no HW acceleration, so where there's a will, there's a way. Naturally it's hard to advise you without actually seeing the machine in question.
The "Prescott family" consists of Pentium 4 and Celeron D chips. The laptop in question (Latitude D630) is equipped with a Core2Duo T7250 which belongs to the Merom family.
https://ark.intel.com/products/codename/1791/Prescott
https://ark.intel.com/products/codename/2683/Merom
If we're being technical, the chip is neither Prescott (product family) nor NetBurst (microarchitecture), it's a Merom Core 2 chip. I'm not a 100% sure why we're bringing up either since the chip has nothing to do with either of them, I must've misunderstood whatever you were trying to say, and still do.
So I did get you right the first time. Prescott was the tail end of Netburst, there's nothing particularly unique about it besides exceptional performance within that microarchitecture. I've never heard of any particular relation between Vista/7 and Prescott specifically, but I may have missed that, it's all ancient history at this point. I thought you meant all the optimisation that went into running Windows on Netburst which was a completely different kind of architecture with a much longer pipeline than its predecessor, but you maintain that's not the case, so I'm confused. Not that it matters in this thread, I'm just unsure of what you mean in general.I am not saying that the users laptop contains a Prescott. I was saying that Windows 7 was designed to run well on that family of chips. The users laptop contains a much, much, much more capable chip.
Doesn't that require an internet connection?
So I did get you right the first time. Prescott was the tail end of Netburst, there's nothing particularly unique about it besides exceptional performance within that microarchitecture. I've never heard of any particular relation between Vista/7 and Prescott specifically, but I may have missed that, it's all ancient history at this point. I thought you meant all the optimisation that went into running Windows on Netburst which was a completely different kind of architecture with a much longer pipeline than its predecessor, but you maintain that's not the case, so I'm confused. Not that it matters in this thread, I'm just unsure of what you mean in general.
As if I didn't knew XP died.That's sort of the idea here.
Imagine if I'm a PC-collector and I bought a old Windows 2000 PC. I delete the hard drive and start fresh. Do I collect information about the PC to fully restore it, or do I just install a lightweight OS and let it be done with?
Fully restoring is how restoration works.
That's not what you said, hence the confusion. What you said was that the OS was built "around the constraints of Prescott". What you're referring to is called a performance envelope. Easy clarification, not sure why you're so frustrated.God, why don't you get it?
This really isn't very hard.
I was stating that Windows 7 was designed around the performance profile of Prescott; that it should preform exceptionally on chips that meet/exceed the performance Prescott offers. That's it. Nothing about optimization or NetBurst itself or anything else. I don't mean anything other than the actual information contained in the words I posted. Forget anything you know or think you know, you do not need that in order to gather the meaning of my words. My words stand alone.
The point I was making is that the users laptop far exceeds what Windows 7 requires in order to run well.
That's not what you said, hence the confusion. What you said was that the OS was built "around the constraints of Prescott". What you're referring to is called a performance envelope. Easy clarification, not sure why you're so frustrated.
By saying "the constraints of Prescott" you're referring to the constraints of a particular implementation of the microarchitecture. A power envelope is the general bracket of computational power expected to be encountered in the time period. You think you're a lot smarter than you really are - I continue to ignore your little quips at me, but I can stop at any time. You phrased your point poorly, you can take the L or you can continue to act smug for no reason, much to my amusement. Either way, I'm done with you purposefully derailing the thread.
Since the thread has gone horribly off-topic, I'm nuking *all* the posts that are not related to *finding drivers for this XP-based machine* and I will continue to do so going forward, this has gone on long enough. If you have no intention of helping the OP do what he intends to do with his machine, you have no business posting here - it's his machine.
You can get Mypal for that - it's a variant of Pale Moon that, contrarily to the original author's claims and attitude, needed just a few changes to still build for XPThe real largest limitation for XP vs 7 for me with the internet would be web browsers not being updated. If one spent the time and effort to backport Chromium and Firefox to XP, you'd probably be at about the same level of protection on that front.
You can get Mypal for that - it's a variant of Pale Moon that, contrarily to the original author's claims and attitude, needed just a few changes to still build for XP
The vast majority of malware comes from the entity between chair and mouse making a tool-assisted speedrun out of any installer program;
the other majority comes from every single major browser having been intentionally designed and configured, out of the box, to execute without warning code from any remote source
This thread exists exclusively because the moderating team (not myself) has determined that while all of these posts were in fact off-topic, the discussion itself is an interesting one and one that's worth having. I myself share that sentiment, it belongs in its own thread.Or it could be the XP vs 7 debate was off-topic to the thread. People may desire to have XP on a system "just because". If the machine becomes infected and they do nothing about it, then you can reasonable argue about how unreasonable they're being. That holds true whatever OS you use. Further, I know of no OS that's immune from RCE. You can at best try to take steps that should hypothetically mitigate the risk, but the law of commonality* has shown that the most popular OS is usually the biggest target for real, wide-spread attacks.
The real largest limitation for XP vs 7 for me with the internet would be web browsers not being updated. If one spent the time and effort to backport Chromium and Firefox to XP, you'd probably be at about the same level of protection on that front. If you're behind a router, most direct port attacks can't work without another infected machine on your network. I tend to be paranoid and lazy, so I'd rather avoid using unsupported older versions of Windows on the internet at all; the laziness comes in having to restore after an infection.
* For lack of a better term, the best ROI for any exploit is the one that has the widest reach. Putting the effort in to support XP along with later versions of Windows probably isn't worth the time/energy for a lot of botnet makers, so it's likely happenstance or specific targeting of XP systems (like embedded ones) that heavily effects the probability of being exploited.