Mike, I tried your suggestion and ran my test on the concomp in the RBDOS directory. The memory leak did not manifest itself.
I have always started RBase with a batch file of some kind to clean up the path, as well as doing some fidling with the drive mappings, so I am sure that the correct RBASE.CFG file is seen and so only the DOS version of RBase is in the path. I see in the shortcut on the program tab an advanced button which seems to allow me to point to a custom autoexec.??? and config.??? for that session. I am going to experiment with making an autoexec.rbd and config.rbd and see if I can do the setup there. I'll keep you posted. Dennis McGrath > If you get this far, you will want to use this icon and revise your > startup > routine > to use the "C:\RBTI\RBDOS65\RBASE65.EXE -R -C <your command file>" > format in the Cmd Line field. Make sure to change the Working > directory to > reflect the directory of the command file that you specify in the Cmd > line. > > This is the inverse of what many developers have done over the years, > and > works much better than the old logic. The old logic was to fire > R:BASE from > a command window either directly or via a batch file. The new logic > is to > use the icon to fire R:BASE directly and call the command file from > R:BASE. > > I hope this helps. > > Mike >
