Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

3.2 Enhancement Pack ?'s

0 views
Skip to first unread message

Joe K. Bales

unread,
Nov 10, 1999, 3:00:00 AM11/10/99
to
I purchased the 3.2 Enhancement pack for a client on 3.12. I have not
opened it yet unitl I make sure it is the correct thing I need.

Can I apply this enhancement the 3.12 server and make the server Y2K OK?

The H/W is Y2K Compliant

I assume that with this Pack I do not need to load any other CLIB or Patches
am I correct of do I need to run something before the 3.2 Enahancemt?

Does this bacially upgrade the 3.12 server to 3.2 or just enough to make it
Y2K OK.

Has anyone done this before on here and if so what problems if any can I
expect and what is the time frame to do this.

Also the Server does not have a CD-ROM . I assume the proper way to install
this patch is to copy the contents of the cdrom from a workstation into a
temp directory and run the patch from there. Any thoughts on this?

thanks

joe

Nick Smeltzer

unread,
Nov 11, 1999, 3:00:00 AM11/11/99
to
In article <MzkW3.2482$yQ.3...@news.rdc1.va.home.com>, Joe K. Bales
<joeb...@home.com> writes

>
>Can I apply this enhancement the 3.12 server and make the server Y2K OK?

yes

>
>The H/W is Y2K Compliant
>
>I assume that with this Pack I do not need to load any other CLIB or Patches
>am I correct of do I need to run something before the 3.2 Enahancemt?

Sort of. But there have been some patches to 3.2 released :(

>
>Does this bacially upgrade the 3.12 server to 3.2 or just enough to make it
>Y2K OK.

Just enough. In fact it will still say its a 3.12 server.

>
>Has anyone done this before on here and if so what problems if any can I
>expect and what is the time frame to do this.

10 mins and no problems unless you have mac name space support

>
>Also the Server does not have a CD-ROM . I assume the proper way to install
>this patch is to copy the contents of the cdrom from a workstation into a
>temp directory and run the patch from there. Any thoughts on this?

You can use a workstation's CD and use rconsole.

--

Nick Smeltzer
Certified Novell Engineer
ni...@greenhse.demon.co.uk (home)
nsme...@groundwork.org.uk (work)

Ken Agress

unread,
Nov 12, 1999, 3:00:00 AM11/12/99
to
On Thu, 11 Nov 1999 18:35:58 +0000, Nick Smeltzer
<Ni...@greenhse.demon.co.uk> wrote:

<snip>


>>
>>I assume that with this Pack I do not need to load any other CLIB or Patches
>>am I correct of do I need to run something before the 3.2 Enahancemt?
>
>Sort of. But there have been some patches to 3.2 released :(

Just to clarify - the patches to 3.2 should be applied after you
complete the upgrade. You shouldn't need to do anything before
applying the "base" 3.2 OS.

Ken Agress/CNE
Note - While I may reply to direct e-mails, if you really
want an answer, please post to the Newsgroups.

Joe K. Bales

unread,
Nov 13, 1999, 3:00:00 AM11/13/99
to
Thanks guys:

I dont know my partner would but os2 namespace may be on there for long file
names will this be a problem and what was the problem to expect with mac
name space


Ken Agress <kena...@earthlink.net> wrote in message
news:I5ArOEStqL7Y7M...@4ax.com...

Nick Smeltzer

unread,
Nov 13, 1999, 3:00:00 AM11/13/99
to
In article <ir7X3.139$RM2....@news.rdc1.va.home.com>, Joe K. Bales
<joeb...@home.com> writes

>Thanks guys:
>
>I dont know my partner would but os2 namespace may be on there for long file
>names will this be a problem and what was the problem to expect with mac
>name space

There won't be a problem with OS2.NAM but there is a major issue with
MAC.NAM. There is no warning on the box or in the instructions (or at
least there wasn't), but installing the enhancement pack has the same
result on your volumes as applying the MAC.NAM patch. If you apply the
patch, the instructions say you need to delete your volume, apply the
patch and then re-create your volume. The enhancement pack doesn't
mention this.

The result: If you have MAC.NAM and apply the enhancement pack you
probably won't be able to mount your volume afterwards - and this has
happened in every case I've seen. The only work around is to copy the
old MAC.NAM from the original 3.12 install disks...

HTH, Nick

0 new messages