CompuServe Messages

Steve, Once you unarc all the DICE files to a disk, you can start by ignoring everything except the directories named BIN, DINCLUDE, & DLIB. These directories contain all the files you'll probably be needing. BIN contains the executables dcc, dpp, etc. DINCLUDE is where all of the files to be included (ie., #include <filename> ) are stored, and DLIB is where all the libraries to be linked (the startup code, etc.) are stored. Here is a script I use when I want to run DICE from a floppy drive (assuming DICE is the name of my disk): assign dlib: DICE:dlib assign dinclude: DICE:dinclude copy >NIL: DICE:bin all to ram:c stack 20000 Now, instead of copying BIN to ram:c, you might want to just add BIN to your search path or make the files in BIN resident, depending on how much ram you have to play with. You need to place Amiga.lib (from the 1.3 Dev. Kit) in DLIB (for large data/large code work, otherwise you have to run it through LIBTOS from the DICE:C directory, this will also save some space). In the DINCLUDE directory you have to make a subdirectory called AMIGA, in this subdirectory you copy all the INCLUDE.H files from the "INCLUDE 1.3 STRIP" disk (again, from the 1.3 Native Developer's Kit). These last two step assume you want to use Amiga specific routines & have the 1.3 includes. The script above assumes that your startup-sequence is creating all the directories you need in ram: or that they exist on a floppy that is accessable while compiling. Especially important is the T: directory, this is where all the intermediate output files go, run DCC with the -v verbose flag to see how/what. My T: is in ram, but if you're short on ram, assign it to a floppy. I assume DICE uses the ENV: directory since you got a requester asking for it, compare your startup-sequence to the original from boot disk that came with your Amiga, make sure you haven't deleted any of the ASSIGNs or MAKEDIRs, I believe you need them all. DICE is memory hungry, I compiled a "datafied" Image, orginally of 48K [ MORE ]