Re: SAN sample code

Tech-Archive recommends: Speed Up your PC by fixing your registry

1) SAN stands for STORAGE and not SYSTEM Area Network. I can bet most
of the people
stopped reading your message after this wrong assertation :)

2) Even if you'd manage to write own NDIS protocol driver it would take
you years to make it
BSD sockets compatible at user level. Ask Max how long did it take them
to write BSD sockets
library for NT kernel. And it was for TCP/IP and not for own protocol.

Grab a copy of ReactOS, check DDK and try reading this and OSR ntdev
forum archives - it would
give you at least approximate view of how large is whole network stack
you'll have to totally rewrite
yourself.

NDIS miniport (I think it's your hardware so it would be probably you
who would write NDIS compatible
driver for it) - NDIS protocol (it would be you who would write it) -
AFD equivalent - User mode DLL

3) Give a try to NDISPROT from the DDK, it has been there for a long
time. Dog slow (extra memory
copies and no event-driven I/O) but it's a pure strigh forward
sekeleton for your future TCP replacement
driver.

4) Still not clear why do you need SAN file system for this (original
post from you). In any case it's 10+
man years so no single person would give you a SAMPLE of it. Try
licensing SFS from DataPlow. It would
be faster.

Regards,
Anton Kolomyeytsev

CEO, Rocket Division Software

www.rocketdivision.com

.