Windows ME & Nascar Heat - Two Problems

It would seem that Nascar Heat and Windows ME do not get along. I've discovered two show-stoppers: 1. I have 256MB of RAM. If I set the AGP Aperture to 128MB, which it should be set at, Nascar Heat crashes at startup before you ever get to the Irwin/Petty screen. Set to 64MB does not cause a problem. 2. Nascar Heat de-stabilizes something in the system that causes VCACHE Blue-Screens Of Death if you don't restart after playing Heat. Looks like we need that patch quicker than we thought :) This is a clean ME install, btw... I don't believe in overlay-upgrades. -Larry

On Sun, 17 Sep 2000 02:41:38 GMT, "Larry" <[email hidden]> wrote: >It would seem that Nascar Heat and Windows ME do not get along. I have both and they work fine. >1. I have 256MB of RAM. If I set the AGP Aperture to 128MB, which it >should be set at, Where did you get the idea that your AGP aperture should be half of your installed ram? >Nascar Heat crashes at startup before you ever get to the >Irwin/Petty screen. Set to 64MB does not cause a problem. What kind of video card are you using? >2. Nascar Heat de-stabilizes something in the system that causes VCACHE >Blue-Screens Of Death if you don't restart after playing Heat. Not here it doesn't. I am running ME and I have 256 MEG of ram, too. NH has no negative effect on my system. >Looks like we need that patch quicker than we thought :) A patch isn't going to fix your misconfigured system. The same game works great on my 256 MEG system running Windows ME, so it's not the game. >This is a clean ME install, btw... I don't believe in overlay-upgrades. Same here. ~daxe

Just about everyone and everywhere recommends you set the AGP Aperture to 1/2 of your installed RAM. Never heard otherwise from anywhere. -Larry "daxe" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (34 lines)

> On Sun, 17 Sep 2000 02:41:38 GMT, "Larry" <[email hidden]> wrote: > > >It would seem that Nascar Heat and Windows ME do not get along. > > I have both and they work fine. > > >1. I have 256MB of RAM. If I set the AGP Aperture to 128MB, which it > >should be set at, > > Where did you get the idea that your AGP aperture should be half of > your installed ram? > > >Nascar Heat crashes at startup before you ever get to the > >Irwin/Petty screen. Set to 64MB does not cause a problem. > > What kind of video card are you using? > > >2. Nascar Heat de-stabilizes something in the system that causes VCACHE > >Blue-Screens Of Death if you don't restart after playing Heat. > > Not here it doesn't. I am running ME and I have 256 MEG of ram, too. > NH has no negative effect on my system. > > >Looks like we need that patch quicker than we thought :) > > A patch isn't going to fix your misconfigured system. The same game > works great on my 256 MEG system running Windows ME, so it's not the > game. > > >This is a clean ME install, btw... I don't believe in overlay-upgrades. > > Same here. > > ~daxe

Why do you assume my system is "Mis-Configured"? I assure you it's not. -Larry "daxe" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (34 lines)

> On Sun, 17 Sep 2000 02:41:38 GMT, "Larry" <[email hidden]> wrote: > > >It would seem that Nascar Heat and Windows ME do not get along. > > I have both and they work fine. > > >1. I have 256MB of RAM. If I set the AGP Aperture to 128MB, which it > >should be set at, > > Where did you get the idea that your AGP aperture should be half of > your installed ram? > > >Nascar Heat crashes at startup before you ever get to the > >Irwin/Petty screen. Set to 64MB does not cause a problem. > > What kind of video card are you using? > > >2. Nascar Heat de-stabilizes something in the system that causes VCACHE > >Blue-Screens Of Death if you don't restart after playing Heat. > > Not here it doesn't. I am running ME and I have 256 MEG of ram, too. > NH has no negative effect on my system. > > >Looks like we need that patch quicker than we thought :) > > A patch isn't going to fix your misconfigured system. The same game > works great on my 256 MEG system running Windows ME, so it's not the > game. > > >This is a clean ME install, btw... I don't believe in overlay-upgrades. > > Same here. > > ~daxe

On Sun, 17 Sep 2000 04:24:42 GMT, "Larry" <[email hidden]> wrote: >Why do you assume my system is "Mis-Configured"? > >I assure you it's not. > >-Larry So, because a program runs on my system with the same OS, but doesn't run on yours, you figure yours DOESN'T have a problem? Ok..whatever you say.... ~daxe

