Multibooter

@NotHereToPlayGames You can install PCMark04 and PCMark05 side-by-side, i.e. no need no uninstall PCMark05 if you install PCMark04.

You can find it at https://archive.org/details/pcmark-04-v-130-installer

I tested the Inspiron 7500 again, with the preceding PCMark04. The Inspiron 7500 is not an old timer yet, i.e. older than 30 years, the Inspiron 7500 was made in 2000. Eventuall the Inspiron 7500 might be compared, except in monetary terms, to a 1908-1927 Ford Model T, https://en.wikipedia.org/wiki/Ford_Model_T PCMark04 showed a similar behaviour to PCMark05: when the 3D test started the screen turned black for a long time. Luckily I needed to do something else and when I came back to the laptop after about 30mins all on a sudden the screen turned on and testing continued, displaying 3D bricks falling down a staircase, very slowly, frame by frame. The whole test completed successfully after maybe four hours. Physics calculation and 3D was 0.405fps. Overall score was 568. I will repeat the test of the Inspiron 7500 with PCMark05 as an overnite job, and will not pull the plug when the screen stays black for a long time.

Thanks, I'll take your word for it. I have never used MU/WU. I have found this final Windows Media Player v11.0.5721.5262 by looking at https://web.archive.org/web/20190615000000*/http://download.microsoft.com/download/0/9/5/0953E553-3BB6-44B1-8973-106F1B7E5049/wmp11-windowsxp-x86-enu.exe and then looking for the most recent BLUE capture which did not load a 404 page. The download starter of the last OK capture on 28Aug2019 is https://web.archive.org/web/20190828083947/http://download.microsoft.com/download/0/9/5/0953E553-3BB6-44B1-8973-106F1B7E5049/wmp11-windowsxp-x86-enu.exe and the actual download link is https://web.archive.org/web/20190828083947if_/http://download.microsoft.com/download/0/9/5/0953E553-3BB6-44B1-8973-106F1B7E5049/wmp11-windowsxp-x86-enu.exe I have never really used Windows Media Player. Instead, I like a rare hacked, portable Korean version, with some English localization, of PotPlayer v1.4.19843 (6May2009), it works great under WinXP and Win98, and is probably the best video viewer for Win98.

I am still new to benchmarking, where did you get the test results from? Isn't 730 better than 203?

@AstroSkipper I love your topic, it reminds me of a pinewood derby, at the Boy Scouts, https://en.wikipedia.org/wiki/Pinewood_derby , great fun to compete. Below are the PCMark05 results for an old Inspiron 7500 laptop (650Mhz Pentium 3 SSE-only). Unfortunately no overall PCMark score was generated. When PCMark05 started its 2nd test, "Physics and 3D", WinXP CRASHED with a black screen, I had to pull the plug, tried three times. The 8MB AGP 2x graphics card in the laptop apparently does not work with all tests of PCMark05. After de-selecting the "Physics and 3D" test, PCMark05 completed the test OK, without crashing the computer, but no overall scores and graphics scores were calculated. I then ran PCMark05 on an old desktop computer, which has also MS-DOS and Win98SE installed. The HDD inside is a 17-year old 7200 rpm 250GB IDE HDD. It has a Geforce 7800 graphics card inside, but the only reason why I don't use the onboard graphics is that the card has a DVI-D connector for a modern monitor. Below are the PCMark05 results. Currently @UCyborg is the leader with a PCMark Score of 11,147 The window title of my screen shots is "PCMark05 - Professional Edition". The registration code by chip.de is only for the Advanced edition. You can upgrade from the Advanced Edition to the Professional edition by right-clicking on "PCMARK"-> Unregister PCMark05 -> Register and then enter the registration code of the Professional edition. The main benefit of the Professional edition is that you can export the test and diagnostic results into Excel, works fine with Excel 2003. @AstroSkipper BTW, my ancient version of Kaspersky has flagged the installer "PCMark05_v120_1901.exe", obtained from your download link, as riskware. "detected: riskware not-a-virus:WebToolbar.Win32.Asparnet.dnq file: Z:\PCMark05 v1.2.0 (26Sep2008)\PCMark05_v120_1901.exe//AskInstallChecker.exe" When you extract the installer "PCMark05_v120_1901.exe" with UniExtract, data1.cab and data2.cab contain AskInstallChecker.exe, file modification date 15May2009. PCMark05_v120_1901.exe is 92,260kB, is digitally signed OK 3Feb2010 and contains in turn PCMark05.exe, digitally signed OK 26Sep2008, The original installer of v1.2.0, "PCMark05_v120_installer.exe", is digitally signed OK 16Nov2006, is only 88,531kB and does not contain the riskware "AskInstallChecker.exe" in data1.cab and data2.cab. "PCMark05_v120_installer.exe" is a hard to find file, and can be downloaded at https://ds-servers.com/gf/pcmark-2005/windows/v120/pcmark-05-full-install-v120.html [click on the big green Скачать button, looks like "CKaYaTb"]. The 1st installer window of the original "PCMark05_v120_installer.exe" displays "v1.2.0", while the installer window of the riskware "PCMark05_v120_1901.exe" displays "v1.2.2". After installation, both builds indicate "v1.2.0" in their About windows. "PCMark05_v120_1901.exe" is an example of the last version for WinXP not necessarily being the best version for WinXP. Below is a screenshot from "PCMark05_v120_installer.exe", i.e. the original version of 16Nov2006 without the riskware. The scores are quite similar. Question: I did not have Windows Media Player installed on my computers before this topic, and PCMark05 requires Windows Media Player 10 or higher. Is there a better/more recent version of Windows Media Player than v11.0.5721.5262 of 30Jan2009 for WinXP SP3?

