RE: Help: SCSI Miniport with WMI causes SCSIPORT to crash!!

Yeah, like I said, I was reluctant to even post it as it wasn’t clear to me that what the intentions of Jamey and Max
were, or even if they really were violating the ‘no brazen advertising rule’. It was just that in both cases the issue at
hand: emulating a disk target and supporting WMI, were being addressed by the assertion that scsiport simply won’t let
you build a virtual device, which is not strictly true, as if that were the root cause of both problems. If the response
had been: ‘you need to do this or that but really you should consider not using scsiport for a virtual device due to the
performance problems’, I would have had no issue at all. I don’t even mind when the answer is: ‘you need to do this or
that, but really you should consider a third-party replacement because of whatever, and by the way, my company makes a
dandy one’. The difference in my mind is that the response is first of all responsive to the problem at hand, and only
tangentially hawking a product.

One of the original posters replied, with what I took to be some amount of frustration, that he understood the virtual
device performance problem and that it was not relevant to his project and that really he needed some help on the actual
problem (WMI support.) It was my perception of that frustration that prompted my posting.

We often complain about posters who ask how to do ‘x’, (where ‘x’ is typically some awful hack,) without explaining what
it is that they are trying to do. The opposite side of this is the responder who answer questions not asked, leaving the
original problem unanswered, and perhaps sending the original poster digressing off into irrelevancies.

And once again I think this is all no big deal. Happy new year.

===========================
Mark Roddy
Consultant, Microsoft DDK MVP
Hollis Technology Solutions
xxxxx@hollistech.com
www.hollistech.com
603-321-1032

-----Original Message-----
From: “benson”
To: “NT Developers Interest List”
Date: Tue, 31 Dec 2002 11:47:02 -0500
Subject: [ntdev] RE: Help: SCSI Miniport with WMI causes SCSIPORT to crash!!

> I think that you are being criticized, but not precisely for
> advertising. The argument goes as follows:
>
> A post from your end of the world stated: “combining WMI and SCSIPORT
> can’t be done at all.”
>
> Mr. Roddy feels that ‘can’t be done’ is too strong of a statement, and
> sort-of accuses you, in a friendly way, of trying to frighten the
> populace into buying your superior alternative to SCSIPORT instead.
>
> I think that it’s much more likely that you are simply expressing your
> opinion that this idea will work so poorly as to be practically
> useless.
>
>
> In my personal opinion, if your postings on this topic were
> advertising,
> you need a new advertising agency. If your posting had said, “it can’t
> be done, so buy our product instead,” there might be a valid complaint
> here.
>
> If you owe the community anything, it would be a followup giving a more
> nuanced summary of the technical situation. Personally, again, I have
> no
> problem with you saying ‘read all the previous traffic on this topic
> and
> weep.’ If the original poster reads all the traffic and doesn’t come
> out
> weeping, well, fine.
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@hollistech.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

I think this may bring the focus back to the original problem…

Any idea how SCSIPORT generates WMI instance names? Does SCSIPORT base
these names on PDO? Can this be a problem if you have a virtual SCSI
miniport?