I was getting the same problem with mine. I have a G4 Power PC that has an upgraded processor. I did this so i could run Leopard.
When i got 6.0.6b1 in the mail i made a copy of the program i was getting the errors with and saved a copy of the data base. I then loaded the 6.0.6b1 and tried it on the original daa base and i did not get the errors again. seems what inspired me was that this upgrade was supposed to help with problems like this. just a thought Gerry >>I got a series of errors, one for each database >>component that needed rebuilding. In each case, the error codes were >>the same: >> >>Class-DB what=100 err=130 > >I have a similar issue as Don had, but worse. I woke up to find >Powermail locked up. It would not quit and I needed to do a force quit. >Upon trying to re-open, Powermail wants to rebuild sort indices and then >when it is done it exits with the same error as above. None of the >options in PowerMail First Aid help, including low level rebuild with >the latest beta. > >I now have a corrupt message database that Powermail can not open. > >Does anyone have any suggestions? I have tried all the usual suspects, >verified/repaired the disk itself, PowerMail First Aid by holding down >command option on startup, etc, to no avail. I have a 4 day old backup, >but would like to recover that mail... I have a copy of Powermail >Salvage from a similar situation a couple years ago, but when I launch >Powermail Salvage on my Intel Macbook or Mac Mini it just does the >spinning beach ball... Does Powermail Salvage even work on Intel Macs? >On Powermail 6 message databases? Any options for me to get my mail back? > >Thanks in advance for any help. > > -- The faster the computer The more impatient the user
