A big problem with a simple solution...

for the error below just do this

Start->run..then type the following -> "Outlook.exe /resetnavpane"

the error
---------------------------
Microsoft Office Outlook
---------------------------
Cannot start Microsoft Office Outlook. Cannot open the Outlook window.
---------------------------
OK   
---------------------------

Must have linux tools

yum
webmin
named
sarg(if you use squid)
jabberd
winscp
password-less login
cacti

Jabberd installation notes

**This is a rough one

When installing udns ensure you install the devel also

After installing gsasl upi meed tp enter the flag below to get all to work

Use these links

http://web.archive.org/web/20061010225021/http://jabberd.jabberstudio.org/2/docs/quickstart.html#qs_1_8

http://jabberd2.xiaoka.com/wiki/InstallGuide

http://jabberd2.xiaoka.com/wiki/InstallGuide/StartupShutdown

Btw, you may need to add /usr/local/lib to /etc/ld.so.conf and re-run

'ldconfig' as root after installing a local library. This makes sure

all applications notice your new library instead of the one in /usr/lib.

Alternatively, configure jabberd with LDFLAGS=-Wl,-rpath,/usr/local/lib

to make it use your own libgsasl.

Generally, if you are not familiar with building free software, it might

be easier to locate pre-built binary packages of jabberd for your

operating system instead.

CFLAGS=-DOPENSSL_NO_KRB5 ./configure --enable-db --disable-mysql (flag to overcome the open ssl problem)

Your Jabberd 2 installation is complete. Below is a listing of file locations for the default installation:

        /usr/local/etc    Jabberd Configuration Files

        /usr/local/bin    Jabberd Binaries (jabberd, c2s, resolver, router, s2s, sm)

/usr/local/etc/c2s.xml remove under there is a compartibility issue

Am happy lol

Conference

When you try to start the server, you may see an error telling you that "Configuration parsing using jabber.xml failed". There are two reasons why you might experience this error. One is that the file you are pointing to does not exist; the solution is to type ./jabberd/jabberd -c /path/to/jabber.xml and thus specify the full path to your configuration file. The other reason is that the file exists but contains an XML error; the solution is to fix your XML (e.g., by pasting your entire jabber.xml file into the XML Syntax Checker at xml.com).

Eith just add the muc xml and deamon to the old parts where the files existed initially or use this file if you want to add the conference to start up

#!/bin/sh

##############################################################

#

#     mu-conference -- script to start Mu-Conference.

#

#############################################################

DAEMON=/usr/local/bin/mu-conference

CONF=/etc/jabber/muc-jcr.xml

NAME=mu-conference

USER=ejabberd

#############################################################

if [ "`/usr/bin/whoami`" != "$USER" ]; then

       echo "You need to be" $USER "user to run this script."

       exit 1

fi

case "$1" in

  debug)

        test -f $DAEMON -a -f $CONF || exit 0

        echo "Starting $NAME in debugging mode."

        $DAEMON -B -d 255 -c $CONF &

        ;;

  start)

        test -f $DAEMON -a -f $CONF || exit 0

        echo "Starting $NAME."

        $DAEMON -B -c $CONF &

        ;;

  stop)

        echo "Stopping $NAME."

        killall $NAME &

        ;;

  restart|reload)

        $0 stop

        sleep 3

        $0 start

        ;;

  *)

        echo "Usage: $0 {debug|start|stop|restart}"

        exit 1

esac

How to add routing client to Network

· Add static routes to
.................o Client Router
.................................. § add default route to interconnecto
.................o Inter-Connecting Base station Router
.................................. § add default route to hotspot and
.................................. § static route to client router
................. o Hotspot
.................................. § Add static route to interconnector
.................................. § Add static route to client router
................. o Proxy servers
.................................. § Add static route to interconnector
.................................. § Add static route to client route

· Configure Squid
................. o Add subnet of client
................. o Set download size
................. o Set port considerations

Creating the Best Troubleahooting Device

