{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "AUTOEXEC BAT", "size": 50, "date": "1993-04-12", "time": "23:01" }, { "name": "BACKBOOT EXE", "size": 15296, "date": "1991-06-06", "time": "8:16" }, { "name": "CHKDSK EXE", "size": 16200, "date": "1992-08-07", "time": "6:02" }, { "name": "CHKLIST CPS", "size": 540, "date": "1993-09-16", "time": "19:49" }, { "name": "COMMAND COM", "size": 50839, "date": "1992-08-07", "time": "6:02" }, { "name": "CONFIG SYS", "size": 50, "date": "1993-04-12", "time": "23:01" }, { "name": "DEBUG EXE", "size": 20634, "date": "1992-08-07", "time": "6:02" }, { "name": "EMM386 EXE", "size": 114782, "date": "1992-08-07", "time": "6:02" }, { "name": "EMSCLEAN EXE", "size": 10914, "date": "1989-08-10", "time": "23:30" }, { "name": "EMSTEST EXE", "size": 10580, "date": "1989-08-10", "time": "23:29" }, { "name": "EXM SYS", "size": 22064, "date": "1990-03-08", "time": "16:43" }, { "name": "EXPAND EXE", "size": 16885, "date": "1992-08-07", "time": "6:02" }, { "name": "HELP COM", "size": 413, "date": "1992-08-07", "time": "6:02" }, { "name": "HELP HLP", "size": 209353, "date": "1992-08-07", "time": "6:02" }, { "name": "HIDE EXE", "size": 11239, "date": "1989-08-10", "time": "21:00" }, { "name": "HIMEM SYS", "size": 13984, "date": "1992-08-07", "time": "6:02" }, { "name": "INSTALL EXE", "size": 49904, "date": "1989-08-10", "time": "10:13" }, { "name": "MEM EXE", "size": 30406, "date": "1992-08-07", "time": "6:02" }, { "name": "RAMDRIVE SYS", "size": 5873, "date": "1992-08-07", "time": "6:02" }, { "name": "README", "size": 7451, "date": "1989-08-11", "time": "0:23" }, { "name": "README COM", "size": 4200, "date": "1993-01-01", "time": "12:00" }, { "name": "SHOW EXE", "size": 11541, "date": "1989-08-10", "time": "21:00" }, { "name": "SMARTDRV EXE", "size": 43609, "date": "1992-08-07", "time": "6:02" }, { "name": "TCPOWER EXE", "size": 17122, "date": "1989-08-10", "time": "20:53" } ] } ] } }, "desc_file": "README", "desc_text": "\r\n\r\n\r\n Important updates to the manual\r\n ----------\r\n\r\n\r\n\r\n\r\n\r\nAs of August 10th 1989, the following new facilities could be of importance\r\nto you:\r\n\r\n\r\n\r\n\r\nTC! POWER is now EMS 4.0 compatible\r\n-----------------------------------\r\nThe manual states that TC! POWER emulates EMS 3.2 and not 4.0.\r\nThis is no longer true. We now give full EMS 4.0 support.\r\n\r\n\r\n\r\nThe device driver name has changed\r\n----------------------------------\r\nThe manual states that the TC! POWER EMS driver is called TCPOWER.SYS.\r\nThis has been changed to TCPOWER.EXE.\r\n\r\n\r\n\r\nIf this is an upgrade\r\n---------------------\r\nIf you are installing this version of TC! POWER as an upgrade to an earlier\r\nversion of the program, simply copy the files on the new distribution diskette\r\ninto your TCPOWER directory. Then make sure you are in your TCPOWER directory\r\nand run INSTALL selecting the install option.\r\nAccept the default parameters (they will be the same as the ones you used\r\nbefore) by pressing END. Then reboot your machine to load the new version into\r\nmemory.\r\n\r\n\r\n\r\n\r\nTC! POWER can now use existing expanded memory\r\n----------------------------------------------\r\nIf you already have an expanded memory board in your machine, TC! POWER will\r\nappend more memory to that board. As long as the expanded memory board is\r\nfully operative when you install TC! POWER using the INSTALL program, your\r\ntotal expanded memory will be the sum of the memory on the board plus the\r\nmemory emulated by TC! POWER minus 64K. The 64K lost is used for moving the\r\n64K pageframe out of conventional memory so TC! POWER occupies only 15K\r\nconventional memory instead of about 80K. An example:\r\n\r\nYou have a 512K ABOVEboard and accept TC! POWERs defaults so it will give\r\nyou 512K. The total will be: 512K + 512K - 64K = 960K\r\n\r\nTC! POWER will use the existing board first, then do spillover to extended\r\nmemory and then do spillover to hard disk. TC! POWER only uses EMS 3.2 calls\r\nwhen communicating with the existing board, so your board can be EMS 3.2 or\r\n4.0 compatible. It doesn't matter as 4.0 is a superset of 3.2.\r\n\r\nBuilding on an expanded memory board like this, TC! POWER will support so\r\ncalled \"page frame aliasing\" necessary to make some applications run.\r\n\r\n\r\n\r\n\r\nTC! POWER can take advantage of the 80386 processor\r\n---------------------------------------------------\r\nWe here assume that your 386 machine does not already have an EMS board.\r\nIf it has, you will use the existing board as described above.\r\nIf you have an 80386 processor, you can use a special driver to turn your\r\nextended memory into expanded memory which looks EXACTLY like a board.\r\nThen TC! POWER will look at that expanded memory as if you had a board\r\nin your machine, and TC! POWER will not occupy 64K conventional memory\r\nfor its pageframe. The situation will be exactly the same as if you had a\r\nboard installed. TC! POWER will now occupy around 15K and not 80K.\r\nThere are several drivers that will help you accomplish this. EMM386.SYS\r\ncomes with MSDOS 4.0 from MicroSoft. QEMM.SYS from Quarterdeck will do the\r\nsame thing for you.\r\nSimply install EMM386.SYS or QEMM.SYS according to their manuals converting\r\nall your extended memory into expanded, reboot your machine, and THEN install\r\nTC! POWER using the INSTALL program. The defaults set forth by TC! POWER should\r\nalways be correct. You can of course increase the HARDDISK USAGE field to\r\ncover your expanded memory needs, but the EXTENDED MEMORY USAGE field will\r\nalready contain its maximum value. The total EMS memory available will be the\r\namount of expanded memory given to you by the 386 driver plus the expanded\r\nmemory emulated by TC! POWER minus 64K.\r\n\r\nUsing EMM386.SYS or QEMM.SYS, TC! POWER will support so called \"page frame\r\naliasing\" necessary to make some programs run. The resulting expanded memory\r\nwill also be much faster than if you told TC! POWER to use your extended\r\nmemory directly. Therefore all your extended memory should be used by\r\nthe 386 driver which will convert it to expanded memory which will eventually\r\nbe used by TC! POWER and passed on to application programs. The whole idea\r\nis of course that TC! POWER will append more expanded memory by using hard\r\ndisk.\r\n\r\n\r\n\r\n\r\nHIDE and SHOW commands free and grab the 64K pageframe\r\n------------------------------------------------------\r\nWhen TC! POWER installs through its DEVICE= directive in CONFIG.SYS, it\r\nis not yet ready to serve your programs. You have to say SHOW to make it\r\noperative. The INSTALL program has been changed to insert the SHOW command\r\ninto the first line of your AUTOEXEC.BAT file. So you should normally not\r\nhave to think about this. Running INSTALL will leave you with an operative\r\nEMS driver.\r\n\r\nWhat IS nice to know is that TC! POWER does not grab 64K conventional memory\r\nfor its pageframe until the SHOW command is given. When you say HIDE\r\nlater on, the 64K pageframe will be freed and TC! POWER will be hidden.\r\n\r\nSo if a program does not use EMS memory at all and you would rather have as\r\nmuch conventional memory as possible, say HIDE before you execute that\r\nprogram and you will have another 64K conventional memory.\r\n\r\nThis allocation / deallocation of 64K conventional take place only if\r\nyou have to use conventional memory for the pageframe. If TC! POWER\r\nis utilizing an existing EMS board or a 386 driver, the 64K pageframe will\r\nnot reside in conventional memory and no allocation / deallocation will\r\nbe performed by SHOW / HIDE. This also applies if you have put the\r\npageframe into a special memory expansion card giving you memory in the\r\nreserved area between 640K and 1MB (by using the /A= parameter).\r\n\r\nHIDE now has an optional switch. Giving the command HIDE /D hides the\r\nTC! POWER EMS driver, frees the pageframe and deletes the swapfile if present.\r\nIf you give the command without any parameters you will avoid deleting the\r\nswapfile, which can have certain advantages. Your disk will probably become\r\nless fragmented resulting in faster disk accesses.\r\n\r\n\r\n\r\n\r\nInstalling or removing drivers in CONFIG.SYS\r\n--------------------------------------------\r\nIf you install or remove drivers in your CONFIG.SYS file which will use\r\nextended memory, you should first deinstall TC! POWER by running the INSTALL\r\nprogram selecting DEINSTALL. Then install the new driver, boot your machine\r\nand re-install TC! POWER by selecting INSTALL in the INSTALL program.\r\nTC! POWER's installation program acts like a tailor, tailoring TC! POWER's\r\nbehaviour and performance. Doing things as described above ensures that\r\nTC! POWER adjusts to the new environment.\r\nIn many cases, this operation is not necessary as TC! POWER ignores the\r\nparameters given on the DEVICE= and adjusts if the environment has changed.\r\nThis will work only as long as all drivers are loaded BEFORE TC! POWER,\r\nand is not the preferred way to do it - the clean thing to do is to\r\ndeinstall and then reinstall TC! POWER after the new drivers have been\r\ninstalled. Then you should have a correct system configuration. This procedure\r\nis necessary if you for instance want to install EMM386 or QEMM when\r\nTC! POWER is already in your machine.\r\n\r\n\r\n\r\n\r\n\r\nThank you for taking the time to read this information. We hope that it was\r\ntime well spent and that you gained a better understanding of what TC! POWER\r\nis capable of doing.\r\n\r\nHappy computing with TC! POWER\r\n\r\nCompuFix/NTI Development" }