dencorso

Kid Abelha - Garotos (interpolating RPM - Loiras Geladas, of which another excerpt is sung, together with the audience, at the end).

+1 I keep MS Updates disabled, so I only get them when I go explicitly to the MS Update site (and then use the Custom option). The log below shows the Nov 2013 Root Certificates were available again on Mar 19, a full week + 1 day after Mar 11 (which was Patch Tuesday)! I bet MS messed up bad with the March 2014 Root Certificates, and revoked them silently right afterwards. All other machines received the returning Nov 2013 after this month's patch Tuesday (because I didn't go to MSU site last month with the other machines).

But... let me understand this right: 1. ) You located the points to patch using the search hexstrings I provided, instead of fixed offsets, right? 2. ) You fixed the checksums, using pechecksum.exe (as recommended) or using modifype.exe, right? 3. ) You replaced usbport.sys by the one reccommended, right? 4. ) It worked, right? Your XP machine became able to see and access more that 4 GiB RAM, right? If all the above is right, please do post a new screenshot of the machine's My Computer's Properties, please. both 1 to 4 are "Yes". Then, congratulations! Now, was only because of your instigation that I came upon the idea of small unique search hexstrings unlike to change on localization as a method providing universal patches... and your success using them on a CHT version (which I did not investigate, all my work was done on the ENU version) constitutes the proof-of-concept for this method. So thanks! Now, as for your BSOD: if your debugging is right (and I do think it is), then the problem is solved for now. Let at least one week of intensive use pass before putting VPCNetS2.sys back. If no other BSOD happens, I think you can consider VPCNetS2.sys really was the source of the problem. In that case, maybe searching for a later, newer version of that file might be in order. Let's wait and see. Of course, please do keep me posted on what happens next, OK?

+1. Business as usual.

But... let me understand this right: 1. ) You located the points to patch using the search hexstrings I provided, instead of fixed offsets, right? 2. ) You fixed the checksums, using pechecksum.exe (as recommended) or using modifype.exe, right? 3. ) You replaced usbport.sys by the one reccommended, right? 4. ) It worked, right? Your XP machine became able to see and access more that 4 GiB RAM, right? If all the above is right, please do post a new screenshot of the machine's My Computer's Properties, please. Now... You've got a crash. Was it a BSOD? Was it a Black Screen? Was it a Full Freeze? Or did the machine just turn off? And what exactly were you doing at that precise moment? Please do bear with me, my crystal ball is out on the shop, for tunning (again!).

There are two unofficial 9x versions, very slightly different one from the other: bearwindows' and Tihiy's. Since you've gone this far, you should e-mail bearwindows (he almost never reads PMs) or PM Tihiy to figure how to get the results bearwindows has posted. It should be a matter of detail. I'm sure they'll get back to you and help. And then you could write a how-to, because it isn't easy, and SNAP is bound to become more and more needed (same holds for SNAP audio).

I'm sorry, but, with all due respect, I have not time nor interest in studying any localized versions (BRZ included). Nor do I have your specific localized (CHT or CHS, I guess...) files to study, in case I found some time to do it. If you grab the ENU version and compare it with the localized one, you'll surely find out the correct offsets. Good luck! BTW, IDA offsets are for the loaded executable, whereas the patching offsets refer to the binary file image before it's loaded, which can be found instead with an hexeditor. Moreover 0x75 means jnz, so the last of the 4 calls shown in you post cannot be the correct place to patch (because it contains no jnz). OK. Get yourself an hexeditor capable of hexstring searching and search for 0x3C017507B8 (for the 1st patch) and 0x3C01751B39 (for the 2nd one). I bet you'll find one occurrence only of each string, even in your localized version, and, if so, then just patch the 0x75XX to 0x9090 in each string, as required. Disclaimer: I guarantee nothing and you agree that whatever you do you do by your own decision and accept all responsibility for the results from your actions. Much later additions: For halmacpi.dll, the hexstring to search for is 0x537417803D (and once found, then patch the 0x74 to 0xEB). These hexstrings ought to be unique (= appear just once in the executable file one intends to patch), and should be universal (= exist in whatever localized version one is intending to patch). HTH

Right thread, but outdated post. This is the current one. Now, a little contribution: halmacpi.dll 5.1.2600.5574 (xpsp_sp3_qfe.080402-1256) from KB951126 => Patch at 0x17813 (same offset in 5574_qfe as in 5512). ntkrpamp.exe 5.1.2600.6419 (xpsp_sp3_qfe.130704-0421) from KB2859537 ==> Patch at 0x15EF1A & 0x1B3A51 (offsets in 6419_qfe do differ from those in 5512). usbport.sys 5.2.3790.5203 (srv03_sp2_qfe.130720-0956) from KB2862330 is also required, but needs no patching. Of course, all the above offsets are for the ENU versions of the files mentioned. I strongly recommend using the reliable n7epsilon's pechecksum.exe v. 1.4 for the mandatory checksum correction.

