Hi Cetin Thanks for the trouble.

In the mean time I put in code to ignore when serial.bin returns a blank so to get things going and one thing is for sure that this blank will occur only when accessed from a node, the original installation access will not have a blank. So for the time being I guess it is okay.


>No I don't have a clear idea. Under w2k and xp I can access and get serial numbers using either that serial.bin or FileScriptingObject, winAPI with VFP but not on w9x machines.
>Cetin
>
>>Thanks Cetin for a very fast reply. In the mean time I was doing research. I tried from a W2K machince as a node onto 2 other W98 machines and it is working well. W98 machine to w98 machine fails.
>>
>>Any idea what might be happening?
>>
>>>Thanks Devcon was a thriller :) VFP8 maybe is the best version so far.
>>>I think I warned you serial reading routines wouldn't work on networked drives. I don't know if there is a way to get remote drive serial numbers using DOS interrupts.
>>>Cetin
>>>
>>>>Hi Cetin
>>>>
>>>>How was your DevCon? Looks like everybody is happy with VFP8.
>>>>
>>>>Sorry to be troubling you again but I seem to have run into a problem with serial.bin I will be glad if you can help me with it. The problem goes:
>>>>
>>>>I have tried this on a standalone manner and it is very well. But on a LAN environment where I have mapped the server C drive as say for eg. E: the following failed from the node:
>>>>
>>>>E:
>>>>CD\app
>>>>FOXR readsrno.prg (which in turn call serial.bin)
>>>>
>>>>here serial.bin returns a blank instead of 4 characters.
>>>>
>>>>But if I shift to the server and...
>>>>C:
>>>>CD\app
>>>>FOXR readsrno.prg
>>>>
>>>>here serial.bin returns the right value.
>>>>
>>>>On the same machine but between drive partitions like C: and D: on the same machine is working well.
>>>>
>>>>Please help.