Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

5 Neutral

About silverni

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. More than virtual machines, Android emulators seems interesting to me, for a long series of reasons. Recent developments in individual computing almost exclusively concern mobile devices; the Windows desktop environment has long been a mature product, recent developments are dictated exclusively by ambiguous and dangerous marketing strategies, oriented exclusively to organizations. For a single user with sufficient experience, recent versions of Windows NT6-10 are in fact a regression in terms of usability, but above all in terms of security (this aspect would require a dedicated post). The world of Android mobile devices, on the other hand, is in a phase of chaotic evolution, new solutions and applications are constantly being offered, almost all the most recent applications presented in the Windows desktop world have an Android version. Conversely, Android is still unstable and presents greater potential risks than WinXP. Reproducing an Android system in a stable and familiar environment like WinXP has many advantages, for example: - become familiar with the world of mobile devices and available apps - check the operation of the system and applications in more depth than is possible using an Android hardware device. Greetings
  2. I currently do everything in WinXP. I created the mini-Win7 virtual machine for over a year, I started it only for testing and tuning, and the system was very solid. I'll probably need it sometime, and it's convenient to keep it ready. Certainly if I were to use the virtual machine over and over again it would be time to abandon WinXP, but for now I don't even see the need for it. The meaning of the thread is that the death of WinXP can be postponed indefinitely, in a future that is currently not predictable. I use VirtualBox 4.3.36 of 2016/01, the last officially supported and definitely working version in WinXP; for 5x the operation in WinXP should be verified, I did not find significant information on the Internet. As an operating system I only tested this mini-Win7, I don't expect I need more complete or modern systems. Among other things, the .vhd file can also be started autonomously from boot, as a secondary operating system for maintenance; and in reality this was the use envisaged by Wimb2, I believe the use as a virtual machine is my invention. I always try to use the minimum tool that allows me to achieve my goals. As a browser I almost always use NM27, the only one that supports the "Print pages to PDF" extension that I use a lot; more rarely I use portable NM28, or Firefox 52. I keep strictly away from sites that are too "trendy" or "experimental"; and in any case for the basic functions NM27 it is sufficient, for example I can download files and consult documentation on Github (and actually also works IExplorer6). As primary defense system I use secpol.msc, much more convenient than PSExec Sysinternals; settings can be changed on the fly and take effect immediately, no need to restart programs. I attach screenshot. Greetings
  3. My English is elementary, I hope you can understand what I say; and for this reason I write very little in the forum. I report my experiences that I think are interesting for all WinXP users. In WinXP I start VirtualBox, and then a virtual machine and a 4GB .vhd file that contains a minimum Win7 Ultimate system; from within the virtual machine I launch for example Palemoon MPC and Firefox Quantum. The 4GB Win7 .vhd file was created using Wimb's instructions on the Reboot.pro and 911CD.net forums. I post a screenshot. An Android emulator can overcome other WinXP limitations (Whatsapp, Skype, App of the banks, ...); until now I have used a minimal Youwave system; soon I will test more powerful emulators compatible with WinXP; some references: Bluestacks and BlueStacks Tweaker https://www.bluestacks.com/ https://bstweaker.tk/ Nox App Player http://en.bignox.com/ MEMU https://www.memuplay.com/it/ Greetings
  4. An ambiguous situation: - CertTrust.xml from Emet 5.2 is dated 15.03.04, and the rules expire on 16.08.01 - CertTrustUpd.xml by MicrosoftEasyFix51012.msi downloaded 16.01.15 is dated 15.09.02, however, the rules expire on 15.08.01 (that have already expired). Regards
  5. EMET 4.1 updated pinned rules https://support.microsoft.com/en-us/kb/2961016#/en-us/kb/2961016 You can download MicrosoftEasyFix51012.msi, which is updated periodically; at 16.01.15 contains CertTrustUpd.xml updated to 15.09.02. It even works in WinXP. It requires Emet is in the default path, in WinXP is: "C:\Program Files\Emet 4.1\" I installed in C:\Program Files\Emet\, just create a temporary copy to "C:\ProgramFiles\Emet 4.1\", the patch does not modify files but only Windows registry. You can also start the program under Sandboxie, when it comes to the final screen close the program with sandboxie; in "%temp%\Fixit_51012\" are available both operational files: import.cmd and certTrustUpd.xml Regards ----- Italian version, my english is basic EMET aggionamenti periodici regole di convalida https://support.microsoft.com/en-us/kb/2961016#/en-us/kb/2961016 Si può prelevare MicrosoftEasyFix51012.msi, che viene aggiornato periodicamente; al 160115 la versione prelevata contiene CertTrustUpd.xml al 150902. Funziona anche in WinXP. Richiede che Emet sia presente nel percorso di default, in WinXP è: "C:\Programmi\Emet 4.1\" Io ho installato in C:\Programmi\Emet\, basta creare una copia temporanea in "C:\Programmi\Emet 4.1\", la patch non modifica i file ma solo i registri. Conviene anche avviare il programma sotto Sandboxie, quando arriva alla schermata finale chiudere la procedura con sandboxie; in "%Temp%\Fixit_51012\" sono disponibili i due file operativi: import.cmd e certTrustUpd.xml
  6. Jaclaz, my english is basic, i'm non sure of automated translation. The suggested procedure can be useful for removing from the WinXP registers the POSReady hack, more conveniently than offline editing [HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady] "Installed"=dword:00000001 ==> Edit to 0 1. Close all programs 2. Create a backup set of registry with ERUNT or Registry Backup 3. Start a registry editor, and load the SYSTEM hive from the backup set created in step 2 4. In the loaded hive, put the Installed DWORD value to 0 5. Unload the hive 6. Run the registry restore and restart WinXP Regards
  7. Procedure to remove the PosReady registry hack from within XP, more convenient than offline editing 1. Close all programs 2. Create a backup set of registry with ERUNT or Registry Backup 3. Start a registry editor, and load the SYSTEM hive from the backup set created in step 2 4. In the loaded hive, put the Installed DWORD value to 0 5. Unload the hive 6. Run the registry restore and restart WinXP === Original for Jaclaz Procedura per rimuovere l'hack PosReady dai registri dall'interno di XP, più comoda dell'editing offline 1. Chiudere tutti i programmi 2. Creare un set di backup dei registri con EruNT o Registry Backup 3. Avviare un editor registri, e caricare l'hive SYSTEM del set di backup creato al punto 2 4. Nell'hive caricato, porre a 0 il valore DWORD Installed 5. Scaricare l'hive 6. Eseguire il restore dei registri e riavviare WinXP Regards
  • Create New...