From: Luiz Petroni (lpetroni_at_compassoarte.com.br)
Date: Tue Apr 01 2003 - 05:58:16 PST
Laurent:
The problem seems to be with how MacOS X treats .pkg files.
I can connect my PB with Newton using Delivery over AppleTalk with no
problems (did not tried TCP/IP yet). Delivery starts the server and
Newton can see it when I run Dock. When I tap "Connect" a connection is
oppened (I suppose) because Delivery activate the IntallPackage button.
The problem is that when I click the InstallPackage button in Delivery
and select a package that I know to be a valid one and I know that it
works with my current installed packages it fails to activated. Newton
display a popup saying that the package is not compatible with current
system and failed to be activated.
I tried with packages that I was able to install with NCU under MacOS 9.
Researching in the archives I also found a app called Packager v1.3,
but when I drag&drop a package on it I don't get any results (I also
suppose) because the package still associated with MacOS X Installer
and the package's icon stay with something like an open box.
Any suggestions?
TIA
--lpetroni
On Tuesday, April 1, 2003, at 10:35 AM, Laurent Daudelin wrote:
> on 01/04/03 07:57, Luiz Petroni at lpetroni_at_compassoarte.com.br wrote:
>
>> It was really very easy to setup and connect my 12"PB and Newton with
>> Delivery (cool piece of software and the icon is very good).
>>
>> But I'm experiencing a problem with the activation of the packages.
>>
>> Do I need to use some kind of PackType app when I move all my packages
>> from MacOS9 to MacOS X?
>> If not why is this package activation error occuring?
>
> You mean, a package activation on the Newton? If it's on the Newton,
> then
> your desktop has nothing to do with it. There is probably already a
> package
> that has been activated earlier that causes those problems on your
> Newton.
> If you need to know for sure, freeze all your packages, then thaw them
> one
> by one and reboot (soft) the Newton each time. Or, you might want to
> start
> with the last package that was properly activated. Then, if you still
> have
> the error, freeze again the last package to be activated correctly.
> And so
> on. Would you happen to have WorksBetter by any chance? I know this
> one to
> be causing a lot of those package activation problems and I had to
> modify
> its name to force it to load the last.
>
> -Laurent.
>
-- This is the NewtonTalk list - http://www.newtontalk.net/ for all inquiries List FAQ/Etiquette/Terms: http://www.newtontalk.net/faq.html Official Newton FAQ: http://www.chuma.org/newton/faq/
This archive was generated by hypermail 2.1.5 : Sat Apr 05 2003 - 20:52:25 PST