View previous topic :: View next topic |
Author |
Message |
Juergen
Joined: 13 Nov 2004 Posts: 85 Location: AZ, USA
|
Posted: Thu Dec 23, 2004 4:47 am Post subject: BASCOM AVR 1.11.7.7 WARNING! |
|
|
Just made teh biggest mistake for this year (maybe because I'm usually running Linux?)! I installed the new 1.11.7.7 over my old version and low and behold: the computer crashes whenever I call up the new BASCOM!
The crash is fully repeatable. My advise: before you udate copy all files in a new directory. This will at least give you a way back.
1.11.7.5 and 6 beta worked w/o problems which is why I may have trusted the new version too much
Installer beware!
Now it's time to search for the backup file to be able to go back to 1.11.7.4 _________________ Juergen
-- In a world without fences and walls, who needs Windows and Gates? -- |
|
Back to top |
|
|
Juergen
Joined: 13 Nov 2004 Posts: 85 Location: AZ, USA
|
Posted: Thu Dec 23, 2004 5:07 am Post subject: Srew up confirmed! |
|
|
More specifics:
I copied the directory back and 1.11.7.4 runs again. After making a local copy on the harddrive (for faster access) I tried the update again with the same result: immediate crash if I call up BASCOM AVR.
I used the new update wizzard (which is a few kB longer) and installed under Windoze ME.
An installation on wifes XPee machine wasn't successful either. XPee doesn't crash but comes up with:
Access violation at address 004E587F in module "bascavr.exe". Read of address 0000005C.
Looks like there's a pretty grown up bug in the executable......
I hate to be a guinea pig...............................................
Juergen _________________ Juergen
-- In a world without fences and walls, who needs Windows and Gates? -- |
|
Back to top |
|
|
Duval JP
Joined: 22 Jun 2004 Posts: 1161 Location: France
|
Posted: Thu Dec 23, 2004 11:37 am Post subject: |
|
|
on Win XP everythink is ok, only some of us as the message : BSCAVRL.DLL could not opened .
but it was because we install the Zip file into a new directory, I put a copy of the .dll in the same dirctory and everything was OK.
now (for me) I have 7.7 and 7.6beta in 2 directory that great !
JP _________________ pleasure to learn, to teach, to create |
|
Back to top |
|
|
dupyv
Joined: 23 Dec 2004 Posts: 1
|
Posted: Thu Dec 23, 2004 8:49 pm Post subject: Re: BASCOM AVR 1.11.7.7 WARNING! |
|
|
I can confirm Juergen's description.
I did a new full installation of BASCOM AVR 1.11.7.7 on my W2000 SP4.
Upon start of BASCOM, Windows comes up with the error:
Access violation at address 004E587F in module "bascavr.exe". Read of address 0000005C.
In the System-Event log, i get an entry from the ServiceControlManager:
"The IOPort service failed to start due to the following error:
The system cannot find the file specified. "
In the Application-Event log, i get an entry from DR Watson
"The application, , generated an application error The error occurred on 12/23/2004 @ 20:44:18.109 The exception generated was c0000025 at address 77FB1DB8 (RtlTraceDatabaseEnumerate) "
Crashes can be reproduced at BASCOM startup each time.
Had to go back to 1.11.7.4 to get a working Bascom. |
|
Back to top |
|
|
sonero
Joined: 01 Nov 2004 Posts: 28
|
Posted: Thu Dec 23, 2004 9:24 pm Post subject: |
|
|
Hi,
After these warnings I installed the new release .7 in a separate directory.
Now I have 1.11.7.4 , 1.11.7.6 and 1.11.7.7 installed on the same windows XPpro SP1 machine.
They all run fine.
There is this still this mysterious problem with the printer.
If I select as the standart printer my network printer and it is not available, Bascom .4 didn't start.
I see the splash screen for a few seconds and that's it.
But with a lokal (LTP1) fake printer it works.
Mark can't reproduce this, even if I seem to be not the only one with this phenomenon.
I can live with this workaround but afaik this issue was never solved.
??????????????????????????
I removed the Wlan card, so my network printer is no longer available, to test it with the newer versions.
All Bascom versions still work????
Maybe a win update in the past fixed this?
I'm clueless...
Ok, I don't have any problems at all.
Maybe you try to play around with the printer.
Best regards,
Norbert |
|
Back to top |
|
|
albertsm
Joined: 09 Apr 2004 Posts: 5913 Location: Holland
|
Posted: Thu Dec 23, 2004 11:26 pm Post subject: |
|
|
Hi,
Quote: | I hate to be a guinea pig |
What are you suggesting???
I am putting a lot of time and energy in free updates.
I distribute beta's so you can test it.
The final step is a full distribution.
I don't know what is wrong yet, but to say i am using you as a guinea pig?
I am not amused.
About the printer : this was an error in windows. (in combination with the compiler i use). I never could reproduce the problem(used various XP versions). When it can be reproduced, it can't be fixed.
But it seems MS fixed it. _________________ Mark |
|
Back to top |
|
|
sonero
Joined: 01 Nov 2004 Posts: 28
|
Posted: Thu Dec 23, 2004 11:44 pm Post subject: |
|
|
Hi,
Mark, don't worry.
The most of us are happy with Bascom and have no problems.
But if you want to make it more professional, don't implement more functions but make it more reliable.
There are about 50 solar pumps with a BLSL motor running in USA, Australia and other countries.
The controller is a Mega16 programmed with Bascom.
Seems to work fine.
Next year we plan to ship at least 2000 of these controllers.
For professional use, reliability is important, not exotic features like different graphic displays.
Best regards,
Norbert |
|
Back to top |
|
|
Juergen
Joined: 13 Nov 2004 Posts: 85 Location: AZ, USA
|
Posted: Fri Dec 24, 2004 1:12 am Post subject: |
|
|
albertsm wrote: | Hi,
Quote: | I hate to be a guinea pig |
What are you suggesting???
I am putting a lot of time and energy in free updates.
|
Mark,
don't take it personal! With software there's always a chance that something goes wrong, especially with the variety of hardware on the market. In my opinion the only bug-free software is the one which is discontinued.
My comment was ment as a joke, sorry if it sounded different to you.
We actually like your software that much that we use it for commercial product......
Juergen |
|
Back to top |
|
|
albertsm
Joined: 09 Apr 2004 Posts: 5913 Location: Holland
|
Posted: Sat Dec 25, 2004 1:11 am Post subject: |
|
|
Hi,
Ok, i am a bit overworked. I prefer to see
There were 2 problems :
- the ioport.sys (needed on NT/XP only) was not copied to the right directorie by setup.exe (for those who tried setup.exe)
- the executable was packed to make it smaller. But this software seems to have a problem on some (ME) systems.
I uploaded a new setup and also modifeed zips so you can use the Wizzard. Also a new demo is uploaded.
I understand that a product needs to be stable. But i had to change a lot in order to support the new chips more easily. Dont worry about exotic new features, i am working for a long time already at a total rewrite for the professional user. One of the keywords is 'reliable'.
Dont ask for release dates, i do not give them.
Merry Christmas,
Mark _________________ Mark |
|
Back to top |
|
|
Jason
Joined: 31 Dec 2004 Posts: 18 Location: Sydney
|
Posted: Fri Dec 31, 2004 2:55 am Post subject: |
|
|
albertsm wrote: |
There were 2 problems :
- the ioport.sys (needed on NT/XP only) was not copied to the right directorie by setup.exe (for those who tried setup.exe)
|
I updated today, 31/12/04, using the Auto Update Wizzard (also downloaded today) and I get the same crashing error as described above. I searched my drives for ioport.sys, but it does not exist on my machine.
bscavr.dll and the .lic file are in the folder.
Any ideas?
Thanks,
Jason. |
|
Back to top |
|
|
Blake
Joined: 31 Dec 2004 Posts: 31
|
Posted: Fri Dec 31, 2004 11:49 pm Post subject: |
|
|
I upgraded (via Upgrade Wizard) on the 28th and opened Bascom and compiled code several times but then got the same problem today when trying to start Bascom. This problem has been reported for both upgrading and for those doing a new installation. Am I the only one that had the program work fine several times before starting this crashing problem. By the way, I am using XP with service pack 2 installed.
Blake |
|
Back to top |
|
|
Twenty
Joined: 30 Nov 2004 Posts: 50 Location: Sydney
|
Posted: Sat Jan 01, 2005 3:23 pm Post subject: Re: BASCOM AVR 1.11.7.7 WARNING! |
|
|
Dupyv,
Perhaps this can help you.
I have the latest version of bascom (1.11.7.7) installed on win2000 SP2. So, today I was somewhat bored and updated win2000 with the latest security updates (I think the latest is SP5). After this my Bascom 1.11.7.7 didn't work and I can exactly confirm the quote below. I have uninstalled and reinstalled the latest version a few times but with no success. I then reinstalled the previous version (1.11.7.4) to get a working software without uninstalling version 1.11.7.7. And then suddenly my 1.11.7.7 version was working again. Strange. And now I can play with this lovely software again
Twenty
dupyv wrote: | I can confirm Juergen's description.
I did a new full installation of BASCOM AVR 1.11.7.7 on my W2000 SP4.
Upon start of BASCOM, Windows comes up with the error:
Access violation at address 004E587F in module "bascavr.exe". Read of address 0000005C.
In the System-Event log, i get an entry from the ServiceControlManager:
"The IOPort service failed to start due to the following error:
The system cannot find the file specified. "
In the Application-Event log, i get an entry from DR Watson
"The application, , generated an application error The error occurred on 12/23/2004 @ 20:44:18.109 The exception generated was c0000025 at address 77FB1DB8 (RtlTraceDatabaseEnumerate) "
Crashes can be reproduced at BASCOM startup each time.
Had to go back to 1.11.7.4 to get a working Bascom. |
|
|
Back to top |
|
|
albertsm
Joined: 09 Apr 2004 Posts: 5913 Location: Holland
|
Posted: Fri Jan 14, 2005 9:25 pm Post subject: |
|
|
Hi,
When you have a working bascom, you can use the Wizzard. When you want a new installation, you need the setup.exe (and a copy of the license file).
As explained before, the ioport.sys was not copied to the proper location in the new setup.exe. And the bascom executable was compressed, which is causing problems in some situations. So that was removed too.
Let me know if there are still problems. _________________ Mark |
|
Back to top |
|
|
Piersante
Joined: 11 Jan 2005 Posts: 1
|
Posted: Fri Feb 11, 2005 11:56 am Post subject: |
|
|
Same problems on windows 2k...
just a copy IOPORT.sys to WINNT\SYSTEM32\DRIVERS
solved all my problems with 1.11.77 installation.
Pier |
|
Back to top |
|
|
|