On Sun, 17 Sep 2000 04:23:50 GMT, "Larry" <[email hidden]> wrote: >Just about everyone and everywhere recommends you set the AGP Aperture to >1/2 of your installed RAM. > >Never heard otherwise from anywhere. > Perhaps you might like to visit here: http://support.intel.com/support/technologies/graphics/agp/aperture2.htm nowhere in here does it *recommend* 1/2 your installed ram as the aperture setting. The default (which may be varied, of course) is 64 meg. Strangely enough, you don't have a problem running NH with that aperture setting, but when you change it and make it higher, it crashes. I call that 'misconfiguration.' When the default setting works and you change it so it doesn't work anymore, that's 'misconfiguration' in my book. All I am complaining about is your assertion that NH needs patching because it won't run with that setting. There are lots of settings on your computer that you could change to prevent the program from running correctly, none of which point to the program as the problem. ~daxe

I run windows ME and Nascar Heat with no problems whatsoever. Maybe you have other problems with your system like a flaky piece of hardware or a BIOS setting wrong. Oh, and I am also running on a fresh install of WinME. Vintook "Larry" <[email hidden]> wrote in message news:CbWw5.11188$[email hidden]... > It would seem that Nascar Heat and Windows ME do not get along. I've > discovered two show-stoppers: > > 1. I have 256MB of RAM. If I set the AGP Aperture to 128MB, which it > should be set at, Nascar Heat crashes at startup before you ever get tothe

Quoted text (12 lines)

> Irwin/Petty screen. Set to 64MB does not cause a problem. > > 2. Nascar Heat de-stabilizes something in the system that causes VCACHE > Blue-Screens Of Death if you don't restart after playing Heat. > > Looks like we need that patch quicker than we thought :) > > This is a clean ME install, btw... I don't believe in overlay-upgrades. > > -Larry > >

I too have been running WinME and Nascar Heat for some time, and have had zero problems. (Although I only have 192meg of RAM and my AGP aperature set to 64) "Vintook" <[email hidden]> wrote in message news:AN3x5.102844$[email hidden]... > I run windows ME and Nascar Heat with no problems whatsoever. Maybe youhave

Quoted text (28 lines)

> other problems with your system like a flaky piece of hardware or a BIOS > setting wrong. Oh, and I am also running on a fresh install of WinME. > > Vintook > > "Larry" <[email hidden]> wrote in message > news:CbWw5.11188$[email hidden]... > > It would seem that Nascar Heat and Windows ME do not get along. I've > > discovered two show-stoppers: > > > > 1. I have 256MB of RAM. If I set the AGP Aperture to 128MB, which it > > should be set at, Nascar Heat crashes at startup before you ever get to > the > > Irwin/Petty screen. Set to 64MB does not cause a problem. > > > > 2. Nascar Heat de-stabilizes something in the system that causes VCACHE > > Blue-Screens Of Death if you don't restart after playing Heat. > > > > Looks like we need that patch quicker than we thought :) > > > > This is a clean ME install, btw... I don't believe in overlay-upgrades. > > > > -Larry > > > > > > >

Nice point daxe. I too am amazed that so many people are quick to blame the game instead of their config. "No one else is having this problem so it's OBVIOUSLY the game, patch this sh*t!" -- Joe Marques Please remove "NO SPAM" to e-mail me. "daxe" <[email hidden]> wrote in message news:[email hidden]... > On Sun, 17 Sep 2000 04:23:50 GMT, "Larry" <[email hidden]> wrote: > > >Just about everyone and everywhere recommends you set the AGP Aperture to > >1/2 of your installed RAM. > > > >Never heard otherwise from anywhere. > > > > > Perhaps you might like to visit here: > > http://support.intel.com/support/technologies/graphics/agp/aperture2.htm > > nowhere in here does it *recommend* 1/2 your installed ram as the > aperture setting. The default (which may be varied, of course) is 64 > meg. Strangely enough, you don't have a problem running NH with that > aperture setting, but when you change it and make it higher, it > crashes. I call that 'misconfiguration.' When the default setting > works and you change it so it doesn't work anymore, that's > 'misconfiguration' in my book. > > All I am complaining about is your assertion that NH needs patching > because it won't run with that setting. There are lots of settings on > your computer that you could change to prevent the program from > running correctly, none of which point to the program as the problem. > > ~daxe

Actualy, I was going to say the same to you. It works on yours, so my system is _obviously_ misconfigured, right? It's not. Everything was installed clean and fresh. 3 Times. I have the exact same symptoms each time. I'm wondering if it isn't the MS SideWinder Software, though. I'm getting odd switch and stick 'glitches' that I don't get when I boot to my Win98 partition. I have a ghost shifting my gears and changing my heads-up display in Nascar 3 too :) He even slams the brakes on at the apex of a corner sometimes! Again, only happens under the clean ME install, doesn't happen if I boot from the Win98 partition. -Larry "daxe" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (14 lines)

