I have a medical device which receives Async commands from an App
running on Windows2000. Windows 2000 App used modified 1394diag driver
and Microsoft Windows stack.

Now I want to move to Windows XP and Microft XP Windows 1394 stack
and driver similar to 1394diag. Do I need 1394 virtual device. (like
1394vdev.sys). When I have actual 1394 device connected, why should I
again create 1394 virtual device. Should I make any changes in INF and
configRom of device.

For one 1394 device to talk with XP, do I need two drivers, virtual
and actual driver. Can someone make me understand this? Where can I
find info for this?

Why should installing driver in XP be different from 2000 for pnp
devices like 1394.

Re: 1394 virtual device by Bill

Bill
Thu Jul 03 09:34:44 CDT 2003

I feel your pain, it took me a while to get my mind around what they had
done to my bus when 1394 came out. But actually, they made some really nice
changes to 1394 for XP. Unfortunately, they made loading a driver for a
fake device much more difficult. At the same time, they made the emulation
capabilities much more robust. So, while it is a pain, I am glad they made
the change.

I tried to explain how this works somewhat in another post on this newsgroup
today under the topic "Virtual 1394 bus", I suggest you look this up.

I am not sure of what your needs are as to how to recommend you proceed on
XP. How is your 1394Diag setup controlling hardware on 2000, as in, what
functionality exactly do you need to bring over? I get that an app is
talking to your driver, but I don't know what your driver is doing enough to
help.

--
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm


"Raj" <r_konjeti@mailcity.com> wrote in message
news:8509fde8.0307021238.38e8d21f@posting.google.com...
> I have a medical device which receives Async commands from an App
> running on Windows2000. Windows 2000 App used modified 1394diag driver
> and Microsoft Windows stack.
>
> Now I want to move to Windows XP and Microft XP Windows 1394 stack
> and driver similar to 1394diag. Do I need 1394 virtual device. (like
> 1394vdev.sys). When I have actual 1394 device connected, why should I
> again create 1394 virtual device. Should I make any changes in INF and
> configRom of device.
>
> For one 1394 device to talk with XP, do I need two drivers, virtual
> and actual driver. Can someone make me understand this? Where can I
> find info for this?
>
> Why should installing driver in XP be different from 2000 for pnp
> devices like 1394.



Re: 1394 virtual device by Bill

Bill
Thu Jul 03 11:48:14 CDT 2003

> I feel your pain, it took me a while to get my mind around what they had
> done to my bus when 1394 came out.

Oops I meant when XP came out. They changed the Windows 1394 bus drivers
between Win98/2000 and WinMe/XP.

--
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm


"Bill McKenzie" <bill.mckenzie@compuware.com> wrote in message
news:3f043ed2$1@10.10.0.241...
> I feel your pain, it took me a while to get my mind around what they had
> done to my bus when 1394 came out. But actually, they made some really
nice
> changes to 1394 for XP. Unfortunately, they made loading a driver for a
> fake device much more difficult. At the same time, they made the
emulation
> capabilities much more robust. So, while it is a pain, I am glad they
made
> the change.
>
> I tried to explain how this works somewhat in another post on this
newsgroup
> today under the topic "Virtual 1394 bus", I suggest you look this up.
>
> I am not sure of what your needs are as to how to recommend you proceed on
> XP. How is your 1394Diag setup controlling hardware on 2000, as in, what
> functionality exactly do you need to bring over? I get that an app is
> talking to your driver, but I don't know what your driver is doing enough
to
> help.
>
> --
> Bill McKenzie
> Compuware Corporation
> Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
> http://frontline.compuware.com/nashua/patches/utility.htm
>
>
> "Raj" <r_konjeti@mailcity.com> wrote in message
> news:8509fde8.0307021238.38e8d21f@posting.google.com...
> > I have a medical device which receives Async commands from an App
> > running on Windows2000. Windows 2000 App used modified 1394diag driver
> > and Microsoft Windows stack.
> >
> > Now I want to move to Windows XP and Microft XP Windows 1394 stack
> > and driver similar to 1394diag. Do I need 1394 virtual device. (like
> > 1394vdev.sys). When I have actual 1394 device connected, why should I
> > again create 1394 virtual device. Should I make any changes in INF and
> > configRom of device.
> >
> > For one 1394 device to talk with XP, do I need two drivers, virtual
> > and actual driver. Can someone make me understand this? Where can I
> > find info for this?
> >
> > Why should installing driver in XP be different from 2000 for pnp
> > devices like 1394.
>
>