[Theilgaard]

I changed the path to this:
../../InstallerFiles/BaseOS/InstallerChoices_Customer.xml

And now it has found it.

I think InstaUp2Date should be able to find this folder by itself. 😉

Thanks.
Søren

[Theilgaard]

In rev 296, I get “No file found at path”, for all packages.

/Søren

[Theilgaard]

[QUOTE][u]Quote by: malroy[/u][p]Hi Guys,

but i am having this error

###### Error: /tmp/InstaUp2DateFolder-U8qJ7y/12 Epson Printer Drivers pointed at /tmp/InstaUp2DateFolder-U8qJ7y/../../../Volumes/SOE/instadmg/InstallerFiles/InstaUp2DatePackages/EPSONPrinterDrivers.pkg, which is an unknown file type (should be a dmg or a folder) ######
12:23:46 ###### Cleaning up ######
[/p][/QUOTE]

I have seen this error myself, with a flatfile package file, build with Apples PackageMaker.

InstaUp2Date has just been updated a few days ago, maybe that will solve the issue.

Please check to see if this is a flat file package (right click on it, and see if you can “Show Package Content”. If not its a flat file package). Maybe it’s some kind of a bug, try to take it out, and run InstaUp2Date again.

(In my case it was a package that installed the admin user, and I simply changed this to the create_user package).

Søren

[Theilgaard]

When I followed the FileWave description, these files is part of their description. I build my installer with LANrev InstallEase manually by draggin the folders in as described in the document, and then I build an Icaberg project, and then the package.

The empty folder mentioned in the document was in the Iceberg project, but I did not put empty files into those folders, as I do not think that empty folder should be a problem for Iceberg.

What puzzled me was the file in /Library/Caches which was not present on the CS3 Design Premium installation, as it is on the CS3 Standard installation. And not all the empty folders mentioned in the description was present in the Standard installation.

I will try using ewhite’s suggestion, and also LANrev in snapshot mode.

/Søren

[Theilgaard]

[QUOTE][u]Quote by: thegooch49[/u][p][QUOTE][u]Quote by: Theilgaard[/u][p] I don’t know if I understand this problem correctly, but it sounds like you are naming you packages with numbers. It is FOLDERS in the AppleUpdates folder you have to create with numbers, and then put you packages into these folders (one in each numbered sub-folder). So it will be the folder number that determines the order of updates, and not the name of the package.[/p][/QUOTE]

Hi, thanks for the help. I have created folders inside of AppleUpdates. In the AppleUpdates, I have created named folders (01,02,etc). In those named folders, I have the apple updates that have the standard name. I’m going to try this again to verify that I’m still having this issue. [/p][/QUOTE]

You can read this thread to see my list with 10.5.3:
[url]https://www.afp548.com/forum/viewtopic.php?showtopic=21023[/url]

– Søren

[Theilgaard]

[QUOTE][u]Quote by: Patrick+Fergus[/u][p]Why is your numbering system so unusual?
[/p][/QUOTE]

In my process of figuring out which update should be in what order, before reading about in these forums, that I could simply read the Software Update Log, I was trying all sorts of things. So I eventually grouped certain updates with numbers.

I also maintain a setup where iLife is part of the AppleUpdates, and these packages are somewhere in between.

I missed a list like this, when I began this jurney, so I posted my confirmed-to-be-working list. At least it does not contain obsolete updates.

– Søren

[Theilgaard]

iTunes is also needed if you consider this to be part of the system. It’s installed with the 10.5 installer, so I consider this to be part of the system.

My AppleUpdates folder now looks like this:

11 MacOSXUpdCombo10.5.3.pkg
22 AirPortUtility_Leopard.pkg
30 QuickTime745_Leopard.pkg
31 iTunes.mpkg
32 FrontRowUpdate2.1.3.pkg
50 BuiltInKybdFirmwareUpdate.pkg
52 MacProFirmwareUpdate.pkg
53 AlKybdFirmwareUpdate.pkg
54 iMacFirmwareUpdate.pkg
55 MacBookProFirmwareUpdate.pkg
56 MacBookFirmwareUpdate.pkg
57 MacBookAirFirmwareUpdate.pkg
58 iMacGraphicsFWUpdate.pkg
71 JavaForMacOSX10.5Update1.pkg (this is the one Patrick described is for Intel 64 bit only)

[Theilgaard]

Does anybody knows how I can select to have predefined input methods (flags) selectable in the login dialogue.

I know that /Library/Preferences/com.apple.login.plist contains the setting to show the input method, but only the US flag is immediately selectable, all others has to be dug out from deep sub-menus.

I can manually add the input methods I want, and my own investigations shows that the file /privat/var/tmp/com.apple.HIToolbox.loginwindow.plist contains the information about this, but if I instal the file on a new image, it does not apply to the login dialogue.

Any suggestions?

[Theilgaard]

