On Tue, 15 Aug 2000 23:43:03 GMT, "Simon Brown"
<[email hidden]> wrote:
>When exactly does this happen? Is it after the initial loading screen
>appears, or before anything happens at all?
The loading screen appears, and then it takes a minute before the menu
appears.
Andre
When exactly does this happen? Is it after the initial loading screen
appears, or before anything happens at all?
"Andre Warringa" <[email hidden]> wrote in message
news:[email hidden]...
Quoted text (9 lines)
> Since I installed my V3 3000 card a couple of weeks ago, it takes > about a minute before the GPL menu appears after I start GPL. > Before that it took only a couple of seconds. > I had some problems with old V2 drivers in the registry, and I thought > it might be related to that, but I did a clean Windows install and > still have the problem. > Any ideas? > > AndreSince I installed my V3 3000 card a couple of weeks ago, it takes
about a minute before the GPL menu appears after I start GPL.
Before that it took only a couple of seconds.
I had some problems with old V2 drivers in the registry, and I thought
it might be related to that, but I did a clean Windows install and
still have the problem.
Any ideas?
Andre
This is when GPL looks for TCP/IP and IPX network devices. It communicates
with your modem and network card, if you have them. You can disable this
checking in the core.ini (you will see the settings in there). That's no
solution, but it might at least give you a clue as to where the problem
lies.
"Andre Warringa" <[email hidden]> wrote in message
news:[email hidden]...
>
> The loading screen appears, and then it takes a minute before the menu
> appears.
>
> Andre
Make sure you have this in you core.ini :
disable_modem = 1
Sid.
"Andre Warringa" <[email hidden]> wrote in message
news:[email hidden]...
Quoted text (9 lines)
> Since I installed my V3 3000 card a couple of weeks ago, it takes > about a minute before the GPL menu appears after I start GPL. > Before that it took only a couple of seconds. > I had some problems with old V2 drivers in the registry, and I thought > it might be related to that, but I did a clean Windows install and > still have the problem. > Any ideas? > > AndreOn Wed, 16 Aug 2000 01:29:03 GMT, "Simon Brown"
<[email hidden]> wrote:
>This is when GPL looks for TCP/IP and IPX network devices. It communicates
>with your modem and network card, if you have them. You can disable this
>checking in the core.ini (you will see the settings in there). That's no
>solution, but it might at least give you a clue as to where the problem
>lies.
Thanks, I'll check the core.ini when I get home from work. But I
wonder why GPL started searching for this after I installed my V3?
Andre
Quoted text (11 lines)
> >"Andre Warringa" <[email hidden]> wrote in message >news:[email hidden]... >> >> The loading screen appears, and then it takes a minute before the menu >> appears. >> >> Andre > > >On Wed, 16 Aug 2000 05:15:35 GMT, "Sid Chapple"
<[email hidden]> wrote:
>Make sure you have this in you core.ini :
>disable_modem = 1
Ah, that did the trick, now loading time is back to a couple of
seconds, thanks :)
Andre
Quoted text (14 lines)
> >Sid. > >"Andre Warringa" <[email hidden]> wrote in message >news:[email hidden]... >> Since I installed my V3 3000 card a couple of weeks ago, it takes >> about a minute before the GPL menu appears after I start GPL. >> Before that it took only a couple of seconds. >> I had some problems with old V2 drivers in the registry, and I thought >> it might be related to that, but I did a clean Windows install and >> still have the problem. >> Any ideas? >> >> AndreGPL would have always been looking for serial ports/modems/network
connections. My guess is that if you tell GPL to not look for modems (set
disable_modem=1 in the [Communications] section of core.ini), the delay will
go away. Maybe installing the V3 generated some kind of conflict that's now
causing Windows' modem code to take longer to timeout looking for modems.
Or, maybe it thinks your V3 card _is_ a modem (it is Windows, so anything's
possible :=)
Randy
Andre Warringa <[email hidden]> wrote in message
news:[email hidden]...
Quoted text (17 lines)
> On Wed, 16 Aug 2000 01:29:03 GMT, "Simon Brown" > <[email hidden]> wrote: > > >This is when GPL looks for TCP/IP and IPX network devices > > Thanks, I'll check the core.ini when I get home from work. But I > wonder why GPL started searching for this after I installed my V3? > > Andre > > > > > >"Andre Warringa" <[email hidden]> wrote in message > >news:[email hidden]... > >> > >> The loading screen appears, and then it takes a minute before the menu > >> appears.On Wed, 16 Aug 2000 10:31:57 -0400, "Randy Cassidy"
<[email hidden]> wrote:
Oh well, at least it works perfect again :)
Andre
Quoted text (9 lines)
>GPL would have always been looking for serial ports/modems/network >connections. My guess is that if you tell GPL to not look for modems (set >disable_modem=1 in the [Communications] section of core.ini), the delay will >go away. Maybe installing the V3 generated some kind of conflict that's now >causing Windows' modem code to take longer to timeout looking for modems. >Or, maybe it thinks your V3 card _is_ a modem (it is Windows, so anything's >possible :=) > >RandyI simply leave my modem at power-on. No annoying delays since then.
JensSchumi
On Wed, 16 Aug 2000 10:31:57 -0400, "Randy Cassidy"
<[email hidden]> wrote:
>GPL would have always been looking for serial ports/modems/network
>connections. My guess is that if you tell GPL to not look for modems (set<snip>
---------------------------------------------
LWFF Ball Bearing conversion at:
http://members.xoom.com/JensSchu/
GPLRank: -0.39
Tried all of below - but made no difference. I can confirm that it
takes just over 30 secs for the screen to come up. Looks suspiciously
like a timeout going off somewhere. But what?
On Thu, 17 Aug 2000 21:42:30 +0100 Alan Chandler
<[email hidden]> wrote:
Alan
[email hidden]
http://www.chandler.u-net.com
Quoted text (22 lines)
>Thanks guys. you seemed to have pointed my at something I had been >wondering about for a while. I thought it was the result of one of >the patches or the fact that I had replaced my CD-ROM drive with a >DVD-ROM drive. > >My delay (European version needs to access the CD)is before anything >happens screen wise, and can be up to about 45 secs or so. I suspect >the reason is that I have recently installed an ethernet card to set >up a home network. > >What I would like to figure out now - is what should I do with the >Core.INI so that I can race (via a modem connection) over the internet >but avoid the delay by disabling my lan connection and ipx. > > >Should I set parameters as follows > >disable_ipx = 1 ; Disable IPX support >disable_modem = 1 ; Don't look for/use modems >disable_network = 1 ; Disable network support >disable_tcp_ip = 0 ; Disable TCP/IP support >Thanks guys. you seemed to have pointed my at something I had been
wondering about for a while. I thought it was the result of one of
the patches or the fact that I had replaced my CD-ROM drive with a
DVD-ROM drive.
My delay (European version needs to access the CD)is before anything
happens screen wise, and can be up to about 45 secs or so. I suspect
the reason is that I have recently installed an ethernet card to set
up a home network.
What I would like to figure out now - is what should I do with the
Core.INI so that I can race (via a modem connection) over the internet
but avoid the delay by disabling my lan connection and ipx.
Should I set parameters as follows
disable_ipx = 1 ; Disable IPX support
disable_modem = 1 ; Don't look for/use modems
disable_network = 1 ; Disable network support
disable_tcp_ip = 0 ; Disable TCP/IP support
I can't find mention of all of these in the readme
Thanks
On Wed, 16 Aug 2000 10:31:57 -0400 "Randy Cassidy"
<[email hidden]> wrote:
Alan
[email hidden]
http://www.chandler.u-net.com
