tag:blogger.com,1999:blog-11573761.post116104848164877960..comments2023-09-23T07:38:46.925-07:00Comments on Chris Quirke's Blog: Bart vs. BAD_POOL_CALLERChris Quirkehttp://www.blogger.com/profile/05538828571660803875noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-11573761.post-31269221771897113362008-02-18T01:00:00.000-08:002008-02-18T01:00:00.000-08:00Hi, Anon II :-)Yes, most new motherboard chipsets...Hi, Anon II :-)<BR/><BR/>Yes, most new motherboard chipsets have S-ATA that isn't supported by the native i386 code set from which Bart is built. How did you integrate the drivers? I've been pulling the HDs and working in a compatible frame while the parent PC does time in MemTest.<BR/><BR/>The registry is a repository of information that defines how the system works, how applications interact, etc. It's a binary file, (nearly?) always approached only via OS APIs.<BR/><BR/>The challenge with operating from Bart is that the registry in effect is Bart's, not the HD installation's, so tools that operate on the registry will miss their mark. RunScanner is a plugin that overcomes this by transparently re-routing a program's registry access to the hives on the hard drive.<BR/><BR/>Yes, there's a bit of file renaming and subfolder navigation required to find matching hives in the Restore Points. It looks fairly intuitive to the eye, but is a challenge if you want to automate the process via batch file, or just haven't done it before.<BR/><BR/>Sorry my walk-through wasn't clearer on the above, but at least it had you digging in the right place - glad it worked :-)Chris Quirkehttps://www.blogger.com/profile/05538828571660803875noreply@blogger.comtag:blogger.com,1999:blog-11573761.post-7817084891019323642008-02-17T12:32:00.000-08:002008-02-17T12:32:00.000-08:00Saved my day too!!! Thanks!I have a HP Pavilion la...Saved my day too!!! Thanks!<BR/><BR/>I have a HP Pavilion laptop (dv5320)<BR/>A couple of notes from my journey...<BR/><BR/>- Getting Bart up and running... Easy enough, but I had to do some research because my C drive wasn't visible. Finally discovered that I had to include the drivers in the BartPE image. Getting the drivers wasn't simple since my laptop is pre-installed with windows, so I didn't have a drivers CD. None-the-less I managed to get them from the HP support site and low and behold, Bart saw my C drive!<BR/><BR/>- I don't really understand the registry too well and don't really understand what RunScanner does... but as you suggested, I selected user by user and quickly came across the user that crashes the system (my daughter... figures!). <BR/><BR/>- I had a little trouble figuring out how to harvest a spare hive. The link between the files in the snapshot and the NTUSER.DAT wasn't very clear to me. Anyway, I guess I did the right thing because it worked. I renamed my daughters NTUSER.DAT, copied one of the NTUSER files in the snapshop (took one with the same file size) and renamed it to NTUSER.DAT<BR/><BR/>- Rebooted the system and no more blue screen!!!<BR/><BR/>Thanks again!!!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-11573761.post-8827162798869927732007-07-14T19:29:00.000-07:002007-07-14T19:29:00.000-07:00mate! you saved my daymate! you saved my dayAnonymousnoreply@blogger.com