Haroen

Is it possible to use the GCBsoftware (SynWrite 6.22.2290) to hexflash without automatic saving to disk? Normally I program by having a leading file with code and test all sorts of situation codes before I save again. After some time I backup that file and move on with more changes. Often I retrieve the previous backups to investigate the trials and errors. So therefore I checked the PullDown menu, Options, Customize and couldn't find such setting.

There is the criteria of HDD versus SSD with only 3000 write cycles. In the past I've changed my original HDD to a SSD and april 2022 had to replace the SSD for failing most likely of exeeding the “Wear Level". From then on I keep track and minimizing software writes to SSD drive for longer life span. So, with every GCB Flash test to the chip I will degrade my SSD and with a Hex even further for making an extra hex-file too. With softwares like GC-Code and AutoVer that will expand the problem by...

SDD drives spread the data around so it doesn't rewrite the same drive memory I think I think so but does that apply to editting the same (GCBfile) over and over again too? A RAM drive? They still exist and are very clever. Write to the RAM drive then move the final file to SDD. Great idea for a very fast separate drive and problem can be solved if GCBsoftware could have the option to only do (Hex)FlashSave to RAM drive and keep the CodeSave to SSD with the existing Save icon. Then even a cheaper...

@Angel Mier Good to know, thanks for the reasurance of the SSD drive criteria. But in the end there still remains the "problem" we all have, and try to correct by alternative methods, of not wanting to save to disk by flashing a chip. No more exidental overwrites. 'workingdir = "tempdir" So, if you set your system temp directory to an external USB drive - all temp file ( including the OS temp files) will be written to the USB drive. You would have to change the System Environment Variables tmp and...

If the GCB-editor can't write to a different directory/drive for the Compiler to flash the gcb supported external chip than indeed Timeline, AutoVer and SynWrite are the only solutions.

Indeed, after every HexFlash 5 files will be created instead of what I thought just one *.gcb file. To avoid saving every hexflash as seperate files for every trial with Timeline, AutoVer and SynWrite I've decided to manually copy a backup file every time I think some part of code should be saved. Not a problem yet because now I'm just learning examples in my spare time. Thanks for the help everyone.

I use the Windows-Explorer method of selecting the file and holding the Right Mouse button and drag the file(with the cursor) to an empty spot in the same folder thus creating copies from Haroen.txt like: Haroen - kopie.txt Haroen - kopie (2).txt Haroen - kopie (3).txt

Thinking out loud... As a GCbasic wannabe I want to know what kind of assumptions I should take I started with an Arduino Nano for PWM without having capabilities info Knowing the EDM freq range 4-5KHz resolution 0.001 There is a list of GCB supported chips *GCB has a glcd.h file for displays in which various displays are bundled together and a specific type can be called by #define. Idea: There may also be a (H)PWM.h file that provides a frequency resolution based on the chosen chip and the desired...