rec.autos.simulators

BTW, I am also not a big fan of the install routine, all those runtime
files could cause some people problems and they certainly waste space on
my hard drive.

Matt Howell

I had this same problem, along with .DLL and incorrect file errors.
I did the install again, double checking my steps, and the third time
I tried the install (with complete reinstalls of N2 and patches) it
worked.  Nothing different, the same steps, and it worked.

My comment on the patch:

Excellent work on the patch, notable improvement on N2, but I got
something to say about the install routines --

Stay the hell out of my Windows system directory!!  You can mess with
anything you want in the actual program directory (folders for the
WIN95 groupies) but you may NOT mess with my Windows or
Windows/System files, they are not yours to stick your random files
into!  At LEAST ask permission! How do you know what I have installed
or what you may wreck by dumping a bunch of .DLL and the like
in there?  

Unless you are going to test and debug the install routines on many
systems configured differently, stick with simple, easy to modify
batch file install programs. You don't know my system, you don't know
anything about my system configuration. I do.  If I can view the
installation steps, in detail, I can modify them if necessary.

As to the troubleshooting section: here's the names of some files,
move them around until it works (about 22 files or so) does not cut
it.  And no uninstall program.  Plenty of disclaimer, I can see why.

As I said, excellent work on the patch, the install program leaves
a LOT to be desired.

Robin

On the subject of installation and system files, please remember that at
the moment TPTCC is in beta test. The install procedure is being changed to
remove the need for so many run-time files.

The cause of most of the problems with the installation seem to be caused
by a chain of problems to do with Microsoft's own problems with date stamps
and version stamps of OLE DLLs. The files being copied are those that
Microsoft provide.  With respect, a batch file would not really help as you
would have to check the version of every single DLL, and this type of
problem can occur with any VB program installation. As I hinted above the
solution seems to be to stop VB using OLE controls during installation and
hence remove the need for so many run-time files.

Regards

Dave Noonan

 hay dave

I can't seem to get hings to work.  first I got the dll error message so
I removed all the files
on the list and re-ran the runtime file and the instulation file

then when I ran the tptcc.exe file I got an error massege
"the file 'TYPELIB.DLL' is out of date.  this program requires a newer
version"

I don't see how this is possible seeing as I used the find files or
folders thing to elimate all
the TYPELIB.DLL files before I did this.  In other words Im using the
TYPELIB.DLL file
that the runtime.exe file gave me so how could it possibly be out of
date?

I have DELL 200 MMX  32 ram      NOT a pro  or  pro II

I have tried installing this over and over, removing the TYPELIB.DLL
file many times.

please help
-thanx-

If you have any experience using Win 95 explorer (file manager), try using the
instructions for installling the Pits touring car patch manually, without the
installer.  Directions are posted at the Pits web site.  I had dll problems
too, but their instructions worked.