VOGONS


First post, by joeman

User metadata
Rank Newbie
Rank
Newbie

Hi just noticed this site a few days ago, thought i'd give it a crack
and hopefully you guys can help me out 😀

ps: !This is not the Plasma Bomb Issue!

The STARGUN.SAV and STARGUN.HI Plague!
Recently downloaded the Full Freeware version of StarGunner v1.1
Opened Dosbox 0.65, mounted SG's directory, and started playing.

Everything seemed fine, but the next time I tried playing it, it stalled
at the start up where it says "Use /? for help" for about 15 seconds and then the Screen Goes Black and Nothing Happens, no apogee logo no main menu, nothing.

I found out that the Game Refuses to Start Up when there is a STARGUN.SAV and STARGUN.HI file present in the directory, this worries me since the .sav file is needed to save any progress made in the game. If the two files are removed from the stargunner directory, the game starts up normally, but of course this means I have to start the game all over again each time.

Here is the second prob. (Don't worry the post is almost over 😉

QuickSave (F6) = Quicker Program Exit!

If this button is hit during the game and a Slot is chosen for a Quicksave,
the game crashes, and DosBox produces the following message:

Can't open save file [2:star0000.sav]

Call Stack:
Save::save ssave.cpp
save_game save.cpp
check_keyboard_save keyboard.cpp
do_gameloop gameloop.cpp
do_mainloop2 stargun.cpp
do_mainloop stargun.cpp
do_main stargun.cpp

I've also tried running with Dosbox 0.61, same results...

Any thoughts or suggestions to this Save Restricting Madness
are more than welcome.

Thanks for reading!

😀

Last edited by joeman on 2006-10-25, 09:52. Edited 1 time in total.

Reply 1 of 23, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

joeman - could you post a link to that freeware version? It might encourage someone to try to reproduce the problem.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 2 of 23, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Did you apply their patch?

1+1=10

Reply 3 of 23, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

write acces there ?
I recall that stargunner worked fine at one point

Water flows down the stream
How to ask questions the smart way!

Reply 4 of 23, by joeman

User metadata
Rank Newbie
Rank
Newbie

@MiniMax
The link to it is on this website,
http://www.3drealms.com/downloads.html
just scroll down to Stargunner

@h-a-l-9000
Do you mean the v1.0 to v1.1 Registered Patch? I didn't think
it would do much as the Freeware version is already v1.1

Reply 5 of 23, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

I downloaded it there too but the game crashed when "plasma bomb" hit the ground. The patch fixed it.

1+1=10

Reply 6 of 23, by joeman

User metadata
Rank Newbie
Rank
Newbie

I had a go with that v1.0 to v1.1 Registered Patch, still no luck...
Dosbox has me seriously puzzled on this 😖

Reply 7 of 23, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

I can not reproduce the STARGUN.SAV and STARGUN.HI plaque here, nor the QuickSave error.

But I did get a stacktrace when I had been killed a number of times (and run out of ships?):

spr out of range [1477/271 group=starg51.spd]

Call Stack:
Flames::load ship.cpp
Ship::load ship.cpp
Save::load ssave.cpp
do_gameloop gameloop.cpp
do_mainloop stargun.cpp
do_main stargun.cpp

I gues the spr is a Stack Pointer Register??

I will try with a different DOSBox core (this was with core=dynamic) and see if that changes anything.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 8 of 23, by SysGOD

User metadata
Rank Member
Rank
Member

I can not reproduce the STARGUN.SAV and STARGUN.HI plaque here, nor the QuickSave error.

same to me. played that game for many hours without any errors.
semes to be completely stable with simple/normal core and cycles=auto.

when i have time, ill try it with dynamic core and manual cycle settings.

Last edited by SysGOD on 2006-10-25, 16:08. Edited 1 time in total.

Reply 9 of 23, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Seems like Stargunner and DOSBox don't like each other very well 🙁

I had it run in demo mode with core=normal, and on several occasions DOSBox (not the game) would crash with a

Exit to error: IRET:Illegal descriptor type 0

message in the console.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 10 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

spr might be sprite.
Maybe try with loadfix and sound disabled, and ems/xms off.
Another possibility would be trying it with msdos+dosbox but
not sure if that'd help here (could be using some unimplemented
dos table, or some memory corruption is happening).

Reply 11 of 23, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Simple core will not work. Got this message, and the the IRET error:

CPU core simple won't run this game,switching to normal
Exit to error: IRET:Illegal descriptor type 0

I will try your suggestions wd, and see if some combination will make the demo stable.

Edit: Tried with core=full, and initially it look good. I ran several demo-runs, without errors, but eventually 'full' also died with the IRET error.

Last edited by MiniMax on 2006-10-25, 17:57. Edited 1 time in total.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 12 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

The simple core doesn't work with paging games at all, thus it
switches to the normal core if paging support is switched on
(the message you got is therefore from the normal core).

Reply 13 of 23, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

It is a bit boring, but this combination seems very stable in the demo-runs:

core=dynamic
xms=false
ems=false
umb=false

and then StarGunner is launched with

stargun /logo- /intro- /vesa- /lfb- /fade- /sound- /nomouse

Time to see if I can get the sound back while keeping it stable.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 14 of 23, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Played a bit through it and appears to work nice..

Title screen says v1.1a

