FileSystem Watcher not working in win98

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hi
i am using filesystemwatcher class in .net but that is not working in win98
& winNT.
Ifound that there are API like
FIndFirstChangeNotification & FindnextChangeNotification to get change
notification in win98 but it doesn't give the information that which file is
chnage & what is the change. I need this information necessiarlity.

I know in WinNT this problem is solved by using ReadDirectoryChangeW Api but
i need some generic solution for both Win98 & WinNT. Also i don't want to
take snapshot of the information before making changes as this is
performance degraded. Suggest me the way.

This is very urgent. So tell me the solution as soon as possible


.



Relevant Pages

  • Re: install says copied files missing/corrupt
    ... hardware's working with Win98, is absolutely *NO* indication of its ... suitability for use with WinNT, Win2K, or WinXP. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Install W2KPro
    ... Run WINNT from the i386-folder on your CD. ... installation will take forever. ... I can boot from the Win98 Start-up ... >W2K Pro on a recent MSDN CD. ...
    (microsoft.public.win2000.setup)
  • Re: Supporting ATL
    ... shipped with, say, Win98 or WinNT out of the box. ... Win2K either, but I'm not sure. ... With sufficient thrust, pigs fly just fine. ...
    (microsoft.public.vc.atl)
  • Simulate user interaction - Avoid screen saver activation
    ... SendInput API and keybd_event API work correctly with Win2000 and WinXP ... Screen saver don't start. ... Under WinNT 4.0 these API, inject key event correctly at active application ...
    (comp.programming)
  • Re: Problem with vbNet Graident Fill code on Win9x
    ... > I am using the Creating a Gradient Form Background via API from ... > vbNet. ... msimg32.dll should be in the system32 directory; ... win98 and Randy's page specifically states that it requires win98 or later ...
    (microsoft.public.vb.general.discussion)