I have taken your led blink file, altered the processor type and tried to produce a hex file using the gcbide program. It tells me it has been produced but I can not find it! I have tried the same by pulling the *filename*.qcb icon over the compile icon as instructed somewhere. It also says it has compiled but I still can not find the hex file. Apart from that it all works fine so far, any clues? My pc is running win98 on a toshiba laptop if that helps.
regards
Bob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
FOUND, my misunderstanding. The program tells me it is saving to one file with a file name but it is not. I gather the filename and location is actually fixed and I guess I would have to rename that file before trying to save another one. At least now I can generate a hex file by dragging the icon across. Still cannot generate a hex file using gcbide (even though it tells me it has completed the tsk) but that is a separate issue!
regards
Bob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 1.3 of GCBIDE will show you in the compiler dialog where "*.asm", "*.gcb" and "*.hex" files are saved. The directory would be where you saved your "*.gcb" file or from where you opened it. A "Noname.gcb" etc will be saved in the GCBasic directory. The old "Noname.gcb" will always be overwritten. So saving is fundumental/good practise.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have taken your led blink file, altered the processor type and tried to produce a hex file using the gcbide program. It tells me it has been produced but I can not find it! I have tried the same by pulling the *filename*.qcb icon over the compile icon as instructed somewhere. It also says it has compiled but I still can not find the hex file. Apart from that it all works fine so far, any clues? My pc is running win98 on a toshiba laptop if that helps.
regards
Bob
FOUND, my misunderstanding. The program tells me it is saving to one file with a file name but it is not. I gather the filename and location is actually fixed and I guess I would have to rename that file before trying to save another one. At least now I can generate a hex file by dragging the icon across. Still cannot generate a hex file using gcbide (even though it tells me it has completed the tsk) but that is a separate issue!
regards
Bob
Version 1.3 of GCBIDE will show you in the compiler dialog where "*.asm", "*.gcb" and "*.hex" files are saved. The directory would be where you saved your "*.gcb" file or from where you opened it. A "Noname.gcb" etc will be saved in the GCBasic directory. The old "Noname.gcb" will always be overwritten. So saving is fundumental/good practise.