Saves Don't Aways Save

BobDye

Another frustrating bug. Since the BREAK statements don't work, I used lots of PRINT #1: whatever to see how the program is progressing. Then I "!"'ed those lines and ran the program again. Lo - those statements still appeared in the output file and when I returned to the program, those lines were not REM! I made a change to the program, REMing those PRINT #! statements again, compiled /saved it, and ran it. It ran well but when I retuned to the program listing, my changes had vanished! After trying several things, the only way that I was able to save my changes was to save and EXIT the program.

mcc

Hello Bob,

What version of TB are you using? Is it the v6. something with the new editor? I never heard of such problems you seem to be having. This HAS to be being caused by the new editor or something they've done to the thing with the "installer".
None of these things have ever manifested themselves with any version of TB I have ever used. You are using the new editor which comes with v6, I assume.

I have never "installed" any version of TB; just copied the LIBs and EXE's into some convenient folder and have NEVER had any such problems as you have been describing. There is NOTHING new in the basic core code; never has changed (because they don't know HOW to change it); the only thing "new" is the editor and whatever this "installer" is.

I don't know what files you get with this v.6, but If you can get to the TBsystem.exe and the various libraries such as TrueCTRL.trc, etc., you should be able to work out of a standard text editor. The GOLD version 5.5b19 which was the last one before the v.6's had a few bugs which are in the part of the TB system which tries to work with Windows, but NOTHING like what you're describing. This "legacy" version is still available, I think, somewhere on this website .

The last "good" version, in my opinion, was the Silver 5.33 which I also have. There is NOTHING wrong with that one ; the only thing is if you bind code into an EXE you must always keep the dll's with it. I don't think they still offer that one, which is a shame. The core of TB has NEVER changed, the problems were always with the extra stuff needed to get it to work under windows. The MAC OS kept changing so much that TB couldn't be kept up with that OS. That's a shame, too.

The only thing I can suggest is to write and save your code in an external third party text editor, of which there are many good free ones, and run the code using the TB system.exe. I assume the system.exe file can be located among whatever files get "installed" with this v6. Sorry I can't be of more help with this.

Regards, Mike C.

daveR

I have TB 6 installed on Windows 10 without any of these issues. I have it installed in my C directory, not the Program Files directory as Windows protects the Program Files directory but not the C directory. Files cannot be written to in Program Files, they are automatically write protected. If this is where you installed True Basic, copy it over to C directory and try again.