I don't really think this is true. I've been able to run Windows 95 on a Celeron 353 M @ 900 MHz with no problems. I do sometimes get a BSOD when I reboot after making a lot of configuration changes, but it's not that common.True it is. But that has been solved by LoneCrusader, since then: Windows 95 2.1GHz CPU Limit BROKEN! This is the second time the answer to your question is easily findable in the Important / "Stickified" / Pinned Windows 95/98/98 SP1/98 SE/ME Topics sticky, which you should read... Sort of... The unofficial SNAP driver should solve both your graphic and sound problems... here's the unofficial SNAP FAQ may be handy. The UniVBE entry at the English Wikipedia may be relevant, too.

Welcome to MSFN! LoneCrusader, BenoitRen and Andrew T. are our resident authorities on 95. I'm sure LoneCrusader will interact with you soon, given the project you're pursuing. I'll see whether I can find the files you're looking for, and post back.

Sfor: Asus Eee PC and Windows 9x

At least one POSReady2009 hotfix is known to install without any modifications on XP SP3: KB2878379-v2 (which contains Winlogon and Licdll v. 5.1.2600.6436)...

Are there any useful parts in them? You sure?

Of course it can be done, in case someone cares to ever do it. It's, however, much easier to convert Microsoft Windows Server 2003 Datacenter x64 Edition to a Workstation, and there's a sub-forum here dedicated to it (there used to be one specific to 2k3, BTW, which should still be around).

No. It's more complicated than that: IMO igxp32.inf in all 544x versions of the intel driver is botched. Problem is that it was botched when support to the Haswell was added, so that there is no good driver for the Haswell at all. Now, the reason nobody came out with a driver after your requests here and elsewhere is that most people who have Haswells don't care for XP (which MS and intel are doing their best to kill, to no avail), and most people who care for XP and have the necessary know-how to correct that .INF don't have a Haswell to test any mods, so they cannot do it properly and, hence, direct their skills to tasks they can accomplish properly and can benefit from (of course). So, you see, it's kind of a Catch-22 situation. That said -- provided you undertake to test whatever modded files are give you, bearing in mind they can leave you with a non-functional video and, in the worst case, cause a reinstall, *and* agree to do it without putting *any* pressure on people who'll be doing it in spare time they really don't have, just for the sake of the challenge -- there may be people willing to try modding the .INF, although, even so, there may not be anyone available right away... In any case, please do tell us what are you using as a graphics driver at the moment? The standard supervga? The default VGA? A scrennshot of the device manager window with the display drivers expanded and the window given by the properties option on the right-click menu of the active display driver, with be driver tab selected, would be much welcome as well (see attached example).

I'll keep using XP for sure (and I still use 98SE, too)!

Simon & Garfunkel - The Sounds of Silence

FYI, they've blocked some forms of MS urls, per robots.txt, but forgot to do so for many others. Last year they've updated their robots.txt, and a lot more of their formerly saved materials went down the memory hole. But there usually are many different forms of urls that lead to the same page at MS, and some have escaped their sanitizing up to this day. So, yeah: grab it while it's still there.

There are 4 things I couldn't care less if I tried real hard: Netflix, Facebook, Twitter, and computer gaming in general. And make no mistake: I love plaing cards (real cards, preferably made from waxed stock-paper) and shooting pool (= pocket billiards).

I don`t hijack this forum. When you can`t find drivers you have no more choice. I can contrbute only with help, in Romania a salary/month is 250 euro, I don`t have enough money for donation to help this forum. @erkange: As @j7n say, you can use a videocard with xp drivers. While donations are much welcome, they're strictly voluntary. Nobody has to donate anything in order to participate. MSFN is free. When one cannot find drivers, one still has many choices: one is buying a videocard, another is selling the board with the haswell and buying a slightly older one with an IvyBridge (like the Asus P8Z68-V LX, which has XP drivers even for USB 3.0!): all this and one still pockets some money in return, because the older board+processor costs less than his/her current board+Haswell. You're in Romania? I'm in Brazil. I'm not sure who's been dealt the better hand by destiny, but being in the EU may be an advantage. The info below is still about right:

Ditto! Best wishes!

The problem is *not* Win XP (either SP1 or later)... The problem is FileZilla. So, with all due respect, do move over to WinSCP, and forget about it.

Read the whole sticky and *all* the links offered thereof at least twice. Then you'll be up to date on the matter.

Long live XP!

7zip cannot, but cabarc sure can.