@modnar I have added your registry fixes to the download links near the beginning of this topic This posting incl.screenshots was archived at http://web.archive.org/web/20240909175949/https://msfn.org/board/topic/186405-sandboxie-under-windows-xp/page/3/ The screenshots in this posting were subsequently deleted, to preserve image posting space - 9Sep2024 I have also tested both of your SCSI fixes (initial and revised) with two different SCSI devices under Sandboxie v5.22 on an old Inspiron 7500 laptop (650Mhz Pentium 3, SSE-only, 512MB RAM). SCSI device 1: an Iomega 1GB jaz drive, connected with an Adaptec 1480 SCSI CardBus PC Card SCSI device 2: a 2TB laptop HDD, WD20 SPZX 5400 rpm SATA, inside an eSATA+USB 2.0 Sharkoon docking station connected via eSATA to an eSATA PC Card The test results of the two SCSI fixes (I refer only to the SCSI fixes!) were a big surprise: 1) The Iomega SCSI jaz drive actually performed slower with your SCSI fixes than without the fixes, against all logical expectations. Without a SCSI fix: 13:34 mins With the initial SCSI fix 13:53 mins [GroupOrderList_SCSI_Class_2d_XP_USP4.reg] With the revised SCSI fix: 15:06 mins [GroupOrderList_SCSI_Class_03-2d_XP_USP4.reg] without a SCSI fix with the revised SCSI fix 2) The second SCSI device (the 2TB SATA HDD connected via an eSATA card), on the other hand, performed faster with the revised SCSI fix, as expected. Without a SCSI fix: 15:02 mins With the initial SCSI fix: 15:58 mins With the revised SCSI fix: 13:55 mins [subsequent 2nd attempt with the revised SCSI fix: 13:16mins] Given these contradictory test results, the speed improvements of the SCSI fixes seem to depend on the specific SCSI devices used. What is also interesting is that the virus-checking was faster on an old Jaz drive+Adaptec 1480 SCSI PC Card (13:34 mins) than on a more recent 5400 rpm SATA HDD+eSATA PC Card.(15:02 mins). Tentative explanation: Kaspersky Anti-Virus had signaled several read errors on the initial test attempts with the old Jaz drive, but after repeating the test 2 or 3 times, no more read errors were signaled by Kaspersky Anti-Virus. Also interesting is the substantial time difference when repeating a test with the same SCSI fix, e.g. repeating the test with the revised SCSI fix (13:55 mins with the 1st attempt, 13:16 mins with the 2nd attempt), under identical conditions. No idea whether the time difference was caused by Sandboxie, by Kaspersky Anti-Virus, or by something cached outside of the sandbox. Below is the methodology used for the tests: A sample of 10 infected files, on two different SCSI devices, was virus-checked with my sandboxed ancient version of Kaspersky. Six virus-checks were made, on two different SCSI devices, without a SCSI fix, with the initial SCSI fix and with the revised SCSI fix. The time required by the virus-checks indicates the efficiency gained when running a sandboxed program with modnar's SCSI fixes. Step 1) Creation of sandbox "Kaspersky" I had installed my ancient version of Kaspersky into a new sandbox called "Kaspersky" [i.e. -> right-click on the installer .exe -> Run Sandboxed -> select the previously created, empty sandbox "Kaspersky"] Step 2) After the installation and customization of my ancient version of Kaspersky I created in the Sandboxie Control Panel a desktop shortcut to I:\Sandboxie\Start.exe /box:Kaspersky "I:\Documents and Settings\All Users\Start Menu\Programs\...lnk Step 3) I then ran Kaspersky with this shortcut into the sandbox and updated Kaspersky Anti-Virus online Step 4) In the sandbox folder M:\Sandbox\ I created a copy of the sandbox M:\Sandbox\Kaspersky\ and renamed it to \Kaspersky_ori\ Step 5) I then ran the sandboxed Kaspersky Anti-Virus on the sandboxed sample of 10 infected files. Step 5 was repeated for the six combinations of two SCSI devices with/without SCSI fix. After each test run I deleted the previously used sandbox \Kaspersky\ and then restored the original sandbox by copying \Kaspersky_ori\ to \Kaspersky\. The reason for restoring the original sandbox \Kaspersky\ before the next test was that Sandboxie would create a copy of the infected files, log files, registry entries etc in the sandbox \Kaspersky\ during the running of sandboxed Kaspersky Anti-Virus. In other words, each of the 6 efficiency tests of modnar's SCSI fixes started in an identical sandbox \Kaspersky\

