This is a statement of problems/solution to a problem with OS/2 and Borland C++ for OS/2 on a Bernoulli Insider 90. When I loaded according to package instructions, It would load fine. When I tried to invoke it from the command line or from the icon, I would get either a "not enough memory" dialog box, or the system would shut down with a TRAP=000e I found the answer. It was the drivers for the Bernoulli drive. I have a Bernoulli Insider 90 with a PC2 interface board. I was running the Iomega OAD drivers v 2.0 dated 7/1/92. I tried loading BCOS2 to C:. It worked fine, there. That ruled out the distribution diskettes. Diagnostic software by AMI, Central Point, and Iomega ruled out a hardware fault. I tried to XCOPY C:\BCOS2 E:\BCOS2. Occasionally, I would get messages saying that the system could not open the file specified. When I tried to run BCOS2 from the E: prompt in an OS2 window or full screen, it said the system could not execute the file specified. When I did a COMP on C:\BCOS2\BIN\BC.EXE E:\BCOS2\BIN\BC.EXE, the system returned an error message SYS0031, which means the disk and the drive are incompatible. or the door is not closed. All diagnostics indicated the drive is running just fine. All behaved to standard. EVERYTHING else read/wrote/ran from the Bernoulli just fine. Only BCOS2 died like a dog and usually took the system down with it. From the C: drive, it flew! I called Iomega. They recommended I download v 2.02 of their OAD drivers. I tried. Initially, it wouldn't work. I called them back. Had to load the stuff on a diskette and run OS2's DDINSTAL. That worked. Remmed out the DISKCACHE statement and erased /CACHE:64 from the IFS line. Rebooted and installed. VICTORY! This time, I tried it twice, rebooted and tried it again. It is stable! That was what it was, the drivers. THE PROCESS! - Have Iomega (ab)users log onto the Iomega BBS at 1-801-392-9819. 9600-8-N-1. - Download OS222.exe. @@@@@@ From here, I am assuming you keep your Bernoulli files on C: It can be some other drive, of course. I am assuming you'll use A: for the install diskette. It could be B:. - Make an OAD subdirectory on an empty diskette. - Copy OS222.exe to the diskette. - At the command line, type A: , then OS222. It will unpack itself. You can then delete OS222.exe. (Hope you saved it somewhere, first.) - Copy everything to the OAD subdirectory, and leave the original in the root. You now have one copy in A:\ and one copy in A:\OAD. - Make an OAD subdirectory on your boot drive off root. If it's already there, save what's now there to a diskette and delete all. - Run DDINSTAL. - - Change destination to C:\OAD, source to A:\. - - Install. - - Exit. - Run GENOAD. - - Scan for physical connections. Keep pressing return until no more happens. Press ESC until you get back to the pulldown menu with Define physical connections. - - Define physical connections. Keep pressing return until no more happens. Press ESC until you get back to the pulldown menu with Define logical connections. - - Define logical connections. Keep pressing return until no more happens. Press ESC until you get back to the pulldown menu with Save Map File. - - Save map file. - - Press ESC until you get a box saying "save config file"? Yes. - - Press ESC until you get back to the first pulldown menu box with Modify CONFIG.SYS. - - Have GENOAD modify your CONFIG.SYS. - - Exit GENOAD. - Using any editor, in CONFIG.SYS, delete /CACHE: whatever from your IFS= line. - REM out DISKCACHE. - Save CONFIG.SYS. - Reboot. - Install Borland C++ for OS2 according to instructions. - Go back in to CONFIG.\SYS and restore the /CACHE: and remove the REM. - Reboot. - Enjoy Borland C++ for OS/2. It's awesome. ......