Ever thought of having the most powerful computer troubleshooting tool at your disposal. Well this is a close shot. You can have everything from
- Xp installation
- Bart PE
- Vista installation, and
- Linux distributions
on one flash drive.

A little not well defined how to is defined as follows. Please, to make sense of it, read each line almost independently unless it looks continuous. Bad english writer, i would re-write later when i have time.

USB_MultiBoot.cmd - Install XP from USB
1. Introduction
The Batch Program USB_MultiBoot.cmd can prepare a Bootable USB-Stick,
which can be used for Install of XP from USB.
Install from USB-Drive is of general use, convenient and faster than Install from CD or DVD,
but is limited to computers that are bootable from USB, as determined by BIOS and
Motherboard.
Updating and Changing an USB-stick is also easier than preparing a new Bootable CD or
DVD.
Install of XP from USB is very useful when the computer has no optical drive,
like e.g. ASUS Eee subnotebook.
Preparing a Bootable USB-Drive with USB_MultiBoot.cmd Involves:
Format USB-stick like a Bootable Harddisk Drive with NTLDR BootSector
using PeToUSB or HP USB Format Tool
Select from the Main Menu of USB_MultiBoot.cmd
1 - Give XP Setup Source Folder and give UserData for XP Setup
2 - Give USB-Drive Target
3 - Make Bootable USB-Drive with XP Setup Folders
Install of XP from USB requires to Reboot from USB-Drive
and Select from Boot Menu: 1. Begin TXT Mode Setup Windows XP
- Download Direct from CD Forum: USB_MultiBoot_10.zip
Or from BootLand Forum: USB_MultiBoot_10.zip
Or from Mirror (Thanks to Siginet) - USB_MultiBoot_10.zip
- Unpack USB_MultiBoot.zip to your Harddisk in a simple Path without SPACES.
USB_MultiBoot.cmd is Vista Compatible, but requires User Account Control OFF.
In this case a BOOTMGR type BootSector is made when Formatting the USB-Drive.
Such Bootsector is Detected and Auto Converted by BootSect.exe to
NTLDR type Bootsector required for booting with boot.ini Menu
XP as OS is Preferred for Speed of FileCopy to USB ( 10 min instead of 30 minutes for Vista
OS )
The procedure for Install of Windows XP from bootable USB-stick was developed by
ilko_t , jaclaz , cdob, porear and wimb at MSFN Forum
- Install XP from USB at MSFN Forum http://www.msfn.org/board/Install-XP-from-USBf157.
html
- List of FAQs http://www.msfn.org/board/FAQs-t116766.html
- More Info See Guide with ScreenShots
- More Help with Bookmarks is available in the Help_Info Folder in USB_MultiBoot.zip
- Use of MultiBoot.cmd and everything in this Guide is COMPLETELY at your own risk.
2. XP-Source Preparation - *** BEFORE YOU START ***
Take care that your XPSOURCE Folder is located on your Harddisk in a simple Path without
SPACES.
Copy the Content of your Windows XP Setup CD to your XPSOURCE Folder on Harddisk
Siginet's RyanVM Integrator or nLite can be used to Integrate Windows UpdatePacks in the
XP-Source.
http://integrator.siginetsoftware.com/index.php?download
http://www.nliteos.com/
Windows XP UpdatePacks and Addons:
http://www.ryanvm.net/msfn/
http://www.ryanvm.net/msfn/updatepack-sp2.html
http://integrator.siginetsoftware.com/index.php?addons
http://www.ryanvm.net/forum/
Supports the use of BTS DriverPacks located in OEM Folder on USB-Drive
http://driverpacks.net/DriverPacks/
For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled.
In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated
which appear in the
XP Setup BootFolder $WIN_NT$.~BT on USB-Drive and can prevent a lot of XP Install Boot
Problems.
First use RyanVM Integrator and then use DPsBase to Improve your XP-Source.
The program supplies a Customised presetup.cmd and changes the winnt.sif file for use of
DriverPacks.
The Complete XP-Source is Copied by USB_MultiBoot.cmd to XP LocalSource Folder
$WIN_NT$.~LS on USB-Drive
Computation of Estimated XP Folder Size is used to prevent USB-stick overflow
and includes $WIN_NT$.~BT + cmpnents + I386 + AMD64 + $OEM$ + OEM Folders.
Excluding LANG and WIN98X Folders from Copy to USB can be Selected
from USB_MultiBoot.cmd Main Menu, which reduces the XP-Source on USB-Drive by 135
MB
Reduction of the XP WINDOWS Folder can be achieved with nLite
but do NOT select Operating System Options-->Manual Install and Upgrade for
removal.
If you did you will get BSOD, error 0x0000006F during Text mode Setup of Windows XP.
======================================================================
===
3. Making Bootable USB-Drive with USB_MultiBoot.cmd
- Remove all other Removable Drives, like USB Backup Harddisks and Memory Cards
- Use USB-stick with High Read/Write Speed of about 15 MB/sec
- Unpack USB_MultiBoot.zip to your Harddisk in a simple Path without SPACES.
- Launch USB_MultiBoot.cmd and Display the Format Menu
- Format USB-Drive with FAT or NTFS - FAT32 is very SLOW for Install of XP
P) - PeToUSB - FAT Format - Max 2 GB
To Format USB-Drive : Enable Disk Format with LBA FAT16X
Do NOT Select here FileCopy of BartPE
FAT Format Supports Direct Booting with MS-DOS using MULTI_CONTENT
Install of XP from USB in 30 minutes - Buffalo FireStix 2 GB
H) - HP USB Disk Storage Format Tool V2.0.6 - NTFS Format - use X_CONTENT
NTFS Format Supports DOS Boot Floppy Images via GRUB4DOS Menu
Install of XP from USB in 16 minutes - Corsair Flash Voyager 4 GB
Do NOT use HP Tool for USB-Harddisks having more than 1 Partition
WARNING - HP Tool Formats whole Disk - Second Partition is Lost
N) - No Format - Use USB-Drive with FAT or NTFS Format by Windows XP
Or Update Existing Bootable USB-Drive having NTLDR Bootsector
- For USB-Harddisk use Main Menu Option 0) to Change USB-stick in USB-Harddisk.
Because that makes that rdummy.sys is used and this is essential for using USB-Harddisk.
rdummy.sys makes Fixed USB-Harddisk seen in XP Setup as Removable Device.
- Select from the Main Menu of USB_MultiBoot.cmd
1 - Give XP Setup Source Folder and give UserData for XP Setup
2 - Give USB-Drive Target
3 - Make Bootable USB-Drive with XP Setup Folders
U_11_Main_Selected.jpg ( 59.4K ) Number of downloads: 166
4. XP Setup Parameters in winnt.sif file and $OEM$ folder
Display and Edit of the 8 required parameters for Unattended Setup allows
to give your ProductKey and TimeZone used in Current_winnt.sif Copy of your winnt.sif file.
The Current_winnt.sif File is auto adjusted for Install of XP from USB and then
copied by USB_MultiBoot.cmd to $WIN_NT$.~BT folder on USB-Drive.
The file useraccounts.cmd with UserName is made in the $OEM$ Folder
copied to $WIN_NT$.~LS folder on USB-Drive.
CMDLINES.TXT is used for making UserAccounts and install of Registry Tweaks at T-12
Info see: http://unattended.msfn.org/unattended.xp/
For the Option Edit UserData for XP Setup we have:
A. Unattended Install - UserName = YourName
in winnt.sif file - unattendswitch="Yes" - UserName is used Automatically
useraccounts.cmd with UserName is created in $OEM$ Folder copied to USB-drive
B. Semi-Unattended Install - UserName = None
in winnt.sif file - unattendswitch="No" - UserNames are given Manually at Windows
Welcome Screens
useraccounts.cmd is Renamed to Inactive txt file in $OEM$ Folder copied to USB-drive
C. Undefined Install - UserName = Unknown
No Changes are made in winnt.sif file or $OEM$ folder
In all cases Selecting Cancel keeps given Settings for winnt.sif file and $OEM$ folder
Unchanged
Selecting Unattended Install in the Editor instead of Cancel will enable to skip the
Welcome Screens
by automatic adding the unattendswitch="Yes" Setting to the [Data] Section of the
Current_winnt.sif file.
The UserName given at Edit Screen 8 will not be used in the case of XPSOURCE made by
nLite.
OEM or nLite winnt.sif File is detected in XPSOURCE and Auto Changed for Install of XP
from USB.
In that case All Setup Parameters come from XPSOURCE and therefore Empty $OEM$_X
Folder is Selected.
Windows XP file SETUPLDR.BIN is Renamed to XPSTP according to the 5-letter limit
requirement
for making NTFS BootSector Files using MakeBS3.cmd of jaclaz
http://www.boot-land.net/forums/?showtopic=2362
In the Attended Install all Setup Parameters are given Manually during the GUI Mode of
Setup Windows XP.
For each XP Source the Program Supports to launch Unattended or Attended Setup.
For Attended Setup a second SetupLoader XATSP is made ,
where winnt.sif is Patched as winat.sif using gsar.exe
So the extra Setup Option does not take extra space from the USB-stick.
Attended Install is always available as Extra Option in the boot.ini Menu.
5. Install of XP from USB
Remove all other Removable Drives, like USB Backup Harddisks and Memory Cards
This will enable that your Computer Harddisk in XP Setup gets DriveLetter C
Boot with USB-Drive plugged and Press [Delete] or F2 to Enter BIOS Setup
Change BIOS Boot Settings:
Harddisk is First Boot Device Type and USB-Drive is seen as First Harddisk
Reboot from USB-Drive and Select 1. Begin TXT Mode Setup Windows XP
Use Only C: Drive of Computer Harddisk as Partition for Install of Windows XP
and then Select Quick Format with NTFS FileSystem, XP Install is Automatic
***** NEVER UNPLUG USB-Drive ***** Until After First Logon of Windows XP
New Harddisk and Creating Partitions after Booting from USB-Drive:
Direct after Deleting and Creating New partitions, Quit XP Setup with F3
OR Switch OFF your Computer and Boot in any case from USB-Drive again and
Run 1. TXT Mode Setup again so that DriveLetters get their Correct Value
So in this case one Boots ** TWICE ** in the TXT-mode Setup XP
USB_MultiBoot.cmd can make USB-stick to be seen in XP Setup as Boot Drive U:
In this preferred case the driveletters of Harddisk Partitions and Optical Drives
will get there desired normal value.
Otherwise USB-stick will get Drive Letter D: and other drives have shifted drive
letter.
The same shifting of drive letters occurs for Install from USB-Harddisk,
for which it is not possible to make it seen as Boot Drive U: by changing migrate.inf
After First Logon there is only 1 USB-Harddisk partition visible as Removable Drive.
After Reboot for Second Logon then all partitions of USB-Harddisk will become
visible
as Fixed Local Drives and the highest partition number of USB-Harddisk will get
DriveLetter D:
This reversal and use of DriveLetters might be unwanted and consequently
the use of USB-stick for XP Setup is Preferred
NON-STANDARD INSTALLS OF WINDOWS XP AND INSTALL OF WIN2003
Install of Windows XP from bootable USB-Drive
next to WINDOWS on the same or on a different partition of the harddisk,
is possible by proper manually adjustment in advance of the BOOT.INI file on the
USB-Drive.
Adjust BOOT.INI on USB-Drive: ( Or Select Correct boot.ini Using Option B in Menu
Screen )
For Install on the Second Partition, change partition(1) in partition(2)
For Install Next to WINDOWS, change WINDOWS to
what will be used as Install FolderName, e.g. WINDOWS.51
Windows Install Folder Name required according to MS-DOS 8.3 format
So these non-standard installs are still possible,
but require only small changes in the BOOT.INI on the USB-Drive in advance.
Otherwise ERROR Message for Setup of WINDOWS XP: WINDOWS\system32\hal.dll
file missing
will orccur on Reboot for GUI Mode.
6. Post-Install of Drivers and Programs
The Folder usb_cfg_extra provides a script for Windows Post-Install Wizard (WPI) -
http://wpiw.net/
WPI is very handy for the Automatic Install of Programs after Install of XP from USB.
In WPI script there is the option to run SFC /purgecache which deletes the dll cache
by deleting the files in Folder C:\WINDOWS\system32\dllcache
This is a very simple way to reduce the WINDOWS Folder Size by 360 MB
The Result is a XP WINDOWS Folder Size on Harddisk of only 785 MB inclusive all Updates.
======================================================================
==========
Advanced Use of USB_MultiBoot.cmd for making MultiBoot USB-Drives
7. Adding Extra Sources for Booting with BartPE, UBCD4WIN, Windows PE 2.0 and
Vista Setup
BartPE - http://www.nu2.nu/pebuilder/
or
UBCD4Win - http://www.ubcd4win.com/index.htm
can be added to USB-Drive by Selecting BartPE Source Folder in the Main Menu. Remove
with Cancel.
The Folder usb_cfg_extra provides scripts for BartPE Menu
Install of Vista from USB is supported and launched via GRUB4DOS Menu
http://www.msfn.org/board/vista-t114092.html&st=6
http://www.msfn.org/board/Install-Vista-fr...6.html&st=2
For Vista Install from USB, Remove on first Restart your USB-stick.
Overflow Control is used by measuring DiskSize, FreeSize, XP-Source and
Extra Source Folders using ASP Drive Object and Visual Basic Scripting.
http://www.w3schools.com/asp/asp_ref_drive.asp
http://www.robvanderwoude.com/index.html
8. Multiple XP Install from USB and Multiple PE (BartPE and UBCD4Win) Booting
from USB
Multiple XP Install from USB is Supported (max 9 sources)
http://www.msfn.org/board/SOLVED-Install-M...SB-t114543.html
Run USB_MultiBoot.cmd again using New XP Source and Empty XX_CONTENT Source
Folder
Multiple PE (BartPE and UBCD4Win) from USB is supported using Multi_Partition USBDrives.
Multi-Partition an USB-stick after using INSTALL_DUMMY.cmd from makebt Folder.
When dummy.sys is Installed in your OS, then USB-sticks are seen as Fixed Local Harddisks.
In that case you can make Multiple Partition USB-sticks with NTFS format,
allowing to combine BartPE and UBCD4WIN or different Vista Versions x86 and x64
http://www.msfn.org/board/Multiple-PE-from....html&st=11
http://www.911cd.net/forums//index.php?sho...20089&st=24
Run USB_MultiBoot.cmd again using New BartPE Source and
using Empty XX_CONTENT Source Folder and No Copy of XP Source

