Jody Thornton

I have one on my xw8200 HP Workstation, and it says designed for XP and XP 64-bit Edition.

Hi Folks: I am looking into one of two new workstations to eventually replace my HP xw8200. I tried installing Windows 8.1 x64 Pro on it but my system isn't suitable. The Z600 and Z800 from HP look like really nice systems, and on the off lease boxes I've come across, the systems have SAS 15K rpm drives on them and between 12 to 16 GB of RAM. Nice! But it appears they do not have UEFI BIOS interfaces on them. I've read up on the recommendations from the HP website for carrying out clean installations of Windows 8 and Windows 8.1. It's hard to get a clear answer but from what I can decipher, you can install Windows 8.1, but without UEFI capability, some of the processor security features will not be available. That in itself doesn't bother me, as long as Windows will run. Does anyone have any exprience installing or running Windows 8.1 on a Z600 or Z800 workstation? Any help or insight would be GREATLY appreciated. Cheers!

My pleasure! But do keep us posted: this thread is serving as a meeting point where we exchange info on what's happening, all the time. Whenever an issue occurs, it's posted here, and so are solutions and workarounds. That a big 10-4!

Hmmmmmm - very tempted to go back and run Windows 2000. I really liked it. What's the latest browser you have managed to run?

There may well be, at some point, but up to now there is none. But we'll deal with that when it happens, as was the case with the win32k.sys that impacted rendering. Observe that just hiding it and waiting for the next month was enough to solve that but, even before that had happened, harkaz had released an unofficial fix. That sounds good to me. So I'll proceed with updating my mom's machine and see what happens. Thanks for the report in a nutshell. I needed that.

So if I may ask (summary-wise without having to read through the whole thread) the following: Can I now assume that entering the registry patch and just ruinning and installing all POSReady updates without any intervention or workarounds is not possible without some added effort?Am I correct that at some point, there will be at least some DLL issues to contend with? I'm not going to be installing any .NET framwork or updates, and I'm already aware of the update that negatively impacts font rendering.Thanks

As always I may be wrong, but IF in any way Windows XP was in practice "not secure anymore" or "less secure" than 7 or 8/8.1, now, one full year after the end of support deadline we would have had between 15% and 25% of all the internet connected PC's compromised one way or the other , and since this has not happened yet the "not secure anymore" or "less secure than" appears like nothing more than an unverified theory or of some wishful thinking. jaclaz ---------------------------------------------------------------------------------------------------- I don't think that neccessarily there would have been attacks if XP were that insecure. I always took the secuirty issues as Microsoft trying to mitigate security problems and be ready by getting users off the OS. As for Moonchild, he simply wants Pale Moon to support current dekstop OSs. The is an XP build for Pale Moon (not the Atom one) and that is for x86 and x64 builds, maintained by Matt Tobin. The link is here: http://binaryoutcast.com/projects/pm4xp/ Support will expire in July 2015 though for this build. As for Firefox supporting XP, but not Pale Moon, all I can say is that Moonchild says he is forking Pale Moon in a different direction thatn Firefox, so it's no longer considered a clone or custom build, but rather a separate browser originally based on Firefox. Pale Moon dispensed with Australis and uses it's own identifier for add ons and what not. We'll see, though for now I'm a happy user of the x64 build.

See I thought it was the April 2015 deadline for MSE. No biggie though. And to answer Dencorso, the 4.4.304.0 version does work without complaint. I just figured that the Vista and 7 installer would be devoid of that code.

I run MSE (the x86 Vista/7 install) on Windows Server 2003. It works quite well, though I do realize that it's not officially supported. However, the last updates show the same "support ending" message that showed up on Windows XP last year. Now, I guess I'm surprised that the code in the Vista/7 installer would detect Server 2003 as XP, but moreover, I'm surprised that this installer would even have the end of support message. My hope was that since MSE in not even supposed to recognize Server 2003, that it would just keep running without issue until January 2020. After all, I used the installation file for Windows Vista and 7. So I went back to v4.304.4 (I think that's right...lol). It takes current definition updates, and keeps running without the notice. I wondered if any one might've know another way around this perhaps. Cheers All! (EDIT - Ooops, I meant to write "without" the notice. That has been corrected. Sorry for the confusion)

I'm usually a later adopter, but while the system is in development, I usually am in anticipation mode, and I'm usually very excited about upcoming versions of Windows. But like you, not so much this time.

