So, a ldconfig later it looks more comfortable but still it does not work: # python vol.py -l Firewire://forensic1394/0 pslist Volatile Systems Volatility Framework 2.1_alpha IOError(u'forensic1394_read_device_v: Bad I/O request size',) IOError(u'forensic1394_read_device_v: Bad I/O request size',) No suitable address space mapping found Tried to open image as: WindowsHiberFileSpace32: No base Address Space EWFAddressSpace: Location is not of file scheme WindowsCrashDumpSpace32: No base Address Space JKIA32PagedMemory: No base Address Space IA32PagedMemoryPae: Module disabled JKIA32PagedMemoryPae: No base Address Space IA32PagedMemory: Module disabled WindowsHiberFileSpace32: Location is not of file scheme EWFAddressSpace: Location is not of file scheme WindowsCrashDumpSpace32: Location is not of file scheme JKIA32PagedMemory - EXCEPTION: Failed to read from firewire device IA32PagedMemoryPae: Module disabled JKIA32PagedMemoryPae - EXCEPTION: Failed to read from firewire device IA32PagedMemory: Module disabled FirewireAddressSpace: Must be first Address Space FileAddressSpace: Must be first Address Space Seems the python bindings were missed in the first approach. What could cause the FW-read-error? Regards Michael -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de