Thank you for the fopen idea. I am not using share and I don't know if
the drive is mapped or UNC. After playing around with fopen though, I
discovered that the error is an OS/network error. What I wanted to do
was, if the network drive failed, then fp would default to the local
drive, whether the environment variable said the net was working or
not. That worked, but I must answer the OS/network error message with
'Ignore'. That is not very secure.
needs more thinking ...
john
On 10/24/2015 06:19 PM, Lew Schwartz wrote:
I think I used to use fopen("Drive:\nul") > 0
-Lew Schwartz
On Sat, Oct 24, 2015 at 6:28 PM, John R. Sowden <jsow...@americansentry.net>
wrote:
Is there is way in FPD 2.6 to test to see if a drive is working without
having the program crash. I have a network where I test for a remote drive
(peer to peer net) before attempting to connect to it. I set a variable
(above is done in the autoexec.bat) re: the sytatus of the remove node
being on line. If there is a change in the drive, such as a reboot of the
remote computer, the environment variable does not change, but the drive is
no longer accessible. When I am in fpd, I want to confirm the drive is
available before using it so it doesn't crash. I checked the sys()
functions, but none seem to meet the concern.
John
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/562da01e.6040...@americansentry.net
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
