Hello All,
On the server pc I have a tdi driver and shared location. On Client machines, I have CAD software installed and tdi driver. All the CAD drawings are saved in this location. From the Clients machine when a drawing is accessed, edited and saved back to location; the next time the same drawing is not opened and the CAD software reports it corrupted.
According to msdn knowledge base article http://support.microsoft.com/en-us/kb/885936 it applies to XP SP2 only. But I am Facing this problem on XP SP3 environment.
Note: when TDI driver is disabled on server machine, the problem vanishes away.
Further, when I analysed the scenario, I found ntwritefile api is used to write to file on shared network location. Next, I found underlying the ntwritefile, there is identification of the target where data has to be written, viz, local file system or remote file system.
Then I learned that the network redirector is responsible for transmitting the data to desired remote file system.
I want to debug this entire scenario, and find out the root cause of why the disabling of tdi driver prevents the error.
“It is important to keep the TDI Driver enabled on Server machine.”
Please can anybody explain how can a writefile over network affect tdi driver?
How can I correct/modify my implementation of tdi driver to overcome this challenge?
What is a TDI driver? is it a TDI filter?
wrote in message news:xxxxx@ntdev…
> Hello All,
>
> On the server pc I have a tdi driver and shared location. On Client machines, I have CAD software installed and tdi driver. All the CAD drawings are saved in this location. From the Clients machine when a drawing is accessed, edited and saved back to location; the next time the same drawing is not opened and the CAD software reports it corrupted.
>
> According to msdn knowledge base article http://support.microsoft.com/en-us/kb/885936 it applies to XP SP2 only. But I am Facing this problem on XP SP3 environment.
>
> Note: when TDI driver is disabled on server machine, the problem vanishes away.
>
> Further, when I analysed the scenario, I found ntwritefile api is used to write to file on shared network location. Next, I found underlying the ntwritefile, there is identification of the target where data has to be written, viz, local file system or remote file system.
> Then I learned that the network redirector is responsible for transmitting the data to desired remote file system.
>
> I want to debug this entire scenario, and find out the root cause of why the disabling of tdi driver prevents the error.
>
> “It is important to keep the TDI Driver enabled on Server machine.”
>
> Please can anybody explain how can a writefile over network affect tdi driver?
> How can I correct/modify my implementation of tdi driver to overcome this challenge?
>
>
>