Registry Trash Keys Finder is a tool which can find registry entries left behind after the un-installation of a program. Some programs, e.g. Total Uninstall, leave flags behind to make the re-installation of the same build past the trial period more difficult. Registry Trash Keys Finder also lists MUICache entries. Where did all these trash keys come from? About 43 trash keys (=210 minus 167) were MUICache log entries created in the sandbox when I was test-running sandboxed 43 different .exe files. For each .exe file run in a sandbox, Windows creates a MUICache entry in the sandbox. Running these 43 .exe files in a sandbox did not leave trails and junk in the normal registry. One of the uses of Sandboxie is to avoid trails and bloating of the registry with MUICache log entries. When Registry Trash Key Finder is run in a particular sandbox, it can quickly list the .exe files which were run in the sandbox, until the sandbox is deleted. [The screenshot was deleted, see note above]

Yes, running 2 instances of Kaspersky simultaneously was for experimenting. I have, for example, also experimented with Registry Trash Keys Finder and ran v3.9.2 and v3.9.4 simultaneously in 2 different sandboxes of Sandboxie v5.40, side-by-side. The purpose of running the 2 versions side-by-side was to compare v3.9.2 vs v3.9.4, because the two versions indicate a slightly different number of trash keys when run normally (i.e. outside of a sandbox). By chance I noticed that v3.9.4, when run normally (i.e. outside of a sandbox), displays 167 trash keys (see bottom left corner of screen shot), but when the same v3.9.4 is run in my Default sandbox 210 trash keys are displayed. Maybe the additional trash keys in the Default sandbox were leftovers of previous test-runs in the Default sandbox. These additional trash keys in the Default sandbox show that it may be useful to empty a sandbox. When run in a 2nd, rarely used sandbox, 168 trash keys were displayed. [The screenshots of Registry Trash Keys Finder were deleted, to make space for other image uploads The posting with the screenshots, before the images were deleted, can be viewed at http://web.archive.org/web/20240904132535/https://msfn.org/board/topic/186405-sandboxie-under-windows-xp/page/3/#comments ]

Here some good sites for downloading old versions of Sandboxie: https://web.archive.org/web/20170601000000*/http://www.sandboxie.com:80/SandboxieInstall.exe [best, only combined 32+64bit versions] https://web.archive.org/web/*/https://www.sandboxie.com/attic/* [32bit, 64bit and combined versions] https://sandboxie-website-archive.github.io/www.sandboxie.com/AllVersions.html [seems to be the same as https://web.archive.org/web/20200310035403/https://www.sandboxie.com/AllVersions ] Maybe this helps identifying the last good versions for various old operating systems.

The information about the last version of Sandboxie for Windows Vista 32bit and 64bit is contradictory. 1) David Xanatos has indicated in his changelog for v5.44 of 3Nov2020, as you noted correctly: "removed support for Windows Vista x64". I initially also assumed that the preceding build, v5.43.7 (3Nov2020) was the last version working OK under Windows Vista x64. Windows Vista 32bit is not mentioned in the changelog. https://github.com/sandboxie-plus/Sandboxie/releases?page=16 BUT: When I test-ran the subsequent v5.44 installer under WinXP I got the following err msg: Maybe David Xanatos wanted to indicate in the changelog that he wasn't supporting Vista after v5.43.7 anymore? Or did he just forget to remove "Vista" from the err msg? The last build where the installer err msg displays "Windows Vista" is v5.64.1 Classic, v5.64.2 does not display Vista anymore. 2) WinClient5270 indicated in his topic https://msfn.org/board/topic/175262-last-versions-of-software-for-windows-vista-and-windows-server-2008/ the last version for Windows Vista is "Sandboxie 5.33 (FREE, CS, UNS) Download here" "List (valid as of Oct. 9, 2022 [i.e. 2 years after the changelog posting above for v5.43.7 by David Xanatos])", "[Unsupported UNS - Not officially supported on Vista, but still works]" 3) David Xanatos also indicated the requirements to run Sandboxie: "Windows XP SP3 (Up until Sandboxie 5.22 and solely in v5.40) Windows Vista SP2 (Up until Sandboxie 5.22)" https://sandboxie-plus.com/sandboxie/frequentlyaskedquestions/ Does the not-mentioning of v5.40 for Vista mean that v5.22 is the last version for Vista? Wikipedia indicates "Windows XP SP3 and Windows Vista SP2 were supported [=by Sophos] up to version 5.22, after which their support [=by Sophos] was dropped." https://en.wikipedia.org/wiki/Sandboxie v5.22? v5.33? v5.43.7? v5.64.1? or maybe v5.40.1 [the corrected 32bit and 64bit versions, not the special XP version v5.40]? for both Vista 32bit and 64bit? Unfortunately, I don't have Windows Vista on my computers (yet). Do we have any users of Sandboxie under Vista? As I mentioned at the beginning of this topic "Postings about Sandboxie under other older operating systems (e.g. Windows Vista) are also welcome."

