Re: Need guidance developing NIC driver
- From: Ken <Ken@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 30 Aug 2005 18:26:02 -0700
Yep, I appreciate those points. I agree.
I think I know the task (broadly).
If by 'prototype' you mean DDK sample, then I think the mux one is best fit.
(In a Microsoft discussion transcript, I see that they have no intention of
doing a 1 to n mux example.)
Tweaking I can do some of, the "further directions" is the big need.
Have set up a laptop with the debug (checked build) version of XP on it, to
act as the target machine. (Interestingly, while installing Visual Studio on
it, I got lots of ASSERT failures, followed by a report of memory leaks. But
the final VS screen reported 'no errors'.)
Courses seem a bit thin on the ground in Australia!
USB uses standard Microsoft driver, to act as a network port. The radios I
mention are voice and data two-ways.
Are you not aware that you can buy USB cables to link two PCs together like
an ethernet network connection? It sounds silly, but is cheaper and easier
in a situation where you want to transfer files or share a dialup internet
connection without network cards. Probably aimed at low-end machines (eg I
have a laptop without a network connection, but it has a USB port). There is
one such cable I'm aware of which doesn't need its own software installed (ie
uses standard USB driver), but I haven't been able to buy one. The cables
have a slave-slave module in the middle, and in the one I have have, they can
provide an IP address.
Regards,
Ken.
"Pavel A." wrote:
> "Ken" <Ken@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:48BED300-73A7-4130-84B3-D484D73D0252@xxxxxxxxxxxxxxxx
> > Thanks for that. Must admit, I was hoping for some more practical advice.
>
> Believe or not, but this is very practical advice, given that , as you
> wrote, you have no driver experience.
> The minimum a consultant can get you :
>
> a. Understand your task and what exactly are the modules to write
> b. Select a prototype ( IM driver and/or others)
> c. Tweak it up for yor project (rename files, services...)
> and give further directions.
> d. help you to setup a development machine and debugger.
>
> Then you may need a course of kernel mode - because, for a moment,
> it is not visual basic.
>
> I could not even understand about these network packets coming
> from USB - is this a specific USB wireless adapter with existing driver,
> or any / different usb wireless adapters (bluetooth? wi-fi? cdma? ), or new
> device for which you need to make a driver yourself...
>
> Good luck,
> --PA
>
>
> > But I took it anyway. Contacted two consultants, Walter Oney and OSR. They
> > both declined to assist. 'Per incident' model is too hard for them. (I'd
> > have thought an open credit card and jotting down some times spent
> > investigating, emailing, on the phone or looking at code, was easy enough.)
> >
> > Sorry Bill, I couldn't rouse any further info either.
> >
> > Ken.
> >
> >
> > "Pavel A." wrote:
> >
> >> "Ken" <Ken@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:8260C516-ADA8-460D-9695-2305E0038CDF@xxxxxxxxxxxxxxxx
> >> > Hello all.
> >> > I am in the same position as Bill. -Expected to write an intermediate
> >> > driver, with no driver experience.
> >>
> >> Find help ( = consultant ) to get you started, or give up.
> >>
> >> --PA
> >>
>
.
- References:
- RE: Need guidance developing NIC driver
- From: Ken
- Re: Need guidance developing NIC driver
- From: Pavel A.
- Re: Need guidance developing NIC driver
- From: Ken
- Re: Need guidance developing NIC driver
- From: Pavel A.
- RE: Need guidance developing NIC driver
- Prev by Date: Re: Need guidance developing NIC driver
- Next by Date: Re: RS232 to USB Help
- Previous by thread: Re: Need guidance developing NIC driver
- Next by thread: Re: Need guidance developing NIC driver
- Index(es):
Relevant Pages
|
