+- QB64 Phoenix Edition (https://qb64phoenix.com/forum)
+-- Forum: QB64 Rising (https://qb64phoenix.com/forum/forumdisplay.php?fid=1)
+--- Forum: Code and Stuff (https://qb64phoenix.com/forum/forumdisplay.php?fid=3)
+---- Forum: Help Me! (https://qb64phoenix.com/forum/forumdisplay.php?fid=10)
+---- Thread: "Can't save program!" message (/showthread.php?tid=734)
RE: "Can't save program!" message - PhilOfPerth - 08-05-2022
As suggested, I've whitelisted QB64.
@Steve you were correct in it being a Permissions issue. Somehow, all the .bas files had been changed to read-only. (maybe by changing the directory?). I have added "Everyone" as a user and given full access. I hope that's a safe thing to do?
RE: "Can't save program!" message - admin - 08-05-2022
I think what you had was a two-fold problem.
First was putting your QB64 into a system folder (C:\Program Files and C:\Program Files (x86) are both considered to be system folders and thus have enhanced security and reduced permissions on them. It's best not to put anything there yourself, as those tend to be "Read Only" access type areas, with all the data files that pertain to them in your AppData folder or MyDocuments folders. EXEs, like QB64.EXE, tend to run into all sorts of issues when trying to write to either of the Program Files directories themselves. That's not to say that you can't do it -- but you can only do it by tweaking permissions, and then being prepared to retweak those exact same permissions every time Windows does an update and resets its security settings.)
By moving your QB64 folder off to a non-system area, such as to C:\QB64\ you should be able to get rid of any issues with the permission levels and UAC causing you problems. (Exception might be with a removeable drive, as Windows might have ownership of it tagged as belonging to another person/PC, which you'd need to overwrite first.)
Your second issue appears to have been with your antivirus speaking up and saying, "I don't know this EXE! It must be bad!" Of course it's not going to know an EXE which you just compiled and created -- its an EXE that's never existed before to get listed in their database of "Okay Products". The antivirus speaks up, quarantines or deletes the file, and causes issues. In this case, it sounds as if your anti-virus has some pretty strong permissions and an incredibly heavy hand, as it seems as if it keeps setting folder permissions and all to "Read Only", even after you've manually went in and changed them! The only way to get around this type of issue, is by whitelisting your folder and telling your antivirus to, "Buzz off! These are EXEs I created! I didn't write myself a virus, you dumb software!!"
As long as it's your PC, and you don't plan on letting everyone in the world use it (such as a library computer, or one in the cyber-cafe coffee shops), you should be more than fine by setting permissions to "Everyone", as you mentioned above. Basically, "Everyone" is an user base that says, "If they can log into this computer, then they can access these files." Since QB64 isn't your top secret porn folder which you need to hide from your wife and kids (at least, I hope it's not), there shouldn't be any real issues by assigning full read/write permissions to "Everyone". After all it's just "Everyone who can log into this PC," and chances are, if someone can already log into your PC, then they can just alter permissions or ownership already, so all those other security features that make you jump through hoops are honestly nothing more than a PITA to begin with.
RE: "Can't save program!" message - SMcNeill - 08-05-2022
(And keep in mind, *admin* from above is the same as *SMcNeill* here. I tend to try and keep an admin account for forum settings and approving new members and all, without doing a lot of posting unless it's something "official" for the forums, but then I tend to forget to log out from time to time and swap back over to lovable little Steve! admin = me -- just in what should be a slightly more "official" voice, except when it comes to typing at 2:00 in the morning and then I end up forgetting which account I'm logged into at the moment. LOL!! )
RE: "Can't save program!" message - PhilOfPerth - 08-05-2022
All my progs are able to be edited again after re-setting all the security stuff.
Thanks all for your patience and help. As you can see, I'm not that au fait with file protocols and stuff; I just enjoy "fiddling" to keep the brain alive, and it's great to know I can get a bit of support when I need it.
RE: "Can't save program!" message - Pete - 08-05-2022
Curious. Have you tried...
Select All
Copy program code
Paste program code to Notepad
Save using Notepad to the same QB64 folder with the same program name?
Pete
RE: "Can't save program!" message - bplus - 08-05-2022
Glad Phil has issues worked out but speaking of admin and Windows protocols: it is only they that are allowed below the user levels and it is uninformed admin of single person computers that get into security breach issues the most with Windows. This vulnerable area is what Windows is clamping down on because all their new spyware opens up that vulnerability.
Best to do your normal work in User Folders ie ...user\name\... not from root, is my advice for Windows users.
RE: "Can't save program!" message - Pete - 08-05-2022
I avoid all Windows controlled folders, altogether. I've even heard stories of files getting messed up with major updates in the sub-directories of Windows\Users\ folder. Just make your own QB64 directory off the root, like C:\myQB64 and you are golden.
Pete
RE: "Can't save program!" message - SMcNeill - 08-05-2022
Even better, put everything on drive D: and avoid the C: drive completely.
RE: "Can't save program!" message - bplus - 08-05-2022
(08-05-2022, 06:00 PM)SMcNeill Wrote: Even better, put everything on drive D: and avoid the C: drive completely.
LOL., wait... he's right! Keep your precious on flash drives. Even Disk Partitions aren't safe from Windows Updates!
RE: "Can't save program!" message - Pete - 08-05-2022
(08-05-2022, 06:00 PM)SMcNeill Wrote: Even better, put everything on drive D: and avoid the C: drive completely.
Well for my little laptop, that would be my optical CD-ROM drive, so no!
Pete