Welcome to this topic and thanks! Supermium 121 (2Feb2024) now runs fine in a sandbox with this Sandboxie setting. I have updated the listing of compatible applications. When exiting Supermium, however, red dots remain in the Sandboxie icon in the System Tray.

The screenshots below show the major issue of virus-checking with Kaspersky installed into a sandbox: 1) You canNOT select in the normal Windows Explorer the specific subfolders or files to be virus-checked. Kaspersky can only check whole partitions etc. For selecting files and folders for virus-checking you have to select the items in the Windows Explorer context menu. When Kaspersky is not normally installed, but installed into a sandbox, then Windows Explorer will NOT display a content menu entry "K scan for viruses". I have created a .reg file with 5 registry patches to display in the normally run Windows Explorer a content menu entry "K scan for viruses". pointing to shellex.dll in the Kaspersky folder in the sandbox, even if Kaspersky was not normally installed. The Windows Explorer context menu did then display a content menu entry "K scan for viruses". but it stayed greyed out. I fiddled around with OpenPipePath and OpenFilePath entries in Template.ini, but I couldn't establish a communication between the context menu entry in the normal Windows Explorer and the sellex.dll in the Kaspersky sandbox. Maybe the 5 registry entries were wrong, or the parameters in the OpenPipePath entry in Template.ini were, or you just cannot do it. This demonstrates that if an application does not install and run immediately in a Sandboxie sandbox, it may require very profound knowledge to get it going. This explains also the huge size of Template.ini, with the many customized holes and settings for many applications. 2) When you right-click on a partition in My Computer and select in the context menu -> Run Sandboxed -> select the sandbox with Kaspersky, you can browse to the folders/files to be virus-checked. The context menu will then display OK "K scan for viruses". The virus-checking, however, has big issues: - it it inconvenient to have to open an extra sandboxed Windows Explorer window for virus-checking - the stuff to be virus-checked will be copied into the sandbox and remain there, even after having exited Kaspersky. You now have a copy of potentially infected stuff. - the virus-checking with Kaspersky installed into a sandbox is very slow, maybe an issue for the Pentium 3, maybe less so with a more recentcomputer. - the many bugs of Sandboxie are added to the few bugs of Kaspersky For several special uses, however, installing Kaspersky into a sandbox may be quite useful (e.g. obtaining quickly additional signature updates for one-time-update trial versions, for comparing downloaded signature updates, for comparing updates of the same Database Release Date with vs. without updating application modules [=updating the installed software build]. Running two instances of Kaspersky simultaneously side-by-side I tried to run on the Pentium 3 laptop two instances of Kaspersky side-by-side (one in sandbox Kaspersky with the signatures of 9Aug2024, the other in sandbox Kaspersky_2 with signatures of 10Aug2024). Only the instance which was loaded first would run. When I selected the 2nd instance in the System Tray, the same Kaspersky came up, even if 2 Kaspersky icons were displayed in the System Tray. When I clicked on -> Exit of one of the two Kaspersky icons in the System Tray, both Kaspersky icons disappeared but the red dots in the Sandboxie icon remained, i.e. one instance of Kaspersky was still running but you couldn't access it via the System Tray anymore. Again, running 2 versions of Kaspersky consecutively works Ok, but 2 versions of Kaspersky canNOT be run simultaneously side-by-side.

