Mercurial > ~darius > hgwebdir.cgi > mikmod
comparison docs/tips.txt @ 4:5d614bcc4287
Initial entry of mikmod into the CVS tree.
| author | darius |
|---|---|
| date | Fri, 23 Jan 1998 16:05:08 +0000 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 3:71e20a32bd84 | 4:5d614bcc4287 |
|---|---|
| 1 | |
| 2 --> MikMod 3.0 | |
| 3 -> Various Programming Tips and Tricks! | |
| 4 | |
| 5 | |
| 6 Here are some tips and tricks that I have jotted down as I think of them. | |
| 7 The list is short for now, but it will no doubt grow as more are thought | |
| 8 up. Also, check for additional information on the Divine Entertainment | |
| 9 website at http://www.epix.net/~dracoirs/ | |
| 10 | |
| 11 Ok, so this little text file is pretty short right now. These things | |
| 12 take time to think of.. :-) | |
| 13 | |
| 14 | |
| 15 -/- Compiling / Makefiles | |
| 16 | |
| 17 Watcom: | |
| 18 | |
| 19 The example files that come with MikMod default to 30k stack buffers | |
| 20 (option stack=30000 on the wlink command line). This is a safety pre- | |
| 21 caution and by no means a requirement. | |
| 22 | |
| 23 You can usually safely use a 10k stack if you are using an interrupt | |
| 24 driven MikMod_Update() and you can safely use a 5k stack if you are | |
| 25 using polling (calling MikMod_Update() from a main program loop). | |
| 26 | |
| 27 ---------- | |
| 28 | |
| 29 If you are writing a module player and are NOT calling MikMod_Update() | |
| 30 from an interrupt, then you can safely remove /ZU from the following | |
| 31 modules in the /MikMod directory: | |
| 32 | |
| 33 MDRIVER.C | |
| 34 VIRTCH.C | |
| 35 | |
| 36 Removing /ZU will slightly reduce code size and increase replay speed. | |
| 37 | |
| 38 ---------- | |
| 39 | |
| 40 If you are using the IDE and want to add PMODE/W to the list of valid | |
| 41 targets, follow these steps: | |
| 42 | |
| 43 a) copy PMWBIND.EXE and PMODEW.LNK to your watcom/binw diectory. | |
| 44 | |
| 45 b) Load WSYSTEM.LNK, and inster the contents of PMODEW.LINK into it | |
| 46 at the very top. | |
| 47 | |
| 48 c) Load IDEDOS32.CFG. Insert a line that reads: | |
| 49 Target *.exe, dw2e_, "PMODE/W Executable" | |
| 50 | |
| 51 d) Load IDE.CFG. Around line 840, you will find the following line: | |
| 52 VSwitch 0, dr2??, "System:", SYS, " ", ONE, REQ, dos4g | |
| 53 Inser this line below it: | |
| 54 VSwitch 0, dw2??, "System:", SYS, " ", ONE, REQ, pmodew | |
| 55 | |
| 56 e) This is the tricky part. There are several lines in IDE.CFG that | |
| 57 contain 'dr2'. Each of these [excluding the special case in step | |
| 58 d] must be duplicated, and 'dr2' replaced with 'dw2' (no other | |
| 59 changes required). Do this right and you will have full IDE cap- | |
| 60 ability with the pmode/w extender! | |
| 61 | |
| 62 There you go, all set to compile with pmode/w within the Watcom IDE! | |
| 63 | |
| 64 ---------- |