Re: PCI Bus filter - can you attach it dynamically?

From: Mark Roddy (markr_at_hollistech.com)
Date: 10/10/04 

Date: Sun, 10 Oct 2004 16:31:50 -0400

In article <eDU7S0urEHA.752@TK2MSFTNGP10.phx.gbl>, sbrcin@ptt.yu says...
> > Impossible. The boot disk stack cannot be stopped.
>
> You have based your assumption that XP is booted from disk connected to controller that is connected on PCI bus.
> You can boot XP from ram***. In that case ntldr (or your custom loader) can load disk image in RAM memory and then boot from there
> as if it was physical medium.
>
> See /rdpath and /rdimageoffset switches in boot.ini.
>
> Regards,
> Slobodan
>

However I think the prior assertion that the function driver for PNP0A03, aka
the pci bus driver, will not unload is probably correct. Yes, the boot device
could be located somewhere other than the PCI tree, so in theory the pci bus
driver could unload. In practice this is not going to happen. The OP wants to
inject his filter into a faulty system without requiring a reboot. The only way
he can do this 'safely' is to have his filter loaded at boot, but have it in
'inactive mode', and then activate it when its services are required. The OP
has rejected this suggestion and so he is now boxed into a requirements
conflict. Eventually he will see the light :-)

> "Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message news:%23w73JQsrEHA.4044@TK2MSFTNGP09.phx.gbl...
> > > Theoretically, what if he would somehow manage to close and eject all drivers
> > above PCI bus?
> >
> > Impossible. The boot disk stack cannot be stopped.
> >
> > --
> > Maxim Shatskih, Windows DDK MVP
> > StorageCraft Corporation
> > maxim@storagecraft.com
> > http://www.storagecraft.com
> >
> >
>
>
> 

-- 
=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
markr@hollistech.com