Nascar 2 Ate My Internet Explorer

Yes, it did. Ok, pre Nascar 2 installation, MSIE3.0 worked fine on both of my machines. After installing N2, of course I did nothing but play the thing ( go figure ). This morning prior to leaving for work, I try to access the Intergraph Site to look for the BIOS upgrades to the Reactor ( they aren't there, BTW ), but guess what? MSIE no longer worked. The window opened up, but it did not fill in, and the only options that still worked were CLOSE, Internet Mail and News. Ok, so I figure I screwed something up. ( Happens all the time ). So I move over to my daughters machine and try to run MSIE there... Same thing. Dang! Done got a virus. So I set about cleaning it up. Several hours later..... No virus found.. Start calling around, but none of my friends ( yes, I have a few ) ever had that happen to them. No help there. So I install and remove MSIE several times on both computers. Still no workie. Ok, what the heck, someone may be having the same problem. So I come here, wade through the ' it's here, it's here' messages and guess what? Someone else had the same problem. Blames Nascar 2. What????? Ok, light comes on. Worked before, right? Doesn't now, right? That degree in rocket science is starting to pay off now!! Ok, another of my friends is a Nascar junkie too, so I call him up, make him stop playing, and ask if his MSIE still works. Guess what? Doesn't. Same problem as me. And not only that, his Win95 AOL software no longer functions. So, anyone else tried to run MSIE after installing Nascar 2? Any help will be appreciated. Thanks in advance. Robert

Let me guess, you also see some of your wallpaper in your browser window too, right? It did the same thing to mine but I thought it was a different program that I had installed. But anyway, here's how I fixed it. I did an uninstall from add/remove programs. Then I loaded IE2.0 from my AWE32 CD. After that I got on the internet and got version 3.01 again. I don't know if you have 2.0 but that's how I solved my dilema. Eric Franzen

Hi, I was reading a message about the same problem just a couple of minutes ago, and the person said that they installed Internet Explorer 3.01 and it worked fine. I don't have Nascar 2 yet, I'am a new PC user and have not even played NASCAR 1! Hopefully the game will come to this part of Canada next week, so I can try the game! Hope this helps, John -- Winners never quit, quiters never win

D.A. That I am, I was installing 3.0, instead of 3.01. After re-installing 3.01 everything is a.o.k. Still, did none of the beta testers have this problem? Is this the first time that it happened to anyone? Did I miss a disclaimer somewhere? Anyhow.... All is well again, have put the gun back in the closet.

I am having the same problem, I have reloaded MSIE twice already. I am also having a problem with my 3-D Expression card, get a message that IniVBE does not yet support relocated IO whith the ATI Mach64 board chipsets. I will try and move the jumper to disable the relocated IO, and see if that works. When I load Nascar2 (works fine with Nascar1) the middle of the screen(windshield) just blinks off and on and won't respond to my pedals or wheel. Any ideas would be of great help. Thanks Wayne

Well me and my buddy Rob Johnson do have something in common after all.:) My IE3.01 was corrupted after installing N2 the other day also. I reinstalled and have had no further problems.

Yes, I had the exact same problem !!! OK, so I fixed it by reinstalling MSIE3.0.. My Question is, What else did it***up.. certainly, not just

Quoted text (7 lines)

>> So I install and remove MSIE several times on both computers. Still no >D.A. That I am, I was installing 3.0, instead of 3.01. After >re-installing 3.01 everything is a.o.k. Still, did none of the beta >testers have this problem? Is this the first time that it happened to >anyone? Did I miss a disclaimer somewhere? Anyhow.... All is well >again, have put the gun back in the closet.

Maybe Netscape and Sierra are in cahoots???? <grin!> personally, never being able to run IE again would still be fine by me :)

Download and install (or re-install if you already had it) IE 3.01. That worked for me. -- Emory University Graduate School of Arts & Sciences Nascar Setups Page: http://userwww.service.emory.edu/~ebusch/

It only happens when you run that univibe.exe or something or other inside windows 95... JCSpeed

