Hi,

I am not sure if neccessary to report because I am using a very old version 2.1.1.0 of Disk Defragmenter Plus (http://www.abexo.com/defrag.htm) that serve my needs.

It’s not possible to be used while eBoostr (latest beta 471) is active. The system shuts down and reboot “normally” so no Checkdisk during boot running and of course no disk defragmenting what should take part after booting with checkdisk and log-in but before showing any icon on the Desktop.

Running Disk Defragmenter with active eBoostr simply reboot the system without any error message.

Setting eBoostr to pause via Edit > Stop caching solves the problem, no more erros and Disk Defragmenter Pro Plus 2.1.1.0 runs fine as usual. This problem does not occur with eBooster 2.x.

BTW: the formerly reported error about the “Last cache/disk hit ratio” flipping between 1/3rd and 2/3rd showing on the eBoostr Control Panel and also on the Systray-Icon all the time after adding “Sytem Memory” is still present in beta 3.0 build 471 on my system with WinXP-sp3 on PCChips M848ALU v2.1 board using AthlonXP3200 and 1,5GB DDR(1)SDRAM (256MB RAm allocated to eBoostr, also happens with 128MB assigned)

–

I am not sure if interesting or simply a local error: already in the last beta my system has gone instable showing crashes from Windows Spooler Service (configured auto restarting) all the time (about 10 minutes) and also often errors of winspool, Event Viewer shows: winspool.drv, version 5.1.2600.5512, fault address 0x00004a9d.
I belive I fixed this problem by reformatting my USB-Stick and recreating the cache file using an 8GB USB-stick/NTFS-formatted which is used by eBoostr about 30% of the stick (100% allocated to eBoostr).

In addition I was not able to open “Computer Management” because initialising of the snap in failed. Setting eBoostr to Paused works sometimes if I disable caching directly after booting up. Because no error except the initialisation error I cannot confirm that it was caused by eBoostr but suspiciously the problem occured while eBoostr was active.
The last two problem have already occured in the former beta and might be a result of adding and removing system memory to eBoostr, at least not occuring anymore sice formatting the stick.