Dec 142017
 
Windows utility checks for optimization of current setup.
File WINTUNE.ZIP from The Programmer’s Corner in
Category Windows 3.X Files
Windows utility checks for optimization of current setup.
File Name File Size Zip Size Zip Type
CMDIALOG.VB_ 10865 10385 deflated
GETINFO.DL_ 20007 19167 deflated
GRAPH.VB_ 41683 40353 deflated
GSW.EX_ 151678 146909 deflated
GSWDLL.DL_ 24408 23507 deflated
HELL16C.DL_ 204335 192406 deflated
README.TXT 8808 3899 deflated
SETUP.EXE 8480 4708 deflated
SETUP.INF 217 159 deflated
SETUP1.EX_ 19684 18964 deflated
SETUPKIT.DL_ 3657 3489 deflated
SS3D.VB_ 28022 27089 deflated
SS3D2.VB_ 44100 42474 deflated
SSIDXTAB.VB_ 39604 38155 deflated
TIPADW16.DL_ 19786 19028 deflated
VBRUN300.DL_ 276684 264316 deflated
VER.DL_ 6307 6058 deflated
WINTUNE.TR_ 3098 2923 deflated
WT20.EX_ 88496 83058 deflated
WTFAQ.HL_ 41946 40302 deflated
WTHELP.HL_ 206307 198597 deflated
WTTIP.HL_ 42642 41073 deflated

Download File WINTUNE.ZIP Here

Contents of the README.TXT file


README.TXT for Wintune 2.0 beta-2, build-5 (9/01/94) Full Install

*** HIGHLY CONFIDENTIAL (not 🙂 INFORMATION FOLLOWS! ***

PLEASE TAKE A FEW MINUTES NOW TO READ THRU
THESE RELEASE NOTES. THEY WILL SAVE YOU AND
US TIME AND TROUBLE LATER.

IN PARTICULAR, IT IS *VERY* IMPORTANT FOR YOU
TO SEND US YOUR RESULTS FROM THIS BETA RELEASE

THANK YOU! --The WINTUNE 2.0 Task Force

-----------------------------------------------------------------
TO INSTALL WINTUNE 2.0:

1) If you have a previous version of WINTUNE 1.5 or 2.0, please delete it,
and all related files. In particular, delete any .TRF files (the format
has changed), WT15.INI from \WINDOWS; and delete HELL16B.DLL,
GETINFO.DLL, TIPADW16.DLL and both SS3D*.VBX files from \WINDOWS\SYSTEM.
Then exit and restart Windows before running WINTUNE setup.

Also, please be aware that a separate UPGRADE .ZIP exists for moving
from Wintune 2.0 beta-1 to beta-2; we will also do this for the final
version--so don't download the full install if you don't have to!

However, since you already did...

2) run SETUP.EXE from File/Run in Progman, and follow the instructions.

3) when setup is complete, run Wintune. PLEASE FILL IN THE USER
INFORMATION FORM as completely as possible. This will make it possible
for us to correctly identify systems that are tested in the beta. In
particular, be sure to check the []Notebook/Laptop flag if you're running
Wintune on a small computer--this will help us generate the right tips.

4) Save your results using File/Save Present Results. Please type as
descriptive a name as possible into the resulting dialog, and click OK.
That will add your system to the WINTUNE.TRF database.

5) When you're finished running Wintune, please exit and restart Windows.

6) *PLEASE* Send your WINTUNE.TRF file to jruley on AOL.

-------------------------------------------------------------------
*** WFWG 3.11 USERS ***
If you use 32-bit file access (VCACHE), you may see some variation in
your disk test results. This is normal--VCACHE uses an aggressive
algorithm that delivers different results depending on how "clean" the
cache is. You can get consistent results from run-to-run by either:
(1) running Wintune (and the disk test) only when you first start Windows,
which will give you a more optimistic (high) result; or (2) running
the disk test several times, and saving only the last result--which will
give you a more conservative result.

---------------------------------------------------------------------
IF YOU HAVE A NON-STANDARD (3rd party) DISK CACHE, Or are running OS/2 or
NT, then you will need to manually set the disk cache size in the WINTUNE
command line. The syntax for this is:

C:\WT20\WINTUNE.EXE /Cnnnn

Where nnnn is your disk cache size in KB. Legal values are 16--16384. ie,
to manually set a 2MB cache size, use command-line switch:

C:\WT20\WINTUNE.EXE /C2048

If you don't set a cache size, you will get a simplified disk test with
results that may not be comparable to those from a test with a detected
cache size.

NT users: Since NT has a dynamic cache, our current test can never be
completely accurate, but as a practical matter, we're getting good results
on both NT 3.1 and 3.5 (in a 32MB memory configuration) with a manually set
cache size of 8MB. This appears to approximately match the performance
of NT's dynamic cache and the built-in Wi16 emulation subsystem.

