| (Forwarded to me from Liz Gabel and Bob Govoni... )
To use Schedule+ as "groupware" on NT, you need to have
MS Exchange installed.. it works fine on Win95.
Kathy
From: TNPUBS::REALOS::young "Michael Young" 19-JAN-1996 14:31:17.99
To: realos::pem-all, zendia::zendia::poirier (19-Jan-1996 1023 -0500)
CC: realos::young, zeke::paskaley, zendia::mcpartlan, zendia::boireau,
zendia::tanner
Subj: Re: Microsoft Office 95
Dave, Please forward this to the scheduler team... I don't have their
distribution list.
The Schedule+ that comes with Office 95 does not work correctly on NT -- it
requires Microsoft Exchange to be installed in order to work with other people
in the workgroup. It works fine on Windows 95 because Exchange is included with
Windows 95.
The problem is that Schedule+ 95 is not compatible with the old Schedule+, so
I'm recommending that everyone that's using WNT by default should stick with the
old version of Schedule+ until we figure out what's going on. When you install
Office 95, DON'T install Schedule+. If you do, don't run it, or it will attempt
to convert your old schedule to the new format.
You should still be able to use the old schedule+ as long as your schedule file
didn't get converted.
If it got converted accidentally, please see me. I can help get it converted
back. (I think).
mike.
|
|
If you are thinking about installing Office95 (or having
it installed) on your PC
***** READ THIS FIRST! *****
Office95 is the swr package that contains Word 7, PowerPoint,
and Excel - all 32-bit applications for Windows 95. You
would need Word 7 to run either D2H V2.0, or RoboHelp95.
Bottom line.. If you're up against any critical project
deadlines right now, hold off on installing Office95 till
you're at a point when you can deal with upgrading.
Some of us are playing around with the new software, partly
because we have to, and partly to learn how to deal with
any problems that crop up so others can avoid them.
I've been doing some experimentation with installing
Office95 (to get Word 7.0) while still retaining
Office 4.2 (to keep Word 6.0)... and then layering
the 16- and 32-bit versions of RoboHelp and D2H on top
of the corresponding versions of Word... and also trying
to get all this to work on both "sides" of a system dual
booted with Windows 95 and NT3.51... (Yes, I'm crazy, and no,
I don't really think it's *all* going to work, but I figured it's
worth a try to see what does work.)
For my installations, I put as much as possible on
my D drive, since my C drive is more or less full
with the operating system software. My D drive is not
partitioned.. the whole disk is "seen" by both operating
systems.
Some people have a partitioned disk, which enables
you to get a little more separation between the
two environments. With this configuration,
you could build the Office95/RoboHelp95/D2HV2.0
environment on one part of the disk, and
leave Office 4.2/RoboHelp3/D2HV1.6 on the other
part of the disk.. (Donna Micozzi did that and
it seems to work.)
Based on my experiments, here's what I believe will work
if you need to set your PC up for both 16-bit and 32-bit
environments:
1. Install Office 4.2 in d:\MSOFFICE
2. Install RoboHelp V3.0 in d:\RoboHelp
...pointing to d:\MSOFFICE\WINWORD\TEMPLATE
as the target for the .DOT template files.
3. Install D2H V1.6 in d:\Doc-to-Help
...pointing to d:\MSOFFICE\WINWORD\TEMPLATE
as the target for the .DOT template files.
(The above three steps are probably already done.. and
you don't need to do both Help tools if you don't need
both help tools.. )
Then, to install/setup the 32-bit software packages:
4. Install Office 95 in a directory called d:\OFFICE95
(On NT, I had to consciously specify new locations
for each of the 32-bit apps so it wouldn't overwrite
the existing Office 4.2 apps.
On Windows 95, it seemed to ignore the presence of the
Office 4.2 software... However if it does put up a message
asking if you want to remove the older version
of the software, say "no".)
5. Install RoboHelp95 in a directory called d:\RH95
...pointing to d:\Office95\Templates
as the target for the .DOT template files.
6. Install Doc-to-Help V2.0 in a directory called d:\D2H-V2
...pointing to d:\Office95\Templates
as the target for the .DOT template files.
(You can choose your own directory names.. just as long
as they're different for what you chose for Office 4.2
and the 16-bit help tools. \RH95 is the default for
RoboHelp95 installation... so they've already made it so
you avoid clobbering RoboHelp V3.0)
If you have a dual-booted system, you have to do the installation
on both "sides" to see the software on both sides... (The
installation not only puts files in the directory you specify,
but it puts stuff in your system registry, and in your system
directory, depending on which OS you have booted.)
So, repeat all the installations on the Windows 95 side of
your system... being careful to specify the EXACT SAME directories
for each of the applications.. (otherwise, you take up more disk
space than you need to.)
There are a few differences between Win95 and NT on the installations...
When installing Office95 on an NT system that already has
Office 4.2.. the setup procedure "finds" the Office 4.2
software and you have to specifically redirect it to your
target directory for Office95 (in my case: D:\OFFICE95)
Also, in the case of NT, you have an opportunity to specify
a different program group for each of the 32-bit apps... I opted
to put each application in its own Program Group...
After you have done all this, almost everything seems to work..
with the following *known* exceptions:
The MS Office 4.2 menu ends up "seeing" the Office95 software.
You have to set up your own icons, or shortcuts, or find
the .EXE in the File Manager or Explorer to invoke the
Office 4.2 apps.
Excel 5.0 (from Office 4.2) gives you an error message on
exiting... (so, take this as an indication that there may
problems with having Excel V5.0 and V7.0 co-resident on
your system)
Word 6 and Word 7 files seem to have transparent
interchange, but there *are* incompatibilities between
PowerPoint V4 and PowerPoint v7 files.. (PPT V4.0 can't read
a PPT V7 file.. it has to be saved to V4.0 format.)
I'm not making any claims at this point re: which
of our custom .DOT templates work/don't work... (We know
some of the templates need upgrading for the 32-bit
software, and people are working on them.. Again, use caution.
If you use SES custom templates, hold off on upgrading till the
whole environment is tested.)
Other than that, you should get into TNPUBS::NSCC notesfile to
catch up on what people are experiencing in upgrading help files
from 16-bit to 32-bit environments...
Hope this helps.. If I have encouraged you to use caution
in upgrading your system, I've accomplished my goal.
Regards,
Kathy
|