ThreadBoard ArchivesSite FeaturesActiveworlds SupportHistoric Archives |
Delphi RC_VERSION_MISMATCH (Sdk)
Delphi RC_VERSION_MISMATCH // Sdkneo2Apr 22, 2000, 5:59am
I have a problem. I'm using Delphi. When I try to initialize AW.dll using
aw_init (aw_build) I get an error 454 RC_VERSION_MISMATCH. I have the 15 build version and the 16 build version but both of them provoques the same error. Can anybody help me? Thanks Neo canopusApr 22, 2000, 4:53pm
Version mismatch usually happens when the 'const AW_BUILD = 16' line in your
akAWAPI Delphi unit doesn't match the Build Number of the aw.dll you are using. Either you keep on using an old build of aw.dll to match your old akAWAPI unit or you use a new version of akAWAPI (check the 'const AW_BUILD = ' line) to match the new version of aw.dll that you have. I think I usually put the newest aw.dll in the akAWAPI package that I post. You mention 'three examples': this sounds like you are using the Delphi Encapsulation of the SDK. Newer akAWAPI (& the matching aw.dll) should still work with the Encapsulation, because mostly methods have been added, not subtracted or revised. But probably the Encapsulation section has an old akAWAPI (& its matching aw.dll) in it: substitute the latest akAWAPI (& matching aw.dll), & see if that helps. It could be that I put the wrong aw.dll in the new akAWAPI package. I'll check. You can check by comparing their Build/Version numbers. Also, I'm not sure whether you must have AW 3.0 Beta to use the latest aw.dll (would that also cause a Version Mismatch?). xelagApr 27, 2000, 4:51pm
Hi Canopus, you can use build 16 bots anywhere, even in an old world build 21...
The newer features will not work in those worlds, but the older features do work fine. Build 16 fixed the 'same world name in different universes' bug, and the coming build 17 has more bug fixes, which are a bonus even if you don't have a 3.0 browser or world server. As far as the version mismatch, I always put the aw.dll in the same folder as the bot program, and never anywhere on the path known to windows, to avoid mismatches. [View Quote] > Version mismatch usually happens when the 'const AW_BUILD = 16' line in your > akAWAPI Delphi unit doesn't match the Build Number of the aw.dll you are > using. > > Either you keep on using an old build of aw.dll to match your old akAWAPI > unit > or you use a new version of akAWAPI (check the 'const AW_BUILD = ' line) to > match the new version of aw.dll that you have. > > I think I usually put the newest aw.dll in the akAWAPI package that I post. > You > mention 'three examples': this sounds like you are using the Delphi > Encapsulation of the SDK. Newer akAWAPI (& the matching aw.dll) should still > work with the Encapsulation, because mostly methods have been added, not > subtracted or revised. But probably the Encapsulation section has an old > akAWAPI > (& its matching aw.dll) in it: substitute the latest akAWAPI (& matching > aw.dll), & see if that helps. > > It could be that I put the wrong aw.dll in the new akAWAPI package. I'll > check. > You can check by comparing their Build/Version numbers. > > Also, I'm not sure whether you must have AW 3.0 Beta to use the latest aw.dll > > (would that also cause a Version Mismatch?). |