[cobalt-users] Re: Miva 4.16, Empresa 4.06 & Sun Cobalt RaQ4r

["Michelle A. Hoyle" <mahlist@xxxxxxxxxxxxx>]

> From: "David J. Duffner" <cobalt@xxxxxxxxxx>
> Subject: RE: [cobalt-users] Re: Miva 4.16, Empresa 4.06 & Sun Cobalt RaQ4r
>
> <SNIP>
> 	Were you trying to 'overlay' the 4.16 & Empresa
> modules over the existing 4.12(3 or 4) installation or
> did you take Miva's files and install them directly
> according to Miva's tech support?


Sorry for the delay, David.  I've been busy.


I did this on a clean RaQ4 after a complete OS restore, so I didn't 
have any Miva packages on it at all.

> 	Did you follow the 4.16 install & Empresa
> install directions and then use the Unix-specific
> install instructions and then the RaQ 3/4 for
> Empresa 3.94/6 instructions?  That seems to be the
> methodology Miva states should be used?

> 	Did you make your own packages for installation
> of the Merchant & Empresa bundles or did you install
> it by hand?  And in either case, again, did you completely
> remove the old Miva install before attempting to do
> this install?


No.  I used the Miva-supplied instructions for installing the new 
versions on the RaQs and followed the instructions carefully by hand. 
I obtained the instructions from Miva technical support.



> 	I've noted that since the 4.16/4.05(6) package is
> completely compiled compared to the other versions that
> things will operate differently and any old references
> could cause the effect you mentioned below.  Thus I asked
> the group to see if someone had hit such a problem and
> possibly figure out how to avoid it.  The co-lo for this
> RaQ can perform this upgrade on-site (at big $$), but
> the hint their techs gave me was that they'd clean out
> the old and install the new as if it were a new box for
> deployment to a client.


That's a good hint, I'd guess, but it didn't seem to help.  I'm 
guessing we can follow Bill Gibbs' method from the earlier message. 
I'll try that on my RaQ4 and on my RaQ550.

Michelle