Yep, me too. Finally. What's up with the beta testers? All you guys use Netscape or ***jack or something? How did that biggie get by? :-) Oh, since we know how to fix it, do we know what files were being replaced/overwritten to cause the problem in the first place? Just curious.

Some things are more important than work. ;) Funny story! I don't have N2 yet, but as a guess, I'd say the networking software for NASCAR's online racing has knocked out your current browser. I heard that MSIE would do the same to Compuserve's browser when MSIE first came out. Turn-about is fair play, I guess. ;) I believe MSIE was installing its own Winsock and pre-empting the existing version (but don't quote me on that), so try looking into that. Good luck! Pick one or more: Model Rockets (competition-NERCB) / PCs (even Atari!) / Papyrus ICR-ICR2-NCR / Who needs a life when you have multiple non-lives?

Did you install TEN? That screws the Windows 95 TP/ICP scrip. -- Chuck Stuart - Mesquite TX USA RaceTime utility program for Nascar1/Indycar2. http://www.metronet.com/~cstuart/

> Yes, I had the exact same problem !!! OK, so I fixed it by reinstalling > MSIE3.0.. My Question is, What else did it***up.. certainly, not just You are most likely correct. The IE3.0 problem is probably due to the registry being overwritten by the install program. Usually the best way to fix registry problems is to reinstall. If someone has regedit experience they could look for it. I would, except I promised not to load the game (or T2 pedals & joyswitch) until xmas :-) A small consession.

God, isn't that the truth! I guess this is true, as you aren't the first to suggest this, but I didn't install the networking software for the online racing. At least I didn't install TEN. Seems more like a .DLL or a .OVL or .RSC file type problem. MSIE would run, but it would not fill in any of the menus, or the center of the window. Just took whatever was on the desktop and stuck it in the MSIE window. I don't remember the Compuserve thing, as I was using Netscape back then. I was trying out AOL with it's unlimited time plan, but I dislike the whole idea of AOL. Don't have a reason, but I don't guess I really need one. Any way, Nascar took it out also. Re-installing MSIE 3.01 fixed it though. Oh, and the humor, or at least the attempt, was so I didn't freak out and start flaming everyone involved. Heck, it even calmed me down. Besides, it isn't their fault that they released a product that rendered 30% of their user base's internet browsers inoperable! :-) BTW : the 30% number is based on a interview with Mr. Bill Gates where he said that MSIE had about a 30% share of the browser market. Any other facts, or non-facts, were made up by me.

Actually, that's two things. 1: Redneck 2: Nascar hates us :-) Robert

Yep, fixed it. Kinda glad I have been wasting al that harddrive space by keeping all those ZIP files off the internet. Now I just need to toss all those old versions..... Thanks,

> Yes, I had the exact same problem !!! OK, so I fixed it by reinstalling > MSIE3.0.. My Question is, What else did it***up.. certainly, not just Actually, 3.0 would not fix mine. Had to install 3.01 .. Anyway, I know for sure that it also took out the Win95 software for AOL. But re-installing 3.01 fixed this problem too.

I had the same problem. When i installed Nascar2 it took out my explorer, news and mail readers. Re-installed 3.01 and back online. > > Yes, I had the exact same problem !!! OK, so I fixed it by reinstalling > > MSIE3.0.. My Question is, What else did it***up.. certainly, not just > Actually, 3.0 would not fix mine. Had to install 3.01 .. Anyway, I > know for sure that it also took out the Win95 software for AOL. But > re-installing 3.01 fixed this problem too.

No, I didn't install TEN. ( Shouldn't is be called $29.95 ) :-) It screwed it up anyway.

I had the same problem with mine. I deleted N2 and reinstalled MSIE 3.01 and Explorer worked just fine. I did a dos only install on N2 as C:\sierra\nascar2 and everything worked fine. I only difference is you have to make your own shortcut to Nascar2.exe and set the icon. One thing is better this way: no b.s. in the sierra directory taking of hard drive space needlessly . Homepage http://user.mc.net/~n9ldx

