Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/07/2021 in all areas

  1. We only delete at a user request, a thread OP request or if there is something violating the forum rules. If you look, you can even find it is not against the rules to go OT, or talk about more than just the topic at hand in your post.
    2 points
  2. I'm not sure if aeroglass will be continued anymore. 1909 goes end of life in just 4 days, even with more modern cumulative updates for that version breaking aero glass. 2004 goes end of life in 7 months, so at this rate we may not get Aero Glass before 2004 goes end of life, meaning he would rather just skip the version if he comes back. I remember hearing about this project rising back in the Win8 days, sad to see it possibly stopping soon. I'm just assuming, he could come back and the project continues. Right now, we can call it an abandonded project.
    2 points
  3. @WalksInSilence , you're welcome . I do not know which country you're in , but I think it's not a problem to buy 4 used modules (Samsung or Hynix , even Elpida with Elpida chips is fine) for cheap . Just make sure the chips are "SEC" , marked with SEC (made by Samsung) , or Hynix. Samsung 16 GB (4x4GB) DDR3-1600 PC3-12800U , for example in Germany is about 45-57 Euro with VAT for 4pcs, should be minus 19% (if shipped to the States) , plus delivery. Better look for CL9 or CL10 , quite easy to find and it will be cheaper than those from "famous" brands. You don't need any cooling on the modules with 1.5v, BTW . I couldn't find a CL9 module picture , these ones are CL11 , but it should give you an idea how they look like . https://computerstoreberlin.de/media/image/product/288228/lg/samsung-16-gb-4x4gb-ddr3-1600-pc3-12800u-m378b5273ch0-ck0-312023.jpg https://computerstoreberlin.de/Samsung-16-GB-4x4GB-DDR3-1600-PC3-12800-M378B5273DH0-CK0-311679 Note SEC on the chips.
    2 points
  4. Many questions regarding making XP and Vista boot independently of each other arise because users face problems when one partition becomes corrupt or they format their active partition, not knowing they will lose the ability to boot their OS. Having independent boot would avoid this scenario. The reason they are dependent is because the boot files for both are stored on ONE and the SAME partition, which is your ACTIVE partition. Vista setup determines to put the boot files on the active partition, which is usually the XP partition since it's active at the time of install. I have come up with a way to boot the two independently with the use of a third "recovery partition." This recovery partition can be multi-purpose if you use BartPE. You can use it to boot XP and Vista, replace system files with patched ones, use disk management services to repartition, etc. (You can also use Windows PE or VistaPE as your recovery partition. You will have to add them to your BCD with bcdedit using the link in the last post about adding WinPE to HDD.) The benefit of this setup is if you hose your third partition, you can boot XP or Vista by making your XP partition active again with a BartPE CD. Requirements Three partitions. I recommend 600 - 700 MB for your third partition, in case you add other plugins/programs. Grub4Dos file called grldr. PE builder for making BartPE. System Setup There's no recommended system setup, but to give you an idea, here's my system setup. My XP partition on C:\ is the active partition, containing the boot files for Vista (C:\BOOT folder and C:\bootmgr). Vista is on D:\ and was installed from within XP. BartPE on E:\ is my recovery partition. If you haven't installed anything yet, then you may consider this setup. Instructions First, install XP to C:, Vista to D:, then BartPE to E:. Instructions for installing BartPE to a HDD partition can be found here: How to Install BartPE to Another Partition.The order in which you install doesn't matter for now. However, it is recommended to install XP first, then Vista, so you won't have to repair boot. If you are already dual-booting XP and Vista, then just install BartPE and continue. Make note which is your active partition if your setup is different. Check disk management. Remember, I'm assuming C:\ is active. [*]Boot to your recovery partition. [*]Copy Vista boot files from active partition to E:\ - Copy C:\BOOT folder to E:\ and C:\bootmgr to E:\. [*]Rename E:\bootmgr to E:\bootmgrv. (You don't have to do this if you are using BartPE, but doing this allows you to keep this one and C:\bootmgr straight; so when you create your menu.lst you know exactly which one is being used to boot Vista.) [*]Rename E:\ntldr to E:\bartpe. Note that this ntldr file should already be there and is not the same as the XP's ntldr. [*]Copy XP boot files to E:\ - Copy C:\boot.ini and C:\ntldr to E:\. [*]Rename E:\ntldr (the XP one) to E:\ntldrxp. [*]Create your menu.lst entries. See below for example. [*]Make E:\ partition the active partition. Sample menu.lst entries #Boot Vista using E:\bootmgrv title Windows Vista (bootmgrv) find --set-root /bootmgrv chainloader /bootmgrv #Boot Vista using C:\bootmgr title Windows Vista (bootmgr) find --set-root /bootmgr chainloader /bootmgr #Boot XP using E:\ntldrxp title Windows XP (ntldrxp) find --set-root /ntldrxp chainloader /ntldrxp #Boot XP using C:\ntldr title Windows XP (ntldr) find --set-root /ntldr chainloader /ntldr #Boot BartPE using E:\bartpe title BartPE (ntldr) find --set-root /bartpe chainloader /bartpe (NOTE: this is not a complete menu.lst; just the entries for items.) Reboot and grldr should load with your menu. The great thing is you can load XP/Vista with the boot files that you copied to E:\ or the ones on C:\. You can have double entries in menu.lst and both will work. If your XP partition becomes corrupt, then you can use boot files on E:\ to load Vista. You probably won't be able to load XP since its corrupt, right?? Haha. If Vista becomes corrupt, you can still load XP. If your recovery partition (BartPE) becomes corrupt, then you can load BartPE from CD, make C:\ your active and can load XP or Vista. Or you can fix your recovery partition the way it was. There are many possibilities with this. Good luck.
    1 point
  5. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210508-e29e57e-uxp-e7e63565e-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20210508-e29e57e-uxp-e7e63565e-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210508-e29e57e-uxp-e7e63565e-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210508-1eb6e649b-uxp-e7e63565e-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210508-1eb6e649b-uxp-e7e63565e-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.3a1.win64-git-20210508-1eb6e649b-uxp-e7e63565e-xpmod.7z Official UXP changes since my last build: - Issue #1767 - Prevent incorrect calling of network change detection function. (4e31a42b2) - Issue #1751 -- Remove XP_MACOSX conditionals from /dom (0dd3424f7) - Issue #1751 -- Remove XP_IOS (56da7e274) - Issue #1751 -- Remove XP_DARWIN (3d671e427) - Issue #1751 -- Remove files unused without XP_DARWIN (cd1f72413) - Issue #1751 -- Remove XP_MACOSX conditionals and support files from /gfx (616b39413) - Merge branch '1767' (b1eb04d3f) - Issue #1751 -- Remove XP_MACOSX conditionals and support files from /xpcom (1bf0734a7) - Issue #1751 -- Remove XP_MACOSX conditionals from /layout (aa0fd3d68) - Issue #1751 -- Remove XP_MACOSX conditionals from the rest of the tree. (6f707bde9) - Issue #1751 -- fix up a few stray #ifs (e7e63565e) Official Basilisk changes since my last build: - Issue #39 - Warn before opening many URI nodes in tabs (bdb17e6) - Merge pull request 'Warn before opening many URI nodes in tabs' (#40) from FranklinDM/Basilisk:issue-39-work into master (173ff3a) - Back-end branch pointer update. (e29e57e) Official Pale-Moon changes since my last build: - [SSUAO] Update Citi bank override. (4eb014170) - New cycle. (1eb6e649b)
    1 point
  6. What you say about the RAM usage is true. Interestingly, Mini Browser uses only a few hundred MBs when run on Windows 7. I think it has something to do with all these api-ms files you find in the browser's directory, because I ran filemon while I opened 360browser and found out that it looks for all these api-ms files that are missing from 360Browser but are present in MiniBrowsers directory. So I copied all these api-ms files over to the 360Brower's directory and when I opened it, it used as much RAM as MiniBrowser does, which proves to me that it's the api-ms files which need a lot of RAM. I'm not a programmer but I assume that these api-ms files are kind of replacement files for stuff that newer versions of Windows have, but older ones don't. But for some reason the guys from 360Browser were able to make it work on XP, without these api-ms files, even though the browser is looking for them.
    1 point
  7. i dont know i just found this topic today but i have a link to my sha2 updates for all windows versions archive in a topic above yours
    1 point
  8. Someone knows why 9th of May ? Why not the 8th ? Or any other date ? I noticed right away , just waited for someone to notice too.
    1 point
  9. I really haven't done that much with Mini Browser but I do agree that I am thus far not impressed with it. However - with only 2GB RAM in a 1-cpu VirtualBox, my 360Chrome uses roughly the same amount of memory as my Mypal v27.9.4 when playing a YouTube video.
    1 point
  10. Welcome back - don't be a stranger :)
    1 point
  11. Thank you for the clarification @Tripredacus @Dave-H and MSFN staff ~OT~ Hey @VistaEX how's it going? You enjoying life as best as can be given the state of the word? I try to get outside and get some fresh air, a struggle for me but I do what I can ... we all do! ~OT~ I'd bet a lot of us are so sick on thinking about this issue - I know I am. I will check out what you are offering. Thanks for your input and help re this topic. Take good care ~XPerceniol
    1 point
  12. Great Britain (that's what they taught us to call it during my school days) is a good country , indeed , let's hope it stays that way during these dark times . Though electronics is somewhat more expensive. Glad to be of help. BTW , these still can be overclocked in the BIOS , I even suggest to buy DDR3 1333 CL9 or DDR3 1066 CL7 and then change the settings in the bios , no need to add any additional voltage , just play with the settings . For example DDR3 1333 CL9 can work at 1600MHZ , but you shall need to up the timings , change to CL10 (if chips are ok , they won't require more voltage).
    1 point
  13. Thanks for the further advice, appreciated. UK BTW.
    1 point
  14. From February 8th, Roy said:
    1 point
  15. on mega you can see a folder named "replacement explorer" as the name suggests there you can find a different version of explorer that you have now replace the old one with this one in C:\Windows boot from the usb or dvd or whatever you have, open cmd, then notepad, then click on "save as" (make sure to change from seeing only .txt files in the right bottom corner on notepad) i had the same problem and thats how i got rid of it
    1 point
  16. Unfortunately, 4.6.0 having been the last version to officially support Server 2008 SP2, it seems unlikely that there will be any further .NET rollups for Server 2008 SP2 after April 2022. (Edit: ESU updates for .NET reportedly cannot be installed by non-customers anyway.)
    1 point
×
×
  • Create New...