CompuServe Thread

Brick, I had a chance to clean up my PAR drive today. So I tried a few tests deleting files and directories. What I discovered might point out some of the problems deleting the PAR's PROJECT directories. >1.While in DOS change to the PAR's drive and then into a PROJECT directory. >2.Leave the PAR's drive in the PROJECT directory then back to DOS and start PAR. >3.Go into that directory which you left active while in the PAR drive, delete all files, go back to the ROOT and try to delete that PROJECT directory – it won't delete! I went back to DOS then into the PAR's drive changed back to the root, reloaded PAR and then I was able to delete the PROJECT directory. This process seems normal, as DOS would act the same, but here is where I think the problem lies. If you leave PAR while in a PROJECT it defaults back to that directory when you enter the software the following session. What happens if that directory is not there? (i.e. If you deleted the PROJECT directory while in DOS!) Do you think this would cause problems locating files on the PAR drive. Well just a thought. Let me know what you think! I also received some garbled files on the PAR after deleting PROJECT directories. I really do think that something is wrong here! Let me know what you think. Mike Morgan, CAD Forms Inc. P.S. While waiting for my wife to get off the phone to upload this message, I tried something else that works strange. >1.Copy two files to the PAR's drive 1 file to the ROOT (test.tga) and another file to a PROJECT directory (test.tga). >2.Leave the PAR's drive in the PROJECT directory then back to DOS and start PAR. If you delete the file in the ROOT this file disappears from the PROJECT directory and the file you deleted in the ROOT is back in the ROOT directory again. This process works normal in the reverse -from DOS leaving the PAR's drive in the ROOT and deleting a file in the PROJECT directory from the PAR the file remains in the ROOT directory- everything appears normal. Also, if you leave the PAR's drive in the ROOT and delete the file in the ROOT (a normal process) everything is O.K.