[QUOTE][u]Quote by: thegooch49[/u][p]Yes, I am. The custom updates run fine. My custom installes are all homemade, so I just prefixed the packages with 01, etc. I don’t want do do this with the apple updates, after the warning about receipts having wrong names.[/p][/QUOTE]

I don’t know if I understand this problem correctly, but it sounds like you are naming you packages with numbers. It is FOLDERS in the AppleUpdates folder you have to create with numbers, and then put you packages into these folders (one in each numbered sub-folder). So it will be the folder number that determines the order of updates, and not the name of the package.

[Theilgaard]

[QUOTE][u]Quote by: dano[/u][p]well…I knew someone would correct me if I was wrong. There is one issue I have run into regarding partition maps related to external drives. This problem occurred under Tiger (haven’t checked under Leopard yet). Disk Utility wouldn’t change the external hard drive’s partition map scheme. If you had formatted your drive while attached to a PowerPC computer and then tried to reformat while attached to an Intel computer, the partition map would not change from APM to GUID. Which makes the external drive non bootable from an Intel Mac. The workaround for this is to erase the disk using the diskutil tool from Terminal.[/p][/QUOTE]

Actually this is not right. You can change the partition map, if you select to “partition” your drive instead of “erasing” it. This way Disk Utility will also allow you to change the size of the partitions, if the partition table is GUID (this is probably the main reason not to select Apple Partition Map for the external drive, except that it will not allow you to boot a PPC machine).

[Theilgaard]

[QUOTE][u]Quote by: Patrick+Fergus[/u][p]Not sure what the problem is–I did the following:

– Was able to connect with via ARD with admin’s login and password, including using kickstart to edit the admin’s rights via an ARD “UNIX Command”

What are you doing?

– Patrick[/p][/QUOTE]

I’m creating a Custom Client Installer using the ARD administration application. Here I can set up privileges to the various (if more than one) user accounts, I can enable other settings, such as ability for any user to control the screen, IF the current user accepts the call, and also enable network based accounts to control ARD. Much easier, and with more options.

This package is installed as a CustomPKG, no need for me to figure out kickstart commands.

[Theilgaard]

[QUOTE][u]Quote by: Patrick+Fergus[/u][p]Disclaimer: We’re using FileWave to manage the installation of third-party software, so I really haven’t thought through building installation pkgs.[/p][/QUOTE]

I think Patrick could have included this link:
[url]http://filewave.org/viewtopic.php?t=643&sid=e415e6e1e176f751dfc9d99ba1232a76[/url]

But actually, [url]http://filewave.org/[/url] have a lot of great whitepapers on how to build packages for certain software, and it’s easy to follow, even if we are building an Apple Installer package.

[Theilgaard]

[QUOTE][u]Quote by: johnemac[/u][p]There was a gotcha with iLife. There is a post here about fixing the iLife Support updater
<https://www.afp548.com/forum/viewtopic.php?forum=45&showtopic=20102&highlight=iLifeMediaBrowser>
[/p][/QUOTE]

Where?

When I quoted the message, initially wanting to ask the question above, I found the URL hidden in the message:
[url]https://www.afp548.com/forum/viewtopic.php?forum=45&showtopic=20102&highlight=iLifeMediaBrowser[/url]

[Theilgaard]

When I login using the admin account, I’m presented with a dialog where I can fix the security settings (permissions I guess):

Before fix:

[code]Last login: Tue Mar 11 04:36:55 on console
Macintosh:~ admin$ cd /Library/StartupItems/
Macintosh:StartupItems admin$ ls -al
total 0
drwxr-xr-x 4 root wheel 136 Mar 11 03:03 .
drwxrwxr-t+ 50 root admin 1700 Mar 11 04:37 ..
drwxrwxr-x 4 root wheel 136 Mar 6 00:55 instauser
Macintosh:StartupItems admin$ ls -al instauser/
total 16
drwxrwxr-x 4 root wheel 136 Mar 6 00:55 .
drwxr-xr-x 4 root wheel 136 Mar 11 03:03 ..
-rw-rw-r– 1 root wheel 163 Aug 8 2007 StartupParameters.plist
-rwxrwxr-x 1 root wheel 459 Mar 6 00:55 instauser
[/code]

After fix:

[code]Macintosh:StartupItems admin$ ls -al ADBind/
Macintosh:StartupItems admin$ ls -al instauser/
total 16
drwxr-xr-x 4 root wheel 136 Mar 6 00:55 .
drwxr-xr-x 4 root wheel 136 Mar 11 03:03 ..
-rw-r–r– 1 root wheel 163 Aug 8 2007 StartupParameters.plist
-rwxr-xr-x 1 root wheel 459 Mar 6 00:55 instauser
[/code]

The strange part is that PackageMaker has set the incorrect settings using the “Apply Recomendations” function.

BTW: Does anybody know why the “Apply Recommendations” settings does not stick to the items, I have to set these settings each time I open the Package Maker project?

[code]

[Theilgaard]

Thank you both very much.

I removed the security update and everything works fine.

I have been testing this today, so sorry for my late reply.

Thanks,

Søren

[Author]

Posts