Luckily we never had to learn of this problem the hard way since our compound-naming protocols would create unique names that have low probability of matching anything Foxboro put in /opt/fox/ciocfg. Plus = we don't do Windows! But Sacha's problem is really two-folds. The first one is due to = Microsoft's lame-brained way of handling file and directory names, with no = distinction between uppercase and lowercase. Deleting this API compound wouldn't = have resulted in the same outcome on a Unix box. The other problem is = Foxboro's bad file system architecture, for dumping user's files and directories = into the same place as system files and directories. At least on the Unix platform, the saving grace is one wouldn't see this kind of erroneous deletion. Duc "off my soapbox for now" Do --=20 Duc M. Do Dow Corning Corp. Carrollton Plant Carrollton, KY, US -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Sascha Wildner Sent: Wednesday, May 05, 2004 10:48 AM To: Foxboro DCS Mail List Subject: [foxboro] /opt/fox/ciocfg Hi List, has anyone ever noticed what happens if you create a compound called = API=20 and then delete it on an AW70? Answer: /opt/fox/ciocfg/api will be deleted. This happens with all directories in /opt/fox/ciocfg with a name that=20 could also be a compound name. Also, it is possible to create a compound with a name of a file that=20 exists already in /opt/fox/ciocfg (like COMBOS) but you cannot create=20 sequence blocks in this compound because it tries to create a directory = with this name. Please excuse if this was already known to everyone. Regards, Sascha --=20 Sascha Wildner erpicon Software Development GmbH Neusser Str. 724-726 50737 K=F6ln Germany Phone: +49 221 9746069 Fax: +49 221 9746099 eMail: swildner@xxxxxxxxxx _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave