cannot install battery update 1.3.2

I've just downloaded this, only to have the installer report i don't have a valid installation; bizarre, seeing as I've installed prior updates without problems. Anyone come accross this problem?

--

Powerbook G4 1.33ghz
Lacie D2 160 FW400 drive
MOTU 828 mkII
PowerCore FireWire

OS X 10.3.2
Logic Platinum 6.3.3
NI Battery 1.3.1
NI Kontakt 1.5.1
NI Traktor DJ 2.5.3
NI Reaktor 4.0.4

 

Hi Nickshim,

Did you move or rename your Battery installation directory?

 

actully yes, I've tidied up my applications folder. I did put the folders back in thier original locations, but I assume that is not enough...

 

Hi,

To keep things simple I'd suggest that you remove the current Battery installation (remove the battery preferences files too that can be found in the users\(current user: your username?)\library\preferences directory) and then install Battery from scratch without moving the original installation folder around, till the 1.3.2 update is installed. But in general I'd suggest to leave the installation directory always in it's original place as to avoid complications with possible updates.

Have fun. Hans Scholten.

 

Thanks for your quick response Hans!

 

Hey,

We're having the exact same problem. When trying to use the update, the installer says that a valid previous version cannot be found.

We tried installing the original from CD in a number of places, yet it still won't work. Where is the proper location for installing (there is no default) the original battery so that the updater can find it?

Thanks for the help.

-=Jeff Merkel=-

 

I, too, have this problem!

I have not moved or altered the Battery folder within the Applications folder, but the 1.3.2 update thinks otherwise. Surely this is a fault of the installer?

 

unable to install battery 1.3.2 os x 3.2 panther

installer won't go further when it reads items remaining to be installed 14 E pdf
then after a long wait , a message comes on saying an unexpected error has occured while installing battery installation E pdf .
i haven't move or deleted any items within my battery folder








powerbook g4 667 panther.3.2 , 1 gig ram ,logic plat 6.3 , motu 828

 

OS X update still not working

I tried trashing the original Battery and re-installing before again trying the update...No luck still. Anyone know what is up with this?

 

Same Here

I just bought Battery after hearing it was OS X compatible. Well, the installer on the CD won't run without classic installed (there is no way I'm installing classic just to install a friggin plug-in - so much for OS X compatibility), and the OS X updater on the site won't allow me to install without a "valid" battery installation. What a joke. I call the sales guys and he basically said - we'll send you an email link to the download when we feel like it. But first you have to fax us your receipt and fill out a form. Are they joking me? What year is this? Fax, form? Whatever happened to designing an installer that would only install after the entry of a valid serial number, instead of punishing the real purchasers of your software with ridiculous requests for faxes that can only be filled at NI's convenience. I have work to do NOW - and I paid for your softwre and overnight shipping so that I could use it NOW - I do not want to wait until tomorrow to use it. I'm sure Arturia or Steinberg would be happy to let me download their latest and greatest releases without a fax? Needless to say I am livid. This is my first experience with NI and if I don't have a working installation by tomorrow all 4 of the products that I purchased yesterday are going right back to zzounds....

 

same problem

when i update on the 1st drive (ATA unit 0, IBM-IC35L060AVER07-0) it was ok. but on the 2nd drive (ATA unit 1, ST380021A ) it failed.
i think NI should announce publicly.

PMG4 867,OSX 10.3.2

 

reply from NI

NI gave me a very quick answer. thanks NI. now i solved the problem. here's howto.

"I know you said you did not move the folder, but did you rename your hard drive? If you did, it is likely that you will experience this error. That is because in the Battery preference file an install directory is written. When this conflicts with the actual location, the installer will not find the application simply because it uses the install directory as a reference to where the application is.

It is very simple to edit the preference file to reflect the new location. Open the Battery.plist file with text edit and correct the install location (install dir)

Then save the file and the updater will work. "

 

Re: reply from NI

WHAT?!!! I'm just a musician. Please explain.!!!!

 

Re: reply from NI

I have opened this file and I do not have a clue as to what I should be changing to correct the problem. Can we get some detailed "step by step" examples of what we should be seeing and what it should be changed to? Like the previous poster stated, I am a musician, not a computer programmer!

 

Re: Re: reply from NI

me neither.

in case,
1. you failed Battery 1.3.2 update installation,
and
2. you renamed your harddrive before update,

then you'll have to do this.

0. find "Battery.plist"
1. open it by textedit
2. find <your former harddrive name>
3. replace them with <your new harddrive name>
4. save Battery.plist
5. do installation

this worked in my case.
if no success, you'd better ask NI techs.
(i think they should announce this publicly, not by email...)

 

I got Battery 1.3.2 working by doing the following steps:

1.) I did a search for "Battery" on my hard drive and then I deleted every trace of it from both my OSX and my OS9 system folder. I also deleted the contents of the Battery application folder (with the exception of the kits and the samples.)

2.) I reinstalled everything from scratch, starting with the Battery OS9 install (via OSX running in classic mode in the background).

3.) I opened the fresh OS9 stand alone Battery application and authorized it with my serial number.

4.) I ran the Battery 131 update and then opened and authorized the stand alone application again.

5.) Finally, I ran the Battery 132 update and (finally after all of the dicking around) it opened and worked properly.