YAM - Yet Another Mailer (#2) - Error 80000008 (#30) - Message List

Error 80000008
 unsolved

Hi! get a strange message and i asked alot of people whats wrong but no one has any answers. First of all i m using amiga 1200, blizzard 1230 MK4 64mb fast ram, OS3.9. The message i get is(translated from swedish) Program failed (error 80000008) Wait until read/writing is finsihed wait restart How can i solve this problem?

Thanks

  • Message #130

    Does your Blizzard board have an FPU? If not, the error nummber most probably was 8000000B instead of 80000008. This one is caused by FPU opcodes in the binary which came in due to a wrong compiled clib2 C-library. If your Blizzard does have an FPU (68881/2), then I have no idea what is going wrong.

    • Message #132

      Does your Blizzard board have an FPU? If not, the error nummber most probably was 8000000B instead of 80000008. This one is caused by FPU opcodes in the binary which came in due to a wrong compiled clib2 C-library. If your Blizzard does have an FPU (68881/2), then I have no idea what is going wrong.

      I have the same problem and i have a BPPC w/o FPU. What to do to solve this ? Thanks, Maurizio

      • Message #133

        These are the solutions I can offer:

        1. get an FPU
        2. wait for the official release of 2.6 (no date yet)
        3. switch to the nightly builds of 2.6 (with all its advantages and disadvantages)
        4. ask Jens to release 2.5p1 which is linked against the updated clib2 as soon as our ARexx problem is fixed.
        • Message #134

          These are the solutions I can offer:

          1. get an FPU
          2. wait for the official release of 2.6 (no date yet)
          3. switch to the nightly builds of 2.6 (with all its advantages and disadvantages)
          4. ask Jens to release 2.5p1 which is linked against the updated clib2 as soon as our ARexx problem is fixed.

          Thanks... i think i will get the nightly builds, butm before can you tell me the advantages and first of all the disadvantages ?

          Maurizio

          • Message #135

            Advantages: several bugs since the release of 2.5 have been fixed

            Disadvantages: nightly builds may contain experimental code which is not yet stable and may cause any kind of unwanted or unexpected behaviour. Possible loss of data is not and cannot be guaranteed.

            Usually we use the nightly builds ourself and test them intensively. But we are humans as everybody else and may miss some serious bugs while adding new features. In general the nightly builds run as stable as the release version. But we don't guarantee that.

            Currently ARexx doesn't work on OS3 due to some missing functions in clib2 and rexxsyslib V44. But we are working on that issue.

            • Message #136

              Advantages: several bugs since the release of 2.5 have been fixed

              Disadvantages: nightly builds may contain experimental code which is not yet stable and may cause any kind of unwanted or unexpected behaviour. Possible loss of data is not and cannot be guaranteed.

              Usually we use the nightly builds ourself and test them intensively. But we are humans as everybody else and may miss some serious bugs while adding new features. In general the nightly builds run as stable as the release version. But we don't guarantee that.

              Currently ARexx doesn't work on OS3 due to some missing functions in clib2 and rexxsyslib V44. But we are working on that issue.

              If i try the previous 2.4 i'll have the same problems or this work also without FPU ?

              • Message #137

                Advantages: several bugs since the release of 2.5 have been fixed

                Disadvantages: nightly builds may contain experimental code which is not yet stable and may cause any kind of unwanted or unexpected behaviour. Possible loss of data is not and cannot be guaranteed.

                Usually we use the nightly builds ourself and test them intensively. But we are humans as everybody else and may miss some serious bugs while adding new features. In general the nightly builds run as stable as the release version. But we don't guarantee that.

                Currently ARexx doesn't work on OS3 due to some missing functions in clib2 and rexxsyslib V44. But we are working on that issue.

                If i try the previous 2.4 i'll have the same problems or this work also without FPU ?

                Sorry but i tried 2.6 nightly build and also 2.4 but i have always the same GURU... Any hints ?

                Maurizio

                • Message #138

                  Please make sure to revert to older MUI subclasses, too. And make sure to expunge these from memory before starting YAM again, because just copying new/old versions to disk does not remove the already loaded versions from memory. Just do an "avail flush" before starting YAM.

                  I think TheBar 26.1 has the same FPU bug as YAM 2.6, so better revert this one to V25 when using YAM 2.5. YAM 2.4 doesn't use it at all.

                  • Message #139

                    Please make sure to revert to older MUI subclasses, too. And make sure to expunge these from memory before starting YAM again, because just copying new/old versions to disk does not remove the already loaded versions from memory. Just do an "avail flush" before starting YAM.

                    I think TheBar 26.1 has the same FPU bug as YAM 2.6, so better revert this one to V25 when using YAM 2.5. YAM 2.4 doesn't use it at all.

                    So it's better for me to use YAM 2.4 ? And why 2.4 has the same GURU also if do not use TheBar ?

                    • Message #140

                      As I said before, make sure to use the older classes by either invoking "avail flush" or by rebooting. As long as the new versions are in memory every MUI application will use these instead of the ones on disk.

                      • Message #141

                        As I said before, make sure to use the older classes by either invoking "avail flush" or by rebooting. As long as the new versions are in memory every MUI application will use these instead of the ones on disk.

                        Yes, i understand this, but you told me 2.4 don't use at all TheBar.mcc, so it's not there the problem... Today i will try again the latest nightly build release with the latest TheBar.mcc (i think v26)...

  • Message #131

    Bump

Attachments

No attachments created.