WIN7
When saving new source purebasic IDE informs me following (with red cross/X icon) but it still saves project.cfg to source directory. I can dismiss it by just by pressing OK since it happens only when I save first time. Source directory is at other drive and has full access. I don't use project manager.
---------------------------
PureBasic
---------------------------
Cannot save Compiler options to file:
project.cfg.new
---------------------------
OK
---------------------------
update: with 4.40 betas 4-6 (before that I did not have win7 so I don't know earlier)
possible bug: WIN7 + purebasic (project.cfg.new)
possible bug: WIN7 + purebasic (project.cfg.new)
Code: Select all
; Hello, World!- Dreamland Fantasy
- Enthusiast

- Posts: 335
- Joined: Fri Jun 11, 2004 9:35 pm
- Location: Glasgow, UK
- Contact:
Re: possible bug: WIN7 + purebasic (project.cfg.new)
Hi Azul,
I don't know if you use Kaspersky Anti-Virus or Internet Security, but there are some known issues with that and Windows 7 that can cause some strange behaviour.
Kind regards,
Francis
I don't know if you use Kaspersky Anti-Virus or Internet Security, but there are some known issues with that and Windows 7 that can cause some strange behaviour.
Kind regards,
Francis
Re: possible bug: WIN7 + purebasic (project.cfg.new)
Sorry for late reply,
I have Comodo (firewall) and Avast (antivirus)
I have Comodo (firewall) and Avast (antivirus)
-
IdeasVacuum
- Always Here

- Posts: 6426
- Joined: Fri Oct 23, 2009 2:33 am
- Location: Wales, UK
- Contact:
Re: possible bug: WIN7 + purebasic (project.cfg.new)
I have seen Avast prevent the install/running of perfectly legitimate applications on WinXP, including software that costs thousands (does not seem to like software communicating with dongles). A false negative. All is not lost, you should be able to Add PB to the Avast "white list", a list of trusted applications - it should then leave PB alone.Azul wrote:Sorry for late reply,
I have Comodo (firewall) and Avast (antivirus)
IdeasVacuum
If it sounds simple, you have not grasped the complexity.
If it sounds simple, you have not grasped the complexity.
Re: possible bug: WIN7 + purebasic (project.cfg.new)
I disabled whole avast and this is still happening.
Code: Select all
; Hello, World!-
IdeasVacuum
- Always Here

- Posts: 6426
- Joined: Fri Oct 23, 2009 2:33 am
- Location: Wales, UK
- Contact:
Re: possible bug: WIN7 + purebasic (project.cfg.new)
I do not have Windows7 but from what I have recently read about the OS, it could be a Win7 security 'feature' that is causing the issue. Ensure that your project folder is not in a system area (like program files) and that your User has full admin privileges.
IdeasVacuum
If it sounds simple, you have not grasped the complexity.
If it sounds simple, you have not grasped the complexity.
Re: possible bug: WIN7 + purebasic (project.cfg.new)
project.cfg does appear into project folder (which is writable and located at d:\) but it just gives error about "project.cfg.new" and after clicking "ok" all is fineIdeasVacuum wrote:I do not have Windows7 but from what I have recently read about the OS, it could be a Win7 security 'feature' that is causing the issue. Ensure that your project folder is not in a system area (like program files) and that your User has full admin privileges.
I reinstalled win7 (for another reason, rc1 to retail .. with full format to HDD) and problem did not go away.
I don't mind clicking that window with every new program but it might cause confusion with new users.
Code: Select all
; Hello, World!Re: possible bug: WIN7 + purebasic (project.cfg.new)
it could be from the win7 security stuff, you could try either turning the security down, or right click purebasic exe, and "run as administrator"
on the other hand it could be avast
i use win7 at work and have not have this problem. i had purebasic installed in program files, then later reinstalled to c:\purebasic. no issues either way
on the other hand it could be avast
i use win7 at work and have not have this problem. i had purebasic installed in program files, then later reinstalled to c:\purebasic. no issues either way