Spake Giridhar Pemmasani:
> Are you sure it was working before under exactly the same
> circumstances? The last call was to RtlUnicodeStringToAnsiString,
> which is not implemented yet. That could be the problem, but it
> should've bombed before too, in that case.
No. I'm sure there must have been *some* change, but I can't figure out
what it could possibly be. The driver version I am sure is the same - I
got it working with 0.2 plus a patch (now in CVS) which I wrote, and I
still have that exact code. The driver I'm sure is the same.
That leaves only the kernel. Unfortuneately, I'm not sure exactly what I
have changed in that config, and I don't have the old one.
The oddest thing is that previously, ndis_init_one didn't seem to be
getting called at all. That's what the logs show, anyways.
> Anyway, I am going to implement this function soon, so wait for it for
> a day or two (or you can add it!)
I think I'll poke at it on the bus today - what are you using as your
reference? I'm intending to use ReactOS, as I have a copy of that