Here's what I did to avoid the bug. First, I backed up my C: drive, just in case MSIE 3.0 got zapped. Second, I shutdown Win95 to DOS mode. Then I used the DOS install for NASCAR2, full install (all 100 meg). NASCAR works fine (all three modes: N2, N2REND, and RENDDMA). MSIE and all of my other Internet programs (MS Mail and Forte Free Agent) seem to be working fine. I don't know if I'll have trouble if I decide to install the TEN networking at a later date, but Sierra should come up with a fix by the time NRO starts up. ;) Pick one or more: Model Rockets (competition-NERCB) / PCs (even Atari!) / Papyrus ICR-ICR2-NCR / Who needs a life when you have multiple non-lives?

You finally found something that will kill MSIE and you're complaining?!?!?!? <VBG> Dave (davids) Sparks Late Night League http://www.sequoia-dev.com/Hawaii/latenite.html

>> Download and install (or re-install if you already had it) IE 3.01. >> That worked for me. >Yep, me too. Finally. What's up with the beta testers? All you guys use >Netscape or ***jack or something? How did that biggie get by? :-) Nope. I use MSIE 2.0 at home on those rare occasions when I surf from home. Also, I don't think I ever tried the Windows install. I always boot straight to DOS when I'm running NASCAR. Dave (davids) Sparks Late Night League http://www.sequoia-dev.com/Hawaii/latenite.html

Yep, sure am. Happen to like the whole MSIE package. News, Mail, and browser all in one and at a great price. Besides, it is my job to hose up my computer, not Sierras!! :-)

Ok, I understand that you guys were just there to test the Nascar game, but surely someone had the task of checking out the installation program? It was tested, right? Or were we all just one big beta test? :-)

>Did you install TEN? That screws the Windows 95 TP/ICP scrip. I did install TEN, and had the same problem. Just re-installed 3.01, and all is well again. Gary Hamann Fremont, Ca "Piece a Cake"

The QA department is supposed to do the exhaustive testing, Robert, not the beta testers. Look at the credit screen, there were at least a half-dozen people at Papyrus who got payed to play with it 8 hours a day (and probably a lot more than that!) Our job was to play user and give feedback on what we liked and didn't like and to report any bugs we found. Is it my fault that I didn't test it with every possible piece of software that exists? I have a life too, you know. <g> Dave (davids) Sparks Late Night League http://www.sequoia-dev.com/Hawaii/latenite.html

Show me, in the first paragraph, where I mentioned beta testers? All I was I was implying was that I found it hard to belive that NO ONE tested the Windows install feature of Nascar 2. Think it works, Bob? Sure it does, Bill. Great job, Jill. Ship it, Will. etc...etc... You are a beta tester. You are not entitled to a life. You are personally responsible for all the bugs in Nascar 1/2/3/4/5, not to mention world hunger. I could actually agree with your ' every piece of software ' logic, if we we talking about some obscure little disk util or something, but not a mainstream browser like MSIE 3.x, or if you were the only tester. This should have been checked before the end user got to it.

>I could actually agree with your ' every piece of software ' logic, if we >we talking about some obscure little disk util or something, but not a >mainstream browser like MSIE 3.x, or if you were the only tester. This >should have been checked before the end user got to it. What I don't understand is why it's always everyone else's responsibility to ensure that anything Microsoft puts out, will work with their software? Microsoft has a good history of changing things around. It's quite possible that they *did* test it, but your version and your specific setup wasn't tested. Didn't I see some posts where some people installed Nascar 2 and NO problems with MSIE3? You can't blame that on Sierra. If you have anyone to blame, it's Microsoft for being "non-standard" with their stuff. How come Netscape didn't have a problem? Or any other programs, just Microsoft? I'd tend to think the culprit was the program that got messed up, personally.

