---------------------------------------- @@ Questions and Answers ........................................ This file contains a list of answers for the most frequently asked questions. You may be able to find the answer to your question in this file. In any case, our Tech Support number is (206) 937-9335. Good Luck ---------------------------------------- ---------------------------------------- Change the CmdPost window title ........................................ Look in CMDPOST.CPM file for Titlefirst= for 1st CP window name TitleRest= for 2nd CP window name Names must be different to work right ---------------------------------------- ---------------------------------------- Change the PATH for DOS apps ........................................ If you need to run a old DOS application with a "different path", a simple batch file has been supplied to assist you in doing this. Instead of having zillions of little BAT files around, a simgle one will do. See the file CP_VIRT.BAT in your installation directory. It can set a path, run a program and pass some parameters. ---------------------------------------- ---------------------------------------- Closed CmdPost, Still in Windows!!??? ........................................ A "feature" of the new Command Post, when it is the primary shell in WIN3 (via the shell= in system.ini) is that the CmdPost window may be closed without exiting Windows. This allows ALL of the shell memory to be freed if you need it. When you close the last window, you will exit Windows. Use the Exit Windows command to terminate Windows immediately. ---------------------------------------- ---------------------------------------- How to get back taskmanager/tasklist ........................................ If either thru an old install program, or thru user modification, the tasklist is gone, the probable solution is to find TASKMANG.EXE in the Windows directory, and rename it to TASKMAN.EXE If on a NETWORK, remove occurrances of TASKMAN.EXE except in the network windows directory. ---------------------------------------- ---------------------------------------- How to size the startup CmdPost window ........................................ 1) Set the CmdPost window just where you want it. 2) Under the MAIN menu item, select Reset Options. It will save current position. ---------------------------------------- ---------------------------------------- How-2-Make a DirChange "stick" ........................................ Executing a DirChange command in a CmdPost menu does not affect the display UNTIL a SetDisplay command is executed. The SetDisplay command makes the DirChange stick so that the display is updated. Example: &SubDirs &Windows Dir DirChange("C:\WINDOWS") SetDisplay("","","") ---------------------------------------- ---------------------------------------- Initialization Failure Error ........................................ Command Post starts up, has initialization failure error. to fix: Edit win.ini file CMDPOST.EXE will be on both the run= and load= line. Remove one reference. ---------------------------------------- ---------------------------------------- Install Fails ........................................ The automatic install does not work 100% of the time (yet). If you have problems with the automatic install, try the manual install. ---------------------------------------- ---------------------------------------- Run= and Load= in WIN.INI no work #1 ........................................ When Command Post is the primary shell (as defined in the system.ini file) the run= and load= lines in the win.ini file are IGNORED. The reasoning here is that anything you want started up should be in the CMDUSER.CPM (or the CMDPOST.CPM) files with the other auto-initialize stuff. See the next card for sample code. ---------------------------------------- ---------------------------------------- Run= and Load= in WIN.INI no work #2 ........................................ Sample code. Instead of using the run= and load= statements in the win.ini file, add something like the following to the top of your cmduser.cpm file: Terminate(IsRunning(),"","") RunIcon("this.exe","") Run("that.exe","") ---------------------------------------- ---------------------------------------- Running screen blanker ........................................ To run the blanker w/o CP, edit WIN.INI, in the windows section add [windows] load=blanker.xyz in the extension section add [extensions] xyz=cp_blnk.exe 5 <<--Notice parm CP_DLL.EXE & CP_BLNK.EXE required files. If you just run it, the default parameter is -5 ---------------------------------------- ---------------------------------------- Translate xxx.exe @^.^ @^.BAK ........................................ One tricky translation from the old menu language to the new one is the translation of lines with only the root of the filename used. The above translates to... File=CurrentFile() Root=FileRoot(File) Run("xxx.exe","%File% %Root%.BAK") ---------------------------------------- ---------------------------------------- WIN2 "Directly Modifies Memory" #1 ........................................ In Windows 2.x, 286 there was a box in the PIF editor for DOS applications that directly modified memory. When Windows saw this box checked, it basically exited Windows, ran the DOS application, and restarted windows when the DOS app exited. In Windows 3.0 there is no such capability. If you need this capability (either in WIN2 or in WIN3 for some reason)... [continued] ---------------------------------------- ---------------------------------------- WIN2 "Directly Modifies Memory" #2 ........................................ Command Post 7.0 does not support the WIN2 286 "Directly Modifies Memory Flag" but here is a reasonable workaround. Write a couple of standard DOS bat file, and a CmdPost menu item for it. The BATFILE titles are: 1) WINDOWS.BAT Main Windows BAT file. 2) DOSAPP1.BAT Bat file for your DOS app [continued] ---------------------------------------- ---------------------------------------- WIN2 "Directly Modifies Memory" #3 ........................................ WINDOWS.BAT MAIN BAT FILE :TOP C: CD \WINDOWS ERASE WINNEXT.BAT WIN IF EXIST WINNEXT.BAT THEN WINNEXT.BAT EXIT ---------------------------------------- ---------------------------------------- WIN2 "Directly Modifies Memory" #4 ........................................ DOSAPP1.BAT SAMPLE BAT FILE D: CD \SOMEODD\DIRECTRY APP1.EXE /options and such WINDOWS.BAT ---------------------------------------- ---------------------------------------- WIN2 "Directly Modifies Memory" #5 ........................................ And the Command Post menu item... &DOSAPPS &DOSAPP1 DirChange("C:\WINDOWS") FileCopy("DOSAPP1.BAT","WINNEXT.BAT") EndSession() ---------------------------------------- ---------------------------------------- WIN2 "Directly Modifies Memory" #6 ........................................ When you start Windows with the WINDOWS.BAT file, the first thing it does is delete the WINNEXT.BAT file. Then it calls Windows. When the CmdPost menu item is executed, the DOSAPP1.BAT file is copied to WINNEXT.BAT, and then Windows is exited. Back to the WINDOWS.BAT file [continued] ---------------------------------------- ---------------------------------------- WIN2 "Directly Modifies Memory" #7 ........................................ The WINDOWS.BAT file checks for existance of the WINNEXT.BAT file, and if it exists, executes it. That runs your DOS app. When you exit your DOS app, the WINDOWS.BAT file is restarted. This way you can run any program incompatible with Windows from Command Post. ----------------------------------------