Hi Konstantin,
yes I have this entry and I killed the subfolder(s)
Parameters/PnPInterface with parameters 1 3 for PNP (which belongs to real
Aha154x). This works as You can see, the ntbootdd.sys driver is loaded (has
started (308)). And all seems to work right. Therefore I came to the idea,
that this is similar to all the other 07B BSODS. I think, that XP (FBA
here?) only wanted to start from that harddrive, on which it was
originally installed. That describes exact all, was has happened until.
And that is my question: Which key(s) have I to kill or to write new, that
XP(E) forgot of any old harddrives and that it is getting the NEW one and
the vendor number for the "Harddrive in Ram" InstancePath is

SCSI\Disk&Ven_NEBBETT&Prod_&Rev_\1&30c669b6&0&000

I think, it is not far away from working and then
is there a big chance for large images in ram without any SDI. You only
have to copy the files by explorer, that works for me in NT4.

Thank You for Your help
Dietmar

PS: Have You ever seen a BSOD 07b in NT4?

Hi all,
after I read all the posts here which belongs to scsi BSOD 07b I came to
the following idea (hihi):
I will export the registry from my running NT4 miniimage in ram. There I
only have to look (or can reimport pieces in minlogons registry), which
number the "scsi" disk have and have all the correct entrys because
>Microsoft says:
"For Windows 2000 and later, a legacy miniport driver is initialized in
exactly the same way as for Microsoft Windows NT 4.0. When a legacy
miniport driver calls ScsiPortInitialize, the port driver calls..."
I think that will work or even put me a big step forward.

Thanks for help
Dietmar

PS: Do You know, that floppydisk is not supported
by minlogon? That is a funny thing: In TD have the drivers flpydisk.sys
and fdc.sys NO entry in registry. But if You simple copy them to system32,
the floppy doesnt work at all after reboot. This is nearly the same as with
my "scsi" disk driver ntbootdd.sys . There are (more) entries in registry
needed.