Finally, Kalyway 10.5.2 installed on Dell Latitude 620

Make sure record all hardwares before start.


Prepare partition for Mac:
Partition your HDD using gparted live cd or Ubuntu dekstop 8.10
Kalyway will use 6-7GB. Prepare 10GB for Kalyway, format with NTFS or FAT32

Download Leopard HDD Installer Helper v3.0
Prepare partition for Leopard HDD Installer (faster install compare with installation from DVD Drive)
Create partition 4-5GB formatted with Fat32, this will use to dump Leopard DVD. After Leopard installation finish, you can delete this partition.
For installation, please follow documentation from Leopard HDD Installer Helper v3.0

VGA Intel 945 Express -- use Intel GMA 950 build-in at Kalyway

NIC Broadcom Netxtreme 57xx 14E4:1600 installed using patches from Taruga at Insanelymac

Sigmatel HDA 8384:7690 installed using AppleHDA patch & Sigmatel 9200 from Insanelymac

Dualboot with WindowsXP

Thanks to indowebster for Kalyway. To burn the Kalyway 10.5.2 DVD installer, you should use burning software which support HFS+ file system.

Sleep function working but unable to wake up, so please disable this function

wifi Intel Pro Wireless 3945ABG not work, not detected. Change the wlan to Dell Wireless 1390, detected & working smooth...

---------------------------------x

Testing Machine Using VMware ESX

Main reason using Virtualization: Maximize space and server utilization and environment friendly
Warning : for 1 physical CPU only

Download VMware-VMvisor-InstallerCD-3.5.0_Update_4-153875.i386.iso from VMWARE websites.
Burn the ISO to CD
Boot your Server or PC using the CD.
Follow the guidance to install or you can download the pdf installer from VMware website.
Check the HW compability at VMware website, very limited hardware supported.
On board NIC usually not detected, test using PCI NIC 10/100 and its work.

-----------------------
To go to linux like console at VMware ESX
press "ALT+F1"
type "unsupported"
all without quote

--------------------------------------
Cloning OS inside VM

You can also use vmkfstools
o Using the VI Client create a new VM on the ESX host and specify any size hard drive (It will not let you create a VM without a hard drive).
o Edit the new VM's settings and remove and delete the hard drive
o Login to service console
o To login interactively use ALT+F1 and type "unsupported"
o The format for vmkfstools -i (import) is source vmdk filename first followed by the destination vmdk filename (use the path of the new VM you created)
o Type "vmkfstools -i /vmfs/volumes/ESX-Local/templates/2003-template.vmdk /vmfs/volumes/ESX-Local/mynewvm/mynewvm.vmdk"
o Edit the VM's settings, add a Hard Disk, select use an existing disk and browse to your VM's directory and select your new disk file
o Once the VM is powered on you can then run a utility such as NewSid to change the SIDs on the new VM. http://www.microsoft.com/technet/sysinternals/Security/NewSid.mspx (in my case i am not use this step)
o You can also run Sysprep on the original VM prior to copying it. http://technet.microsoft.com/en-us/library/bb457067.aspx (in my case i am not use this step)
--------------------------------------
Downgrade VM partition capacity

For example, you create a disk with 40GB size, but when you realize this size is too big, you only use 10GB. 30GB wasted. So you need to down size to 20GB. Use VMware Converter Tool. Source and destination same VMware machine.
--------------------------------------

Extend Size of VirtualBox Harddisk (vdi)

When create vdi, sometimes not well planned. The partition is too small. We have to extend it.
Preparation :
- gparted live CD or Ubuntu live CD Desktop edition 8.10 with Gparted inside it.
- bootbuild

1. Make a new vdi partition with bigger size as required.
2. Using VirtualBox, Clone the vdi disk content with gparted from Ubuntu live CD (Boot from cd with 2 vdi hdd attached).
3. When try to boot the new cloned vdi disk, error will come. Fix using bootbuild.
4. Retry to boot new vdi disk, should be ok.
5. (optional) delete old vdi disk.
6. Done.

Wis rampung...

Spool or Print Directly

My little experience. This make our application which running on Windows Server 2003 became unstable and we request support from Developer team from regional.It started from Intermec barcode printer which failed to print after 2-3 times printing. We have to turn the printer off then turn it after 2nd or 3rd printing to make sure printing process done smoothly. The application team suspect windows spooling problem, they change the Spool option to Print directly to the printer.
After Intermec printer firmware upgraded to 10.3.1 the printer run normal. But another problem came when users make wrong printing to turned off printer. The application is hang. Event viewer show "Application Hang" without no additional information. After investiges, we have conclusion: Dont use "Print directly to the printer" option if your printer turn off at night. Because Windows will send the command to the printer directly and it will wait until printing process done, if the printer cannot be reach, the application will wait forever. To stop this problem, you can stop the restart spooling service.

One day before... We have prepare to reinstall the whole... starting from the scratch... luckily we found the user which sent the wrong print job.

Wis wae...

Running Ubuntu apt-get behind MS ISA proxy

1. Download ntlmaps deb package for Ubuntu from another PC. This package use for authentication to MS ISA
2. Install ntlmaps deb package with sudo dkpg –i ntlmaps.deb (ntlmaps_0.9.9.0.1-10_all.deb for Ubuntu 8.10). At the end of installation process it will asking for :
- Port 5865 (or just follow the default port)
- MS ISA server address / ip and port
- Windows username and password to authenticate to MS ISA
3. After installation finish perform
export http_proxy=http://127.0.0.1:5865
4. Done
5. You should able to run apt-get. For example: sudo apt-get update, sudo apt-get install squid

Example to use it :
service ntlmaps start
export http_proxy=http://127.0.0.1:5865
apt-get install winbind

Wis wae...