Re: [Vol-users] Problem with 2.2_alpha

It turns out I am just impatient! I waited at least ten minutes and nothing. However to answer your question: Vol.py -f /cases/memdump.mem imageinfo > 1.imaginfo I do it this way so I know what modules I've run and in which order. Thanks, Michael. Regards, Lee Armet | Senior Investigator, Forensic Technology Services| Global Security & Investigations | TD Bank Group‬‪ T: (416) 982-6855 | M: (647) 242-0002‬‪ *From*: Michael Hale Ligh [mailto:michael.hale@gmail.com] *Sent*: Tuesday, August 14, 2012 12:24 PM *To*: Armet, Lee *Cc*: Vol-users(a)volatilityfoundation.org <Vol-users(a)volatilityfoundation.org> *Subject*: Re: [Vol-users] Problem with 2.2_alpha Armet, What was your full command line used to produce the hang? If you'd like to try an older version of volatility, that would be a good idea as well - the 2.1 and 2.0 releases are available here: http://code.google.com/p/volatility/downloads/list. Thanks, MHL On Tue, Aug 14, 2012 at 11:22 AM, Armet, Lee <Lee.Armet(a)td.com> wrote: