non-NB: upgrading a machine to Win98

["Paul Falzer" <paul.falzer>]

> From: Steven Uran [mailto:Steven.Uran]
>
I would be very grateful for comment or advice on running the
Win98 upgrade on an older computer with Win3.11 and which also
has QEMM and a multiple bootup setup.
>
Would it be advisable (indispensable?) to replace the
autoexec.bat and config.sys pair with a simple, plain vanilla
configuration so as not to confuse the Win98 upgrade and  if so
what should that autoexec.bat and config.sys pair contain?>
>


Steven,

I don't know how your multiple boot setup might affect your
upgrade from Win 3.11 to Win 98. Perhaps others on this list can
assist you with the boot setup issue. I can offer a few
suggestions about your system files. I assume that you know the
system requirements for Windows 98, have determined that your
machine will support it, and backed up your critical files
(including the win.ini and system.ini files in your Windows
directory) to an external medium.

As to your config and autoexec: In your config.sys, you will want
to remove ALL references to QEMM and run himem and emm386
instead. This is the only step you must take before you install
Windows 98. You need not physically remove QEMM from your disk,
however. If memory serves me, the win installation detects a
third party memory manager and removes it before installation
begins. But, it's best to do this manually. The only other step I
would definitely recommend is to create a bootable diskette with
your current configuration files and make sure it works (see
below).

My Windows 95 config.sys:

device=C:\WINDOWS\himem.sys
device=C:\WINDOWS\emm386.exe NOEMS x=D000-D7FF

rem NOTE: Exclude regions are unique to each computer. Use the
exclude region(s) from your QEMM line. Use the RAM parameter
instead of NOEMS if you are running applications that require
expanded (rather than extended) memory.

dos=high,umb
fileshigh=150
buffershigh=30

rem NOTE: I'm assuming that you are running at least DOS 5.0.
Prior to version 5.0, you could not load anything into the upper
memory region (the region between 640 and 1024) -- what's called
"loading high" -- unless, of course, you are running QEMM,
Netroom, or another third party memory manager. The fileshigh and
buffershigh commands were not supported until DOS 6 or 7 (I don't
remember which). So, you might want to substitute a "files" and
"buffers" statement for the "fileshigh" and "buffershigh"
statements that appear above. In any case, be sure to remove all
references to qemm.sys from your config and autoexec.

break=off
shell=c:\command.com c:\ /e:\2048 /p

rem NOTE: Point to the location of your command.com file. Mine is
in the root of c:, which is the best place for it. If yours in
in, say, c:\dos, the line would read: shell=c:\dos\command.com
c:\dos /e:2048 /p

rem NOTE: Add additional device drivers here. Depending on your
version of DOS, you can use a "devicehigh" command. However, do
not use a "devicehigh" command with himem and emm386. Himem
should automatically load into high memory (the region above
1024k).

rem NOTE: I do not load a real mode cache utility such as smart
drive. If you have a caching utility, keep it through the
installation, but consider removing it or changing the parameters
after Windows 98 is installed. You will need a real mode cache
for peripherals such as diskette or CD-ROM drives, or if you
elect to work outside of Windows. In any case, you'll want to
select the smallest size for your cache that meets your needs.
For instance smartdrv.exe 4096 256 creates a 4 MB cache outside
of Windows and a 1/4 MB cache when you working inside Windows.
For information on parameters, type "smartdrv.exe /?" at a DOS
prompt (window, full-screen, or outside of Windows).

rem NOTE: I don't load setver.exe or ansi.sys. I would suggest
that you remove or rem them out unless you have a specific reason
to keep them.


My Windows 95 autoexec.bat:

@C:\PROGRA~1\NORTON~1\NAVDX.EXE /Startup

rem NOTE: This line loads my antivirus software. Carry any
similar line forward from your current autoexec.

@echo off

PATH
c:\windows;c:\windows\command;c:\windows\system;C:\PROGRA~1\ACCES
S97\OFFICE;c:\xw;C:\MSSQL7\BINN;

rem NOTE: You will modify your path AFTER you install Windows 98.
Keep your current path statement for now, but remove any
reference to QEMM. For Windows 98, it's advisable to include a
path to your windows root directory, your windows command
sub-directory, and your windows system sub-directory. The other
entries you see are for my system.

set temp=c:\temp
set tmp=c:\temp

rem NOTE: These entries point to your temporary directory. If you
haven't already, make a directory on your boot drive called
"temp." Point to this directory using the statements above. Then,
delete the *.tmp files that currently are on your hard drive.

rem NOTE: You can load additional drivers here or execute
additional commands such as SET statements, as needed. The shell
statement that appears in the config.sys sets a comspec; you will
not need a separate "SET COMSPEC" command in your autoexec. With
DOS 5+, you can use the command "lh" to load drivers into upper
memory. With Windows 9x, you do not start up Windows
automatically with a c:\windows\win.com command, as you do in
Windows 3.x.


A few housekeeping points: First, it's good practice though not
necessary to check your disk for errors, using SCAN, Norton Disk
Doctor, or another utility before you upgrade. Second, make
copies of your current config.sys and autoexec.bat files and
place them on a bootable diskette, so that if your system hangs
you will be able to boot up and make changes. Check this diskette
by booting from it before you make significant changes to your
configuration files. Tip: include a text editor such as edit.exe
on your boot diskette. Another tip: Instead of deleting your
current system files, rename them to, say, config.sy_ and
autoexec.ba_. Third, boot to Windows 3.11 (your current OS) with
the new config.sys and autoexec.bat files, to ensure that
everything is working properly. Keep your finger on the "pause"
key (upper right area of your keyboard) in case you encounter an
error and want to inspect it. You "unpause" by hitting any other
key, for instance, the space bar. Fourth, after you upgrade, it's
good practice to defragment your hard drive. Finally, there's
nothing wrong with documenting your config and autoexec files
with "rem" (i.e., remark) statements such as you see above. BTW,
the entries in your config and autoexec are NOT case sensitive.