The unofficial Shadow Defender Support Thread.

You wrote this great

 

+1 → +∞

 

I think you may be refering to Diskshot. It looks promising but it is only available in Korean language ATM.

 

Thank you brother

 

I've tested TRIM with TRIMCheck on my SSD with three programs:
1) ShadowDefender
2) Acronis Try and Decide
3) Deep Freeze

In every scenario TRIMCheck says TRIM is disabled.

BUT!:
My QUESTION is: Doesn't is this somethind normal? I mean in shadow mode the files created with TRIMCheck are some virtual files inside the much bigger shadow file created be the virtualization software. Ergo TRIM is applied on the bigger shadow file (created by the virtualization program) on the system startup.

 

I really don't know how exactly SD treats the Shadow files. But if TRIM is applied at startup, then try this. Run TRIMcheck once while in shadow mode, reboot and run it for the 2nd time without entering shadow mode. I 've SD uninstalled, so i can't do it myself. The proggie goes to read a specific location of the disk, so it doesn't matter what's the name of the file or what the data says. If TRIM has been active, after reboot, it will read 00 00 00 00 in the location it wrote before.

 

Thinking about it, it won't work. Cause TRIMcheck's logfile will also be gone after reboot, so it won't remember where it went to write. Maybe one must try this: Run shadowed the 1st time. Save the file that is created in a non shadowed volume. Reboot. Move the file created from TRIMcheck, back to the same directory of TRIMcheck and run it for the 2nd time. Verify that TRIM check goes to read at the same location (a number shown in the command prompt). See the result. If it works, i think it still is sub-optimal, cause if one reboots once a week, it means TRIM will work once a week. That's not how TRIM was conceived to work. But it's better than nothing.

 

I've checked this solution right now (run shadowed - saving the file in a non shadowed volume - reboot - moving back the file - verify). The result: "TRIM appears to be WORKING!"

 

Good job! Well, at least when you reboot, TRIM is applied. That's something. Thanks for testing. I will then re-install Shadow Defender, although i don't think i will use it on long sessions, just program testing.

Nice idea you had there.

 

DARN, darn, darn! For whatever reason, it doesn't work on my computer! I tried to follow the method i suggested above twice and twice i got "NOT working"...

Maybe there is a conflict with ERP? With my SSD's controller? I don't know... But even after reboot, the data is still there.

 

Uninstalled, reinstalled, tried again, nothing. TRIM won't work even after reboot... Either:

- There is a driver conflict with ERP or something else (the 2nd time i installed SD, when i clicked "register", i got immediate BSOD with driver IRQL not less or equal).
- There is a lack of cooperation between the "after reboot TRIM" and my SSD's controller.

Other people with SSDs may try, so we can see how others do. I used v.355.

 

FYI, Tooltime Time Freeze that i just tried, works with TRIM while in "shadow" mode. No reboot, no nothing.

Unfortunately, i had a massive corruption of pretty much everything. I reboot and i see:

-my mail notifier having lost all settings.
- Iron having lost the speed dial and graphical corruption everywhere. I was seeing only a white page with a half "webstore" icon, that i normally don't see.
- So i launch IE to come here and my internet connection doesn't work.

Macrium image just restored... Boy... And to think that i run very few items at startup...

 

"An interrupt request level (IRQL) defines the hardware priority at which a processor operates at any given time. In the Windows Driver Model, a thread running at a low IRQL can be interrupted to run code at a higher IRQL. The number of IRQL's and their specific values are processor-dependent."
Technet Link
Credits to original page owner

.............................................
Me, I suspect that these are kernel driver ram usage conflicts

 

Yeah, probably SD conflicting with ERP or some hardware driver. Because at the moment i had no AV and Tinywall usually has no conflict with anything. It was caused by "ntoskrnl.exe", so not much light into the real culprit.

Anyway, i 've uninstalled SD and will wait to hear Tony's take on this. Frankly, aftrer months of awaiting an SSD-compatible version, i am quite used to be without Shadow Defender. I use more images. More trouble, but doable.

 

New version of SD released today.

 

Changelog....
Version 1.2.0.370 - February 17, 2013
What's New: Optimize SSD Trim function.
What's Fixed: A bug in Windows 8.

 

Thanks.

 

I am happy to report that TRIM works fine with TRIMCheck, while in Shadow Mode!

 

It seems that somebody at ShadowDefender is listening to users! Cant wait to try out the new version.
Hope it sorts out the major issues that I have been facing.

 

Build 370 running great on my HDD-mSSD laptop ...no issues whatsoever!

 

And he was very quick in solving the problem! And Shadow Defender is a one man project. Amazing. I just ditched Avast again!

 

Thanks but I ran TRIMCheck in Shadow Mode and waited 30 seconds to run again in Shadow Mode and it says it does not work for me. But, The Windows command is enabled for TRIM. Just reporting but don't know what to make of it.

Gary

 

Damn. Are you sure you set the memory cache to 0? Because if you have memory cache active, the TRIMCheck will write to RAM and the test will fail.

 

Sorry, you are right. I turned off memory cache, forgot earlier, and ran it in Shadow Mode and yes TRIM works. Thanks for your confirm and most of all to Tony's brilliant programming. Sorry for the confusion.

But, now, I am wondering, are we safe to run SD with Memory cache enabled with an SSD. Will TRIM related functions be affected adversely? I don't really know but would like your input.

Gary

 

Glad it works for you too! Seems it's fixed once and for all!

Yes, now you can re-activate the RAM cache. Simply, while it writes in RAM, there is nothing to TRIM there. RAM doesn't support TRIM, but who cares... When the RAM cache is full and Shadow Defender starts again writing on the SSD, THEN the TRIM will be working again and that's where it matters.

In 2 words, now we 're golden.