The screenshot below shows my ancient version of Kaspersky, installed into sandbox Kaspersky_2, while virus-checking.

The screenshots below show the "Update completed successfully" windows in sandbox "Kaspersky" (9Aug2024) and in sandbox "Kaspersky_2" (10Aug2024).

Thanks, I had forgotten about the size 2MB limitation. I am also reducing the size of the screenshots to be uploaded. Sandboxie v5.22 and my ancient version of Kaspersky Update on 22Feb2025: screenshots were removed from this posting, because of limited upload space. The page showing the screenshots was archived at https://web.archive.org/web/20250222143024/https://msfn.org/board/topic/186405-sandboxie-under-windows-xp/page/2/#comments I have installed, updated and run my ancient version of Kaspersky in 2 separate sandboxes of Sandboxie v5.22 on a 24-year-old Inspiron 7500 laptop (650MHz Pentium 3 SSE-only, 512MB RAM) under WinXP SP3. The findings below apply only to Sandboxie v5.22, not necessarily to v5.40 (SSE2) by David Xanatos, and only to the virus-checking features of my ancient version of Kaspersky, not to the protection components, which I have not installed. I first created 2 additional sandboxes, "Sandbox Kaspersky" and "Sandbox Kaspersky_2". as shown in the screenshot below of "Sandboxie Control", Another screenshot shows the content of the folder "M:\Sandbox\", which contains the 3 sandbox folders of Sandboxie and renamed backup copies of the sandbox folders. "Copy of Kaspersky_after_customization" is the a renamed copy of "Kaspersky" with the installed and customized trial version which has not yet been updated, the Update button is still ungreyed [=functional, 1 update is possible], size: 166MB. "Copy of Kaspersky_updated_9Aug2024" is a backup copy of "Copy of Kaspersky_after_customization" after updating the signatures. It was created by making a copy of "Kaspersky" after the successful update, size: 927 MB. After the update the Update button turned greyed out [= no more updates possible]. "Kaspersky_2" was initially created as a copy of "Copy of Kaspersky_after_customization", i.e. the Update button is still ungreyed [=functional, 1 update is possible]. On the next day "Kaspersky_2" [with the functional, ungreyed Update button] was updated. After the update the Update button turned again greyed out [= no more updates possible], size 1.24GB (much larger). A binary compare with Beyond Compare of "Sandbox Kaspersky" vs "Sandbox Kaspersky_2" indicates that temporaryFolder was 391MB larger, maybe I should have used a different Update folder location for the update of 10Aug2024 (see screenshot below). The old Pentium 3 laptop now contained two functional Kasperskys under the same WinXP. "Sandbox Kaspersky" contained Kaspersky with the signature updates of 9Aug2024, "Sandbox Kaspersky_2" contains Kaspersky with the signature updates of 10Aug2024, i.e. with updates of the following day.

