N4: Any one else locking up?

Hi, Just rebooted and started N4 in single player. I was qualifying in a track (geesh - I forget the name, but it's a famous one that starts with T) and it locked up about 10 seconds into it! I can hear the sound, but am frozen. I was playing it in OpenGL in 16-bit color at 1024x768 with my desktop set at 16-bit color and 1280x1024. WTF is up with this game? It is pretty rare that I have problems with a game. Specs: Athlon 700 256MB RAM Hercules GeForce 2 GTS 64MB Pro Windows managing my swap file Windows 98SE Direct X 8.0a I don't plan on playing it on-line much, if at all (due to my connect speed). I bought it at Software ETC so I now have 3 days left to return it. Are there some sound and/or video settings that would make it more stable? Thanks, -paul

Well - I just rebooted and tried the same track again - but this time use EndItAll to make sure I was running with bare bones. It locked up when I clicked on the Drive button under Qualifying. So, I rebooted and just disabled Norton Antivirus this time and was able to get past the interface and begin qualifying. It froze IN THE EXACT SAME SPOT on the track!! If I move my throttle, I can hear the difference. I think the game is still playing but the video is frozen!! Man, I thought this sim would be the reason for me to finally get a wheel. What a piece of junk!! -pw

Quoted text (32 lines)

>Hi, > >Just rebooted and started N4 in single player. I was qualifying in a >track (geesh - I forget the name, but it's a famous one that starts >with T) and it locked up about 10 seconds into it! I can hear the >sound, but am frozen. > >I was playing it in OpenGL in 16-bit color at 1024x768 with my >desktop set at 16-bit color and 1280x1024. > >WTF is up with this game? It is pretty rare that I have problems with >a game. > >Specs: > >Athlon 700 >256MB RAM >Hercules GeForce 2 GTS 64MB Pro >Windows managing my swap file >Windows 98SE >Direct X 8.0a > >I don't plan on playing it on-line much, if at all (due to my connect >speed). I bought it at Software ETC so I now have 3 days left to >return it. > >Are there some sound and/or video settings that would make it more >stable? > >Thanks, > >-paul

It's not the sim pw, you have a problem somewhere and probably can get it figured out. Do a ctrl-alt-del before launching the sim, only think you should show is systray and explorer - anything else is unneeded. Make sure you video and sound card drivers are up to date. Are you trying to run eax? 3dsound? Lots of things you can look at before giving up on it. -- Don Burnette D Burnette in N4 Some people do nothing wrong. The problem is, they do nothing. And THAT is wrong. "pw" <[email hidden]> wrote in message news:98ev55$9pv$[email hidden]... > Well - I just rebooted and tried the same track again - but this time > use EndItAll to make sure I was running with bare bones. It locked up > when I clicked on the Drive button under Qualifying. > > So, I rebooted and just disabled Norton Antivirus this time and was > able to get past the interface and begin qualifying. It froze IN THE > EXACT SAME SPOT on the track!! If I move my throttle, I can hear the > difference. I think the game is still playing but the video is > frozen!! > > Man, I thought this sim would be the reason for me to finally get a > wheel. What a piece of junk!! > > -pw > > >Hi, > > > >Just rebooted and started N4 in single player. I was qualifying in a > >track (geesh - I forget the name, but it's a famous one that starts > >with T) and it locked up about 10 seconds into it! I can hear the > >sound, but am frozen. > > > >I was playing it in OpenGL in 16-bit color at 1024x768 with my > >desktop set at 16-bit color and 1280x1024. > > > >WTF is up with this game? It is pretty rare that I have problems with > >a game. > > > >Specs: > > > >Athlon 700 > >256MB RAM > >Hercules GeForce 2 GTS 64MB Pro > >Windows managing my swap file > >Windows 98SE > >Direct X 8.0a > > > >I don't plan on playing it on-line much, if at all (due to my connect > >speed). I bought it at Software ETC so I now have 3 days left to > >return it. > > > >Are there some sound and/or video settings that would make it more > >stable? > > > >Thanks, > > > >-paul >

I was crashing too, a LOT! . It AINT the game, it's us. NASCAR 4 is selling VERY fast and there are a LOT of folks out there running the game. Search the web and the newsgroups and you will find VERY few people complaining of crashes and lockups. Of those who are crashing most of them fix the trouble with a little work. Possible trouble 1 Do you have that NiVida board in AGP 4X? If so that may be your trouble. Get into your bios and disable 4X and operate in 2X. Dont worry about losing that many FPS by switching from 4 to 2X. There is just not that much difference in speed and the stability is one HELL of a lot better. NiVidia hasent got this AGP 4X thing down quite right yet and until they do 4X is a crap shoot. Possible trouble 2 I note you are using DX8a. What drivers are you using on your herc? If they are Herc drivers or any of the "Official Release Drivers" from NiVidia they are NOT optimized for DX8. DX8 optimized release drivers do not exist. If you want DX8 optimized drivers you have to use Beta drivers. I started using the 10.50 today and it seems fine so far. Another one that is supposed to be pretty good is the 756. You can get either (and a lot more besides) at "reactorcritical.com" or "the-ctrl-alt-del.com" If you go there you will see 1080 drivers. Stay away from them. They are optimised for Win2000 and will likely slow you down. Possible trouble 3 I note you have a T-Bird. Me too. What motherboard do you have and what sound card. If you have an Abit KT series and a Soundblaster Live you MIGHT have trouble. If you have any board with VIA KX133 or KT133 chipsets and any Areal Vortex based soundcard you DO have trouble. Possible trouble 4 If you have an Athlon you likely have VIA chips. If you do, go here: http://www.viahardware.com/download/index.shtm#4in1 You will be looking at a download page full of VIA drivers. You want the "4.29 FINAL" at the top link. This is a "4 in 1" and contains every chipset driver you need except one. That one is "USB Filter Driver 1.08". You can pick that one up at a link near the bottom of the page. If you do not have VIA chips (possible but unlikely with an Athlon) or if you dont know what chipset you have dont get any of these drivers until you email me so I can ask you some questions about your machine. There are other possible trouble spots but these will do for now. It is possible that you have already got a handle on these but just in case you dont know I mentioned them here. In any case, the trouble AINT with NASCAR 4. It is us who are crashing it, not it that is crashing us. NASCAR 4 was locking up constantly but now it is pretty trouble free. "pw" <[email hidden]> wrote in message news:98ev55$9pv$[email hidden]...

Quoted text (49 lines)

> Well - I just rebooted and tried the same track again - but this time > use EndItAll to make sure I was running with bare bones. It locked up > when I clicked on the Drive button under Qualifying. > > So, I rebooted and just disabled Norton Antivirus this time and was > able to get past the interface and begin qualifying. It froze IN THE > EXACT SAME SPOT on the track!! If I move my throttle, I can hear the > difference. I think the game is still playing but the video is > frozen!! > > Man, I thought this sim would be the reason for me to finally get a > wheel. What a piece of junk!! > > -pw > > >Hi, > > > >Just rebooted and started N4 in single player. I was qualifying in a > >track (geesh - I forget the name, but it's a famous one that starts > >with T) and it locked up about 10 seconds into it! I can hear the > >sound, but am frozen. > > > >I was playing it in OpenGL in 16-bit color at 1024x768 with my > >desktop set at 16-bit color and 1280x1024. > > > >WTF is up with this game? It is pretty rare that I have problems with > >a game. > > > >Specs: > > > >Athlon 700 > >256MB RAM > >Hercules GeForce 2 GTS 64MB Pro > >Windows managing my swap file > >Windows 98SE > >Direct X 8.0a > > > >I don't plan on playing it on-line much, if at all (due to my connect > >speed). I bought it at Software ETC so I now have 3 days left to > >return it. > > > >Are there some sound and/or video settings that would make it more > >stable? > > > >Thanks, > > > >-paul > >

"Joe L." <[email hidden]> wrote in message news:jMFq6.4267$[email hidden]...

Quoted text (8 lines)

> I was crashing too, a LOT! . It AINT the game, it's us. NASCAR 4 is > selling VERY fast and there are a LOT of folks out there running the game. > Search the web and the newsgroups and you will find VERY few people > complaining of crashes and lockups. Of those who are crashing most of them > fix the trouble with a little work. > > Possible trouble 1> Possible trouble 3 > I note you have a T-Bird. Me too. What motherboard do you have and

what > sound card. If you have an Abit KT series and a Soundblaster Live youMIGHT > have trouble. If you have any board with VIA KX133 or KT133 chipsets and > any Areal Vortex based soundcard you DO have trouble. Thanks Joe...I think I'll point out...I just re-installed N4 after an upgrade to a tbird with a via chipset and an Aureal sound card. Everything worked for my first two hours online...no lockups...I should mention, No NVIDIA product has graced this system....even with win98se's supposed problems with via chipset...no problemo...via 4n1 v4.28 mobo drivers 3dfx V5. with the November 20th drivers... 40 to 60 fps...worked very well. (kt133a) chipset...Microstar mobo. dave henrie

Quoted text (8 lines)

> > Possible trouble 4 > If you have an Athlon you likely have VIA chips. If you do, go here: > > http://www.viahardware.com/download/index.shtm#4in1 > > You will be looking at a download page full of VIA drivers. You want the > "4.29 FINAL" at the top link. This is a "4 in 1" and contains every

chipset > driver you need except one. That one is "USB Filter Driver 1.08". You can > pick that one up at a link near the bottom of the page. > If you do not have VIA chips (possible but unlikely with an Athlon)or

Quoted text (65 lines)

> if you dont know what chipset you have dont get any of these drivers until > you email me so I can ask you some questions about your machine. > > There are other possible trouble spots but these will do for now. It is > possible that you have already got a handle on these but just in case you > dont know I mentioned them here. In any case, the trouble AINT with NASCAR > 4. It is us who are crashing it, not it that is crashing us. NASCAR 4 was > locking up constantly but now it is pretty trouble free. > > > > > "pw" <[email hidden]> wrote in message > news:98ev55$9pv$[email hidden]... > > Well - I just rebooted and tried the same track again - but this time > > use EndItAll to make sure I was running with bare bones. It locked up > > when I clicked on the Drive button under Qualifying. > > > > So, I rebooted and just disabled Norton Antivirus this time and was > > able to get past the interface and begin qualifying. It froze IN THE > > EXACT SAME SPOT on the track!! If I move my throttle, I can hear the > > difference. I think the game is still playing but the video is > > frozen!! > > > > Man, I thought this sim would be the reason for me to finally get a > > wheel. What a piece of junk!! > > > > -pw > > > > >Hi, > > > > > >Just rebooted and started N4 in single player. I was qualifying in a > > >track (geesh - I forget the name, but it's a famous one that starts > > >with T) and it locked up about 10 seconds into it! I can hear the > > >sound, but am frozen. > > > > > >I was playing it in OpenGL in 16-bit color at 1024x768 with my > > >desktop set at 16-bit color and 1280x1024. > > > > > >WTF is up with this game? It is pretty rare that I have problems with > > >a game. > > > > > >Specs: > > > > > >Athlon 700 > > >256MB RAM > > >Hercules GeForce 2 GTS 64MB Pro > > >Windows managing my swap file > > >Windows 98SE > > >Direct X 8.0a > > > > > >I don't plan on playing it on-line much, if at all (due to my connect > > >speed). I bought it at Software ETC so I now have 3 days left to > > >return it. > > > > > >Are there some sound and/or video settings that would make it more > > >stable? > > > > > >Thanks, > > > > > >-paul > > > > > >

PW, I had the same prob with my Herc Geforce II GTS 64. My problem was directly related to my vid card overheating in my small tower case. In an attempt to verify this you can simply pop the case open and try to run. The card runs very hot. I think that the game taxes the vid card regardless of which video mode. This was even happening to me in the demo of N4. Cooling seems to have helped my prob. My specs: Thunderbird 1.1ghz 512meg pc133 Hercules Geforce 2 GTS 64 SBLive--> Liveware 3.0 WinME DX 8.0 No overclocking. Talon "pw" <[email hidden]> wrote in message news:98ev55$9pv$[email hidden]...

Quoted text (48 lines)

> Well - I just rebooted and tried the same track again - but this time > use EndItAll to make sure I was running with bare bones. It locked up > when I clicked on the Drive button under Qualifying. > > So, I rebooted and just disabled Norton Antivirus this time and was > able to get past the interface and begin qualifying. It froze IN THE > EXACT SAME SPOT on the track!! If I move my throttle, I can hear the > difference. I think the game is still playing but the video is > frozen!! > > Man, I thought this sim would be the reason for me to finally get a > wheel. What a piece of junk!! > > -pw > > >Hi, > > > >Just rebooted and started N4 in single player. I was qualifying in a > >track (geesh - I forget the name, but it's a famous one that starts > >with T) and it locked up about 10 seconds into it! I can hear the > >sound, but am frozen. > > > >I was playing it in OpenGL in 16-bit color at 1024x768 with my > >desktop set at 16-bit color and 1280x1024. > > > >WTF is up with this game? It is pretty rare that I have problems with > >a game. > > > >Specs: > > > >Athlon 700 > >256MB RAM > >Hercules GeForce 2 GTS 64MB Pro > >Windows managing my swap file > >Windows 98SE > >Direct X 8.0a > > > >I don't plan on playing it on-line much, if at all (due to my connect > >speed). I bought it at Software ETC so I now have 3 days left to > >return it. > > > >Are there some sound and/or video settings that would make it more > >stable? > > > >Thanks, > > > >-paul >

My screen will freeze for 5 seconds every race online and offline, Online that will warp me back to last place. These lockups seem to happen alot with the Geforce Series Cards. So Im going out and getting a Voodoo card a 4 or a 5 and see if that fixes the problems.

Quoted text (20 lines)

>PW, > >I had the same prob with my Herc Geforce II GTS 64. My problem was directly >related to my vid card overheating in my small tower case. In an attempt to >verify this you can simply pop the case open and try to run. The card runs >very hot. I think that the game taxes the vid card regardless of which >video mode. This was even happening to me in the demo of N4. Cooling seems >to have helped my prob. > >My specs: >Thunderbird 1.1ghz >512meg pc133 >Hercules Geforce 2 GTS 64 >SBLive--> Liveware 3.0 >WinME >DX 8.0 >No overclocking. > >Talon >

Hi, Are you saying that running the game with the case open helped stop crashing, or did you add another fan? Thanks, -pw

Hi, > I was crashing too, a LOT! . It AINT the game, it's us. NASCAR 4 is >selling VERY fast and there are a LOT of folks out there running the game. >Search the web and the newsgroups and you will find VERY few people >complaining of crashes and lockups. I've noticed that. > >Possible trouble 1 > Do you have that NiVida board in AGP 4X? If so that may be your trouble. >Get into your bios and disable 4X and operate in 2X. Hercules board, NVidia chip (64MB DDR GTS Pro). It is a AGP board. How do I get into my bios to disable the 4X and operate into 2X (or check if it's in 4X)? > >Possible trouble 2 > I note you are using DX8a. What drivers are you using on your herc? Hercules 6.35 > If >they are Herc drivers or any of the "Official Release Drivers" from NiVidia >they are NOT optimized for DX8. DX8 optimized release drivers do not exist. Thanks for that info! >If you want DX8 optimized drivers you have to use Beta drivers. I started >using the 10.50 today and it seems fine so far. Another one that is supposed >to be pretty good is the 756. You can get either (and a lot more besides) at >"reactorcritical.com" or "the-ctrl-alt-del.com" Whose drivers are these, btw? They won't screw up other games, will they? I just played a couple of other games (not sims :-) for hours last night w/o a single crash. But, one of them was "UnDying" and it requires Direct X 8 (and the reason I installed it) so it looks like that backs up your point about DX8. > If you go there you will >see 1080 drivers. Stay away from them. They are optimised for Win2000 and >will likely slow you down. Okay, will do!

Quoted text (7 lines)

> >Possible trouble 3 > I note you have a T-Bird. Me too. What motherboard do you have and what >sound card. If you have an Abit KT series and a Soundblaster Live you MIGHT >have trouble. If you have any board with VIA KX133 or KT133 chipsets and >any Areal Vortex based soundcard you DO have trouble. >

Not a T-Bird. I was actually on the cutting edge for a little while. It's the original Athlon 700 CPU with a Athlon GigaByte GA-IX mobo.

Quoted text (8 lines)

>you email me so I can ask you some questions about your machine. > > There are other possible trouble spots but these will do for now. It is >possible that you have already got a handle on these but just in case you >dont know I mentioned them here. In any case, the trouble AINT with NASCAR >4. It is us who are crashing it, not it that is crashing us. NASCAR 4 was >locking up constantly but now it is pretty trouble free. >

Okay - I will keep it and keep plugging away at it until I get it to work! Thanks so much! -pw

On Sun, 11 Mar 2001 04:38:43 GMT, "Don Burnette" <[email hidden]> wrote: >It's not the sim pw, you have a problem somewhere and probably can get it >figured out. >Do a ctrl-alt-del before launching the sim, only think you should show is >systray and explorer - anything else is unneeded. >Make sure you video and sound card drivers are up to date. Are you trying to >run eax? 3dsound? I have Direct Sound checked and 3D unchecked. >Lots of things you can look at before giving up on it. I will keep plugging away at it! After locking up twice in a row with OpenGL at 16 bit color, then 32-bit color, I tried it with D3D in 32 bit color and finished the qualifying, and then started the race! I certainly have less problems w/ N4 in D3D and more in OGL. Thanks, -pw

Then for you it's "so far so good". But take a look at this: ---------------------------------------------------------------------------- ---------------------------- The following problem was noted for VIA KX133 chipset motherboards before the KT133 chipset was released. The KT7 motherboard uses the VIA KT133 chipset which is very similar to the KX133 chipset. The following comments therefore apply to the KT7 and KT7-RAID motherboards. For audio cards that use A3D audio chip there appears to be an incompatibility that causes the KX133 system to deadlock when system traffic is heavy. The reason for this is that the A3D chip issues one memory read request cycle to the North Bridge and expects a grant within 4 mico-sec of latency time. If PCI TRDY# is not asserted after 4 mico-sec, the A3D hardware will de-assert the FRAME# and REQ# to terminate the operation. However, the A3D audio software driver cannot acknowledge the termination and continues waiting for hardware response. Hence the system hangs. This issue will only occur during heavy system traffic when the North Bridge cannot grant access to A3D audio chip within the 4 mico-sec latency time. There is no known work-around for this issue, and the principal advice is not to use A3D-based sound cards with KX133 based motherboards. Source: VIA Application note Serial #AN137 Date 07/05/00. ---------------------------------------------------------------------------- ----------------------------- So there are documented nails in your electronic road., you simply have not hit them yet. Most reports from folks who have hit the nails say it only happens when the machine is REALLY working hard. 'PW" said he has an Athlon. That Athlon makes it VERY likely that he has VIA chips on his MB. Areal Vortex sound cards are very common so he just might have one of them too. If he does he just might have hit the nails you have, so far, missed. Just checking. Me? I have the KT7/SB Live combination I mentioned. Lots of nails there too. Sounds like PW is only a few days from tossing NASCAR 4 out the window in disgust. Before we lose him I am just standing here yelling "WAIT A MINUTE!!!! If you got one of "these" and one of "those" then maby your trouble is "this" and you need to .........." I'm Fishing. "Dave Henrie" <[email hidden]> wrote in message news:zHGq6.549120$[email hidden]... > > Thanks Joe...I think I'll point out...I just re-installed N4 after an > upgrade to a tbird > with a via chipset and an Aureal sound card. Everything worked for myfirst > two hours online...no lockups...I should mention, No NVIDIA product has > graced > this system....even with win98se's supposed problems with viachipset...no > problemo...via 4n1 v4.28 mobo drivers 3dfx V5. with the November 20th > drivers... > 40 to 60 fps...worked very well. (kt133a) chipset...Microstar mobo. > dave henrie >

Not sure if your using this board or not? Lots of info. here. http://www.icrontic.com/faqs/kt7faq/kt7faq.htm J. Janasov pw <[email hidden]> wrote in message news:98gbkc$lhi$[email hidden]... > >PW, > > > >I had the same prob with my Herc Geforce II GTS 64. My problem wasdirectly > >related to my vid card overheating in my small tower case. In an attemptto > >verify this you can simply pop the case open and try to run. The cardruns > >very hot. I think that the game taxes the vid card regardless of which > >video mode. This was even happening to me in the demo of N4. Coolingseems

Quoted text (22 lines)

> >to have helped my prob. > > > >My specs: > >Thunderbird 1.1ghz > >512meg pc133 > >Hercules Geforce 2 GTS 64 > >SBLive--> Liveware 3.0 > >WinME > >DX 8.0 > >No overclocking. > > > >Talon > > > > Hi, > > Are you saying that running the game with the case open helped stop > crashing, or did you add another fan? > > Thanks, > > -pw

About all I can think of is I have the KX133A chipset...perhaps they have addressed this issue...(brand new 3rd revision Microstar motherboard) dave henrie "Joe L." <[email hidden]> wrote in message news:R4Qq6.5350$[email hidden]... > Then for you it's "so far so good". But take a look at this: > ---------------------------------------------------------------------------- > ---------------------------- > The following problem was noted for VIA KX133 chipset motherboards before > the KT133 chipset was released. The KT7 motherboard uses the VIA KT133 > chipset which is very similar to the KX133 chipset. The following comments > therefore apply to the KT7 and KT7-RAID motherboards. > > For audio cards that use A3D audio chip there appears to be an > incompatibility that causes the KX133 system to deadlock when system traffic > is heavy. The reason for this is that the A3D chip issues one memory read > request cycle to the North Bridge and expects a grant within 4 mico-sec of > latency time. If PCI TRDY# is not asserted after 4 mico-sec, the A3D > hardware will de-assert the FRAME# and REQ# to terminate the operation. > However, the A3D audio software driver cannot acknowledge the termination > and continues waiting for hardware response. Hence the system hangs. This > issue will only occur during heavy system traffic when the North Bridge > cannot grant access to A3D audio chip within the 4 mico-sec latency time. > There is no known work-around for this issue, and the principal advice is > not to use A3D-based sound cards with KX133 based motherboards. Source: VIA > Application note Serial #AN137 Date 07/05/00. > -------------------------------------------------------------------------- -- > ----------------------------- > So there are documented nails in your electronic road., you simply have > not hit them yet. Most reports from folks who have hit the nails say it > only happens when the machine is REALLY working hard. 'PW" said he has an > Athlon. That Athlon makes it VERY likely that he has VIA chips on his MB. > Areal Vortex sound cards are very common so he just might have one of them > too. If he does he just might have hit the nails you have, so far, missed. > Just checking. > Me? I have the KT7/SB Live combination I mentioned. Lots of nails there > too. > Sounds like PW is only a few days from tossing NASCAR 4 out the window > in disgust. Before we lose him I am just standing here yelling "WAIT A > MINUTE!!!! If you got one of "these" and one of "those" then maby your > trouble is "this" and you need to .........." > I'm Fishing. > > "Dave Henrie" <[email hidden]> wrote in message > news:zHGq6.549120$[email hidden]... > > > > Thanks Joe...I think I'll point out...I just re-installed N4 after an > > upgrade to a tbird > > with a via chipset and an Aureal sound card. Everything worked for my > first > > two hours online...no lockups...I should mention, No NVIDIA product has > > graced > > this system....even with win98se's supposed problems with via > chipset...no > > problemo...via 4n1 v4.28 mobo drivers 3dfx V5. with the November 20th > > drivers... > > 40 to 60 fps...worked very well. (kt133a) chipset...Microstar mobo. > > dave henrie > > > > >

OK, I looked up "Athlon GigaByte GA-IX". I found a "GA-7IX" (note the added "7") but nothing on "GA-IX" (without the "7"). Everything I write here will be assuming you mistakenly left out the "7" and you really have the "GA-7IX". There are a few links below that should work. If they dont let me know. "pw" <[email hidden]> wrote in message news:98gc4h$mnn$[email hidden]... >>Possible trouble 1 > How do I get into my bios to disable the 4X and operate into 2X (or > check if it's in 4X)? If you have the board I think you do your board does not support AGP 4X so disregard. Your board has an "AMD 750 Chipset" consisting of an "AMD 751 PCI/AGP Controler" and an "AMD 756 PCI/ISA/IDE Controler". This gives you AGP 1X and 2X *BUT* go here: http://www.geforcefaq.com/#hw:gef:troub:inst:athlon Under "What's all this with the GeForce and the Athlon?" It seems like early AMD 750 chipsets had trouble with GForce cards and AGP 2X. Because of that trouble NiVida drivers "switched off" 2X everytime they saw an AMD chipset. This means you are probably operating at 1X. That "new version" of the 750 they talk about in the above link is likely the implementation of sometihng called "Super Bypass" that you can read about here: http://www6.tomshardware.com/mainboard/99q4/991229/ The gist of this seems to be that early 750 chipsets were faulty and the "Super Bypass" did not work. Later production runs corrected the fault but there was never any recall of the bad chips. I dont know if there is any way to tell which ones you have but it seems this "shut-off" of 2X that NiVida built into the GForce drivers cant tell either so it shuts off 2X even if you have the "good" chips. Back at the first link (gforcefaq) a little lower down there is a link to some regisrty hacks that can turn on 2X. You may or may not want to try them depending on what chipset (good or bad) you think you have. You may also want to forget the whole 1X/2X thing. What I read here seems to say that the performance diffrence between 1X and 2X is not all that great so it may not be worth hasseling with. In any case my take on all of this is that you are NOW operating in AGP 1X because the Herc/NiVida drivers you installed saw your AMD chips and put you in 1X. 1X should be as stable as you can get. Until we get NASCAR 4 running it is probably a good idea leave it at 1X and not mess with that 2X registry hack.

Quoted text (9 lines)

> > > > >Possible trouble 2 > > I note you are using DX8a. What drivers are you using on your herc? > > Hercules 6.35 > > > If > >they are Herc drivers or any of the "Official Release Drivers" from

NiVidia > >they are NOT optimized for DX8. DX8 optimized release drivers do notexist. > > Thanks for that info! > > >If you want DX8 optimized drivers you have to use Beta drivers. I started > >using the 10.50 today and it seems fine so far. Another one that issupposed > >to be pretty good is the 756. You can get either (and a lot more besides)at

Quoted text (7 lines)

> >"reactorcritical.com" or "the-ctrl-alt-del.com" > > Whose drivers are these, btw? They won't screw up other games, will > they? I just played a couple of other games (not sims :-) for hours > last night w/o a single crash. But, one of them was "UnDying" and it > requires Direct X 8 (and the reason I installed it) so it looks like > that backs up your point about DX8.

These are all "Beta Reference Drivers" The term "Beta" roughly means something that has not been throughly tested and blessed as an "Official Release". This does not mean they are faulty, just not tested. These drivers are written by NiVida but because they are not tested and blessed they are not supposed to be available but there are always new ones being leaked. If you call Herc or NiVida about them they will not help you because you are not supposed to have them in the first place. But the fact remains that these betas are often better than the "official" drivers. You will run into beta drivers that screw things up and you will run into beta drivers that are PERFECT. Only way to really tell which is which on your machine is to install them and test them yourself. Nice thing is that they are easy to uninstall if they do screw things up. The 1050 and the 756 are the two latest "leaks". The 1050 seems fine, I havent tried the 756 yet. You may want to try others if these dont work out. Speaking of drivers, go here: http://www4.gigabyte.com.tw/support/d_amd.htm These are the latest drivers for your MoBoard. If you havent already done so get them all and install them. If you already have these versions and want to try something else go here: http://www.amd.com/products/cpg/bin/ These are AMD drivers straight from AMD like the reference drivers are straight from NiVida. There are some newer versions there than the ones on the Gigabite site but looking at the readme's there dosent seem be be anything that addresses faults for YOUR chipset so I dont they will be any better for you than the ones on Gigabite. Still, here they are. That leaves your soundcard drivers. You dont say what soundcard you have but whatever it is go up on the site and get whatever the latest driver is. It may just be your sound card and NOT your GForce that is locking you up. > >Possible trouble 3 > > I note you have a T-Bird. Me too. What motherboard do you have andwhat > >sound card. If you have an Abit KT series and a Soundblaster Live youMIGHT > >have trouble. If you have any board with VIA KX133 or KT133 chipsets and > >any Areal Vortex based soundcard you DO have trouble. Forget these. Let me know how things work out with the above. There are other things we can try but before that I need to know a couple of things. The questions are below the line. If you dont have any idea what I am asking dont worry about it. Just say "HUH!?!?!?" and I will let you know how to get the answers. ====================================================================== A couple of questions. If you have the moboard I think you have (the one with the "7") I may have some BIOS tweaks for you later. I downloaded your manual from the Gigabite site but it will take me a bit to go over. You asked how to get into the BIOS earlier. I take it you have never been in there. If so: Has ANYONE EVER been in there and changed anything? If someone has been in the BIOS has there been any changes to the machine since they were in there (New card, new OS, more or different ram and such)? What version of BIOS do you have? Have you ever flashed a bios?

Hi Joe! You are too kind! Any way, here are some answers for you: > OK, I looked up "Athlon GigaByte GA-IX". I found a "GA-7IX" (note the >added "7") but nothing on "GA-IX" (without the "7"). Everything I write >here will be assuming you mistakenly left out the "7" and you really have >the "GA-7IX". There are a few links below that should work. If they dont let >me know. > Yes, my manual is incorrect. I noticed upon boot up that I have a GA-7IX.F1

Quoted text (11 lines)

> >Speaking of drivers, go here: > >http://www4.gigabyte.com.tw/support/d_amd.htm > >These are the latest drivers for your MoBoard. If you havent already done so >get them all and install them. If you already have these versions and want >to try something else go here: > >http://www.amd.com/products/cpg/bin/

I can not tell which file(s) listed there are for me (am using Win98SE). > >That leaves your soundcard drivers. You dont say what soundcard you have but >whatever it is go up on the site and get whatever the latest driver is. It >may just be your sound card and NOT your GForce that is locking you up. > That thought had occurred to me. I was there a few days ago and think I couldn't find any drivers, or I got frustrated with the site. I have a Diamond Monster Sound MX300 (I believe it's an Aureal based card). I am running N4 with the DirectSound option w/o the 3D sound checked. Max Voices/Sounds are set at the minimun (8). > A couple of questions. If you have the moboard I think you have (the one >with the "7") I may have some BIOS tweaks for you later. I downloaded your >manual from the Gigabite site but it will take me a bit to go over. You >asked how to get into the BIOS earlier. I take it you have never been in >there. If so: I pressed the DEL key while booting and got into the bios menu. >Has ANYONE EVER been in there and changed anything? >If someone has been in the BIOS has there been any changes to the machine >since they were in there (New card, new OS, more or different ram and such)? Since my PC arrived about a year and a few months ago I have: Swapped the original Hercules Prophet 256 GeForce 1 for a Hercules GeForce 2 MX. Then, just recently, swapped it for a Hercules GTS 64 MB DDR Pro card. Went from Direct X 7.0 to Direct X 7.0a, then to Direct X 8.0a. Tried the NVidia 6.50 drivers (this is when I had the MX card) but I couldn't set my desktop to above 1024x768 (I followed the readme exactly). Finally was able to get the Herc 6.35 drivers reinstalled. When I got my Pro card, I uninstalled all of the present drivers and then installed the 6.35 Herc drivers (I wrote down how I did it, if you are interested). Then, I installed DX8.0a a couple of days later. >What version of BIOS do you have? I am guessing Award Software V1.0A as it flies by on the screen when I boot up (couldn't find a version number in the bios menu). >Have you ever flashed a bios? > Nope! Heard of the procedure though! Too scared to try it and don't really know how :-) By the way, how come I can qualify and start a race (I think it eventually crashes after a few laps) in D3D at 1024x768 32-bit color in a track that starts with a T (from Alabama) but when I run it in OpenGL at either 16-bit or 32-bit color, without changing any settings but my desktop colors, it locks up (sound goes on though) at the same exact place in the track?? Thanks!!!! -paul

I forgot one more change I made Joe! Rats! I added another 128 megs of RAM. I originally had PC-100 SD-RAM (128MB). But the matching (spec to spec, and approved by my PC maker: Falcon-NW) 128MB was PC-133 SD-RAM. One stick, just like my original. Norton Systemworks reports it as OK. And I uninstalled B-17, ran Norton's disk doctor and speed disk before installing N4. -paul

"pw" <[email hidden]> wrote in message news:98hlvl$nrr$[email hidden]... > Yes, my manual is incorrect. I noticed upon boot up that I have a > GA-7IX.F1 OK, I have version "PCB Rev. 1.0 / First Edition (Aug.18, 1999)" of your manual here. To make sure we are all looking at the same stuff download the manual I have: Here: http://www1.giga-byte.com/support/user_pdf/7ix_10_1_aug1899.pdf This is an Adobe file. If you have Adobe reader installed the manual should start loading as soon as you click the link. If you dont know what Adobe Reader is let me know. > > I can not tell which file(s) listed there are for me (am using > Win98SE). I took a quick look at the files on the AMD site. There are versions there that are newer than the files on the Gigabyte site but the readme's attatched to those newer versions seem to indicate that they were written to implement a chipset you dont have and dont make any changes for the chipset you do have. This means that they likely will do you no harm but will also do you no good. In the mean time it is certain that the drivers on the Gigabyte site are for your chipset and will fit your OS. They may be duplicates of drivers you already have but if so they will do no harm. If they are updates they may do you good. There is nothing to lose. Get all three. http://www4.gigabyte.com.tw/support/d_amd.htm >I have a Diamond Monster Sound MX300 (I believe it's an Aureal based > card). I am running N4 with the DirectSound option w/o the 3D sound > checked. Max Voices/Sounds are set at the minimun (8) I used to have that card, I bought it along with a Diamond video card. The frustration you had with Diamond support site is the main reason I sold it. It was a good card but Diamond NEVER even attempted to provided any support. If you had dug further into the site you would have found a file that Diamond laughingly called an "update". It is not. It is simply same 102 BETA driver they have had posted there since shortly after they released the card over two years ago. They have simply renamed it from 102 beta to 102 release. I know this because bought the card when it first hit the streets and I have used this driver in the past, both when they called it a "beta" and after when they changed the name to "release". Diamond is lying. That 102 driver is still a BETA. Aureal wrote MANY updates to these drivers but Diamond simply ignored them. Over a year of constant requests for support only got me a constant string of promises, NONE of which were ever performed. I was only one of many Diamond customers who got the same treatment. What was true of sound card support was equally true of video card support. Diamond was, without doubt, the absolute worst company I had ever dealt with or heard of regarding support and I have seen nothing since then from any source to show me they have improved one bit. Posting an accurate and full description of my opinion of Diamond here would probably get me arrested for distributing pornography so let me just say "Diamond Sucks" and let it go at that. Having vented I feel better so now lets get back to your drivers. After having heard the above rant if you still want the (piece-of-crap) Diamond (sucks) "update" (so-called) it is here: http://www.diamondmm.com/default.asp?menu=support&submenu=Legacy_Audio&item= drivers&product=Monster_Sound_MX300 Ok, Everything in the previous rant above applies to Diamond but NOT to Aureal. Aureal was a damn good company that produced excelent Vortex 2 technology with 3D sound that beat the hell out of Creative's EAX. What killed Aureal was the fact that EAX was simpler and cheaper to write into a program than Vortex. Vortex sounded a LOT better but EAX sounded "good enough". So: "Cheap and Good Enough EAX" won over "More Expensive but Better Vortex". Damn shame but there it is. The MX-300 is an "Aureal Vortex 2" reference design that Diamond simply licensed, copied and put the MX-300 name on. Diamond did not have one damn thing to do with the card's design so it is more accurate to say your card is an "Aureal VORTEX 2" card while forgetting "Diamond" or "MX-300" any other such cuss words you may find engraved on the card. Be thankful for this for it is the reason you have a good sound card. There is, of course, a "but".... Aureal was a good company that supported the Vortex 2 as much as they could right up to the time they went broke and were bought out by Creative. Creative is doing nothing to support VORTEX 2, preferring instead to sit on the Aureal technology and promote their own EAX. Another damn shame. What this means to you is that your Aureal Vortex 2 card is starving to death for lack of updated drivers. As good as the your hardware is you need to start planning for a new one. In the mean time are Aureal fan sites out there with the drivers you are looking for. You need reference drivers for an Aureal Vortex 2 (AU 8830) http://vortexofsound.com/ http://vortexofsound.com/drivers/drv_v29x.htm

Quoted text (9 lines)

> >What version of BIOS do you have? > > I am guessing Award Software V1.0A as it flies by on the screen when I > boot up (couldn't find a version number in the bios menu). > > Have you ever flashed a bios? > > Nope! Heard of the procedure though! Too scared to try it and don't > really know how :-)

Decision time! There is reason to be scared! Flashing a BIOS is not complex or difficult but an error is potentially fatal. Because of this potential for disaster flasing a BIOS is not something you should do unless you need to. A new BIOS is not necessarily better than an old BIOS; depending on what the new BIOS fixes. Example: If a new BIOS fixes some trouble with "XYZ Scanners" but you dont use "XYZ Scanners" why flash the new BIOS when you gain nothing? But if the new BIOS DOES fix something you have then you might consider flashing. Go Here: http://www3.gigabyte.com.tw/support/swamd.htm#link7ix This is the Gigabyte BIOS page. The listing for your GA-7IX should be visible. Based on what you have written you have one of two possible BIOS versions. You said that your boot screen says you have a "GA-7IX.F1" That "F1" would seem to be the BIOS version. You also said "I am guessing Award Software V1.0A That also may be your BIOS version. Either way you have a decision to make. Take a look at "F1 (Oct.12, 1999)" Number 1: "Patch New AMD 700MHZ cpu unstable problem". If your BIOS is V1.0A you have this trouble but even if you have "F1" already you are not all that much better off. Take a look at a couple of the others BIOS in that list and note two things: Find the file "F2 (Mar.03, 2000) and look at Number 12. "Enable Super Bypass , when the following condition are met: 1)IG Revision C5 or later 2)IG Trcd is 2 or 1 cycle". Remenber "Super Bypass" from my last post? If you have that early broken chipset you dont have "Super Bypass". If you have the later "fixed" chipset you STILL dont have "Super Bypass" because your BIOS dosent know what it is. This BIOS will turn Super Bypass on for you *IF* you have the fixed chipset. Now find F3 (Apr.06, 2000) and look at Number 1: " Fix Performance is poor due to wrong programming L2 cache table" I have found nothing that says what this "poor performance" is but it *may* be contributing to your crashes. You will also see an "F4 Beta" BIOS up there that corrects a problem with a GA-MG400 Gigabyte Video Card. Since you dont have the card you dont have the problem so dont worry about this one. But the "F3" just **might** fix a few things for you. ESPECIALY if you have version 1.0a of the BIOS and not the "F1". If you decide to flash at all you only have to do it once because the "F3" has all the fixes of the previous versions. I have flashed numerous times, all successfully. The operation is not hard. Not really all that much more complex than changing a driver. What is scary about flashing is that if a mistake is made you end up with a very expensive paper weight. Sometimes this can be fixed with a "Blind Bios Install Disk" (I can tell you what that is and how to make one) but usually it can be fixed only with another BIOS chip from Gigabyte (mabe $30+/-). Below the line is the instructions from Gigabyte. Read them over and think about it. The first time I tried it I was sweating bullets but afterwards I wondered what all the fuss was about. Take it one step at a time and check off the steps as you do them. If you follow the instructions EXACTLY I believe you will be fine. Paper weights are made by people who get cocky and rush through. Still, there IS a risk to YOUR machine. Decision time. ============================================================================ ===== Gigabyte Technology Flash BIOS Update and Recovery Procedures BIOS Update Procedure: 1. Make a boot disk. Go to the DOS command prompt in MS-DOS or Windows 9x and, with an available floppy disk in "A", type (without the quotes), "format A: /s" That will format the floppy and transfer the needed system files to it. NOTES: A. This procedure will erase any prior data on that floppy, so please proceed accordingly. B. Typically four files will be transferred, only COMMAND.COM being visible when running a simple directory listing. C. Please leave the diskette UN-write protected for the balance of this procedure. 2. Download the BIOS upgrade file (zip file) and awdflash.exe utility from a Gigabyte web site to a temp directory on your hard drive, or directly to the floppy you made in step 1.. NOTE: The BIOS zip file may or may not include the required flash utility file. If it does not, that file is also available, separately, near the top of each applicable download page on the web site. 3. Extract both files to the boot floppy you made in step 1 using an extraction utility such as pkunzip or winzip. NOTE: Both of these utilities are available on many shareware download pages like www.shareware.com. 4. Reboot the system to the DOS command prompt using the boot diskette you just made. 5. At the DOS command prompt, type (without quotes), "awdflash filename.xxx", where filename.xxx is the file name of the BIOS file you just extracted. Hit enter. 6. Your first option, in sequence, will be to save the old BIOS. We recommend that you do that in case, for whatever reason, you decide you don't wish to use the new version once it is installed. NOTES: A. If you decide to save the old BIOS, PLEASE make sure you do NOT save it to the same file name as the new BIOS - if you use the same BIOS name the old file will be written over the new file with NO warning prompt. A simple file name to save the old BIOS to is OLDBIOS.BIN. B. If you do NOT decide to save the old BIOS, PLEASE at least write down the version number of the old BIOS and store that information with your important computer documents. Enter N (for "no") and skip to step 9. 7. To save the old BIOS, hit Y (for "yes") 8. Enter a name for the OLD BIOS file and hit enter. NOTE: PLEASE be sure you do NOT save the old BIOS file to the same file name as the new BIOS - if you use the same BIOS name, the old file will write over the new BIOS file WITHOUT a warning prompt. A simple file name for saving the old BIOS to is OLDBIOS.BIN. 9. Your second option, in sequence, will be whether you want to flash your BIOS. Enter Y (for "yes"). NOTE: This is the critical step. Once you kit the enter key, do NOT touch the keyboard, the reset button, or power switch while the flashing is in progress. There will be bar progressing across the screen while the flashing is progressing. 10. When the flashing process is complete, you will be asked to reset or power off the system. Remove the floppy diskette from the floppy drive and either hit the reset button or the power button. 11. Reboot the system and note that the BIOS version on the initial boot-up screen has changed to the new BIOS version. Your BIOS upgrade is now complete. Recovering Your Old BIOS: 1. Assuming you have the floppy made during the upgrade procedure noted above, boot the system with that diskette in the floppy drive. If you do not have floppy made during the upgrade procedure noted above, you will need to repeat steps 1 though 3 (above) for the version of the BIOS you wish to recover to. 2. Complete steps 4, 5, 6B, 9, 10, and 11 (above) substituting the name of the BIOS you wish to recover for the upgrade BIOS at step 5. � 2000 Gigabyte Technology Co., Ltd. All rights reserved. ============================================================================ ======

Quoted text (24 lines)

> > By the way, how come I can qualify and start a race (I think it > eventually crashes after a few laps) in D3D at 1024x768 32-bit color > in a track that starts with a T (from Alabama) but when I run it in > OpenGL at either 16-bit or 32-bit color, without changing any settings > but my desktop colors, it locks up (sound goes on though) at the same > exact place in the track?? > > Thanks!!!! > > -paul > > >I forgot one more change I made Joe! Rats! > >I added another 128 megs of RAM. I originally had PC-100 SD-RAM >(128MB). But the matching (spec to spec, and approved by my PC maker: >Falcon-NW) 128MB was PC-133 SD-RAM. One stick, just like my original. > >Norton Systemworks reports it as OK. And I uninstalled B-17, ran >Norton's disk doctor and speed disk before installing N4. > > >-paul

Hi Joe,

Quoted text (8 lines)

> >OK, I have version "PCB Rev. 1.0 / First Edition (Aug.18, 1999)" of your >manual here. To make sure we are all looking at the same stuff download the >manual I have: >Here: > >http://www1.giga-byte.com/support/user_pdf/7ix_10_1_aug1899.pdf >

I am downloading it now. It is taking forever. I guess IE is downloading it. Weird that IE is doing the download this time.

Quoted text (7 lines)

>. They may be >duplicates of drivers you already have but if so they will do no harm. If >they are updates they may do you good. There is nothing to lose. Get all >three. > >http://www4.gigabyte.com.tw/support/d_amd.htm >

Well, I downloaded the three last night (amd_agp, amd756_ide, amd756_irq). You are sure installing these won't mess up my system, right? :-) >It is not. It is simply same 102 >BETA driver they have had posted there since shortly after they released the >card over two years ago. They have simply renamed it from 102 beta to 102 I saw that 14 meg download today. I like the card. Falcon-NW says there is no need for me to get the SB Live card (not much of a difference in quality, and I think there are compatibility issues with AMD systems).

Quoted text (8 lines)

> > You need reference drivers for an Aureal Vortex 2 (AU 8830) > >http://vortexofsound.com/ > >http://vortexofsound.com/drivers/drv_v29x.htm > >

I have the Aureal drivers installed. I will check and see if the above links are for something newer. > Decision time! There is reason to be scared! Flashing a BIOS is not >complex or difficult but an error is potentially fatal. Because of this >potential for disaster flasing a BIOS is not something you should do unless Thanks for the link. I am going to pass on flashing my BIOS for now. I also heard it was dangerous. I use this PC for my business and can't afford to not be able to use it every day. BTW, I just tried N4 in OpenGL 16-bit again and it locked up again in qualifying on that track. I rebooted, switched to D3D 32-bit color and got past qualifying, started a race but had to quit after a few laps. Won't be too positive about that, as a friend was playing it the other day and it CTD during the 20th lap. Weird. Thanks again! -paul

Quoted text (8 lines)

> > You need reference drivers for an Aureal Vortex 2 (AU 8830) > >http://vortexofsound.com/ > >http://vortexofsound.com/drivers/drv_v29x.htm > >

Can't get them Joe - the link for the full install goes to: DOWNLOAD ERROR! The file you attempted to download was linked illegally from another site. We apologize for the incovenience, and encourage you to email the webmaster of the offending site to notify them that they should be linking in accordance with our policies. Please feel free to explore our site, and download the file from here. Thank you. -pw

Quoted text (7 lines)

> > You need reference drivers for an Aureal Vortex 2 (AU 8830) > >http://vortexofsound.com/ > >http://vortexofsound.com/drivers/drv_v29x.htm >

I have those drivers installed already (4.06.3048) -pw

"pw" <[email hidden]> wrote in message news:98jlh9$fmu$[email hidden]... > Hi Joe, > > > > >OK, I have version "PCB Rev. 1.0 / First Edition (Aug.18, 1999)" of your > >manual here. To make sure we are all looking at the same stuff downloadthe

Quoted text (20 lines)

> >manual I have: > >Here: > > > >http://www1.giga-byte.com/support/user_pdf/7ix_10_1_aug1899.pdf > > > > I am downloading it now. It is taking forever. I guess IE is > downloading it. Weird that IE is doing the download this time. > > >. They may be > >duplicates of drivers you already have but if so they will do no harm. If > >they are updates they may do you good. There is nothing to lose. Get all > >three. > > > >http://www4.gigabyte.com.tw/support/d_amd.htm > > > > Well, I downloaded the three last night (amd_agp, amd756_ide, > amd756_irq). You are sure installing these won't mess up my system, > right? :-)

As certain as I can be given the info on the Gigsbyte site. Those numbers on the files correspond to the two chips that make up your 750 chipset and it says in the readme that they are for Win9x. All of that means they are for your MB with your OS. > > >It is not. It is simply same 102 > >BETA driver they have had posted there since shortly after they releasedthe > >card over two years ago. They have simply renamed it from 102 beta to 102 > > I saw that 14 meg download today. I like the card. Falcon-NW says > there is no need for me to get the SB Live card (not much of a > difference in quality, and I think there are compatibility issues with > AMD systems). There is a compatability issue between SB Live and my ABit K7-Raid mb too. That Aureal IS a nice board and it will likely do fine as long as you stay with Win98se.

Quoted text (17 lines)

> > > > > You need reference drivers for an Aureal Vortex 2 (AU 8830) > > > >http://vortexofsound.com/ > > > >http://vortexofsound.com/drivers/drv_v29x.htm > > > > > > I have the Aureal drivers installed. I will check and see if the above > links are for something newer. > > > > Decision time! There is reason to be scared! Flashing a BIOS is not > >complex or difficult but an error is potentially fatal. Because of this > >potential for disaster flasing a BIOS is not something you should do

unless > > Thanks for the link. I am going to pass on flashing my BIOS for now. > I also heard it was dangerous. I use this PC for my business and > can't afford to not be able to use it every day. Well, at least you know what new BIOS is available and what it does. One thing though, it is a good idea to download those BIOS and save them on a Floppy. That way you know you have them if you change your mind.

Quoted text (13 lines)

> > BTW, I just tried N4 in OpenGL 16-bit again and it locked up again in > qualifying on that track. I rebooted, switched to D3D 32-bit color > and got past qualifying, started a race but had to quit after a few > laps. Won't be too positive about that, as a friend was playing it > the other day and it CTD during the 20th lap. > > Weird. > > Thanks again! > > -paul >

Hey Joe!

Quoted text (11 lines)

>> >> Well, I downloaded the three last night (amd_agp, amd756_ide, >> amd756_irq). You are sure installing these won't mess up my system, >> right? :-) > >As certain as I can be given the info on the Gigsbyte site. Those numbers on >the files correspond to the two chips that make up your 750 chipset and it >says in the readme that they are for Win9x. All of that means they are for >your MB with your OS. > >>

The amd_agp contains two files. One for A2K(agp2k510.exe) and something called mini_port471.exe which is for Win9X. But all but one (I believe - perhaps all, will have to recheck) are dated prior to when my PC was built. It was manufactured about the 1st week of November 2000. >There is a compatability issue between SB Live and my ABit K7-Raid mb too. >That Aureal IS a nice board and it will likely do fine as long as you stay >with Win98se. Okay - am planning on it! > > Well, at least you know what new BIOS is available and what it does. One >thing though, it is a good idea to download those BIOS and save them on a >Floppy. That way you know you have them if you change your mind. > Got it. Thanks! Disregard my optimistic stuff below. I redid the race and it CTD at about 15 laps into it. <s> Thanks so much Joe! Let me know if you have any other ideas. I see someone else is crashing in N4, but that post stated he is getting the blue screen of death, which I am not. -paul

Quoted text (14 lines)

>> >> BTW, I just tried N4 in OpenGL 16-bit again and it locked up again in >> qualifying on that track. I rebooted, switched to D3D 32-bit color >> and got past qualifying, started a race but had to quit after a few >> laps. Won't be too positive about that, as a friend was playing it >> the other day and it CTD during the 20th lap. >> >> Weird. >> >> Thanks again! >> >> -paul >> >

Guess what Joe? . . . . . . . I finished all 29 laps of one race and 30 of 40 in Daytona (was getting late, had to quit - and a nasty crash (of the good kind!)). You know what I did? I know you may shake your head over this one though :-) I changed my desktop resolution (and colors, of course) to the same as in the game. I tried it at 1280x960 and 1024x768 in D3D and my frame rates seemed the same regardless. Haven't tried OpenGL yet though. I still think there is something wrong in that department. I realize I am still being optimistic, but even so, at least I can play it for a while - and it didn't crash in about an hour of play last night! Thank you so much for kind and enthusiastic help! You are one knowledgeable person! Do you mind if I ask what you do for a living? Thanks again. Regards, -paul