Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/23/2020 in all areas

  1. ******************************************************* * authroots.sst 2020-02-26 22:33 Roots * * delroots.sst 2019-08-21 22:44 Roots * * roots.sst 2019-07-23 23:27 Roots * * updroots.sst 2020-02-26 22:33 Roots * * disallowedcert.sst 2019-08-13 17:18 Revoked * ******************************************************* ******************************************************* * * * Roots Certificates * * * * successfully updated! * * * ******************************************************* ******************************************************* * * * Revoked Certificates * * * * successfully updated! * * * ******************************************************* Aby kontynuować, naciśnij dowolny klawisz . . . I wasn'tgetting into details what ahve changed, but it looks like update won't harm anyone, and might help :)
    2 points
  2. UEFI, that changes everything. I was thinking MBR, but in that case, all the EFI bootloaders should stay intact even if newer ones are added. I know that when I installed Debian on my Kaby Lake laptop, the old Windows 10 boot loader remained present and usable, and both grub and Windows Boot Manager were listed in the UEFI firmware's boot options. So you wouldn't need to restore anything, in all likelihood.
    1 point
  3. The reason why AutoIT EXEs get flagged is that the compiler uses UPX packing and this is what antivirus programs pick up on. So a lot of AutoIt programs will be flagged as malware or a virus just for being compiled. Imagine that some day some antivirus were to detect everything made by the Visual Basic compiler to be malware! https://www.autoitscript.com/wiki/AutoIt_and_Malware
    1 point
  4. I am pretty sure that Her Majesty the Queen wil be amused by this . Anyway, welcome on board . jaclaz
    1 point
  5. This simple script is the VBS way of renaming a file using Drag And Drop and changing the file name to one with using HourMinuteSecond.FileExtension for it new name '-> Object To Copy And Delete File Dim Fso :Set Fso = CreateObject("Scripting.FileSystemObject") '-> Run Time Varibles Dim FName, Nname '-> Check For Drag And Drop And Then Process A Single File If WScript.Arguments.Count = 1 Then '-> Get File So You Can Get It Path Set FName = Fso.GetFile(WScript.Arguments(0)) '-> File New Name Using HourMinutesSecomds.FileExtension Nname = Hour(Now) & Minute(Now) & Second(Now) & "." & Right(FName.Path,3) '-> Copy Drag And Drop File To It New Name FName.Copy(Replace(FName.Path,FName.Name,Nname)),True '-> Delete The Original Faile Fso.DeleteFile WScript.Arguments(0),True Else '-> For No File Or To Many File Error If WScript.Arguments.Count = 0 Then WScript.Echo _ "Drag and Drop One File On To This Script To Have It Function" If WScript.Arguments.Count > 1 Then WScript.Echo _ "To Many Files, This Script Can Process Only 1 File at a Time" End If
    1 point
  6. For MSFN icons issues with Opera: Disable webfonts in opera:config and download these font: https://msfn.org/board/applications/core/interface/font/fontawesome-webfont.ttf and https://msfn.org/board/applications/core/interface/font/icomoon.ttf and put them in your font folder. Restart Opera. A relevant old topic: https://msfn.org/board/topic/173621-strange-fonts-or-characters-opera-1202/#comments
    1 point
  7. Yes, this has been known for quite some time, however the original posts on it were removed following the June 2018 server crash, so allow me to post here how to get it working, since it requires special steps: 1. Download the 52.9.1 64 bit installer, linked on the list. 2. Extract it using 7zip. In the extracted folder, open the "core" subdirectory: 3. Download @blackwingcat's "Pemaker" program here. After downloading, be sure to run it as administrator, otherwise the following will not work. 4. After opening Pemaker, click the "English" checkbox, and then click on the "load" button on the main program window under the "main" tab. After doing this, browse to the "firefox.exe" file in the core subdirectory of the extracted 52.9.1 installer, and open it in Pemaker. After doing this, change the "OSVersion" and "SubSysVersion" values to 6.0 from 6.1: 5. After doing this, click on the "Save" button and save the file to a location different from the "core" subdirectory, such as your desktop. Repeat these steps for all .EXE files in the "core" directory. 6. After doing this, copy and paste all your modified .EXE files to the "core" subdirectory, replacing all original .exe files. 7. If you did everything correctly, you should now be able to run Firefox 52.9.1 ESR 64-bit just fine in Windows Vista! I will update the Firefox list entry to include this guide.
    1 point
×
×
  • Create New...