My old PC finally died a couple of months ago and I replace it with a nice Duel Core Intel PC with Windows 7 64bit. Now it seems that my EBASIC doesn’t work very well. My two biggest complaints so far are that when I double click on a file with an EBASIC extension ( .INC or .EBA for example). The Ebdev application starts but it won’t open the file, instead I get an error dialog saying there was a problem. Second when I try to develop an application I have to shutdown EBASIC and restart after testing the program. This is the only way I can recompile any corrections to the program. It seems to think my application is still running after I terminate it. Even in debug mode it thinks the program is still running.
I’ve checked past threads here on the forum and I don’t really see anyone else complaining about windows7. So is it me or does Ebasic truly have issues with windows7 and maybe Ebasic 2.0 will clean things up. I never had any problems with my XP version so I’m just looking for some feed back and advice, besides taking a sledge hammer to it
Im running Win7 x64 and eBasic works fine.
run ebasic as administrator and go to tools/ register file exe.... ( you only have to do this once )
Ive never had any problems compiling programs, maybe you should post the error you get when trying to compile a program
Yipee, turning off the MS Fire Wall messages has done the trick. They were becoming an annoyance anyway.. thanks
I have same problem it can't open the output file error after recompiling
tried running as admin and reg extentions no luck
did you
install it as admin?
QuoteI have same problem it can't open the output file error after recompiling
Not sure what you mean by
Quotecan't open the output file error
LarryMc