I haven't thought of binary numbers on this level in perhaps going on a decade but I believe the only difference between looking at a bunch of F's as a large number & looking at it as a -1 is if you consider the leftmost bit to be a parity bit or something of the sort. -1 could very well send the correct message then for that reason.


>Hi,
>See http://support.microsoft.com/default.aspx?scid=kb;en-us;297684&Product=win2000
>
>Depends on whether you use the command line or reg hacks, it does cause some confusion.
>
>
>
>>Are you sure? I looked it up in my MSFT network books and it stated -1...
>>
>>>Hi,
>>>Please Note: To disable autodisconnect is not 0 or -1, this will cause disconnection after a few seconds. The correct setting is ffffffff Hex i.e. 4294967295 minutes.
>>>
>>>>Thanks Neil.
>>>>
>>>>We discussed autodisconnect but I actually never verified its settings in the registry myself. The hardware technician might have though. I will do that on all of the workstations. I will try a setting of -1 (turning it off) and see if it makes any difference...
>>>>
>>>>
>>>>>Hi,
>>>>>Is autodisconnect disabled?
>>>>>Is that particular workstation being spiked.
>>>>>Check the event logs on that workstation, had similar problem when the workstation had an unrelated APP where the COM easn't setup correctly.
>>>>>
>>>>>
>>>>>>I have posted other messages here regarding problems at this one site. Originally the problem was a receipt form losing focus and the user having to press the windows button twice to switch it back. There is one Windows 2003 server and numerous Windows XP SP2 workstations. The site has the same hardware as numerous other sites. This is one site in hundreds (actually over a thousand) and only this one site experiences problems. We have replaced the server, the switch, all network cables and nics and all printers. For 3 days nothing went wrong then today when very busy, 4 users were in the program and all were on different forms and using different records in different tables. One of them was on the receipt screen. All of a sudden every workstation locked up in our program. The program completely froze for everyone of them. I asked about tape backups possibly running, other apps running, etc but no information from the user on that (according to the users nothing else in
>>>>>>running). The user on the receipt form killed the app (killed the process) and then the remaining other workstation unfroze on their own. Has anyone seen this in the past? They are using a vfp8 SP1 version of our app. I can verify that exclusive is OFF and multilocks in ON and the file nor the record is locked. Besides, the other workstations were not using the same files or records. Norton Antivirus is disabled for testing. Write cache is turned off on the server and every workstation. Every workstation has at least 512 mb ram.