Below a collection of WCOP8 IDE questions and answers. If you have questions to (or
troubles with) your WCOP8 IDE installation please consult this list before you request technical support.
- Examine information passed from WCOP8 IDE to DOS
- DOS-box show as default
- Hide the DOS-box when running Windows NT
- Could not start a DOS-prompt message
- Unable to launch EPU message
- Unable to launch Debug Module message
- Unable to launch iceMASTER message
- Unable to launch iceDEMO/iceSIM
- DOS-box sometimes lock-up
- How to check for latest version of
WCOP8 IDE
- Can I use the Project Wizard from WCOP8 IDE ver. 1.x?
- Launching WCOP8 IDE automatically when
double-clicking a project/file
- Creating a shortcut to WCOP8 IDE on the desktop in
Windows 95/NT 4.x
- Does WCOP8 IDE support command line parameters?
- Does WCOP8 IDE support Drag-and-Drop?
- Does WCOP8 IDE have Microsoft IntelliMouse support?
- Why do I get "Runtime error 202" when locating
tools?
- Why can't the C-compiler find the header files?
----
Q: Is it possible to examine the
information which is passed from WCOP8 IDE to the DOS programs such as
Assembler/Linker or Debug tools?
A: The DOS box which WCOP8 IDE uses to communicate with the various DOS tools
can be toggled on/off via the Window menu. When the DOS box is toggled ON all information
which is pasted to the DOS box can be seen on the screen in real time. Whenever WCOP8 IDE
is opened the default setting is NOT shown.
----
Q: Is it possible to have the DOS-box shown
as default upon launch in Windows 3.x, 95 and 98?
A: Yes - open the WCOP8.INI file located in you Windows directory in a text
editor (eg Notepad). Change the "ShowBox" setting from "0" to
"1".
----
Q: Is it possible to hide the DOS-box
when running Windows NT?
A: No - due to the way DOS-boxes are handled in Windows NT they will have to be
visible otherwise the invocation will fail from time to time. This means that whenever
WCOP8 IDE is active also a WCOP8 IDE controlled DOS box will also be seen in the system.
Please note that all handling of these DOS boxes is automatically done by WCOP8 IDE.
----
Q: A message similar to "Could not
start a DOS-prompt" is presented and WCOP8 IDE closes?
A: There is a number of reasons which causes this message to be shown but they
all occur because the WCOP8 IDE tool either was not able to launch the DOS-box or unable
to detect whether the DOS box is up and ready to receive input. Try one following steps:
- If you are running on either Windows 3.x, 95 or 98 locate the WCOP8.PIF file in your
Windows directory and execute, e.g. using Explorer. A DOS-box should now appear with the
title bar "@DOSWINDOW@". If this is not the case then there is a problem with
your Windows installation and a re-installation might be necessary.
- If you are running on Windows NT locate the WCOPNT.PIF file in your Windows directory
and execute, eg using Windows Explorer. A DOS-box should now appear with the title bar
"@DOSWINDOW@". If this is not the case then either there is a problem with your
Windows installation and a re-installation might be necessary or the WCOPAUTO.NT or
WCOPCONF.NT files contain information that locks up your system. Open the WCOPAUTO.NT and
WCOPCONF.NT files in a text editor (eg Notepad) and analyse the contents for statements
that could block your system.
- If the above does not create the problem then the detected Windows version might be
wrong. Open the WCOP8.INI file located in the Windows directory in a text editor (eg
Notepad). Locate the "[InstallInfo]" section and check that the value supplied
for "WinVer" is: 1=Win3.x, 2=Win95/98, 3=WinNT3.x and 4=WinNT4. If the wrong
value is stated then correct it, save the file and try launching the WCOP8 IDE tool.
----
Q: A message similar to "Unable to
launch EPU!" is presented when trying to launch the MetaLink DOS EPU?
A: There is a number of reasons which causes this message to be shown but they
all occur because the WCOP8 IDE tool either was not able to launch the DOS-box or unable
to detect whether the DOS box was up and ready to receive input. Try one following steps:
- If you are running on either Windows 3.x, 95 or 98 locate the EPU.PIF file in your
Windows directory and execute eg using Windows Explorer. A DOS-box should now appear with
the title bar "EPU-Window". If this is not the case then there is a problem with
your Windows installation and a re-installation might be necessary.
- If you are running on Windows NT locate the EPUNT.PIF file in your Windows directory and
execute, eg using Windows Explorer. A DOS-box should now appear with the title bar
"EPU-Window". If this is not the case then either there is a problem with your
Windows installation and a re-installation might be
necessary or the WCOPAUTO.NT or WCOPCONF.NT files contain information that locks up your
system. Open the WCOPAUTO.NT and WCOPCONF.NT files in a text editor (eg Notepad) and
analyse the contents for statements that could block your system.
----
Q: A message similar to "Unable
to launch Debug Module!" is presented when trying to launch the MetaLink DOS
Debug Module?
A: See the above answer for the MetaLink EPU…
----
Q: A message similar to "Unable to
launch iceMASTER!" is presented when trying to launch the MetaLink DOS iceMASTER?
A: See the above answer for the MetaLink EPU…
----
Q: A message similar to "Unable
to launch iceDEMO/iceSIM!" is presented when trying to launch the MetaLink DOS
iceDEMO/iceSIM?
A: See the above answer for the MetaLink EPU…
----
Q: When I compile my files using WCOP8 IDE a DOS-box lock-up sometimes occur. Why does this
happen and what can I do to avoid it?
A: A lock-up condition sometimes occurs when using WCOP8 IDE with some older
versions of the Byte Craft C compiler. We have seen that under rough tests this compiler
locks up in the DOS box and the WCOP8 IDE looses contact with it. This is not always due
to an error in the WCOP8 IDE since the same would be the case if the compiler was invoked
manually from a DOS box. If such a DOS box lock-up occurs WCOP8 IDE automatically detects
this and notifies the user and the lock-up can be corrected by closing the DOS box.
If a DOS box lock-up occurred when using the C compiler, double check the C source code
(maybe an invalid or misspelled C compiler #pragma is used) and also check the system
performance settings in the WCOP8 IDE configuration program. Try to set the system
performance setting to a lower value. Relaunch the WCOP8 IDE and try again.
If lock-up or any other kind of problems persist then send us an e-mail with a detailed
description of the behaviour.
----
Q: How can I check whether my copy of WCOP8 IDE is the latest revision
available?
A: The revision of your current WCOP8 IDE s/w can be checked by selecting the
About item in the Help menu. On the "About" form the WCOP8 IDE revision number
will be shown. To get a newer version you can browse to our WWW site at http://www.kkd.dk.
Here you will find the latest revisions which can be downloaded and used for upgrading of
your current revision. An automatic link to our homepage can be found in the Help menu by
choosing the KKD On The Web item.
----
Q: Can I use the Project Wizard from WCOP8 IDE
ver. 1.x?
A: No - The project handling has been changed significantly in ver. 2.x.
Working with projects is now a much more simple task and there is no longer a need for a
Project Wizard.
I the Project Wizard is used anyway the project might not assemble/compile or link
properly.
----
Q: Launching WCOP8 IDE automatically
when double-clicking a project/file
A: In order to do this an association between
file extensions and WCOP8 IDE is required. When this association has been created it will
be possible to launch WCOP8IDE and open files/projects from within your File Manager just
by double clicking them.
The association between file extensions and programs is made
differently in Windows 3.x/NT 3.5x and Windows 95/NT 4.x. In the following it is shown how
to associate all files with the extension .PRJ to WCOP8 IDE for both Windows types:
Windows 3.x/NT 3.5x
1. Launch the Windows File Manger from your system folder
2. Browse and select a file with the extension .PRJ (eg the project which is supplied with
WCOP8 IDE in the example directory)
3. Choose "associate" from the "File" menu in the File Manager
4. If WCOP8 IDE is not on the list of programs, use the Browse facility to find the
program file WCOP8.EXE
5. Select OK twice
Windows 95/NT 4.x
1. Launch the Windows Explorer from your Start menu
2. Browse and select a file with the extension .PRJ (eg the project which is supplied with
WCOP8 IDE in the example directory)
3. Double click on the file and an "Open with.." dialog box appears
4. Type a short description of the file type (eg "WCOP8 IDE projects")
5. If WCOP8 IDE is not on the list of programs, use the "Other…" facility
to find the program file WCOP8.EXE
6. Select OK
When the above steps have been performed all files with the extension .PRJ can be
opened within WCOP8 IDE just by double clicking them in your File Manager.
If double clicking Assembler files (.ASM) or C files (.C) should also invoke WCOP8 IDE,
the above steps have to be performed on both these file types as well.
----
Q: Creating a shortcut to WCOP8 IDE on
the desktop in Windows 95/NT 4.x
A: In Windows 95/NT 4.x shortcuts to .PRJ files can be created and placed on
the Windows desk-top. By double clicking these shortcuts, WCOP8 IDE is launched and the
project opened. A Windows 95/NT 4.x shortcut can be created as follows:
1. Press the right mouse button on the Windows 95/NT 4.x desktop
2. Select "New" and then "Shortcut"
3. Use the "Browse" button to search all valid drives for the desired project
file
4. When the file has been located use the "Open" button to select it
5. Press the "Next" button
6. Enter a name for the shortcut
7. Press the "Finish" button
When done, a shortcut icon to the selected project is shown on the Windows 95/NT 4.x
desktop.
----
Q: Does WCOP8 IDE support command
line parameters?
A: Yes - When invoking WCOP8 IDE it is possible to specify one or more
file(s) or a project on the command line. The file(s) specified will the be opened in an
editor window. If the file specified has a .PRJ extension WCOP8 IDE interprets this as an
"Open Project" command and opens the project as specified in the .PRJ file. All
other extensions will be interpreted as an "Open File" command.
Examples:
c:\cop8\wcop8>WCOP8.EXE c:\cop8\wcop8\example\my_proj.prj will launch WCOP8 IDE and
then open the project "MY_PROJ.PRJ".
c:\cop8\wcop8>WCOP8.EXE c:\cop8\wcop8\example\test.asm will
launch WCOP8 IDE and then open "TEST.ASM" in an editor window.
----
Q: Does WCOP8 IDE support Drag-and-Drop?
A: Yes - Drag-and-Drop means that a file can be dragged from one program and dropped, i.e. opened in another program. In
order to do so, both programs have to support the drag and drop feature. WCOP8 IDE
supports three types of drag-and-drop:
1. Whenever a file (with an extension different from
.PRJ) is dropped onto the WCOP8 IDE workspace the file is automatically opened.
2. Whenever a file with the .PRJ extension is dropped onto the WCOP8 IDE workspace the
project is automatically opened.
3. Whenever a file with the .ASM or .C extension is dropped onto a project window the file
is included in the project provided it is a project containing the same file types.
----
Q: Does WCOP8 IDE have Microsoft IntelliMouse
support?
A: No not directly but if you are using an updated driver you can select
"Universal Scrolling" which will enable support for IntelliMouse in
WCOP8 IDE. If this is not possible in your driver then download an updated version from: http://www.microsoft.com/products/hardware/mouse/driver/default.htm
----
Q: Why do I get "Runtime error 202"
when locating tools?
A: If you have C drive with huge capacity or a very deep directory structure
WCOP8 IDE can have a stack overflow when recursing through the disk contents. A work
around would be to open the "WCOP8.INI" file located in your Windows directory
and change/add the following section:
[DefaultTools]
ASMCompiler=<path to your assembler, e.g. c:\cop8\assembler\asmcop.exe>
Linker=<path to your linker, e.g. c:\cop8\assembler\lncop.exe>
Promcop=<path to your PROM utility, e.g. c:\cop8\assembler\promcop.exe>
CCompiler=<path to your C compiler, e.g. c:\cop8\c\cop8c.exe>
BCLink=<path to your C compiler, e.g. c:\cop8\c\bclink.exe>
If you do not have or do not want to install a particular tool simply write "no
match" instead of the path. Relaunch WCOP8 IDE to make the new settings active.
The problem has been fixed in verion 2.05 or later.
----
Q: Why can't the C-compiler find the
header files?
A: ByteCraft moved the chip specific header files from the compiler
directory to a subdirectory, i.e. ..\headers. Version 2.04 (or previous) does not support
this. Either you must copy the files to the compiler directory or even better upgrade to
WCOP8 IDE version 2.05 (or later). |
