>Thanks, I need to learn how to find things on the Microsoft knowledge base. I find it to be quite intimidating. Anyway, since the API calls don't work on most windows systems I will eliminate this as one of my options. I have too many business depending on my software every day to be in the business of predicting how it might or might not work on different vesions of Windows.
>< - You heard it first here Billy Boy! - >

I'd recommend the MSDN Library. I think that a free year's subscription can still be obtained by registered VFP owners. Among other things, it contains the complete KB and is updated quarterly.

I'm not sure as to the reasons why this issue exists with Win9x/Me as opposed to Win2K Pro, for example. However, the information has to come through the network OS. While you may find that it works on a WinNT/2K network and stations, it won't on say, a Win2K workstation hitting a Novell server. Even the workaround provided by the KB article fails. So it isn't simply a Windows issue.

The Platform SDK (which is part of the MDSN Library also) documents what functions are available on what Platforms. Naturally, Win2K/NT has many functions that aren't available on other Win32 platforms. The converse, however, is not true.

By and large I've found that the information provided by the Platform SDK is accurate and consistent across the various flavors of Win32, and is, therefore, your best source of information. In this case, the following appears in the description regarding the volume serial number:

"Windows 95/98/Me: If the queried volume is a network drive, the serial number will not be returned."