dynamic core
25000 cycles
other settings default
in directory E:\STARGUN
Dosbox CVS

FILE_ID.DIZ  - CRC32: 2C2551F9
PATCH001.EXE - CRC32: 27338F75
readme.txt - CRC32: 0E7C2986
SETUP.EXE - CRC32: 892D7D56
sgmanual.pdf - CRC32: F71D0428
STAR0000.SAV - CRC32: 0AF72AC2
STARGUN.CFG - CRC32: D7446C87
STARGUN.DLT - CRC32: 78E2F294
STARGUN.EXE - CRC32: 99A857EC
STARGUN.HI - CRC32: 59B2CA0C
STARGUN.SAV - CRC32: B41107BF
STARGUN0.DLT - CRC32: BD750955
STARHELP.EXE - CRC32: 52A1C782

CRC tool: http://www34.brinkster.com/dizzyk/crc32.asp

or maybe you have to play hours to find the bug?

Reply 15 of 23, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Nice Apogee!!! I didn't notice it before, but the stack trace (which I agree with wd is probably a problem with a sprite) was caught by the StarGunner runtime system, and the nice programmers at Apogee had it write to an error log:

                                                                 StarGunner
System Configuration (C) Copyright 1996
___________________________________________________________________________
#
# CMDLINE = C:\STARGUN\STARGUN.EXE
# STARGUN =
# version = 1.0b
# compiled = Nov 12 1996 @ 21:19:59
# memory = 3570k : 4194300k (3660156, 3660156 max)
# ULTRASND = 240,3,3,5,5
# BLASTER = A220 I7 D1 H5 T6
# COMSPEC = Z:\COMMAND.COM
# dos = 5.0
# vrs = 17025

___________________________________________________________________________
Error Log.. If this file contains any data below this StarGunner
line then please forward this to the Stargunner Team. (C) Copyright 1996
___________________________________________________________________________
#
Mission 5 Zone 1 Stage 1 Level 0
Time 0 AuxTime 0

SeqList 0 0

Nodes = 0
------------------------------

Anims

Nodes = 0
------------------------------

BulletsList

Nodes = 0
------------------------------

BulletsList

Nodes = 0
------------------------------

BulletsList

Nodes = 0
------------------------------
spr out of range [1477/271 group=starg51.spd]


Call Stack:
Flames::load ship.cpp
Ship::load ship.cpp
Save::load ssave.cpp
do_gameloop gameloop.cpp
do_mainloop2 stargun.cpp
do_mainloop stargun.cpp
do_main stargun.cpp

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 16 of 23, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

# version = 1.0b
# my version = 1.1a
If you downloaded it from their homepage it is not as 1.1 as they think.

1+1=10

Reply 17 of 23, by SysGOD

User metadata
Rank Member
Rank
Member
CPU core simple won't run this game, switching to normal 

ups ok guys your right, didnt notice the message when testing.

but i get no IRET:Illegal descriptor type 0 error.
i have tested SG (patched to 1.1a) again with a default dosbox.conf. only changed it to normal (cycles=auto) and dynamic core (cycles=25000)... runs good so far.
the game itself is set to GUS for sound and vesa 2.0.

if i understand that error log correctly, the sprite problem occurs in mission 5 in zone 1 with v1.0b, is that right?

Last edited by SysGOD on 2006-10-25, 19:48. Edited 1 time in total.

Reply 18 of 23, by MiniMax

User metadata
Rank Moderator
Rank
Moderator
h-a-l-9000 wrote:
Played a bit through it and appears to work nice.. […]
Show full quote

Played a bit through it and appears to work nice..

Title screen says v1.1a

dynamic core
25000 cycles
other settings default
in directory E:\STARGUN
Dosbox CVS

FILE_ID.DIZ  - CRC32: 2C2551F9
PATCH001.EXE - CRC32: 27338F75
readme.txt - CRC32: 0E7C2986
SETUP.EXE - CRC32: 892D7D56
sgmanual.pdf - CRC32: F71D0428
STAR0000.SAV - CRC32: 0AF72AC2
STARGUN.CFG - CRC32: D7446C87
STARGUN.DLT - CRC32: 78E2F294
STARGUN.EXE - CRC32: 99A857EC
STARGUN.HI - CRC32: 59B2CA0C
STARGUN.SAV - CRC32: B41107BF
STARGUN0.DLT - CRC32: BD750955
STARHELP.EXE - CRC32: 52A1C782

The free version says version 1.0b and has slightly a different CRC32 for STARGUN.EXE:

readme.txt   - CRC32: 0E7C2986
SETUP.EXE - CRC32: 892D7D56
sgmanual.pdf - CRC32: F71D0428
STARGUN.DLT - CRC32: 78E2F294
STARGUN.EXE - CRC32: 24A87645 << v1.1 appears to be 99A857EC
STARHELP.EXE - CRC32: 52A1C782
h-a-l-9000 wrote:

or maybe you have to play hours to find the bug?

The demo is self-running. I just let it play for 10-20 minutes.
I can't say for sure yet, but it seems like disabling XMS/EMS/UMB and maybe the loadfix'ing makes it stable. I have had it running for a long time using GUS without the demo crashing. Currently trying with SoundBlaster sound.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 19 of 23, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Well use their 1.1 patch?

1+1=10