> I've been looking lately at upgrading from OS/2 Warp 3 to Warp 4. Is
>anyone aware of any special steps I should take or any unique little quirks
>that might arise. I'm not too concerned about hardware issues as everything
>I have works just fine and has up-to-date drivers. I've applied up to
If you want to migrate your Warp 3 configuration, you'll have to back out FP26.
Warp 4, based on a diverging codebase at roughly FP22, will blow chunks if you
don't do this.
Quote:>What does the upgrade version of Warp 4 look for? If I were to
>end up re-installing due to a problem, would I have to install Warp 3 the
>"upgrade" to 4?
Warp 4 Upgrade is an "honor" license, and doesn't require a SYSLEVEL token.
Quote:>Would I be better off formatting and installing onto a clean partition?
If you can't/won't migrate, this is recommended. If you have BootManager and
a spare 300Mb partition or two, you can install alongside Warp 3 FP26 and share
an APPS partition ;-)
Read through _Up and Running!_, twice, cover to cover. Choose an Install Method
and _do the worksheet_. Browse the CD and lookit all the goodies. Read the
READMEs, print out _at least_ README and README.INS from the root of the CD.
During the install, "Network Adapters and Protocols" _will_ trip you up..
After the install completes, Shutdown and reboot, for "good luck", before trying
anything fancy.. Selective Install and Selective Uninstall seem "confused", be
very careful with them. When you verify your installed components, items that
you _deselected_ have been installed - "Installer knows best". Use Desktop Find
to collect the FIpackage objects that IBM didn't tell you about into a folder, you'll
eventually want to blow away at least ART. Some follow-up component installs
(Peer, VT..) are buggy/broken. You will probably re-install a couple times
before you'll get a configuration to settle with. Do the Backup thang..
I find the on-line documentation poorly indexed and frustrating.