Hey Noel, I'm with you on dates/times on files in Explorer. I think that started on Vista, because I have files that show as "Today". (I use Explorer++ as a file management replacement. It works enough like how I had XP's Explorer set up) Also I agree about defeating UAC and Indexing easily enough. (I have a good search tool, which reminds me of the old Windows 95 style search. Hey it worked!) I also hate the caption buttons on the last couple 10 TP builds. Even going back to the Windows 8x style would be an improvement.

Stick to your guns Noel. Last year I had left this forum, because a couple strong arm types were angry with my speculation of how security issues/concerns might affect Windoiws XP's end of life. But see everyone should get a chance to an opinion, and so should you. (And yes, submix8c, I apologize for going off the handle with you. I don't fault myself for why I did it, but I certainly overreacted. Fair? ) In the end though I find I'm more of a similar opinion to you folks than on the Ten Forums, where everyone seems to exalt Windows 10 TP. One fellow, Jeff (who goes by Bunny J) though nice enough, seems to agree with absolutely EVERYTHING that Microsoft presents with 10 TP. He acts almost too agreeable, like the way a fan boy would be. It becomes irksome after awhile, because I really don't get what's so great about 10. In fact, I prefer 8.1 with Classic Shell. But all of their forum members seem to clump together to go on and on about 10 TP's greatness.

Go to this site. He has a whole boatload of compatible 2K3 Updates for XP x64 Edition: http://wp.xin.at/xp-x64-post-mortem-updates

Darn; I was hoping they'd bring back Presto and the classic 8.x theme.

Some links that might be valuable (just be cautious with them of course) http://www.neowin.net/forum/topic/80511-winxp-guide-making-your-windows-folder-smaller/ http://www.neowin.net/forum/topic/316422-slimming-down-windows-xp/ !!!! But this page is quite valuable !!!! http://www.graphixanstuff.com/Forum/index.php?showforum=68

I would eventually move to 10, but I hate some things like the new Start Menu and the caption buttons on the last build. I find that 8.1 runs well (I tried it in a VM and didn't hate it)

Well it does have to do with Vista's extended phase support expiry. If I jump to Windows 8.1 (which I can tailor to my liking), I will need a new machine with UEFI so I can run the x64 build. My HP xw8200 workstation is not compatible Bios-wise (I don't believe it is anyway). I do like to stay with an updateable OS, but I realize that the end of the world doesn't arrive with the end of extended=-phase support.

So if that is the case, there will have to be two sets of updates between Classic and R2, since the codebases are different, right?

Did you ever get the issue fixed as well? Mine is.

It does seem that the pushed updates are gonna happen, though yes, I do aggree that it appears you'd be prompted for such updates to be installed. I have to admit that I've lost interest in the Windows 10 TP. I'm staying put with Vista SP2 and running it until April 2017. At that point, I'll get a new machine and install Windows 8.1 (x64 build)

I ran and scanned it with a number of scanners, but never found an issue. My system still works, but I did use it in a Windows 8.1 VM.

I've been running Vista Ultimate x64 Edition (SP2 integrated) for just over a year, and it smokes. XP x64 Edition ran a hair more responsively, but it's hardly noticeable. I tried and supported Vista in its RTM days and it was crap (REALLY slow), but on a good machine with SP2 integrated, there's no issue now. Am I right in assessing the x64 build as more stable as well? I've just never seemed to like the x86 build of Vista, but the x64 build seems "better".

Well if Server 2008 "Classic" is getting updates, I might be able to stretch out Vista for a little longer if there is a source of patched updates. I really like my Vista system. I admit that I really loved Windows XP x64 Edition, and just to add salt to that wound...lol, there is a fellow who patches XP 64-bit Edition updates from Server 2003, so I could have stayed with XP x64 Edition in the end. However, that would have meant that in July, I would've had to migrate over to another OS. Whereas now that I've made the jump to Vista last year (Feb 2014), that is all behind me now.

Well thank you for the detailed answer. I had the font issues on that same update in Vista (while running the Pale Moon browser). Uninstalling the update fixed it. I will try to quiz my mom and see if she installed updates (plus I should have looked at the update history)

A lot of Vista users seem to think that since Server 2008 R2 will receive extended phase updates until 2020 (since it shares the same codebase as Windows 7), that Server 2008 "Classic" will also get updates. Has this been officially spoken of somewhere? I would think that as of April 2017, Server 2008 users will need to migrate to R2, no? Cheers!