OS/2 users: you should manually set Wintune's cache size to the same size
as that set in the DISKCACHE line in CONFIG.SYS (for FAT drives) or to that
set with CACHE= in the IFS=HPFS.IFS line of CONFIG.SYS. For instance, if you
are using OS/2 with a FAT drive, and DISKCACHE = 1024,L,W set:

C:\WT20\WINTUNE.EXE /C1024

If you are running HPFS and have IFS=C:\OS2\HPFS.IFS /CACHE:512 ...

Then set:

C:\WT20\WINTUNE.EXE /C512

-------------------------------------------------------------------
NEW FEATURES IN BETA-2:

* Support for user-set disk cache (see above)
* "Cached" disk test now at 20% of cache size (formerly 50%)
* Both Cached and Uncached disk details saved & reported
* Merge support for .TRF files
* Final User Interface
* CD-ROM Test Works
* Details displays updated
* Printing works (formatting isn't perfect yet)
* Video "loss of focus" problems are fixed
* Tips, Q&A and Help all Updated

-------------------------------------------------------------------
Known Bugs/Work-arounds/Bug-fixes:

- Disk results different from Wintune 1.0: The disk test in 2.0 is *very*
different than in 1.0, and we don't expect it to match. The 2.0
results (which are a weighted average of cached and un-cached
performance) are *far* more accurate than those in Wintune 1.0 We now
detect both WFWG 3.11 32-bit cache and SMARTDRV. If you are using Windows
NT, OS/2, or an undetected 3rd-party disk cache, you will need to set a
/C command-line switch as discussed above.

- Where's the Bird (in the video test)? As with Wintune 1.0, he's only
displayed in a Full Test (now set in Edit/Options). He's *supposed*
to be replaced by a better graphic--which I have not received from the art
department (hint! ... Hint! ... HINT!!!).

- Incorrect tips on NT systems. The OS and Windows version detection is
deliberately disabled on this version so that Wintune thinks it is running
under Windows 3.1 when on NT. This will be corrected before final release.

- GPFs:Wintune should never GPF in this release. If it does, please
run Dr. Watson, and send me the gory details

- WFWG/Windows 3.11 reported as version 3.1. We have code to correct this,
but it didn't get in this release--don't worry, it doesn't effect the
tips we're reccomending.

---------------------------------------------------------------------
Things to try:

1) Select a disk, click the "Start" button, and let it run to
completion. When Wintune displays the list of tips, double-click on one
to display our suggestions. You should get concrete instructions on how
to improve your system performance (if you don't, PLEASE let me know!)

2) Save your results (File/Save Present Results). Change to another disk
and repeat step 1. Go to the Comparisons tab, click "Choose comparitive
info", and pick your earlier data set for comparison. Look at the Disk
sub-tab to see how the different disks compare.

3) Go back "Home" and check out WINTUNE's tips. Try to follow them. Are
the instructions in our helpfile sufficient? Do the tips really help?

4) *FOR EXPERT USERS ONLY* Make sure your work is saved--and deliberately
hose your system. (Be sure to save copies of your AUTOEXEC.BAT and
CONFIG.SYS files first!) Comment out the SMARTDRIVE line in AUTOEXEC.BAT.
Set BUFFERS=99 in CONFIG.SYS. Go into the CMOS settings and disable
your CPU's internal cache. Turn off your "Turbo" switch. Then run WINTUNE.
Do we catch the problems?

---------------------------------------------------------------------------- ----
***If you find a bug: ***

1) save your results

2) go to details/all, copy all text

3) Send me a mail message (my e-mail addresses are below). Detail what's
wrong. Follow that with the text copied in (2), and attach your .TRF file.


-------------------------------------------------------------------
*HELP*US*HELP*YOU* !!!!

We've gone almost as far as we can running Wintune in-house
at WinMag. To go the next step, we need feedback from *YOU*:

1) If you find a bug, tell us. DON'T ASSUME WE ALREADY KNOW
ABOUT IT--we'd rather hear ten people tell us about a bug than miss it! Please
report bugs in the Wintune 2.0 Beta topic in the WinMag forum on AOL.

2) Send us a .TRF file with your results (File/Save Present Results) You can
e-mail to jruley on AOL, or to [email protected] Please annotate your
results as meaningfully as you can, using the User Information dialog displayed
on startup (and available thru File/User Information) *and* in the description
line you fill out when you save a results set. We will use this information to
distinguish .TRFs for different systems.

3) After tuning your system, send us your TRF file *again*. Please be sure to
annotate the "tuned" result set using the description line. If you'd like to
comment on Wintune, use the "Other Information" line in File/User Information.

Send .TRF files by AOL e-mail to jruley. Please ask questions in the Wintune 2.0
Beta topic in the WinMag forum on AOL. If you aren't on AOL, you can send
mail to me at [email protected], but I cannot guarantee you an immediate
answer 🙂

John D. Ruley
Editor-at-Large
[email protected]
CIS: 76227,117
BIX: jruley
AOL: jruley


 December 14, 2017  Add comments

Leave a Reply