1) Thanks. Did I understand right that you would leave the two Tag values for dmboot and i2omgmt unchanged? 2) I have installed your registry fixes for Sandboxie on 2 computers and both work fine (on an SSE-only Pentium 3 laptop with v5.22 and on an SSE2 Pentium dual-core desktop with v5.40). BTW, the original installers of both v5.22 and v5.40 install "DependsOnService" instead of "DependOnService" [no "s"]. Removing the "s" is a bug fix, do you have any details of the bug, before the fix? David Xanatos has also referred to "DependOnService" [no "s"] in his posting on 10Jan2022 https://www.wilderssecurity.com/threads/sandboxie-plus-1-0-7.443250/page-2 3) I have added your registry fixes to a posting near the front of this topic, thanks .

@modnar Thanks for your instructions. My old Inspiron laptop (650MHz Pentium 3, 512MB RAM, Sandboxie v5.22) can definitely use efficiency improvements. 1) I have run GroupOrderList_Filter_0B_XP_USP4.reg and GroupOrderList_SCSI_Class_2d_XP_USP4.reg to update the values of Filter and SCSI Class. I did not run GroupOrderList_Primary_Disk_05_XP_USP4.reg because Primary Disk had already the same value as in the .reg file. 2) CurrentControlSet/Services/dmboot has the Tag value 0b (11) and CurrentControlSet/Services/i2omgmt has the Tag value 2d (45). Should they be changed, and if so, to what value?

Mypal68 v68.13.8b (7Jan2024) is a special build for SSE-only by feodor2 and works great on my 24-year-old Inspiron 7500 laptop (650MHz Pentium 3, 512MB RAM) under WinXP SP3. It does not run under WinXP SP2. Mypal68 v68.13.8b is slower than New Moon 28 and Serpent 52 by roytam1 because it is based on more recent Firefox 68, which is more resource intensive than earlier versions of Firefox. New Moon 28 is my main browser on the SSE-only Pentium 3 laptop, but Mypal68 v68.13.8b by feodor2 is just as essential, it can load websites which New Moon 28 and Serpent 52 by roytam1 cannot load. The COMBO of New Moon 28+Serpent 52+Mypal68 makes an old Pentium 3 computer still quite useful. All 3 work well inside a sandbox of Sandboxie v5.22 under WinXP in an SSE-only computer. The corresponding SSE2 versions of Mypal68 by feodor2 and of New Moon 28 and Serpent 52 by roytam1 also work well in a sandbox of the special edition for WinXP by David Xanatos of Sandboxie v5.40 in an SSE2 computer. Below is a screenshot of the About screen of Mypal68 v68.13.8b (7Jan2024) by feodor2, during sandboxed web browsing on an SSE-only computer under WinXP SP3, in a sandbox of Sandboxie v5.22. Sandboxie indicates that Mypal68 is running in a sandbox by displaying a yellow line around the window. Also, the window title is embedded between "#" signs.

Thanks for your tentative recommendation. It is very reasonable to assume that the sandbox of a specialized sandbox software is better than a sandbox added as another feature to a general anti-malware program. Also, Sandboxie v5.22 (by Sophos, last version for SSE-only) is of 30Oct2017 and Sandboxie v5.40 (by David Xanatos, SSE2) is of 9Apr2020, while Avast Antivirus 2015 v10.3.2225 Premium is of 28Jul2015. The actual testing of the effective protection provided by a sandbox, by actually running a huge amount of infected files in the sandbox, looks like a major project.

