Skip to content
View in the app

A better way to browse. Learn more.

HarpGamer

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

GE_028: GetMemAnnex Error: IS_DISK(26633 [0x6809])

Featured Replies

Defect Name: GE_028: GetMemAnnex Error: IS_DISK(26633 [0x6809])

Build: HCE 2007.028 GE

Repeatable: Y

Operating System: W2000

DB used: HCDB-070524

Scenario used: HDSL-9_modified

Long Description: By playing the scenario HSDL-9 after a while the GE_028 crash and the attached error file will be generated. I guess this is rather as database error than a game engine error. This assumption is based on the behavior of the SAM SA-10d and SAM SA-6 platform: They are destroyable but by destroying no destruct message appears and they are not counted as destroyed on the table.

 

 

 

 

 

Logging begins. Build Date = Nov 27 2007, Build Time=23:36:55

0 harpoon.c:416 - done processing arguments. Activating logging for:

0 bitmap.c:148 - creating pallette

0 bitmap.c:148 - creating pallette

0 bitmap.c:148 - creating pallette

0 dllexport.c:68 - hfind == INVALID_HANDLE

0 harpoon.c:130 - validateclock test 1 = 1

0 bitmap.c:148 - creating pallette

0 bitmap.c:148 - creating pallette

0 setup.c:1108 - SetUp(0x0) entered

0 setup.c:1111 - Deleting old memory

0 setup.c:1119 - init_global_variables

100000 setup.c:1141 - BattlesetSelector

100000 setup.c:1168 - load Map

100000 loadgame.c:204 - begining restore of saved file version 0x34803209

100000 loadgame.c:45 - about to read globals, size=279, file offset=76

100000 loadgame.c:60 - after globals read, file offset=355

124349 initannx.c:612 - this scenario is from battlesetnumber 26, using annex version 1

124349 initannx.c:657 - reading scenario file version 0

124349 initannx.c:658 - Database Versions:

Res: HCDB-070524,1179974583

Rsr: HC Gold Edition Official DB 1179974583

124349 setup.c:1241 - OpenBattlsetResFile

124349 setup.c:1362 - InitDisplayOp

124351 initutil.c:685 - RCS=137 Size=12 Name=Ka-27PL Helix A

124356 initutil.c:685 - RCS=157 Size=13 Name=MiG-25PD Foxbat E

124372 combat2.c:874 - Friendly Unit AC00(Sachishio) was hit 1 times for 38 DP.

124375 loadgame.c:204 - begining restore of saved file version 0x34803209

124375 memfs.c:1471 - test

124375 memfs.c:1471 - test

124375 loadgame.c:45 - about to read globals, size=279, file offset=76

124375 loadgame.c:60 - after globals read, file offset=355

124349 initannx.c:612 - this scenario is from battlesetnumber 26, using annex version 1

124349 initannx.c:657 - reading scenario file version 0

124349 initannx.c:658 - Database Versions:

Res: HCDB-070524,1179974583

Rsr: HC Gold Edition Official DB 1179974583

124351 savegame.c:722 - about to save globals, size=279, file offset=76

124351 savegame.c:728 - after globals save, file offset=355

124356 initutil.c:685 - RCS=157 Size=13 Name=MiG-25PD Foxbat E

124451 savegame.c:722 - about to save globals, size=279, file offset=76

124451 savegame.c:728 - after globals save, file offset=355

124462 combat2.c:874 - Friendly Unit AC00(Sachishio) was hit 1 times for 30018 DP.

124468 savegame.c:722 - about to save globals, size=279, file offset=76

124468 savegame.c:728 - after globals save, file offset=355

124602 initutil.c:685 - RCS=138 Size=12 Name=Ka-25PL Hormone A

124616 initutil.c:685 - RCS=138 Size=12 Name=Yak-38 Forger A

124620 initutil.c:685 - RCS=137 Size=12 Name=Ka-27PL Helix A

124621 initutil.c:685 - RCS=138 Size=12 Name=Yak-38 Forger A