> What I don't understand is why it's always everyone else's > responsibility to ensure that anything Microsoft puts out, will work > with their software? Microsoft has a good history of changing things > around. It's quite possible that they *did* test it, but your version > and your specific setup wasn't tested. Didn't I see some posts where > some people installed Nascar 2 and NO problems with MSIE3? No, you did not see ANY posts where this happened. If you installed N2 from window with MSIE 3.0 or higher on your system, it wiped outthe browser. Period. I can't understand why people, let's say people like you, seem to find fault with everything MS puts out. And it wasn't only MSIE that was affected. I don't know for sure, but I belive David Sparks said that it didn't affect his MSIE 2.0. Well, sorry, I like the newer one. I didn't try Netscape, so I don't know if it worked or not. And yes, I can blame it on Sierra. Actually, I can blame it on you if I like. But since you don't think it is the creator of the setups fault, there is probably no way I can get you to take the blame. MSIE and Win95 have been out a considerable time longer than N2. Those that come after must make sure that they work with what's out there. Or create something that replaces it, not trashes it.

: You are a beta tester. You are not entitled to a life. You are personally : responsible for all the bugs in Nascar 1/2/3/4/5, not to mention world : hunger. : : I could actually agree with your ' every piece of software ' logic, if we : we talking about some obscure little disk util or something, but not a : mainstream browser like MSIE 3.x, or if you were the only tester. This : should have been checked before the end user got to it. Hey, these guys only have the title of a beta-tester. They do that "testing" on their own time with their own equipment. Papy/Sierra gave them nothing except "beta" software and big fat NDA to sign. The quality assurance procedures should've got any blantant bugs like you mention. You're assuming that the problem is strictly Internet Explorer... it may not be. On the systems they tested it may have worked just fine, even with IE installed. I don't know that for sure, but it's a possibility that IE is not entirely the problem... maybe it's the VRML extension, or DirectX drivers, or NetMeeting, or ComicChat, or etc. Could be any of those add-ons for IE... who knows. My point is simply that it is entirely possible for this to have slipped through the QA... AND that there is no way that the "free beta-testers" could be held responsible at all. IMO, David Sparks, Terry Adams, Brian Tate, and the rest of the N2 "free beta-testing" gang did a helluva service for all of us. bill -- --------------------------------------------------------------------------- Sky diving... take the dare... -- ------------------------------ Bill Pogue Deep In The Heart Of The South

>I didn't try Netscape, so I don't know if it worked or not. And yes, I can >blame it on Sierra. Actually, I can blame it on you if I like. But since >you don't think it is the creator of the setups fault, there is probably no >way I can get you to take the blame. hehehe, yeah, I guess you *could* blame it on me. But it'd be the same effect. I'm trying be objective about the whole thing. Microsoft has a habit of their programs working great with "their programs" but usually not with anyone else's stuff. It usually turns out that "everyone else has to re-do everything." the amazing thing is, usually "all those companies with screwed up products" had little or NO trouble with any other software out there. But since Microsoft writes the OS, they seem to "use the boundaries" a little closer than other companies. There isn't anything "personal" in that. Netscape 3.x and MSIE 3.x came out about the same time. I haven't heard any reports of it. Sure, you could blame it on Sierra. But if you really look at this intelligently, I think you'll at least see what I'm talking about. fact: netscape uses telecommunications in Windows95 fact: MSIE 3 does the same thing so if they use the same files, how come one gets messed up and the other doesn't? it sounds like MSIE is hogging something it doesn't like to "share" with other apps. I'm sure you could blame THAT on Sierra too.

