FTK Imager is portable, though not if you use a stricter definition for portable apps... It does write to the registry -- not a big deal at all when running from a small bootable OS like LiveXP, as those writes go away when you shut it down, but something some folks worry about when/if running a portable app on a regular Windows install.
FTK Imager can also install a driver when run as a portable in XP Pro SP3 32, FRIdrv.sys listed as coming from beyondlogic.org -- Googling that site for FRIdrv.sys gets zero hits, so I think all you can do is read about the dev's I/O port driver & hope it applies if you're looking for info. It did not install the driver in XP VMs running in 7, & Uniextract wouldn't work so I don't know yet what the criteria is for installation as driver & service. Nor do I know yet what if any impact it has on FTK Imager's operations, &/or if the driver install should be part of building something like a LiveXP image, since many drivers &/or services won't work properly until reboot.
As far as more complete portability goes, I was able to restrict it to 2 driver-related registry keys by using the Portable App Creator [d/l from portableapps.com forums] -- while those keys were included in the modded portable install, they were still created in the Windows registry anyway -- it's possible that converting to that format the *right* way would eliminate writing those 2 keys, but I wasn't sure if there was any call for it, or need, or if it even works adding the driver/service without a reboot. It also may be that the easy answer is to use a win7-based boot setup -- I have no idea what WinFE is based on.
At any rate, maybe that'll be of interest or help someone -- I was monitoring & converting several apps, & that's just what I came up with for FTK Imager during the process... haven't had a chance to check it out or anything yet.
Portable Info on FTK Imager
No replies to this topic
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users