124892 initutil.c:685 - RCS=135 Size=12 Name=SH-60B Seahawk

124933 initutil.c:685 - RCS=135 Size=12 Name=SH-60B Seahawk

124996 initutil.c:685 - RCS=156 Size=13 Name=Su-27 Flanker B

125062 initutil.c:685 - RCS=135 Size=12 Name=SH-60B Seahawk

125129 initutil.c:685 - RCS=135 Size=12 Name=SH-60B Seahawk

125200 initutil.c:685 - RCS=160 Size=13 Name=Tu-16RM-2 Badger D

125200 initutil.c:685 - RCS=159 Size=13 Name=Tu-22M3 Backfire C

125202 staff.c:325 - creating refueling event

Group=0x1c45728 (AZAS Endurance = 2816957 num_tanker=1, platstart=1 platnow=1

125207 initutil.c:685 - RCS=135 Size=12 Name=SH-60B Seahawk

125265 loadgame.c:204 - begining restore of saved file version 0x34803209

125265 memfs.c:1471 - test

125265 memfs.c:1471 - test

125265 loadgame.c:45 - about to read globals, size=279, file offset=76

125265 loadgame.c:60 - after globals read, file offset=355

124451 initannx.c:612 - this scenario is from battlesetnumber 26, using annex version 1

124451 initannx.c:657 - reading scenario file version 0

124451 initannx.c:658 - Database Versions:

Res: HCDB-070524,1179974583

Rsr: HC Gold Edition Official DB 1179974583

124459 annex.c:174 - GetMemAnnex Error: IS_DISK(26633 [0x6809]) = 0

Scenario used: HDSL-9_modified ...

 

This is a modified version of Ralf's "Backyard" scenario ?

 

Long Description: By playing the scenario HSDL-9 after a while the GE_028 crash and the attached error file will be generated. I guess this is rather as database error than a game engine error. This assumption is based on the behavior of the SAM SA-10d and SAM SA-6 platform: They are destroyable but by destroying no destruct message appears and they are not counted as destroyed on the table.

 

Its unlikely to have been a database issue.

  • Author
This is a modified version of Ralf's "Backyard" scenario ?

 

No. With a "running" SE_024 and the HCDB-070524 I removed the bases/planes which I anyway loos, replaced the A-6 and F-14 with Super bug's and added from HCDB-070524, downed pilot's, two bases, 1 RQ-4B and 1 UCAV for testing.

Gopher, please keep working at uploading those files (your custom scenario and the saved game before the crash), zip and upload...

  • Author

I will do so as soon I don't forgot the USB-stick.

Yesterday I was able to digin more in the error and find out that the file (game save) is corrupt. By opening the scenarion and erasing the all other units to have only the estimated "bug-units" the game didn't crash by playing.

  • Author

Ok, two files are attached.

One file provide the game crash above then the sub ACU is attacked.

The other file is the same game, but show the effect hat the SAM unit will mit be listed a destroyed the AGM hit.

Both effect happen with 028 GE.

Corrupt_file_Backyard.zip

Game_crash_Backyard.zip

  • 2 months later...
  • Author
Anybody have ideas on this one?

 

With the GE.023.2008 installation, the game did not crash on my PC. But the sub get sunk and I received the message "nuke allowed", while I play basically without any allowed nuke's. <_<

 

 

As compensation for the game crash, I have now more often AC which circle around a waypoint instead going further, and AC which launch from a ship to an assigned formation patrol and then run out of fuel (? beacuse they have the same waypoint problem?).

  • 1 month later...

Gopher, I believe your original ID 26633 (a ASW missile) problem was fixed in 2008.034 and 2008.035. The nuclear release seems to be caused by even your loadable save being corrupt, the launching platform, the Kirov, doesn't even have that nuclear weapon on board in HCDB-070524 (nor HCDB-080406).

 

So I think outside of the waypoint thing (reported better elsewhere), we're done with this thread.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.