It's not the NASCAR2 install that's eating your MSIE, it's the TEN install routine that's full of bugs...Papyrus had assumed that all was well (after all, it's been on-line for some time), and went ahead and placed it in the sim. Since Papyrus can't jump in and fix it, it'll be upto TEN to do something. In the meantime, if you have AOL 3.0, Compu$erve 3.01, or MSN, then simply reinstall one of these to restore your IP connection. :) Best Regards, Marc J. Nelson Sim Racing News

> : You are a beta tester. You are not entitled to a life. You are personally > : responsible for all the bugs in Nascar 1/2/3/4/5, not to mention world > : hunger. > : If you cannot see the intended humour in this statement, please forgive. I wasn't aware of the seriousness level that was here in this group. Perhaps your part of the " Deep south " doesn't belive in humour? Sorry, mine does. Gee, you mean it's just a title they have, not a job? Duh.... Also, sorry you missed my attempt at humor. Perhaps it was one of those " A & B " converstaions? I assume nothing. You just somehow missed the mentions of it messing up the AOL internet frontend as well. This is highly unlikely, unless they did a DOS install, and I have yet to see anyone say that the Win install did not mess up their 3.x version of IE. Have you noted anyone saying so? Well sorry, but I thought that the 'testers' were supposed to test the product. Even if they are doing it for free, I just can't imagine that the NDA only said that they couldn't tell us about it, but it also holds them to their agreement to test it. I would think that the primary job of a BETA tester would be to try to crash the software, and tell how they did it so that they could prevent it's happening again. And of course to report oh now the software interacts with the public in general. And with the MSIE bug, it didn't take any trying at all. Here is my theory: The beta guys / gals tested Nascar 2 in all it's glory. Drove the ***out of it, and found a whole slew of bugs. Papy fixed the ' quick fix ' bugs, left the minor ones in so the product could ship. Then someone else wrote an install program, and stuck it on the CD with Nascar 2. Then they shipped it to the disk producers, or whoever. The beta guys never got a chance to test the actual, shipped product before we did. So they got the new, install related bugs just like we did. And if not, oh well, stuff happens. Too bad the bugs they reported weren't corrected before shipment.

This is not to disagrre with the experts, or anything, but I DID NOT install TEN on my system. On either system, in fact. So, how did the bug bite me? This isn't a flame, I really want to know.

Ok, I will try, will probably won't get as close as you are. Gee, it is my OS, so I should write it to work with your programs? Answer: If yours were out there first, I should try to maintain compatabilty as long as the NEWER product is hampered by compromises to the older ones. On the machine I am typing this, for example,I am wasting 8 megs of memory for 16 bit support in Win95. They wrote the software, published the boundaries, and if the software vendors don's stay within those boundaries, whose fault is it? If MS doesn't stay within them, sue their ass. I will try to be intelligent, but it will be a chore. :-) I don't have Netscape, so I don't know. I do not know what files are written to my disk, or where they were written during the Win95 N2 install. Ten should not come into it, because I did not instal it. It is my belief that it installed a .DLL somewhere the wrote over a .DLL that IE used. Everytime I install a new version of IE, it overwrites a bunch of stuff, else there wouldn't be any point of upgrading, right? I see where you are coming from, but I just can't fault MS in this case. They upgrade their software, like everyone else, and if another company's install program replaces a file that is needed by one of the MS apps, at least they should check to see if it is a newer version before doing so. But then again, it could be something different. Since no one has officially stated why the install wipes out IE, we are left to speculate. Is this a fact? I haven't heard. Fact: After a Win95 install of N2, I cannot access the internet from my Win95 AOL frontend software. Fact: ***jack works. Why? I don't know. No, that one is definately your fault. :-)

contributed:

Quoted text (13 lines)

