>>>>Well, sure. Except that I DO have a purpose. A training session is being run with my app, which I want to be fully functional only if the user has the right token - in this case, a floppy diskette. The volume serial number is the only diskette property not copied by DISKCOPY, which makes it difficult to make more than 1 token diskette for the training class.
>>>
>>>PMFJI--Just an idea from left field, but could you write a custom copy routine that branded the disk with its own serial number? Then you could make sure that they matched.
>>
>>That's exactly what I'd like to do. Use DISKCOPY to make a copy of my token diskette, then brand each copy's serial number to be the same as the original.
>>
>>MSKB article Q69223 has the specifics on how it's stored, but an example of how to set it in Win32 would be very nice.
>
>I think I may have mis-explained my idea. Place a file on the floppy that contains the serial number of that floppy. In your program, open that file and compare the serial number of the disk to the serial number in the file. You will have to encode the serial number of course, and name it something goofy so no-one can guess which file is which.

Thanks for the clarification. I like your idea! No need to hack the serial number at all.

Since I'm already encrypting strings it'll be little extra effort to do this.

Thanks again.