>>>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.
>>
>>The problem is that article won't work on NT. The article says it *might* not work. Uh, using DOS interrupts? It doesn't stand a chance of working. Alas, we have no Win32 equivalent to SetVolumeInformation(), like we do with GetVolumeInformation(). Beats me as to why; I guess the Win32 devs figured we didn't need it.
>
>I kinda figured Win32 would have a hard time with nasty things like direct disk access :-) In a way, this is nice to know, because it means that casual users are even less likely to be able to completely duplicate the token diskette(s).
Al,
Don't be so sure :) I don't know how to with win32 but very simple if you just use debug (in win32 DeviceIOControl ?). Any average user would guess it might be serial number change if diskettes don't match and many could change it with few lines of ASM.
There are other diskcopy resistant ways but unfortunately all I could do with them is 16bits ASM way (not supported since VFP3).
After setup you could use a DOS based 'licenser' com/exe which could do nonstandart read/write from/to diskette. That way you wouldn't worry about diskette duplexing (few copiers get out of DOS standarts).
Cetin