Thanks for the info about issues of Sandboxie under WinXP and with FAT32. I have installed WinXP on a FAT32 partition for compatibility with Win98 and because I prefer the folder dates of FAT32 to the folder dates of NTFS. My main security-related use of a sandbox is for checking out/test-running malware etc, to see whether it is really malware or something useful. Avast Antivirus 2015 v10.3.2225 Premium (28Jul2015) works OK under WinXP and SSE-only and has a HDD-based sandbox feature, i.e. no major RAM requirement. If you had to run malware under WinXP, with no Anti-Exploit software running in the background, would the Avast Antivirus 2015 sandbox be safer or the Sandboxie sandbox?

Sandboxie before registry fixes - GroupOrderList - SCSI Class Sandboxie v5.40 SSE2 on top Sandboxie v5.22 SSE-only at bottom [Pictures were deleted since problem was RESOLVED with registry fixes by modnar, see under posting: Version history Page with pictures was archived at https://web.archive.org/web/20240808195712/https://msfn.org/board/topic/186405-sandboxie-under-windows-xp/#comments ]

Thanks for your suggestions. 1) I have changed the registry: -> renamed in HKLM\SYSTEM\CurrentControlSet\Services\SbieDrv the value from "DependsOnService" to "DependOnService" [no "s"] 2) I didn't quite get on what to change in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\GroupOrderList for Filter and SCSI Class. Below are screen shots under WinXP SP3 of GroupOrderList on a desktop (SSE2 dual core, Sandboxie v5.40) and on my old Inspiron 7500 laptop (SSE-only Pentium 3, Sandboxie v5.22). Could you upload a .reg patch or a screenshot with the recommended changes for Filter and SCSI Class for v5.22 and v5.40? Sandboxie before registry fixes - GroupOrderList - Filter Sandboxie v5.40 SSE2 on top Sandboxie v5.22 SSE-only at bottom [Pictures were deleted since problem was RESOLVED with registry fixes by modnar, see under posting: Version history Page with pictures was archived at https://web.archive.org/web/20240808195712/https://msfn.org/board/topic/186405-sandboxie-under-windows-xp/#comments ]

Version history up to v5.30: [Ronen Tzur, Invincea and Sophos, last capture on 23Apr2020] https://web.archive.org/web/20200423140308/https://www.sandboxie.com/VersionChanges from v5.40.1 onwards [David Xanatos] https://github.com/xanasoft/Sandboxie-Plus/blob/master/CHANGELOG.md Registry fixes by modnar for Sandboxie v5.22 and v5.40 (special edition of Sandboxie by David Xanatos for WinXP, SSE2, 9Apr2020): 1) Rename in registry HKLM\SYSTEM\CurrentControlSet\Services\SbieDrv "DependsOnService" to "DependOnService" [no "s"] 2) Registry fixes to improve compatibility and efficiency, revised on 27Apr2025: GroupOrderList_FSFilter_Infrastructure_03_XP_USP4.regGroupOrderList_Filter_06_XP_USP4.reg Restart Windows after running the registry fixes. SbieDrv_Group_File_System.reg, also listed above earlier, was removed on 16Mar2025 because of the revisions and is not needed anymore. Below are corrections regarding earlier registry fixes by modnar, as of 22Feb2025: 1) The following are virgin backup settings to undo 2 registry patches which were posted here before 22Feb2025 and which have been rejected subsequently: GroupOrderList_Primary_Disk_05_XP_USP4.regGroupOrderList_SCSI_Class_03_XP_USP4.reg 2) If you have run NtfsDisableLastAccessUpdate_1.reg (to reduce the stress on the disk), previously posted here, please remove it from your system (delete it from HKeyLocalMachine/System/CurrentControlSet/Control/Filesystem so there are only 3 factory entries: NtfsDisable8dot3NameCreation (0), Win31FileSystem (0), Win95TruncatedExtensions (1) and reboot) Source - old versions https://web.archive.org/web/20170601000000*/http://www.sandboxie.com:80/SandboxieInstall.exe [best, only combined 32+64bit versions] https://web.archive.org/web/*/https://www.sandboxie.com/attic/* [32bit, 64bit and combined versions] https://sandboxie-website-archive.github.io/www.sandboxie.com/AllVersions.html [seems to be the same as https://web.archive.org/web/20200310035403/https://www.sandboxie.com/AllVersions ] Temporary postings:

Sandboxie - Uses (security-related) (uses and examples will be added)