home *** CD-ROM | disk | FTP | other *** search
-
- CODEPAD INSTALLATION INSTRUCTIONS
-
- To use CodePad you will need a 386 PC or higher and Microsoft
- Windows 3.0 running in 386 Enhanced or Standard mode.
-
- 1) Copy the contents of this disk into a directory that is on your
- search path such as the WINDOWS directory. The search path is
- specified by the DOS environment variable PATH which is usually
- set from your AUTOEXEC.BAT file.
-
- 2) Add CODEPAD.EXE to the Windows Program Manager.
-
- 3) Update the [Extensions] section of your WIN.INI file to run
- CODEPAD.EXE for the file extensions that you wish to edit. More
- information on setting up extensions is given below.
-
- 4) If you use the Microsoft Windows Software Development Kit (SDK),
- make sure that the SDKWIN.HLP file is reachable from your search
- path. This will allow you to mark and look up SDK topics from
- within CodePad itself, (Press F2).
-
- 5) CodePad can now be run by clicking on a filename in either the
- Windows File Manager or the MS-DOS Executive, or by clicking on
- the CodePad icon in the Program Manager. Detailed user
- instructions are provided in CodePad's on-line Help, (Press F1).
-
-
-
- ORDERING INFORMATION
-
- Send an order requesting the CodePad Editor along with a check or
- money order for $99 to:
-
- Cognetic Systems, Inc.
- 12534 Pinecrest Rd.
- Herndon, Virginia 22071
- (703) 476-7154
-
- *** Be sure to state whether you want a 5-1/4 or 3-1/2 disk.
-
-
-
- CODEPAD LIMITS
-
- CodePad can load large files up to 13,000 lines. A line must be shorter
- than 32,000 characters.
-
-
-
- SUGGESTIONS FOR SETTING UP A WINDOWS DEVELOPMENT ENVIRONMENT
-
- Although not required, you may want to set up a Windows Environment for
- programming. You will need to use Windows 3.0 in 386 enhanced mode and
- you should have at least 4 Megabytes of memory.
-
- The first step is to define as many extensions as you can think of in
- your WIN.INI file. These should include extensions for the CodePad
- Editor, extensions for Make files, the icon editor, SDK paint, etc.
- A sample list of extensions is given at the bottom of this file. Once
- this has been done you can point and click in either the File Manager
- or the MSDOS Executive to run programs.
-
- Set up a MAKE.PIF file to run your make program. Set the KB Required
- field to as large a value as your system will allow. Set the
- Display Usage box to Windowed and set the Execution Box to Background.
- The Close on Exit box should not be checked so that you can read
- any error messages from Make. In the Advanced features section set the
- Background Priority field to 85% and Foreground Priority field to 100%.
-
- If you get an error message during a Make that says "out of heap space"
- this means that the task has run out of conventional DOS memory. There
- are several things you can do to fix this problem:
-
- 1) Make sure to load only the TSR's that you really nead.
-
- 2) Set the buffers= value in CONFIG.SYS to a smaller value. If you
- are using the Window's SMARTDRIVE, buffers can be set as low as
- 10 and still give good results.
-
- 3) Use NMK.COM instead of NMAKE.EXE for your make program. There is
- a big difference in the size of these two programs.
-
-
-
- IMPORTANT CODEPAD FEATURES
-
- Some important CodePad Features that you will want to learn to use
- right away are described below:
-
- 1) Perhaps the most useful capability that CodePad offers is that it
- allows you to view and edit many files at once in a real GUI
- windowing environment. You can now visually grasp more of your
- work than ever before. With this in mind CodePad was developed
- for and tested on the IBM 8514/A monitor as well as the standard
- VGA monitor.
-
- 2) You can browse through source code by dragging the scroll tab with
- the mouse. This causes the source to scroll dynamically as the
- scroll tab is moved. This browsing capability has been optimized
- for both VGA and IBM 8514/A monitors.
-
- 3) CodePad lets you go to a specific line number in your source code
- so that you can locate compiler errors. Also the current line
- number is displayed in the upper right hand corner of the window.
-
- 4) CodePad lets you choose the screen font that you like best. You
- can select any of 5 different mono-spaced fonts.
-
- 5) If you have the Windows SDK Development Kit and have installed
- the SDKWIN.HLP file you can use CodePad to look up help for Windows
- API functions and macros. Simply select a term in your source code
- and press F2.
-
- 6) Mark and Search capability: You can select a term with the mouse
- and press F3 to find its next occurrence. This works for the current
- window as well as across multiple CodePad Windows. For example, you
- can select a Windows macro with your mouse in one window, and then
- run a second instance of CodePad on the WINDOWS.H file. Pressing F3
- will look up the text in the new file.
-
- 7) If you are a Windows user you already know how to use many of
- CodePad's features. Even so, CodePad comes with extensive on-line
- help where you can read about CodePad's advanced features and
- learn to use various mouse editing short cuts.
-
-
-
- SAMPLE EXTENSIONS FOR YOUR WIN.INI FILE
-
- doc=winword.exe ^.doc
- rtf=winword.exe ^.rtf
- sty=winword.exe ^.sty
- ico=sdkpaint.exe ^.ico
- cur=sdkpaint.exe ^.cur
- bmp=sdkpaint.exe ^.bmp
- res=dialog.exe ^.res
- mak=make.pif ^.mak
- dlg=codepad.exe ^.dlg
- .=codepad.exe ^.
- c=codepad.exe ^.c
- h=codepad.exe ^.h
- x=codepad.exe ^.x
- y=codepad.exe ^.y
- z=codepad.exe ^.z
- log=codepad.exe ^.log
- txt=codepad.exe ^.txt
- ini=codepad.exe ^.ini
- bat=codepad.exe ^.bat
- sys=codepad.exe ^.sys
- map=codepad.exe ^.map
- out=codepad.exe ^.out
- old=codepad.exe ^.old
- def=codepad.exe ^.def
- rc=codepad.exe ^.rc
- sav=codepad.exe ^.sav
- new=codepad.exe ^.new
- err=codepad.exe ^.err
- dat=codepad.exe ^.dat
- ans=codepad.exe ^.ans
- sym=codepad.exe ^.sym
- app=codepad.exe ^.app
- dev=codepad.exe ^.dev
- me=codepad.exe ^.me
- asm=codepad.exe ^.asm
- ref=codepad.exe ^.ref
-