I have been having problems setting up both GCBIDE and BasicIDE on both of my computers. Crimson editor seams to work just fine. When I use GCBIDE or BasicIDE the DOS screen flashed for a fraction of a second but no compiling takes place. Does anyone know what I am doing wrong or have a fix for my problem?
Rob
WB0GIH
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The environment setup for GCBIDE is not set properly. Click the "Enviroment setup" button and set the path to GCBasic compiler and ICprog (If you are using ICprog - recommended)
More info for GCBIDE at http://gcbide.googlepages.com/home
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I checked the Environment setup to be sure the path was set properly on both IDE's. I have Great Cow Basic set for Verbose Mode so it takes a few seconds to compile in the DOS window when it id working, however, the DOS window only flashes for a fraction of a second. Its the same problem on both GCBIDE and basicIDE it is leaving me quite bewildered.
I appreciate any help
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can not see first hand on your PC what you have done, but let
us start from scratch.
- Go to GCBIDE directory and delete the "Path.cfg" file.
- Start GCBIDE.
- GCBIDE will not start but a dialog will display the message :
"Missing config file. Set paths"
- Click OK button in dialog screen.
- Dialog will close and GCBIDE will open.
- Set the environment variables. (Paths to GCBIDE and ICPROG)
- Typically GCBasic will be located at c:\Program files\Gcbasic\
BOTH PATHS TO BE SET, even if you do not want to use ICProg.
- If you do not want to use ICProg then enter the following in
the box: C:\IC-prog\
- GCBIDE is currently designed to only call ICPROG.
- It is recommended that you rather use GCBIDE to get the paths
than typing it in by hand.
Ensure that you have only one GCBIDE installed on your PC. The
path file for version 1.3 and 1.4 do not have the same format.
So make sure that version 1.4 is at least not in the same
directory as previous versions.
NOW EXIT GCBIDE AND RUN GCBIDE AGAIN. The problem should be
resolved. The new path file is now located in your GCBIDE
directory and may be viewed but not edited. To use the chip
wizard it is very important to also have the latest Chipdata
file downloaded to GCBasic.
Let us know if resolved. It is important because other users
could have the same problem, meaning a bug.
Emile
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is something that I have already tried. The fact that both BasicIDE and GCBIDE have the same problem leads me to believe that it is a compiler problem however crimson editor works great with the compiler. I have deleted and installed all programs twice. I am an experienced computer user but this on is beyond me. I do like the way GCBIDE is operates if I could get it to work
Again, Thank you for your time and consideration
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is very funny behaviour. I can only speak for GCBIDE. It is giving no trouble with me. With version 1.4 you simply choose a PIC that is supported from the list and set the required usage of the pins graphically. This generates a startoff code which will compile.
(ie Inputs and outputs) On success the compiler dialog will indicate the location of all the relavent files generated. The hex file that is generated can now be directly programmed into your PIC from GCBIDE. GCBIDE calls ICProg as per commandline to do the job. When ICProg is finnished it returns control to GCBIDE. For all this to happen the paths have to be set correctly.
This brings to mind whether you might have some hijackers etc present on your PC. Check for virusses.
For what it is worth, the following for some insight so as to persue your problem.
GCBIDE use "gcbasic.exe /NP file.gcb /O:Compiled.asm /A:GCASM" as the comandline syntax. The GCBasic compiler has the capability to compile the hex file without third party compilers. It has the build in compiler GCASM. Since GCBIDE uses GCASM it is important to have THE LATEST VERSION OF GCBasic TOGETHER WITH THE UPDATE FILES. You simply overwrite the existing GCBasic files with the new ones.
Maybe other users have similar problems or can shed light onto the subject.
Emile
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Emile, I loaded everything onto my laptop and had the same problem. This time the DOS screen flashed just barley long enough to reed it. It displayed.
****************************************
Great Cow Basic (version #)
Cannot find code.gcb
***************************************
The file I am trying ti compile is named morse code.gcb
I do not know if this helps or not
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With GCBIDE a blank/space inbetween the filename will make no differance and will work. GCBIDE uses GCBasic's build in compiler, GCASM to compile the asm to the hex.
Hi Rob
"Morse code.gcb" as per "c:\Program Files\Gcbasic\Demos\Morse code.txt" compiles fine on all my machines. The dos screen flashing quickly without showing errors/success indicates that GCBIDE found the compiler and instructed it by means of commandline (proof that the path has been set), but GCBasic can not find the path back to the file to be compiled. How is that possible? Something fishy.
For me to get a clear picture of your setup, answer all off the following questions then I will have a look at it again.
1. Where did you download GCBIDE from ?
2. Was it the installer program or the zip for GCBIDE ?
3. Where did you download GCBasic from ?
4. Was it the installer program or the zip for GCBasic ?
5. Where is GCBIDE installed ?
6. Where is GCBasic installed ?
7. What is the contents of "path.cfg" in the GCBIDE directory ?
8. What is the file size of "GCBIDE-14.exe" after installation?
9. What is the file size of "Gcbasic.exe" after installation?
10. What is size of "16f84a.dat" in Gcbasic\chipdata directory ?
11. How long have you been using GCBasic ?
12. Have you used previus versions of GCBIDE ?
13. What operating system is running on your PC ?
14. Has any program installed a working path on your PC ?
15. What is the contents of "autoexec.bat" and "config.sys"
located in the root of your boot drive ?
I do not question your PC knowledge. By duplicating your senario on my PC, could get to the answer.
Emile
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>Hi Reelf
>
>With GCBIDE a blank/space inbetween the filename will make no differance and will work. >GCBIDE uses GCBasic's build in compiler, GCASM to compile the asm to the hex.
Really ? Okay, then please ignore my message. Though, I always avoid using blanks and all the other "funny characters" that Windows allows in filenames...
regards,
Reelf
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This problem is probably be due to a change I recently made to the command line parameter handling code in GCBASIC.
Originally, GCBASIC would remove from the command line anything starting with a switch, and then use whatever remained as the filename. However, this caused some trouble when trying to pass spaces to GCBASIC in the name of the assembler or programmer (/A: and /P: switches), so I rewrote the code in GCBASIC to make use of the command line handling code supplied with FreeBASIC. Now, the command line is split up based on the location of unquoted spaces. While this means that more spaces can be used in parameters as long as they're in quotes, it means that GCBASIC will not accept input filenames with spaces unless there are quotes on either side of the filename.
Please try one of these workarounds:
- remove the spaces from the filename
- install a slightly older version of GCBASIC. I can't help here, I haven't got a backup from just before the change.
I'm sorry for this trouble, I should have checked for any compatibility problems before releasing the change.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A new version of GCBIDE will be out ASAP to accommodate for the changes in GCBasic. I preached to all of you to have the latest version of GCBasic, and I did not! Apologies!
Thanks a lot for asking questions like this on the forum, another "BUG/??" identified, keep it up. Also a big thanks to Hugh for his commitment to the fantastic GCBasic.
Regards
Emile
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been having problems setting up both GCBIDE and BasicIDE on both of my computers. Crimson editor seams to work just fine. When I use GCBIDE or BasicIDE the DOS screen flashed for a fraction of a second but no compiling takes place. Does anyone know what I am doing wrong or have a fix for my problem?
Rob
WB0GIH
The environment setup for GCBIDE is not set properly. Click the "Enviroment setup" button and set the path to GCBasic compiler and ICprog (If you are using ICprog - recommended)
More info for GCBIDE at http://gcbide.googlepages.com/home
I checked the Environment setup to be sure the path was set properly on both IDE's. I have Great Cow Basic set for Verbose Mode so it takes a few seconds to compile in the DOS window when it id working, however, the DOS window only flashes for a fraction of a second. Its the same problem on both GCBIDE and basicIDE it is leaving me quite bewildered.
I appreciate any help
Rob
I can not see first hand on your PC what you have done, but let
us start from scratch.
- Go to GCBIDE directory and delete the "Path.cfg" file.
- Start GCBIDE.
- GCBIDE will not start but a dialog will display the message :
"Missing config file. Set paths"
- Click OK button in dialog screen.
- Dialog will close and GCBIDE will open.
- Set the environment variables. (Paths to GCBIDE and ICPROG)
- Typically GCBasic will be located at c:\Program files\Gcbasic\ BOTH PATHS TO BE SET, even if you do not want to use ICProg.
- If you do not want to use ICProg then enter the following in
the box: C:\IC-prog\
- GCBIDE is currently designed to only call ICPROG.
- It is recommended that you rather use GCBIDE to get the paths
than typing it in by hand.
Ensure that you have only one GCBIDE installed on your PC. The
path file for version 1.3 and 1.4 do not have the same format.
So make sure that version 1.4 is at least not in the same
directory as previous versions.
NOW EXIT GCBIDE AND RUN GCBIDE AGAIN. The problem should be
resolved. The new path file is now located in your GCBIDE
directory and may be viewed but not edited. To use the chip
wizard it is very important to also have the latest Chipdata
file downloaded to GCBasic.
Let us know if resolved. It is important because other users
could have the same problem, meaning a bug.
Emile
Emile, Thank you for the response
This is something that I have already tried. The fact that both BasicIDE and GCBIDE have the same problem leads me to believe that it is a compiler problem however crimson editor works great with the compiler. I have deleted and installed all programs twice. I am an experienced computer user but this on is beyond me. I do like the way GCBIDE is operates if I could get it to work
Again, Thank you for your time and consideration
Rob
It is very funny behaviour. I can only speak for GCBIDE. It is giving no trouble with me. With version 1.4 you simply choose a PIC that is supported from the list and set the required usage of the pins graphically. This generates a startoff code which will compile.
(ie Inputs and outputs) On success the compiler dialog will indicate the location of all the relavent files generated. The hex file that is generated can now be directly programmed into your PIC from GCBIDE. GCBIDE calls ICProg as per commandline to do the job. When ICProg is finnished it returns control to GCBIDE. For all this to happen the paths have to be set correctly.
This brings to mind whether you might have some hijackers etc present on your PC. Check for virusses.
For what it is worth, the following for some insight so as to persue your problem.
GCBIDE use "gcbasic.exe /NP file.gcb /O:Compiled.asm /A:GCASM" as the comandline syntax. The GCBasic compiler has the capability to compile the hex file without third party compilers. It has the build in compiler GCASM. Since GCBIDE uses GCASM it is important to have THE LATEST VERSION OF GCBasic TOGETHER WITH THE UPDATE FILES. You simply overwrite the existing GCBasic files with the new ones.
Maybe other users have similar problems or can shed light onto the subject.
Emile
Thank you, I'll wait and see if anyone else comes up with the same problrm. If I find the problem I'll let you know
Rob
Emile, I loaded everything onto my laptop and had the same problem. This time the DOS screen flashed just barley long enough to reed it. It displayed.
****************************************
Great Cow Basic (version #)
Cannot find code.gcb
***************************************
The file I am trying ti compile is named morse code.gcb
I do not know if this helps or not
Rob
Do you have a blank in the filename ? As DOS-calls are used, this won't work.
regards,
Reelf
Hi Reelf
With GCBIDE a blank/space inbetween the filename will make no differance and will work. GCBIDE uses GCBasic's build in compiler, GCASM to compile the asm to the hex.
Hi Rob
"Morse code.gcb" as per "c:\Program Files\Gcbasic\Demos\Morse code.txt" compiles fine on all my machines. The dos screen flashing quickly without showing errors/success indicates that GCBIDE found the compiler and instructed it by means of commandline (proof that the path has been set), but GCBasic can not find the path back to the file to be compiled. How is that possible? Something fishy.
For me to get a clear picture of your setup, answer all off the following questions then I will have a look at it again.
1. Where did you download GCBIDE from ?
2. Was it the installer program or the zip for GCBIDE ?
3. Where did you download GCBasic from ?
4. Was it the installer program or the zip for GCBasic ?
5. Where is GCBIDE installed ?
6. Where is GCBasic installed ?
7. What is the contents of "path.cfg" in the GCBIDE directory ?
8. What is the file size of "GCBIDE-14.exe" after installation?
9. What is the file size of "Gcbasic.exe" after installation?
10. What is size of "16f84a.dat" in Gcbasic\chipdata directory ?
11. How long have you been using GCBasic ?
12. Have you used previus versions of GCBIDE ?
13. What operating system is running on your PC ?
14. Has any program installed a working path on your PC ?
15. What is the contents of "autoexec.bat" and "config.sys"
located in the root of your boot drive ?
I do not question your PC knowledge. By duplicating your senario on my PC, could get to the answer.
Emile
>Hi Reelf
>
>With GCBIDE a blank/space inbetween the filename will make no differance and will work. >GCBIDE uses GCBasic's build in compiler, GCASM to compile the asm to the hex.
Really ? Okay, then please ignore my message. Though, I always avoid using blanks and all the other "funny characters" that Windows allows in filenames...
regards,
Reelf
This problem is probably be due to a change I recently made to the command line parameter handling code in GCBASIC.
Originally, GCBASIC would remove from the command line anything starting with a switch, and then use whatever remained as the filename. However, this caused some trouble when trying to pass spaces to GCBASIC in the name of the assembler or programmer (/A: and /P: switches), so I rewrote the code in GCBASIC to make use of the command line handling code supplied with FreeBASIC. Now, the command line is split up based on the location of unquoted spaces. While this means that more spaces can be used in parameters as long as they're in quotes, it means that GCBASIC will not accept input filenames with spaces unless there are quotes on either side of the filename.
Please try one of these workarounds:
- remove the spaces from the filename
- install a slightly older version of GCBASIC. I can't help here, I haven't got a backup from just before the change.
I'm sorry for this trouble, I should have checked for any compatibility problems before releasing the change.
Hi Rob / Reelf
A new version of GCBIDE will be out ASAP to accommodate for the changes in GCBasic. I preached to all of you to have the latest version of GCBasic, and I did not! Apologies!
Thanks a lot for asking questions like this on the forum, another "BUG/??" identified, keep it up. Also a big thanks to Hugh for his commitment to the fantastic GCBasic.
Regards
Emile