dencorso

On Basilisk/UXP, when I go to Help => About, what I get is this: Which file provides this window? OR Which file should I edit to change the night-blue background or to add art to it?

On Basilisk/UXP, when I go to Help => About, what I get is this: Why doesn't the 'browser\VisualElements\VisualElements_150.png', which exists, get rendered over it?

"OSVersion"="3.6.1.0.0" shouldn't be present, for the tick boxes to show. Now, "OSVersion"="3.5.1.0.0" is not needed either (it must be the default value). HTH

It's OK! I never forget to wear my own Velostat cap while browsing the web!

I remember talk. The Whatsapp before Whatsapp.

Move the HDD to the machine it boots OK from, install this, reboot, and move back to the probem machine. Let's see what happens.

OK. So... what version of Win 95 are you running, exactly?

I'm using (hand-installed) 192 quite happily, ATM. Why shouldn't I?

It's not VPD.VxD that's freezing the system, but the next .VxD it attempts to load, IMO.

Now, since you've not even bought the board yet, if you haven't got any real strong reason to go with a different board, and just intend to experience running XP x64 at its fastest, my advice to you would be: hunt the net and the physical stores for a ASUS Sabretooth X99 and enjoy the work already done and kindly shared with all by @XP-x64-Lover, instead of going through it all again, with no guarantee to get a satisfactory result at the end. Had you already got the other board at hand it'd be different, of course. There are just my 2¢, so feel free to ignore 'em, but I'd feel real bad had I not shared 'em with you. Cheers!

Just to be picky: XP is going to reach EoS (end of service / end of support), which MS can decree unilaterally, this coming April. That won't, however, be EoL (end of life) because users all around the world will keep on running it and it'll still command something more than half the 3.5% market share it does today, at that point, which is more than 2k, 9x/ME and many flavors of PC-unix do, these days. On OS can only die when nobody uses it anymore, so that, in truth, not even OS/360 or CP/M-86 have really reached that point yet. Just my 2¢, but I respectfully ask you to edit the 1st line of your 1st post in this thread to change it to say EoS, instead of EoL. My current slogan is: EoS != EoL. Long live XP!

True enough. Let's move on. It's OK by me. And, BTW, welcome to MSFN!

I'm not. I'm 56. Am I younger than you?

Of course! With all due respect, you young people are too much sensitive nowadays. Aggressiveness one gets from a drill sgnt. Destro is slightly rough, but he only gave you reality with no frills. Getting any rather recent motherboard running XP (and worse, XP x64) nowadays is a hard, frustrating and time demanding task. If someone is hard at work with it, we'll always offer suggestions, propose tests and help troubleshooting. But it cannot be done in abstract. Thats about it.

So?

He wasn't aggressive at all. Fact.

Thx, @Destro!

@rloew: I'd love to have you test some of those older, universally compatible VIA PCI USB 2 cards (I don't remember the chip they're based on right now), on the particular adapter I've mentioned on the post quoted below: Of course, considering I'm proposing it, I'd be glad to make you a gift of one such adapter, provided amazon.com still offers them, as a token of my interest on the matter. Would you consider it?

With all due respect, let me tell you what: ProxHTTPSProxyMII (available from @heinoganda by request via PM) provides full certificates (ciphers) and TLS 1.1/1.2 (although the latest updates have now solved the TLS issue) for both IE8 and other browsers (esp. Chrome 49). Thence, Chrome 49 / ProxHTTPSProxyMII fully solve the HTML5 issue. @roytam1's New Moon and Basilisk/UXP (best, IMO) also do solve the HTML5 and cipher issue, not requiring the addition of ProxHTTPSProxyMII. So I think we're pretty well covered on this matter. IMO there isn't any real HTML5 / cipher / TLS issue with XP at the moment. Moreover, @heinoganda also has been providing a certificate updater for the root cerificates and a flash updater specific for Chrome 49, allowing it to remain easy to use and functinal. Using IE8 just for MU/WU and either the latest Basilisk/UXP or Chrome 49 / ProxHTTPSProxyMII has provided me a fully satisfactory browsing experience up to now, and I bet it'll continue so for as long as @heinoganda and @roytam1 kindly keep on supporting the community with their awesome work.

https://forum.palemoon.org/viewtopic.php?f=4&t=19826&p=147080#p147080

No. When it manages to get loaded it works as native NVMe (faster than AHCI, unless limited by NVMe/PCI-e adapter, version of PCI-e x4 bus present or maximum bandwidth capabilities of the southbridge the moderboard is built on). It's awesome!!! ................ BTW, I think you might break your list in two parts: one listing thingsthat have some support, like USB 3, NVMe and UDF 2.5/2.6, and the other listing only desirable things with no support whatsoever. It makes for a faster and clearer referencing, IMO. Of course, this is just my 2¢, and you should feel free to ignore it.

Sure. I said the OFA drivers was ported to 2k3 (which already uses storport.sys)... point being that the OFA drivers (both v. 1.3 and 1.5) use one storport.sys that is Vista+, being absent on 2k3, which was explicitly implemented internally by Kai, to allow those drivers to work on 2k3. No OFA drivers have ever been converted to scsiport.sys ever, but when one drops the latest version of 2k3's storport.sys into the system32\drivers of XP, provided nobody causes scsiport.sys to load before the kernel tries to initialize the NVMe.sys, it apparently causes storport.sys to get loaded and then gets loaded itself, starts and works successfuly. But if scsiport.sys is already loaded it fails to even start (EventID: 7026. The following boot-start or system-start driver(s) failed to load: nvme). That's about all I know about it.