dencorso

Absolutely! XP Pro SP3, hands down.

I had the same issue. I do think it was more than just dns, because I was equally unable to reach MSFN by IP. In any case, for those of us who happen to also be members of RyanVM's forum, we now have a thread there (thanks to tomasz86) to regroup and exchange information on the status of MSFN, should the need ever arise again.

No. Not high-priority. But simplicity. The point is Extended Unicode characters and special characters "<" ">" "#" are not being parsed correctly because a pair of quote marks (or maybe double-quote marks) is missing in presumably *one* script. So it should be terribly easy to fix. OTOH, the really high-priority fixes you're requesting appear to me to be much more complex to fix. Then again, you shouldn't be so sure you'll never change yout nick to ヤクラツ デ ン コ ル ソ

xper, please, do give this issue a look... I'm positive it didn't exist in the previous versions of IP.Board

Yes. MySQL.

Non-SSE2 machines cannot run Win 8... so, if I had to hazard a guess, I'd say the 12 y old machine has a P4 cpu (Willamette?).

Since we're giving links, it'd be unfair on my part if I failed to mention 911CD and reboot.pro.

I've always taken that to mean that XP has less need of daily discussion because it works, is less controversial, and most of the bugs are solved and answer easily found. While that is certainly true, it's true also that there's RyanVM's, xable's and some other places where one can equally go for XP and be equally competently helped by knowledgeable people who love XP... And in fact there's considerable overlap in the membership roster of all the mentioned places.

While Charlotte and some others are defending the more radical position, which is running fully unpatched (SP3 out of the box, I presume, but maybe not even that) and without any antivirus (at least real-time), that never was my case. From the start I'm just defending patching to the brim with what MS offers (intelligently and within reason), and using a real-time antivirus, but continuing to run after MS stops providing patches (but adding any unofficial ported patches that may be offered by reliable 3rd parties, if and when available). Just that. Moreover I do favor only keeping the machine up when using it and being behind one (or more) provider(s) of dynamic IPs, and renewing them daily. All this adds to security, as does using a non-sse2 capable machine, for the time being (remember those viruses which relied on "POP CS"? It's the same idea, but reversed). All I'm saying is that end-of-support at 2014 is not a definitive showstopper, even if it does make life more difficult in some aspects.

Sorry, enxz! I'm not a native speaker, and although I usually can fill the gaps one inadvertently leaves on writing, that missing "k" was too much for me. For those who do it for the kicks (and those use to be the ablest invaders), an easy pwn is of no interest.

As it's written, the above sentence actually makes no sense. Please do correct and elaborate it. In any case, if I got right the gist of it, if the vast majority (of hackers? of invaders? of Venusian Incas? of Borg drones?) would say "XP, duh!", that surely *is* an added layer of security XP has, which the newer 7 & 8.x don't.

Well... so it seems it was down while I was sleeping, and hence I didn't become aware of it till now.

/GS is the default for MSVC++ since MSVS .NET 2003... That means it's already used from right before XP SP2 times...

MSFN was never down from here, in the latest 10h. Must have been something in-between you and MSFN that went down, not MSFN itself.

Theoretical knowledge tells you how things ought to be. Statistics tell you how things use to be. BTW:

Take 200 pairs of machines, of many models and makes, but each pair consisting of identical hardware. Deploy in one Win 8 and in the other Win XP SP3. Put each machine alone behind a router and have exactly half the routers have the firewall active and half have it full deactivated (but don't tell the actuall users which is which). Disperse the pairs around the world. Run that setup at least six months and each time an infection/invasion happens, tally it, use ATA format and redeploy it's OS again from the master image. Treat all that raw data with good robust statistics and come back with facts. Without that (or something like it), all you have is theory and opinion. Opinion, any one is entitled to hold any, but they are a hard sell. Now, in many instances, when the models are mature, in theory, there's no difference between theory and practice, but in practice that's not necessarily so.

As the good Judge Patrice Lessner would put it: "...in *your* opinion!" To affirm that as a fact, at the very least a double-blind test is required, with representative samples for each group of machines. You've shown no reliable data, in fact, no data whatsoever.

My take is: he either died of commotio cordis, 18 hours after a well-placed Dim-Mak or, although this is somewhat less probable, from anaphylactic shock, due to the bite of a stealth albino black-widow, of course! Now, do tell me: what do boob-jobs have to do with ATM hacking?

That really depends how you define security. In my case I know that most hackers are incapable of getting into my system, whether they want to or not. Can you say that about an unpatched XP box? Sure I can! Most hackers means not all hackers. One single intruder gets into your machine and you're pwned. You cannot be positive no one'll ever be able to get into your machine, no matter what. Hence, in disagreeing with me you've just agreed with my point. Nobody is ever secure. No matter what.

Nobody is ever secure. But XP SP3 after 2014, just like 2k SP4+ today, should be at least as secure as 8.1 (or whatever the name of the bleeding-edge windows-of-the-moment), if not more. Hardware firewalls at the router and responsible use, maybe coupled to an anti-virus should be enough, most of the time. A good, up-to-date, off-line backup covers all other eventualities. Moreover, all the malware will sure be targetting 7+ machines, preferably those running x64.

This may be relevant: Reference: Windows XP Ram Limit posts #17 and 22 to the end. Obs: 0x1B2A51 for 5.1.2600.5512 becomes 0x1B3A51 for 5.1.2600.6387...

The GeForce 320.49 driver supports the series 700 boards, for XP, but not the 700M series. So, it's just a matter of adding to the .INF for XP the appropriate VEN= and DEV= entries one may copy from the .INF for, say, Vista or 7. And you probably can do likewise for the ATI board, too.

I know you know what you do. But so does daNIL. He was the one who 1st decided to provide the > 4 GiB address patch for XP. He gave up because of the problems with HAL.DLL. So that's definitive for me, and the issue with USB may be just the tip of the proverbial iceberg. So, with all due respect, forgive me for asking but, are you *sure* you used the right HAL from SP1? Remember there are actually at least 5 varieties of hal for XP, and the one selected gets renamed (actually copied to) HAL.DLL. Now, while the file name changes to hal.dll, the original filename in the properties tab remains untouched, so that, by looking at it you may find the original name of hal.dll. The definitive reference on the main builds of hall.dll is this, of course, but it does not cover the security updates and hotfixes. What you describe makes me think you picked the wrong hall.dll to start with. Of course, I may be wrong. But there's no harm in double checking, so please do it.