>> It's not the NASCAR2 install that's eating your MSIE, it's the TEN >> install routine that's full of bugs...Papyrus had assumed that all >> was well (after all, it's been on-line for some time), and went ahead >> and placed it in the sim. Since Papyrus can't jump in and fix it, >> it'll be upto TEN to do something. In the meantime, if you have >> AOL 3.0, Compu$erve 3.01, or MSN, then simply reinstall one of >> these to restore your IP connection. :) >This is not to disagrre with the experts, or anything, but I DID NOT >install TEN on my system. On either system, in fact. So, how did the bug >bite me? >This isn't a flame, I really want to know.

It shouldn't be taken as a flame but who knows? I had (have) the same trouble with N2 eating IE. Mine just keeps going on though. Tried the update through Sierra thing and all I got was an update failed and it won't let me do it again without uninstalling and doing it all over. BTW - I never installed TEN in any of the installations and I've done several on my system trying to get it right. I would guess that it's the Sierra auto-update feature that's causing the trouble. The IP settings were never corrupted either. They all stayed there but IE went by the wayside. *------------------------------------------* Life is a tragedy for those who feel, and a comedy for those who think! *------------------------------------------* Joe II

>Ok, I will try, will probably won't get as close as you are. hey, that's ok. I was just trying to get ya'll to see things from "both sides". not saying it's Sierra OR MS's fault, just that it's easy to pick the first target in sight. From my programming experience, I've found that sometimes the obvious target isn't necessarily the correct one (actually, MOST of the time - hehehe) well, that's a little bit more specific... AOL frontend software... is that what the others have as well, or are they using Windows95 DUN? LOL!

>Gee, you mean it's just a title they have, not a job? Duh.... Dividends in N2 beta software. :) Simply reinstall the AOL "frontend", and all should be fine. N2 doesn't mess with anything it's not supposed to, it's the TEN software that makes an attempt to re-do the IP scripts. OK...Consder me as the first to confirm that the normal Win95 install (without TEN) does not***with your IP scripts. Plain-Jane Win95 install worked fine for me without a hitch...I tested it nearly a dozen times (relesed version) after wipe-deleting the Sierra dir. Only when I reinstalled TEN (at any time) that my IP get goofed-up. :( That's pretty much all we did as beta-testers - tried to get N2 to crash. Some of us even wrote our own dump routines, and Papyrus provided us with several. This way, all we had to do (in the event of a crash) is submit the *.DMP file along with the condition that caused the crash, as well as anything else we found. Hmmm...What I do recall is Adam, Charlie, and the rest of the Papyrus gang giving up their weekends and working late into the night. I know, because I called Mike Newhall at 2:30 am PST (just to leave a message for him for the next morning) and he was there!!...WORKING!! We all worked pretty hard to help Papy get a solid product out for you guys. I only see a few minor bugs, and one's which won't keep you from having a good time. :) BTW, Papyrus could have actually gotten the game out a couple days earlier, but due to the death of NASCAR pace car driver Elmo Langley, they decided to hold it up just to put in their condolences to his family. That showed real class, and my thanks go to the folks at Papyrus. Glad to know that they enjoy this sport as much as I. :) Is your Hawaii name "Mushroom"? ;) Having a wonderful time at 'dega...wish you were here. ;) Best Regards, Marc J. Nelson Sim Racing News Rendition Development Group & Ex-Beta Tester for a very additicting sim!! :)

>This is not to disagrre with the experts, or anything, but I DID NOT >install TEN on my system. On either system, in fact. So, how did the bug >bite me? >This isn't a flame, I really want to know. I know it's not a flame, and I'm glad you guys are posting. :) I'm not sure why you're having this problem. After I recieved the release version of the game, I installed it (fresh) to see what kind of monkey- business was going on (I had suspected TEN only 2-days prior). After installing the game nearly a dozen times, I found that there didn't seem to be a problem with a normal Win95 install (less TEN). I then went to give TEN a try, and no sooner it was installed that it had its clutches on my IP script...OUCH!! I wipe-deleted the directory, reinstalled CIS, and then tried it again with the same results. Then the same procedure, only without TEN and all was fine. I talked to Papyrus yesterday, and they too had identified TEN as the probable cause. As soo as I know, I'll post here and on my site. :) Best Regards, Marc J. Nelson Sim Racing News

Kissing up, eh BIll? I'm still gonna whoop your tail in head-to-head. <g> Besides, it wasn't free testing, we get a free copy of N2 out of it. At least that's what I heard, even though I haven't seen mine yet. So don't ask me any questions about what's in the manual, 'cause I haven't seen it yet. Dave (davids) Sparks Late Night League http://www.sequoia-dev.com/Hawaii/latenite.html

It was not the TEN install routine that wiped out MSIE. It was the AutoUpdate program that wiped out MSIE. AutoUpdate was Sierra's program, and the AutoUpdate program has not been online for some time.

>It was not the TEN install routine that wiped out MSIE. It was the >AutoUpdate program that wiped out MSIE. AutoUpdate was Sierra's program, >and the AutoUpdate program has not been online for some time. Perhaps you're right...The info I had posted had come straight from Papyrus - hence refering to *assuming all was well*. Thanks for the update. :) Best Regards, Marc J. Nelson Sim Racing News - USA http://members.aol.com/simracing/