rec.autos.simulators

I'm trying to get GPLAPTIM to work. I downloaded it and all seemed well
when I had it installed (admittedly only for a few runs) with "Loadhigh
gplaptim.com" in the autoexec.bat.

I then also tried wclaunch which apparently doesn't want/need this line.
Now it won't work, dropping out of FIGP.BAT after failing to load a
gplaptim.log file. I've given it one - empty - but nothing. I've
restored the TSR to the autoexec.bat - no luck. What's gone wrong?

I'd like to get this established as I'm interested in LF3000.....but
this is essential. What have I done wrong?

Cheers!

---
 * RM 1.3 U0414 * Cannot close BLOUSE.ZIP - replace floppies and retry.

One thing which consistently kills GP.EXE with no error message is a lack of
memory. You probably want at least 600k free conventional memory if you
start loading TSRs like GPLAPTIM, more like 620 if you want GPLAPTIM
and GPPERF and SSPLITTIM and CCPIT.

Nothing. Microsoft made all the mistakes that make things like this
hard to do. MS-DOS, the Thing that Should Not Be.

Chisa
-- Gizmo van der HOF
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Launchpad is an experimental internet BBS. The views of its users do not
necessarily represent those of UNC-Chapel Hill, OIT, or the SysOps.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Why?  All you do is type INSTALL.  ;)

The only problems you will see is if you are not using MS-DOS, it will
not work with 4-DOS.

MM> > I'm trying to get GPLAPTIM to work. I downloaded it and all seemed
MM> well > when I had it installed (admittedly only for a few runs) with
MM> "Loadhigh > gplaptim.com" in the autoexec.bat.

MM> Do you have 1.05 of F1GP ? You need that...

I do.

It may be something to do with WCLAUNCH doing things like re-naming the
gplaptim.log to gplaptim.old. I've read the gplaptim.log file with the
windows package, and the dos one, kicked in on their own. But from
WCLAUNCH I get this failure to read the log file, followed by a drop to
DOS.

No good to me this.

Cheers!

---
 * RM 1.3 U0414 * Error - File not found. Fake it? [Y/N]

DG> One thing which consistently kills GP.EXE with no error message is a
DG> lack of memory. You probably want at least 600k free conventional
DG> memory if you start loading TSRs like GPLAPTIM, more like 620 if you
DG> want GPLAPTIM and GPPERF and SSPLITTIM and CCPIT.

I don't think memory is a problem - OS/2 session with 640k base [ B-) ]
but don't think OS/2 is the problem.

Well, if you can't use WCLAUNCH - maybe I can't either. Perhaps I'll go
your way.

Cheers!

---
 * RM 1.3 U0414 * Backup not found: (A)bort (R)etry (P)anic!

I don't know how this could have happened.  WCLAUNCH will not let you
***this up.

In WCLAUNCH, do the following:

 - Start it up  ;)
 - Select AI Editors
 - Select GPLAP
 - Select Enable
 - Select the log file button
 - Enter any log file name you want.  It is wise to use a RAM Drive.
 - Select Decompress To
 - Enter any name for the file
 - Select all of the options for GPLAP that you want to see in the lap chart.
 - Select Done

Then exit the program.  When WC is starting, make sure you see GPLAPTIM
Activated (or something like that).

Do the driving part.

Exit WC and the lap chart should be shown to you.

If you still get problems, make sure that your CONFIG.SYS file is setup
correctly.  It shows an example CONFIG.SYS in the installation portion of
the WCLAUNCH manual.

When I said WCLAUNCH will not let you***it up, I meant that even if
you never select the log file or decompress to file, default names are
given.  This is to ensure that a problem like this didn't occur.

And WCLAUNCH will only rename gplaptim.log to gplaptim.old if it
encounters the existing file.  For RAM Drive users, this file is gone
when you reboot your computer so WCLAUNCH will not name it to .old.  Same
goes for the decompress to file.

If all else fails, read the manual for WCLAUNCH.  It explains a few
things in there that you might find interesting.