The Major BBS Forums (Archive)

FYI - Mega Slots is creating the following error and causes WG to hang and force a reboot; creating a Windows error display:

C:\WG32\wgsappo.exe <in Window Header>

Unrecognized errorlevel=-1073741819 returned from wgserver.exe!

I'm running WG3.2 under Windows XP Pro Service pack 2 with all the latest patches on a Pentium III 1ghz, 128MB RAM, 40 MB HD. It's an older Gateway, but seems to run everthing else fine.

Tried removing all addons and only running the BBS and Mega, still the same error.

Once the error window is closed, any attempt to restart WG results in a WG error window; Betrieve Error code 25 on galssc2.dat. The file is locked open <so windows thinks> and the WG service shows 'started', but will not stop or close down.

Be glad to try some other options if you give me a hint on what the problem might be.

Toyduck

Toyduck wrote:FYI - Mega Slots is creating the following error and causes WG to hang and force a reboot; creating a Windows error display:

C:\WG32\wgsappo.exe <in Window Header>

Unrecognized errorlevel=-1073741819 returned from wgserver.exe!

I'm running WG3.2 under Windows XP Pro Service pack 2 with all the latest patches on a Pentium III 1ghz, 128MB RAM, 40 MB HD. It's an older Gateway, but seems to run everthing else fine.

Tried removing all addons and only running the BBS and Mega, still the same error.

Once the error window is closed, any attempt to restart WG results in a WG error window; Betrieve Error code 25 on galssc2.dat. The file is locked open <so windows thinks> and the WG service shows 'started', but will not stop or close down.

Be glad to try some other options if you give me a hint on what the problem might be.

Toyduck

yeah thats a known issue, dont think hes gotten around to it yet.

dspain wrote: yeah thats a known issue, dont think hes gotten around to it yet.

Okey dokey...

Toyduck wrote:

dspain wrote: yeah thats a known issue, dont think hes gotten around to it yet.

Okey dokey...

Yeah, but the good news is that I replicated it. So now I have to figure out what the hell the difference was on the two computers that it didn't happen on and the computers where it did..

I hope it isn't a Windows Server 2003 compatibility issue....

Questman wrote:

Toyduck wrote:

dspain wrote: yeah thats a known issue, dont think hes gotten around to it yet.

Okey dokey...

Yeah, but the good news is that I replicated it. So now I have to figure out what the hell the difference was on the two computers that it didn't happen on and the computers where it did..

I hope it isn't a Windows Server 2003 compatibility issue....

funny you say that i found a couple errors that happen to me with my mud that only happen on XP and not windows 2000 or 2003.
think its more of a borland incompatibility error?

Questman wrote:

Toyduck wrote:

dspain wrote: yeah thats a known issue, dont think hes gotten around to it yet.

Okey dokey...

Yeah, but the good news is that I replicated it. So now I have to figure out what the hell the difference was on the two computers that it didn't happen on and the computers where it did..

I hope it isn't a Windows Server 2003 compatibility issue....

I got the same error with Windows XP Pro SP2 on an AMD and Windows 2000 server on a AMD athlon.

Don

wow, sounds like some programs were never finished or debuged well.

frcorey wrote:wow, sounds like some programs were never finished or debuged well.

No, I think some of it may be what flavor of windows are you using..and on what type of machine.

I'v found some considerable performance differences between Win2000 and WinXP and WinServer, and different problems.

Yes. The difference between WG 3.x versions and Win32 OS versions do lead to some quirks. It's disappointing and frustrating.