|
Posted by RJK on September 30, 2006, 11:40 pm
If you were Registered and logged in, you could reply and use other advanced thread options
(Kerry, I think I love you ! ....)
AHA ! ...so it's not just me !
A couple of months or so ago, I made a BartPE cd-r and and was relying on
ntfs4dos.exe to access my ntfs boot drive with a view to running multi-av
command line scanners - and lost my mbr, after trying to run multi-av.
Lukily I'd ghosted just a few hours b4 it all went bang. So now I have to
keep postponing another fight with BartPE / ntfs4dos.exe / multi-av until
I've got a spare machine free, or I've just ghosted my own.
I think that the next time I "have a go" I'll download the cls's myself and
and perhaps knock up a batch file, but, ...so many other things to do !
regards, Richard
> cquirke (MVP Windows shell/user) wrote:
>> On Sat, 30 Sep 2006 15:23:37 -0400, "David H. Lipman"
>>> From: "cquirke (MVP Windows shell/user)"
>>
>>>> Hmm... I've been looking at Multi-AV, and I was thinking there could
>>>> be good synergy here. It's hard-coded to use a dir in C:\, and I'd
>>>> love to free up that dependency.
>>
>>> It is deliberate. It is for complete knowlege of where the AV-CLS
>>> tree
>>> is located and in 8.3 format. It is also for the situations where
>>> one boots off a DOS DISK or a DOS DISISK with NTFS4DOS and runs one
>>> of
>>> the three batch files.
>>
>> OK, I can see how it could ease drop-and-go linkage to a subsequent
>> DOS mode boot. I may be able to work around that.
>>
>>> This will remain static. I see NO reason to change this.
>>
>> I'd want to change it if any of the logic that launches these tools
>> were to be incorporated into Bart, i.e. the process of copying off
>> Bart CDR to %Temp% if writeability is required.
>>
>> Then again, if it's only the batch files that are needed for that, I
>> can re-do those, and I could shell your updater with something that
>> pulls the scanners from C: into the Bart build subtree (which
>> obviously can't encompass a dir off C:\ otherwise).
>>
>> Bart has two mechanisms to incorporate material into the CDR:
>> - a "custom" subtree that's dropped as-is
>> - the "plugin" subtree that's the source for plugins
>>
>> Neither case can cope with a dir directly off C:\, even if the bart
>> builder subtree is on C: (as mine doesn't happen to be). The "plugin"
>> subtree is always under Bart builder's base, and to use the "custom"
>> subtree, I'd have to make C:\ the "custom" base and I'd end up with
>> everything else dumped on the CDR as well.
>>
>> But that's OK, I can slurp and burp. In fact, knowing your subtree
>> will always be where it is can make that easier ;-)
>>
>
> I've used Multi_av from BartPE a few times. I quit when for some reason
> there was major file system corruption. I don't see how Multi_av could
> have caused it but it happened none the less. It was a very infected
> computer which I probably would have flattened and rebuilt anyway but
> after running Multi_av from BartPE I had no choice. When using it with
> BartPE I installed and updated it from the Windows installation then
> booted to BartPE to run it. Now if after running Multi_av in safe mode I
> still suspect something is amiss I boot from BartPE and run the individual
> scanners with different switches from what Multi_av uses, to report only
> not clean or delete. Then I can manually delete anything after I figure
> out what it is. I've found that from safe mode Multi_av does a good enough
> job that I've never felt the urge to try and integrate it into a BartPE
> CD.
>
> --
> Kerry
> MS-MVP Windows - Shell/User
> http://www.vistahelp.ca
>
>
| 
XML site map