RE: Geek Squad MRI 5.10.7 ISO CRACKED 08-29-2019, 11:16 PM
#44
As a former Geek Squad Agent I have been searching for a replacement for MRI, and one the one tool I miss the most have automated hardware diagnostics. So I still use MRI for the other scans, and the ability to mount the windows registry but for hardware diagnostics on some systems I have been using PaetedMagic. I don't like relying on PartedMagic because I have seen failing slow drives pass extended smart testing but fail Linear read and or butterfly read, and most of partedmagic test rely on smart testing. So I found you could add HDDscan to MRI and use it for hardrive testing since it offers butterfly read as wall as all the other smart tests. You can download the .zip and extract it to the the MRI USB or manually add it to the ISO. Once booted into MRI browse to where you extracted HDDScan in FMOD and run it.
For repairs on my office network, I added a batch file , after it starts PE networking, the batch file runs a netuse command a maps a network drive that has a bunch of additional portable apps that will run in the PE interface built for MRI. I can also use FMOD to do a data backup to my NAS, which is useful for backups on devices with embedded storage and unbootable corrupt windows. Keep in mind if you mount a network drive with FMOD open, it will slow to a near halt until you kill FMOD. Once you close FMOD it runs fine and you can re-open it and the mapped drive will show-up.
While this works and I am able to still run hardware diagnostics I miss PC Doctor. Having diagnostics automated with FACE or ran by itself, made repairs have much less touch time. Now having to testing each component one at a time, requires me to babysit the repair instead of a set and forget.
additional notes:
FMOD typically only shows network drives in PE not in windows. Which I was told has to do with CDP (client data privacy), but I never got a real answer in the GS forums when I worked there. I am assuming it works in PE because our mule we used for data transfers booted to a PE based image. It used a FMOD on steroids, and most up-to-date stores no longer used internal storage in the mule. They pushed to a network drive mapped from a server in the server room or sometimes off site. This is why GS data transfers through the mule took so long.
For repairs on my office network, I added a batch file , after it starts PE networking, the batch file runs a netuse command a maps a network drive that has a bunch of additional portable apps that will run in the PE interface built for MRI. I can also use FMOD to do a data backup to my NAS, which is useful for backups on devices with embedded storage and unbootable corrupt windows. Keep in mind if you mount a network drive with FMOD open, it will slow to a near halt until you kill FMOD. Once you close FMOD it runs fine and you can re-open it and the mapped drive will show-up.
While this works and I am able to still run hardware diagnostics I miss PC Doctor. Having diagnostics automated with FACE or ran by itself, made repairs have much less touch time. Now having to testing each component one at a time, requires me to babysit the repair instead of a set and forget.
additional notes:
FMOD typically only shows network drives in PE not in windows. Which I was told has to do with CDP (client data privacy), but I never got a real answer in the GS forums when I worked there. I am assuming it works in PE because our mule we used for data transfers booted to a PE based image. It used a FMOD on steroids, and most up-to-date stores no longer used internal storage in the mule. They pushed to a network drive mapped from a server in the server room or sometimes off site. This is why GS data transfers through the mule took so long.
![[+]](https://sinister.ly/images/modern/collapse_collapsed.png)