Windows NT Boot Error Msg: Missing Last Known Good Menu

Revision :2.1
SYMPTOMS
When your computer running Windows NT starts up, you may receive
on of the following error messages:
Windows NT could not start because the following file is
missing or corrupt: \%systemroot%\SYSTEM32\CONFIG\SYSTEMHardware
Profile/Last Known Good menu.
-or-
Windows NT could not start because the following are missing or corrupt:
\Winnt.sbs\system32\config\SYSTEMware profile/last known good menu.
You can attempt to repair this file by starting Windows NT setup.
-or-
Windows NT could not start because the following are missing or corrupt:
\Winnt\system32\config\SYSTEMware profile/last known good menu.
You can attempt to repair this file by starting Windows NT setup.
NOTE: %systemroot% is the installation directory for Windows NT.
CAUSE
Both the System and System.alt registry files are corrupted or missing.
RESOLUTION
Use the emergency repair disk (ERD) and select "inspect registry files" on the first menu selection screen.
On the second menu selection screen select "replace SYSTEM configuration." This will replace the damaged
System registry hive in the %systemroot%\System32\Config directory with the System hive on the ERD.
NOTE: Any system changes made after the ERD was last updated will be lost.
For additional information, please see the following article(s) in the Microsoft Knowledge Base:
ARTICLE-ID: 103280 (http://support.microsoft.com/kb/103280/EN-US/)
TITLE : Using an Emergency Repair Disk Created by Windows NT
If there is no ERD, a restore from a tape that contains a backup of the registry will be needed.
If you do not have an ERD or backup tape, you can recover the System hive by expanding it from the
%systemroot%\repair directory using the following steps:
1. Install a parallel copy of Windows NT to an NTTemp directory.
2. From a command line prompt, go to the repair directory of the original Windows NT installation.
For example: CD \winnt\repair
3. Use Expand.exe to expand the System._ file to System.
Expand SYSTEM._ SYSTEM
4. Copy the expanded SYSTEM file to the %systemroot%\System32\Config directory.
Copy System c:\winnt\system32\config
5. Try to boot back into the original Windows NT installation.

Installing Leopard on An unsupported MAC or with out the DVD

After, weeks of trying and failing the best method i found for installing Mac OS X 10.5 with out the DVD is with the help of an old ipod anything from 4th generation downwards with firewire support.

I have 2 links 1 to the program called XAR if you intend to reduce the processor requirements level. A How to would follow bellow but if you don't intend to go through the trouble you can download the one i made which has a limit of 497mhz, which is the second link. Just download it and replace the file in your ipod with this path

/System/Installation/Packages/OSInstall.mpkg


http://rapidshare.com/files/77763196/OSInstall.mpkg.html
http://rapidshare.com/files/77761804/xar-1.5.1.tar.gz.html


Dropping Installation requirements
If you are good with terminal, copy the following file from the mounted image (/System/Installation/Packages/OSInstall.mpkg somewhere so you can work on it (Desktop works well), for those not so good, you can use this terminal command which is useful anyway! I have found that depending on the build version or dmg you have, it may or may not show the folders. If it does show it, you don't have to do this next step.

Code:

defaults write com.apple.finder AppleShowAllFiles True

Followed by

Code:

Killall Finder

This will show all hidden files. To change it back, simply change the value to False and kill the Finder. Now, go into to the DMG, you should see some new stuff in there. You want to navigate to /System/Installation/Packages/OSInstall.mpkg, copy this file to the desktop.

Now create a folder called package on the Desktop. Fire up terminal again, navigate to the package folder. You should be at the home directory by default so you can type the following:

Code:

cd desktop/package

Now comes the fun part. Extract the xar archive and put in the same folder. Type the following:

Code:

./xar -x -v -f ~/Desktop/OSInstall.mpkg

If this fails, there is a problem with your xar installation. I will work with you to troubleshoot this. If it works you should see some files being extracted to the package folder. Great!

Hack that code!
Now, if you made it here we are getting close. Now, go into the package folder you made. You should see a file called Distribution. Good, back it up somewhere and then open the original with Textedit(I used Text wrangler). You should now see some wonderful code. You want to pay attention to this part of the script (changed to GM version):

Code:

 var minRam = 512;

 function checkSupportedMachine(machineType){
  // Fail on G3
  if (1 != system.sysctl('hw.vectorunit') ) {
   return false;
  }

  var badMachines = ['MacBook3,1','iMac','PowerBook1,1','PowerBook2,1', 'AAPL,Gossamer', 'AAPL,PowerMac G3', 'AAPL,PowerBook1998', 'AAPL,PowerBook1999'];
  
  if(machineType){
   var length = badMachines.length;
   
   // Fail if any of the compatible values match the list of badMachines
   for( var j = 0; j < length; j++ ){
    if(machineType == badMachines[j]){
      return false;
    }

   }
   
  }
 
  // require 867Mhz+
  if (system.sysctl("hw.cpufrequency") < 866000000) {
   return false; 
  }
   
  return true;
 }

Now, you can probably see where you need to make edits. First take a look at the G3 section. You can simply change it to return true, if you need to install on a G3. It has been said that you still can't install on a G3, I have no way to test this at the moment. I have to wonder though, why even add a section about G3s if it was just not an option (as in you couldn't even boot the disk as some have said). Same goes for the badMachines section. Or you can also simply remove the "bad machines" you have.

Now comes the cpu speed.

Code:

if (system.sysctl("hw.cpufrequency") < xxx000000) {
return false;

Where 'xxx' is the minimum processor speed. I have a DP 500 (which makes no difference, it is still seen at 500Mhz), so I changed mine to 499. I don't think you will gain any advantage by dropping it lower than the speed you need, other than having a disc that can be used on any Mac if you drop it to say, 0Mhz, although I would do 1Mhz as 0 may cause a problem.

Simple changing the false to a true will also work here. And is probably a more elegant solution throughout. I actually think removing the entire section would be the best solution. However, I have not tested this theory. My concern is that something else is there to be sure these things have returned values. Until we get a test on this, I am more inclined to say the section should remain in place, but simply be edited.

You can also edit the RAM and anything else really. Just be sure what you are doing will help you in some way

Now, save the document and exit textedit.

Wrap it up
Now we are going to reverse the step 3 by repackaging the altered contents. Hop back into terminal and type the following:

Code:

./xar -c ./ -v -f ~/Desktop/NewOSInstall.mpkg

And just like that, you should have a new package on your desktop.

New mpkg placement
Now that we have a new mpkg, navigate back to the /System/Installation/Packages folder. Rename the old OSInstall.mpkg, I usually do OSInstall.mpkg.old, Finder will ask if you want to append the new extension, say yes. Now, drop in the NewOSInstall.mpkg, rename it to OSInstall.mpkg.

You now have a disc image ready.


All things been equal this is the procedure in installing the Leopard on your ipod then you PC

1. Reset your iPod and force it into Disk Mode - Press and hold Menu + Center until you see the Apple logo. Then Press and Hold Center + Play/Pause. The screen should turn to gray-scale and show “OK to Disconnect” (circa old old ipods).
2. Connect the iPod to your computer (do not use a USB hub if possible).
3. iTunes will launch automatically and probably start syncing. Make sure “Enable Disk Use” is checked on the settings for iTunes and press Sync one more time.
4. Quit iTunes and launch the Activity Monitor and quit the iTunes Helper.
5. You should still see the iPod listed on your desktop as a mounted drive. If you don’t see the iPod mounted on the desktop, return to step 1.
6. Open Disk Utility
7. Select the iPod (the top one, mine is labeled 74.5 GB Apple iPod Media) then select the Partition tab.
8. Change the selection from “Current Partition Scheme” to “1 Partition”. Click on Options and select GUID Partition Table and press OK. (NOTE: If you are going to use a PowerPC based Mac, ie G4 or G5, you need to select Apple Partition Map here. GUID is for Intel Macs ONLY)
9. Give the Partition a name and select Partition. The system will ask you to authenticate.
10. Click on the Restore tab and drag the iPod partition to the Destination field
11. Drag the Leopard image file to the Source field and press Restore.
12. Once complete, open System Preferences and go to the Start up Disk option. Make sure you see the iPod listed there. Select the appropriate drive and click restart.
13. Install Leopard!

** If you are using a PowerPC Based Mac (G4, G5), you must use the Startup Disk utility in System Preferences to select the startup volume and reboot from this tool. Notes:

• It’s really important the iPod stay in Forced Disk mode. If you try and boot up the Mac with the iPod connected but not in Disk Mode, it won’t do anything

You can get a view on how to format your ipod from this video
http://www.youtube.com/watch?v=s1Bz88pN_zU