2020. 2. 16. 06:00ㆍ카테고리 없음
64Gb Ram XP Patch here Found it on the internet,and unfortunatelly I lost the adress,but I've save it on my drive.Disclaimer I won't be held responsible for anyone bricking their OS by trying this.By downloading this patch,using it,and potentially destroying your XP because you didnt back up your boot.ini, you agree that is solely your responsability.Always do backups. Have an XP image at ready, backup your boot.ini in a text file,and be sure all your important data is safe.That being said, if one follows those steps carefully (btw,I chose second method-you only change the last line in the boot.ini), nothing can truly go wrong,and in the end, you're gonna have a nice SP3 running on 8,12,or 16 Gb RAM,according to your memory installed.I'm using it for a week everyday with no issues.And again, I think you guys are well versed in Windows,so it should be fine.Edited January 2, 2017 by liquidLD. You mean, over 4GB on 32-bit Xp?
The Sp3 is a hint to the 32-bit version.So, using the Pae, each task (or application?) can access its own 4GB, like in Server Windows, up to the 64GB Dram, is that it?yes, on 32 bit XP. It's my understanding that in a 32 bit PAE system,no app can acces more than 3-4 Gb, but the system can utilise in some manner all the memory available.So,even if one app cannot use,let's say,more than 3 or 4 Gb, the OS,as a whole can. And it's always good to have lots of memory.
Especially when you run many apps at once.edited for some grammar mistakes (not a native speaker) Edited January 2, 2017 by liquidLD. Oww, comeon, this horse has been beaten to death.Windows XP 'Gold' or SP1 has no issues with PAE (more than 4 Gb of memory), it was an artificial limitation introduced with SP2, there is a whole loooong thread dedicated to the matter and to the possible patches and to the issues that they may cause.:jaclazWhy would anyone use SP1 just to have PAE? Isnt it more appropriate to use the latest service pack and still have Pae support?As for 'Gold' something, sorry, I dont know about it. I just talk about what I know, my own experience.I saw some of the 'death beats',and they involve a lot of configs,and boot params. What I use is simple,very simple. I'm sorry to bore you, I understand you might not want this, but some,maybe they want.
I remember looking for ways to use 8Gb in XP a long time.Actually,it involves only copying the two files in C:/windows/system32/,and writing this in your boot.ini:boot loadertimeout=30default=multi(0)disk(0)rdisk(0)partition(1)WINDOWSoperating systemsmulti(0)disk(0)rdisk(0)partition(1)WINDOWS='Microsoft Windows XP Professional' /kernel=ntkl64g.exe /hal=hal64g.dll /fastdetect /PAE /noexecute=alwaysoffThats all. No fiddling around with ten billions parameters,and hacks,you know?edit man, thats a long messy thread. I'm gonna make a clear simple one, for the ones that might want it Edited January 2, 2017 by liquidLD.
After reading all that long complicated thread for achieving 'True Pae' on XP 32 bit, (sent to me by friend jaclaz after he saw the link I posted in another thread - just for the record) I decided to make this simple one, to achieve the same.The interface in the screenshots is localised,so if you need help,just ask. As always, your responsability if you follow my guide. BACKUP,FIRST.Here is the patch0. Copy hal64g.dll and ntkl64g.exe to C:/windows/system32/1. Go to Control Panel - System- Complex-Settings2. Click on Edit button3.
Windows Xp 32 Bit Iso
After backing up (or not) the default boot.ini in a file, delete all the text and paste this text:boot loadertimeout=30default=multi(0)disk(0)rdisk(0)partition(1)WINDOWSoperating systemsmulti(0)disk(0)rdisk(0)partition(1)WINDOWS='Microsoft Windows XP Professional' /kernel=ntkl64g.exe /hal=hal64g.dll /fastdetect /PAE /noexecute=alwaysoff.4. Save and reboot.Everything should be set up,and your Ram,all of it,should appear,and be available. Good luck.Edited January 2, 2017 by liquidLD. That's simply the Chinese patch which has been discussed over and over again and it may create some incompatibilities with USB drivers (as it has been discussed over and over again). There's another patch as well, which is the Russian patch, which achieves the same result as the Chinese one (same files), but includes some sys files from Windows Server 2003 x86 in order to avoid (well, at least, to limit) the USB issue discovered. I have been using the same method you posted for months, then I switched to the Russian patch 'cause I was too lazy to replace system files with the ones from Windows Server 2003 x86.@bluebolt. Yes, I think it should be merged to the other main topic too.