****** QUAKE ERROR ******
Ray Rarey
I just upgraded from Quake 1.01 to 1.06 on my Pentium 133, and I got
the following error. This is an output of the screen:
C:\QUAKE>quake
Quake v1.06
Locked 1 Mb image
Locked 7 Mb data
Exiting due to signal SIGSEGV
Page fault at eip=00044d6d
eax=18372f18 ebx=007cb000 ecx=00062a6c edx=007b9004 esi=00124ffc
edi=007bb000
ebp=00124ffc esp=0011b26c cs=00a7 ds=00af es=00af fs=00cf gs=00cf
ss=00af
Call frame traceback EIPs:
0x00044d6d
0x0004f200
C:\QUAKE>
C:\QUAKE>
I am running quake in DOS on a win 3.1 machine, I have a pentium 133
with 12 megs or RAM. I have the full version of Quake. If anyone can
tell me why this error is occurring and/or what can be done to correct
it, it would be greatly appreciated.
Thanks in advance,
Ray Rarey
Matthew J Smalley
Hi Ray,
Ray Rarey <ra...@accessus.net> wrote in article
<329BB3...@accessus.net>...
> Exiting due to signal SIGSEGV
> I am running quake in DOS on a win 3.1 machine, I have a pentium 133
> with 12 megs or RAM. I have the full version of Quake. If anyone can
> tell me why this error is occurring and/or what can be done to correct
> it, it would be greatly appreciated.
I got this error: when I told Win95 to use all my 16MB of RAM: when I cut
it back to 8MB, it worked OK: try changing -winmem to 4 or something???
Regards:
Matthew.
MercyKiller
Peace,
MercyKiller
Zeppo
MercyKiller <al...@worldaccess.com> wrote:
Try this link, it helped me.
http://www.geocities.com/SiliconValley/Park/3738/qsegv.html
barhay
listen I got the EXACT EXACT same error message see below: I also patched
to ver1.06
Quake v1.06
Loaded 1 Mb image
Allocated 8 Mb data
malloc'd: 8437760
Added packfile c:/bobby/games/quake/id1/pak0.pak (339 files)
Added packfile c:/bobby/games/quake/id1/pak1.pak (85 files)
PackFile: c:/bobby/games/quake/id1/pak1.pak : gfx/pop.lmp
Playing registered version.
Exiting due to signal SIGSEGV
eax=000afa80 ebx=00000031 ecx=000af920 edx=e07a3f82 esi=82d3e3b4
edi=000af920
ebp=000af910 esp=0011b138 cs=00af ds=00b7 es=00b7 fs=00e7 gs=00d7 ss=00b7
Call frame traceback EIPs:
0x000268d4
the only difference is that I have 16m ram , pentium 75, i also have the
registered version
what the fuck is going on ???
HELP US PLEASE
bar...@globalserve.net
roac...@ix.netcom.com
On Tue, 26 Nov 1996 19:18:32 -0800, Ray Rarey <ra...@accessus.net>
wrote:
>I just upgraded from Quake 1.01 to 1.06 on my Pentium 133, and I got
>the following error. This is an output of the screen:
>
>C:\QUAKE>quake
>Quake v1.06
>Locked 1 Mb image
>Locked 7 Mb data
>Exiting due to signal SIGSEGV
>Page fault at eip=00044d6d
>eax=18372f18 ebx=007cb000 ecx=00062a6c edx=007b9004 esi=00124ffc
>edi=007bb000
>ebp=00124ffc esp=0011b26c cs=00a7 ds=00af es=00af fs=00cf gs=00cf
>ss=00af
>Call frame traceback EIPs:
> 0x00044d6d
> 0x0004f200
>C:\QUAKE>
>C:\QUAKE>
>
>I am running quake in DOS on a win 3.1 machine, I have a pentium 133
>with 12 megs or RAM. I have the full version of Quake. If anyone can
>tell me why this error is occurring and/or what can be done to correct
>it, it would be greatly appreciated.
>
>
> Thanks in advance,
>
>
> Ray Rarey
Hey guys,
I just upgraded too... ASUS M/B, Cyrix 166+, 32 megs of RAM,
and I'm getting page faults up the yin-yang! I can't finish a one hour
session of ANY program without getting a page fault... Are they
attributed to memory in any way? HAAALP!!!
Jason Pollock
Well, if all you people have the reg'ed version of the software, why
not email/call id software? They have probably heard of the problem
already, and they would probably like to hear about the problem.
Jason
Loretta J. Locicero
> >I just upgraded from Quake 1.01 to 1.06 on my Pentium 133, and I got
> >the following error. This is an output of the screen:
> >
> >C:\QUAKE>quake
> >Quake v1.06
> >Locked 1 Mb image
> >Locked 7 Mb data
> >Exiting due to signal SIGSEGV
> >Page fault at eip=00044d6d
> >eax=18372f18 ebx=007cb000 ecx=00062a6c edx=007b9004 esi=00124ffc
> >edi=007bb000
> >ebp=00124ffc esp=0011b26c cs=00a7 ds=00af es=00af fs=00cf gs=00cf
> >ss=00af
> >Call frame traceback EIPs:
> > 0x00044d6d
> > 0x0004f200
> >C:\QUAKE>
> >C:\QUAKE>
> >
> >I am running quake in DOS on a win 3.1 machine, I have a pentium 133
> >with 12 megs or RAM. I have the full version of Quake. If anyone can
> >tell me why this error is occurring and/or what can be done to correct
> >it, it would be greatly appreciated.
> and I'm getting page faults up the yin-yang! I can't finish a one hour
> session of ANY program without getting a page fault... Are they
> attributed to memory in any way? HAAALP!!!
I was getting the same kind of errors in a Cyrix 100+ with 80 Meg RAM
(yes! 80), until I switched my high memory manager to the himem and
emm386 that came with windows 3.1. Before that, I was using Novell DOS
7's memory managers, followed by Netroom 3.04. Both produced the errors.
Microsoft, OK. Go figure.
Now I am more than ever certain that the memory manager is responsible.
P.S.: The amount of memory that is loaded depends on the Expanded
Memory allocated by DOS, not the total linear Extended Memory installed.
Matthew Ang
Loretta J. Locicero <ljl...@mail.idt.net> wrote in article
<329FC8...@mail.idt.net>...
> I was getting the same kind of errors in a Cyrix 100+ with 80 Meg RAM
> (yes! 80), until I switched my high memory manager to the himem and
> emm386 that came with windows 3.1. Before that, I was using Novell DOS
> 7's memory managers, followed by Netroom 3.04. Both produced the errors.
> Microsoft, OK. Go figure.
>
> Now I am more than ever certain that the memory manager is responsible.
>
Oh, you're quite right about the memory manager being the problem. I
didn't have any problem with Quake because I was using Microsoft's EMM386,
but I did have problems with a number of other games and they all reported
Page Fault errors. When the memory manager was diabled however, the error
just disappeared like magic.
Matt.
John
I did that already and haven't heard a lick back from them. Everyone
I've talked to has had similar results when writing id. I gave up
playing quake as a result because none of the suggestions I've received
concerning my problem playing Quake on the net with Q95.bat have worked.
-mutant
Beavman
Scott wrote:
>
> Looks like you don't have enough memory....
> >the following error. This is an output of the screen:
> >
> >C:\QUAKE>quake
> >Quake v1.06
> >Locked 1 Mb image
> >Locked 7 Mb data
> >Exiting due to signal SIGSEGV
> >Page fault at eip=00044d6d
> >eax=18372f18 ebx=007cb000 ecx=00062a6c edx=007b9004 esi=00124ffc
> >edi=007bb000
> >ebp=00124ffc esp=0011b26c cs=00a7 ds=00af es=00af fs=00cf gs=00cf
> >ss=00af
> >Call frame traceback EIPs:
> > 0x00044d6d
> > 0x0004f200
> >C:\QUAKE>
> >C:\QUAKE>
> >
> >I am running quake in DOS on a win 3.1 machine, I have a pentium 133
> >with 12 megs or RAM. I have the full version of Quake. If anyone can
> >tell me why this error is occurring and/or what can be done to correct
> >it, it would be greatly appreciated.
> >
> >
> >
> >
> > Ray Rarey
No he said he has a p133 with 12 megs of ram.. thats plenty to play in
dos.. like hes trying to do.. I can play with my p-75 with 8megs and it
locks 5 megs.. so thats not his problem...
ANyways,
--
Tommy Humphries
E-Mail---->tom...@flash.net
Homepage---->http://www.flash.net/~tommyh/
Scott
Scott Radliff
On Fri, 29 Nov 1996 21:15:51 GMT, roac...@ix.netcom.com wrote:
> I just upgraded too... ASUS M/B, Cyrix 166+, 32 megs of RAM,
>and I'm getting page faults up the yin-yang! I can't finish a one hour
>session of ANY program without getting a page fault... Are they
>attributed to memory in any way? HAAALP!!!
Sounds like you are having a overheating problem.
If you have a heat sink fan on you processor then good, but you will
also need a fan blowing over the whole MBD assembly (esspecialy the
processor w/heatsink) I would check out your cableing on the system
board, and IDE cables (really suseptable to heat) to see if anything
is starting to melt.
Marquie
Benedikt Laube
people are beginning to understand that Quake itself is one big error,
and buying it or spending time to download a warez version is one
of the biggest errors one can make.
bye, onion-heads
NnTPservers suck....
NnTPservers suck...
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
NnTPservers suck....
Jackson
I got the exact same error. I have a p-100 40mb RAM and Windows 95. I
only get this error when I try to run Q95.bat. Running Quake.exe the game
runs fine. I have the shareware version 1.06.
Barry(aka Grumpy)
Beavman wrote:
>
> Scott wrote:
I think there is a lack of base memory
In 95 all you should need in the config + auto files is a blaster
statement , and possibly a cdrom set up/ mscdex
try that and make sure there is at least 580 k base memory
B
> >
> > Looks like you don't have enough memory....
> >
> > wrote:
> >
> > >I just upgraded from Quake 1.01 to 1.06 on my Pentium 133, and I got
> > >the following error. This is an output of the screen:
> > >
> > >C:\QUAKE>quake
> > >Quake v1.06
> > >Locked 1 Mb image
> > >Locked 7 Mb data
> > >Exiting due to signal SIGSEGV
> > >Page fault at eip=00044d6d
> > >eax=18372f18 ebx=007cb000 ecx=00062a6c edx=007b9004 esi=00124ffc
> > >edi=007bb000
> > >ebp=00124ffc esp=0011b26c cs=00a7 ds=00af es=00af fs=00cf gs=00cf
> > >ss=00af
> > >Call frame traceback EIPs:
> > > 0x00044d6d
> > > 0x0004f200
> > >C:\QUAKE>
> > >C:\QUAKE>
> > >
> > >I am running quake in DOS on a win 3.1 machine, I have a pentium 133
> > >with 12 megs or RAM. I have the full version of Quake. If anyone can
> > >tell me why this error is occurring and/or what can be done to correct
> > >it, it would be greatly appreciated.
> > >
> > >
> > >
> > >
> > > Ray Rarey
>
> dos.. like hes trying to do.. I can play with my p-75 with 8megs and it
> locks 5 megs.. so thats not his problem...
>
> ANyways,
> --
> Tommy Humphries
> E-Mail---->tom...@flash.net
> Homepage---->http://www.flash.net/~tommyh/
--
The very act of forwarding unsolicited spammail means you agree
to pay upon my request the sum of $1.00 per unsolicited word
Demand for payment , or spammail, may be returned two
hundred fold to you with suitable comments and editing
James Allen
Listen people:
The SIGSEV and page fualt error message has nothing do with what hardware
you have in your system or whether you have a heat sink or not. If your
IDE cable wasnt on right, your computer wouldnt even boot, dont be
rediculous.
Here is the problem: You folks are still living in the world of Real-Mode
16bit games that demand heavily managed memory. Quake is a 32-bit
Protected-Mode game running on a DOS EXtender. YOU DONT NEED MEMORY
MANAGEMENT!!! Quake will manage your memory.
These page fault errors you are getting are from obscure or improperly
configured memory managers conflicting with Quake's 32-bit heap manager.
How do you fix it you ask? DISABLE THEM ALL! Quake runs best WITHOUT
EMM386, without HIMEM.SYS!
If you booted your PC without a config.sys or autoexec.bat, I promise you
that you will not recieve that error. Quake would run great, albeit
without sound and music, but you can figure out how to fix that. Just add
the neccassary garbage to your autoexec.bat.
The point is: NO MEMORY MANAGERS!
Quake runs in Protected Mode on a DOS Extender, the less bullshit you have
loading up at bootup the Better!
Have Fun... See you guys/gals in NETQUAKE!
Sincerely,
James
jer...@bitstream.net aka Spin-Control
Scott Lyon
Benedikt Laube wrote:
> people are beginning to understand that Quake itself is one big error,
> and buying it or spending time to download a warez version is one
> of the biggest errors one can make.
Only for mnetal incompetents Benedikt....I guess that puts you at the
top of the list.......
--
********************************************
sco...@cyberlynk.com
GAMERS CORNER -> http://www.cyberlynk.com/~scottl
Handle -> MUGGER. NET QUAKE Rules !!!!!
********************************************
Loretta J. Locicero
>
> Here is the problem: You folks are still living in the world of Real-Mode
> 16bit games that demand heavily managed memory. Quake is a 32-bit
> Protected-Mode game running on a DOS EXtender. YOU DONT NEED MEMORY
> MANAGEMENT!!! Quake will manage your memory.
>
> These page fault errors you are getting are from obscure or improperly
> configured memory managers conflicting with Quake's 32-bit heap manager.
> How do you fix it you ask? DISABLE THEM ALL! Quake runs best WITHOUT
> EMM386, without HIMEM.SYS!
>
> If you booted your PC without a config.sys or autoexec.bat, I promise you
> that you will not recieve that error. Quake would run great, albeit
> without sound and music, but you can figure out how to fix that. Just add
> the neccassary garbage to your autoexec.bat.
>
> The point is: NO MEMORY MANAGERS!
>
> Quake runs in Protected Mode on a DOS Extender, the less bullshit you have
> loading up at bootup the Better!
>
> Have Fun... See you guys/gals in NETQUAKE!
>
> Sincerely,
>
> James
>
> jer...@bitstream.net aka Spin-Control
>
>
any of my 80 Megs of RAM and Quake didn't see it when starting up. Go
figure...
John
> Listen people:
>
> Here is the problem: You folks are still living in the world of Real-Mode
> 16bit games that demand heavily managed memory. Quake is a 32-bit
> Protected-Mode game running on a DOS EXtender. YOU DONT NEED MEMORY
> MANAGEMENT!!! Quake will manage your memory.
>
> These page fault errors you are getting are from obscure or improperly
> configured memory managers conflicting with Quake's 32-bit heap manager.
> How do you fix it you ask? DISABLE THEM ALL! Quake runs best WITHOUT
> EMM386, without HIMEM.SYS!
>
>
>
> Quake runs in Protected Mode on a DOS Extender, the less bullshit you have
> loading up at bootup the Better!
>
> Have Fun... See you guys/gals in NETQUAKE!
>
> Sincerely,
>
> James
>
> jer...@bitstream.net aka Spin-Control
While you are absolutely right about not needing memory managers for
Quake, your suggestion to totally delete autoexec.bat and config.sys
won't necessarily fix SIGSEGV errors. I am getting SIGSEGV errors when
I try to run netquake and deleting autoexec.bat and config.sys did
nothing to help. I posted the reason people get these errors (see the
message titled SIGSEGV: Official Word that I posted the other day) as
told to me by id tech support. According to id, the "error exiting due
to SIGSEGV" message is caused by a bug in MPath. Supposedly, id is
working on a fix now. I'm guessing that when Quakeworld comes out is
when the fix will be released.
My 2 Pesos,
Mutant
Dave Readman
la...@hrz.uni-kassel.de (Benedikt Laube) wrote:
>On Tue, 26 Nov 1996 19:18:32 -0800, Ray Rarey <ra...@accessus.net>
>wrote:
>
>>I just upgraded from Quake 1.01 to 1.06 on my Pentium 133, and I got
>>the following error. This is an output of the screen:
>>
>>C:\QUAKE>quake
>>Quake v1.06
>>Locked 1 Mb image
>>Locked 7 Mb data
>>Exiting due to signal SIGSEGV
>>Page fault at eip=00044d6d
>>eax=18372f18 ebx=007cb000 ecx=00062a6c edx=007b9004 esi=00124ffc
>>edi=007bb000
>>ebp=00124ffc esp=0011b26c cs=00a7 ds=00af es=00af fs=00cf gs=00cf
>>ss=00af
>>Call frame traceback EIPs:
>> 0x00044d6d
>> 0x0004f200
>>C:\QUAKE>
>>C:\QUAKE>
>>
>>I am running quake in DOS on a win 3.1 machine, I have a pentium 133
>>with 12 megs or RAM. I have the full version of Quake. If anyone can
>>tell me why this error is occurring and/or what can be done to correct
>>it, it would be greatly appreciated.
>
>people are beginning to understand that Quake itself is one big error,
>and buying it or spending time to download a warez version is one
>of the biggest errors one can make.
>
>bye, onion-heads
>
>
>NnTPservers suck....
>NnTPservers suck...
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
>NnTPservers suck....
Ray,
I got the same problem when I upgraded my Cyrix P6-150 from
Quake 1.01 to 1.06. The "Page fault" is the same, althhough the other
numbers differ slightly. I found, as a work-around, that it worked
fine from a boot disk using EXACTLY the same config & autoexec I
normally use. I don't understand it. My Pentium 120 was unaffected by
the upgrade. I run Win-95 with msdos.sys altered to allow me to boot
to command-line-interface and the same 16 bit drivers loaded that I
would use on a DOS machine. This is the first game to have ANY
problems. Were you using DOS or Win-95. I'd like to know. (it might
give a clu as to what's going on.)
BTW: I wiped my hard - drive & loaded DOs 6.22 andf Quake 1.06 ran
fine. Back to Win95 and I need a boot disk again.
Dave Readman WWW to The Jaguar's Lair
"The Jaguar" Official Web page for "Bridge Crew"
jag...@werple.mira.net.au A TRUE co-operative multi-player game
"....All's well that ends!" http://werple.mira.net.au/~jaguar/main.html
James B. Langley
I get this when I run q95.bat...
Quake v1.01
Loaded 1 Mb image
Allocated 8 Mb data
malloc'd: 8445952
Added packfile c:/quake_sw/id1/pak0.pak (339 files)
FindFile: can't find gfx/pop.lmp
Playing shareware version.
Exiting due to signal SIGSEGV
Page fault at eip=00025324
eax=fffff573 ebx=00119114 ecx=825ad370 edx=825aa4d0 esi=00000002
edi=0005b198
ebp=001192cc esp=001190f4 cs=00a7 ds=00af es=00af fs=00df gs=00cf ss=00af
Call frame traceback EIPs:
0x00025324
I have 1.06, have nothing in my config.sys or autoexec.bat. This is a
bummer cause I just changed to a K5 - 100 motherboard and it really flys
compared to what I had before. I wonder if the video card has anything to
do with this.
No I haven't registered the game yet and will not until I solve this
problem. BTW, I can run it fine when I shut down to DOS.
Jackson <m...@dmv.com> wrote in article <01bbe161$18563200$c3401ece@mrj>...
James B. Langley
I'm not going to register SHAREWARE that does not run on my machine.
That's the whole purpose of what shareware is all about! I did the same
thing with DOOM 2, and then bought it. ID makes great stuff, but let's be
sure it runs first.
Jason Pollock <jpol...@bnr.ca> wrote in article
<57nq1r$8...@bcrkh13.bnr.ca>...
Joshua K. Oswald
If memory managers are the problem, why does this error happen to some
of us using Win95. I know Win95 also uses a memory manager, but as far
as I know there is no way to modify the settings or disable it (which
would decrease performance anyway). And the memory manager theory does
not explain why Quake worked fine for a month until I reformatted my HD
and reinstalled the game. I was able to solve the error by using the DNS
trick suggested by some people, but I know this does not work for most
so I don't propose it is a remedy. I think the real solution is what id
software should be looking for. How 'bout it guys??
Josh
James Allen wrote:
>
> On Mon, 2 Dec 1996, Scott Radliff wrote:
>
> > On Fri, 29 Nov 1996 21:15:51 GMT, roac...@ix.netcom.com wrote:
> >
> >
> > > I just upgraded too... ASUS M/B, Cyrix 166+, 32 megs of RAM,
> > >and I'm getting page faults up the yin-yang! I can't finish a one hour
> > >session of ANY program without getting a page fault... Are they
> > >attributed to memory in any way? HAAALP!!!
> >
> > Sounds like you are having a overheating problem.
> >
> > If you have a heat sink fan on you processor then good, but you will
> > also need a fan blowing over the whole MBD assembly (esspecialy the
> > processor w/heatsink) I would check out your cableing on the system
> > board, and IDE cables (really suseptable to heat) to see if anything
> > is starting to melt.
> >
> > Marquie
> >
> >
>
> Listen people:
>
> The SIGSEV and page fualt error message has nothing do with what hardware
> you have in your system or whether you have a heat sink or not. If your
> IDE cable wasnt on right, your computer wouldnt even boot, dont be
> rediculous.
>
> Here is the problem: You folks are still living in the world of Real-Mode
> 16bit games that demand heavily managed memory. Quake is a 32-bit
> Protected-Mode game running on a DOS EXtender. YOU DONT NEED MEMORY
> MANAGEMENT!!! Quake will manage your memory.
>
> These page fault errors you are getting are from obscure or improperly
> configured memory managers conflicting with Quake's 32-bit heap manager.
> How do you fix it you ask? DISABLE THEM ALL! Quake runs best WITHOUT
> EMM386, without HIMEM.SYS!
>
> If you booted your PC without a config.sys or autoexec.bat, I promise you
> that you will not recieve that error. Quake would run great, albeit
> without sound and music, but you can figure out how to fix that. Just add
> the neccassary garbage to your autoexec.bat.
>
Rooke
I'm also getting the same error as you, but mine problem seems to be worse.
I'll try to run Quake in DOS, but I get the error stated below(Boot Disk
was used). When I try to run it in Windows95, it runs just fine. I know
the problem is in the patch because this accured after installing the
1.01-1.06 patch. Could anybody please suggest a solution to our problem.
Thanks.
Henry
>Benedikt Laube <la...@hrz.uni-kassel.de> wrote in article
<32a5390...@news.hrz.uni-kassel.de>...
> On Tue, 26 Nov 1996 19:18:32 -0800, Ray Rarey <ra...@accessus.net>
> wrote:
>
> >I just upgraded from Quake 1.01 to 1.06 on my Pentium 133, and I got
> >the following error. This is an output of the screen:
> >
> >C:\QUAKE>quake
> >Quake v1.06
> >Locked 1 Mb image
> >Locked 7 Mb data
> >Exiting due to signal SIGSEGV
> >Page fault at eip=00044d6d
> >eax=18372f18 ebx=007cb000 ecx=00062a6c edx=007b9004 esi=00124ffc
> >edi=007bb000
> >ebp=00124ffc esp=0011b26c cs=00a7 ds=00af es=00af fs=00cf gs=00cf
> >ss=00af
> >Call frame traceback EIPs:
Ismail Saeed
I won't pretend to know everything about this error, but it seems to me
that Quake 1.06 is either more of a memory hog or takes more memory to
get initialized. (The latter would be my better guess)
That's my thought on this SIGSEGV error. I've gotten them if I
control-break during Quake startup (before graphics show up) on both
1.01 and 1.06. I can't say I've seen them otherwise (don't flame me,
I'm thinking as I type....).
EVERYONE who gets this error and has windows 95, how much RAM do you
guys have? If you ALL have less than 16 I can see a definite scenario
solvable. But if it occurs on 16 meg machines too, hmm.
One thing I know that might be worth a shot by anyone who gets this
error. Quake is able to use less than 8 megs of data (as it says in
startup) on computers with 8 megs of ram only (naturally). I know the
winmem switch can be used to specify MORE and LESS, just type in how
many megs.
Has anyone who gets this error tried typing winmem -6? I know Quake
works with a 6mb data buffer because thats what it used to have on my
486 dx2 50 before I got this p166. Maybe this will MAKE Quake take less
memory than its doing normally in startup and let it actually get MOVING
along in the startup.
Anyone who gets this error, please experiment with what I've said and
tell me if i'm in a ballpark or a really bad batter. Post whatever
results you get to the newsgroup, and if you can email them to me also.
That way, I can see some different results and come up with something
and people on this group get the benefit of figuring this out too.
Since so many people have this error, I've decided to TRY and figure it
out.
Thanks for reading........
Slipgate
Carlos Ochoa
I had the same problem. I get around this problem by rebooting and then
pressing F8 when I see "starting Windows95". Then I go through step by
step confirmation and put no when asked to stop Windows. It worked for me
I hope it works for you.
Rooke <hst...@nmsu.edu> wrote in article
<01bbe4ee$ab0b1440$903e...@NMSU.nmsu.edu>...
Ismail Saeed
Ismail Saeed wrote:
This is a mail reply I got to this post.
Thank you Damian Carr, I'll see what I come up with (it would help
solving it if I actually got the error myself :()
Slipgate,
Regarding the SIGSEGV problem: I upgraded to v1.06 and have started to
see this pop up quite often. It only happens when I run the Q95.bat file
for a net game. It has yet to turn up in DOS. An interesting bit of info
to throw a spanner into the memory side of things: With trial & error
I've found that It won't allow me to allocate more than 42MB to -winmem,
if I do it crashes with the SIGSEGV error, and I'm running 128MB of EDO
& DIMM RAM on a P166! But get this, a friend of mine with a P150 and
64MB EDO allocates 60MB and has yet to have a problem (he's running
v1.06 as well). A page fault would signify a memory problem, but for it
to happen at both end's of the scale is very strange indeed. Let me
know if you come across any ideas as to why this is happening as I'd
like to try and solve this as well.
Daemion.
--
Cat Nap Productions Web Site.
http://light.iinet.net.au/~daemion/
-----------------------------------
John Chih-Wei Tang
> I won't pretend to know everything about this error, but it seems to me
> that Quake 1.06 is either more of a memory hog or takes more memory to
> get initialized. (The latter would be my better guess)
>
> That's my thought on this SIGSEGV error. I've gotten them if I
> control-break during Quake startup (before graphics show up) on both
> 1.01 and 1.06. I can't say I've seen them otherwise (don't flame me,
> I'm thinking as I type....).
AFAIK, the SIGSEGV error has nothing to do with memory allocation. Last I
heard the error was caused by a bug in the Mpath enabler. What you can do
to eliminate this problem, is to simply remove the "-mpath" command from
the Q95.BAT batch file. Or, in my experience, this can also result from
having more than 1 TCP/IP stack. e.g. You've got a TCP/IP stack on both
your NIC, and your DUA. Just remove the one on the NIC, and the error
should go away. I know some people are working on this problem, but can't
remember where you can get more information.. somebody in the know can fill
in the details here.
John
David Carpenter
Ismail Saeed wrote:
> I won't pretend to know everything about this error, but it seems to me
> that Quake 1.06 is either more of a memory hog or takes more memory to
> get initialized. (The latter would be my better guess)
>
> That's my thought on this SIGSEGV error. I've gotten them if I
> control-break during Quake startup (before graphics show up) on both
> 1.01 and 1.06. I can't say I've seen them otherwise (don't flame me,
> I'm thinking as I type....).
> Anyone who gets this error, please experiment with what I've said and
> tell me if i'm in a ballpark or a really bad batter. Post whatever
> results you get to the newsgroup, and if you can email them to me also.
> That way, I can see some different results and come up with something
> and people on this group get the benefit of figuring this out too.
>
> Since so many people have this error, I've decided to TRY and figure it
> out.
>
> Thanks for reading........
>
> Slipgate
I've been getting the same error and I have a 16 meg machine <p100 at
that> and it only occurs in Dos mode running version 1.06. It seems to
me that this is the only version that you can get the error in, based on
the fact that I had 1.01 and never got it until upgrading to 1.06. In
Windows95 dos mode I can run the game fine, but man is it slow in
Windows Dos mode. At that the game only uses an 8mb Data file <I think
that is what it is called>, in the older version in straight dos I was
able to get it up to 13mb. Well, that is all the info I can provide for
you. Good Luck in your research!
-Pick