> On Sun, 17 Sep 2000 04:24:42 GMT, "Larry" <[email hidden]> wrote: > > >Why do you assume my system is "Mis-Configured"? > > > >I assure you it's not. > > > >-Larry > > So, because a program runs on my system with the same OS, but doesn't > run on yours, you figure yours DOESN'T have a problem? > > Ok..whatever you say.... > > ~daxe

Ok. -Larry "daxe" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (27 lines)

> On Sun, 17 Sep 2000 04:23:50 GMT, "Larry" <[email hidden]> wrote: > > >Just about everyone and everywhere recommends you set the AGP Aperture to > >1/2 of your installed RAM. > > > >Never heard otherwise from anywhere. > > > > > Perhaps you might like to visit here: > > http://support.intel.com/support/technologies/graphics/agp/aperture2.htm > > nowhere in here does it *recommend* 1/2 your installed ram as the > aperture setting. The default (which may be varied, of course) is 64 > meg. Strangely enough, you don't have a problem running NH with that > aperture setting, but when you change it and make it higher, it > crashes. I call that 'misconfiguration.' When the default setting > works and you change it so it doesn't work anymore, that's > 'misconfiguration' in my book. > > All I am complaining about is your assertion that NH needs patching > because it won't run with that setting. There are lots of settings on > your computer that you could change to prevent the program from > running correctly, none of which point to the program as the problem. > > ~daxe

Maybe we can ask Ed to test NH with ME and let us know what to expect or not to expect. That's probably the best solution :) We don't all have the exact same configuration so none of us are _wrong_. -larry "DoubleU" <[email hidden]> wrote in message news:H05x5.2642$[email hidden]... > I too have been running WinME and Nascar Heat for some time, and have had > zero problems. (Although I only have 192meg of RAM and my AGP aperatureset

Quoted text (18 lines)

> to 64) > > "Vintook" <[email hidden]> wrote in message > news:AN3x5.102844$[email hidden]... > > I run windows ME and Nascar Heat with no problems whatsoever. Maybe you > have > > other problems with your system like a flaky piece of hardware or a BIOS > > setting wrong. Oh, and I am also running on a fresh install of WinME. > > > > Vintook > > > > "Larry" <[email hidden]> wrote in message > > news:CbWw5.11188$[email hidden]... > > > It would seem that Nascar Heat and Windows ME do not get along. I've > > > discovered two show-stoppers: > > > > > > 1. I have 256MB of RAM. If I set the AGP Aperture to 128MB, which it > > > should be set at, Nascar Heat crashes at startup before you ever get

to > > the > > > Irwin/Petty screen. Set to 64MB does not cause a problem. > > > > > > 2. Nascar Heat de-stabilizes something in the system that causesVCACHE > > > Blue-Screens Of Death if you don't restart after playing Heat. > > > > > > Looks like we need that patch quicker than we thought :) > > > > > > This is a clean ME install, btw... I don't believe inoverlay-upgrades.

Quoted text (9 lines)

> > > > > > -Larry > > > > > > > > > > > > > >

On Sun, 17 Sep 2000 22:07:25 GMT, "Larry" <[email hidden]> wrote: >Actualy, I was going to say the same to you. > >It works on yours, so my system is _obviously_ misconfigured, right? > >It's not. This is a pretty simple concept, Larry. A system configured to run the game is correctly configured because the game runs. A system configured so the game doesn't run is misconfigured as far as that game goes. Should you have to change you computer just for that game? Probably not. But so far nobody but YOU is having a problem running the game in ME, so if it isn't the game, and it's not ME, that leaves one other place to look: your computer is misconfigured to run the game. Is that so hard to grasp? I'm not suggesting for moment that you don't know what you're doing or can't set up a computer correctly, but I think the reality is that your computer needs a patch to run the game, not vice-versa. ~daxe

In article <eIXw5.11729$[email hidden]>, "Larry" <[email hidden]> writes: >Why do you assume my system is "Mis-Configured"? > >I assure you it's not. > >-Larry Because if he's running the same game on the same OS just fine, it *ain't* the game... Do you have any virus checkers running? Those will screw up a program like ANYTHING... Eldred -- Tiger Stadium R.I.P. 1912-1999 Homepage - http://www.umich.edu/~epickett GPL hcp. +49.67 Never argue with an idiot. He brings you down to his level, then beats you with experience... Remove SPAM-OFF to reply.