I currently have Win95 and when I run Nascar or Indycar racing they
both cut out and write lots of stuff on the screen really fast so I
can't see it and then restarts and goes back to Windows 95. Any Help?
:-)
Robert Knauber
> I currently have Win95 and when I run Nascar or Indycar racing they
> both cut out and write lots of stuff on the screen really fast so I
> can't see it and then restarts and goes back to Windows 95. Any Help?
> :-)
> Robert Knauber
I'm by no means an expert here, but I can report what I've experienced with
Windows '95 (this is from memory, as I'm at work and am not in front of my
PC). Since IndyCar is a DOS program, Windows tries to execute it in a DOS
window (possibly full screen, possibly not), using an environment
controlled by the parameters you've established in the "Properties". To
see these properties, click the right mouse button on the application's
icon (or Shortcut icon), and select "Properties". In one of the tabbed
sections (I forget which), you can deselect "Close Window On Exit". This
will allow you to see the error message that you are getting.
Of course, the error message you are getting is one that tells you,
effectively, that IndyCar has executed an illegal instruction (or something
similar -- probably because it uses a third party protected mode scheme),
and that you'll need to run IndyCar in MSDOS mode. MSDOS mode can be
selected through the "Properties" menus.
Running in MSDOS mode means that Windows will shut itself down and reboot
in DOS, where the application will be executed in a "clean" MSDOS
environment. After you quit the application, the machine will reboot
itself in Win '95. Note that all this means the application cannot be run
in the Windows multitasking environment, and all your Windows apps will be
shut down while you execute the app (no big deal, since this is probably
what you were doing with the app under Windows 3.1).
Note that DOS has changed as well with this release of Windows, and you may
experience problems running the app in this environment, too, as I noted in
a previous post to this newsgroup. I still haven't found the solution to
the keyboard control problem I reported here over the weekend.
Good luck, and I hope I haven't supplied you with info that is too far off
base.
Gordon
--
Gordon D. Wishon
Office of Information Technology
Georgia Institute of Technology
Atlanta, Georgia 30332-0700


































