The Major BBS Forums (Archive)

Not sure how to really put it, but I've noticed that sometimes the console seems frozen, although the server still functions otherwise. For example If I wanted to say hit F7 to login, or use tab to cycle thru the various console menu's I couldn't. The only work around to this is to shutdown the server using an external program to login and shutdown.

So I guess what I'm asking or verifying is that is this an OS issue? Or something in WG causing this.

-360

JLittge wrote:Not sure how to really put it, but I've noticed that sometimes the console seems frozen, although the server still functions otherwise. For example If I wanted to say hit F7 to login, or use tab to cycle thru the various console menu's I couldn't. The only work around to this is to shutdown the server using an external program to login and shutdown.

So I guess what I'm asking or verifying is that is this an OS issue? Or something in WG causing this.

-360

it's hard to say. wg is a complicated server type system. are you running 100% stock with no modes or addons? if it's a addon, unlink it from the runtime with wgsdmod and see if it stops doing it. if it's a dos wg on a 32 bit os that could be it too. it ran slow enoght on XP as it was. it's just a 16 bit program and most down run well on 32 bit systems or higher.

frcorey wrote:

JLittge wrote:Not sure how to really put it, but I've noticed that sometimes the console seems frozen, although the server still functions otherwise. For example If I wanted to say hit F7 to login, or use tab to cycle thru the various console menu's I couldn't. The only work around to this is to shutdown the server using an external program to login and shutdown.

So I guess what I'm asking or verifying is that is this an OS issue? Or something in WG causing this.

-360

it's hard to say. wg is a complicated server type system. are you running 100% stock with no modes or addons? if it's a addon, unlink it from the runtime with wgsdmod and see if it stops doing it. if it's a dos wg on a 32 bit os that could be it too. it ran slow enoght on XP as it was. it's just a 16 bit program and most down run well on 32 bit systems or higher.

Yea running v3.30-NT on XP Pro. It's just an annoyance really.

JLittge wrote:

frcorey wrote:

JLittge wrote:Not sure how to really put it, but I've noticed that sometimes the console seems frozen, although the server still functions otherwise. For example If I wanted to say hit F7 to login, or use tab to cycle thru the various console menu's I couldn't. The only work around to this is to shutdown the server using an external program to login and shutdown.

So I guess what I'm asking or verifying is that is this an OS issue? Or something in WG causing this.

-360

it's hard to say. wg is a complicated server type system. are you running 100% stock with no modes or addons? if it's a addon, unlink it from the runtime with wgsdmod and see if it stops doing it. if it's a dos wg on a 32 bit os that could be it too. it ran slow enoght on XP as it was. it's just a 16 bit program and most down run well on 32 bit systems or higher.

Yea running v3.30-NT on XP Pro. It's just an annoyance really.

3.3 has some problems, but I never saw that one.
I ran it on XP sp3 for years. 3.2 is much better thou.

I have never had a problem with the dos console after this fix.

I think i found a fix for this thanks to Synchronet authur
Rob Swindel(digital man) in the dove net forums.
Here is what he said:
Got a question for you: Is there a way to increase system space for environm
> variables on Windows 2000 Server (the kind do set in batch files with the se
> command)?

Yes. Use Windows explorer to browse all files in your \windows folder. Right
click on the file "_default.pif" (it may appear as just "_default"). Under the
"Memory" tab, set the "Initial environment" to 4096. If memory serves, that
should do it for ya.

digital man
this has worked for me so far,console is back to normal.

banjaxster wrote:I have never had a problem with the dos console after this fix.

I think i found a fix for this thanks to Synchronet authur
Rob Swindel(digital man) in the dove net forums.
Here is what he said:
Got a question for you: Is there a way to increase system space for environm
> variables on Windows 2000 Server (the kind do set in batch files with the se
> command)?

Yes. Use Windows explorer to browse all files in your \windows folder. Right
click on the file "_default.pif" (it may appear as just "_default"). Under the
"Memory" tab, set the "Initial environment" to 4096. If memory serves, that
should do it for ya.

digital man
this has worked for me so far,console is back to normal.

Hopefully this will fix the random console lockup.