egv@aicchi.UUCP (Vann) (03/18/86)
I am writing an application to automate the process of diskette duplication. The program is written in C language using the C86 compiler. The coding was done aboard an IBM PC/AT. The final application is to run aboard an IBM 3270 PC/AT. The diskette duplication device is a Mountain Hardware 3250. Several days ago we transferred the .EXE to the 3270 PC/At. The application failed consistently whenever we tried to do "FWRITE's". But this only occurred when the Control Program was running on the 3270 PC/AT. If the system were IPL'd without that progra aboard it ran well. Accidentally, we found too that if we removed some of the PROMPT, SET or PATH commands from a batch file which invoked our application and ran the Control Program, we could get my application to run too. Has anyone seen this kind of behavior before? We would greatly appreciate knowing h changing the batch file could cause an applications FWRITE's to begin to function. Is there some common area being used by the application, DOS, and the Control Program that is getting clobbered? Am I having environment problems? HELP??? *** REPLACE THIS LINE WITH YOUR MESSAGE ***