Solution : http://support.microsoft.com/kb/896861

1. When you login to the webconsole you get the error: Your OfficeScan Session has timed out. Please log in again
2. When you use the remote installerr you get the error: Incorrect parameter in the initialization file

You can fix this problem by change the NTFS rights (Everyone/modify) on the maps.

C:\Program Files (x86)\Trend Micro\OfficeScan\PCCSRV\TEMP
C:\Program Files (x86)\Trend Micro\OfficeScan\PCCSRV\Web_OSCE\Web_console

Please TrendMicro fix your installer!

# useradd newuser

Set a password for the new user

# passwd newuser

Once done, edit the ‘passwd’ file

# nano /etc/passwd

set the UID:GUD bits to 0:0. Say for example the new user is ‘newuser’, the line should look like

newuser:x:0:0::/home/newuser:/bin/bash


Extract to the SVN Repo Installer (from this zip) to: E/XBMC/plugins/programs/

Go to programs from the XBMC menu and run the script.

Tip: add the SVN Repo Installer to your favorites and run it from there to save memory.

Source: http://code.google.com/p/xbmc-xbox-skins/

1. This ISO (Custom XBOX HD Maker)
2. Auto installer deluxe (4.5 or higher) (Download: http://aideluxe.com)
3. Computer with an IDE connection
4. CD Burner
5. Screwdriver with a couple of tork plugs
6. Second-hand XBOX1 with remote (http://marktplaats.nl max €40)
7. XBOX1 component cable (http://bol.com €6, free shipping coupon @ http://retailmenot.com)

First download and burn the XBOX HD Maker and Auto installer Deluxe to a CD or DVD.

Then disconnect al the  IDE cables except the IDE CD player. Put the XBOX HD Maker CD in the computer. Start the pc and before the BIOS recognize the harddisk press the pause key. Now the boot process is on pause

Now remove the rubber feeds under the xbox. Then remove all the six tork screws (2 screws are under a sticker). Remove the disk bay (screw are under the IDE cable) and remove the 4 disk screws.

Pull out the IDE cable from your XBOX DVD player. When you start the XBOX now you see a red light is blinking. This is gooood

Now you must connect a video/scart cable (a tv is not necessary but without the cable the xbox cannot start) and power on the XBOX, let the red light blink 3 times and then put the IDE cable from the XBOX hard disk as fast as possible. Now the disk is unlocked so we can flash that XBOX FATX DISK.

Connect the IDE cable from the computer to the disk (primary master is the best, otherwise you can use the secondary master). Then press on the spacebar to continue the boot process and the BIOS must recognize the XBOX disk.

The pc must boot from CD and start the XBOX HD Maker Linux Distribution. Follow the steps on the screen. You must wipe the disk completely and rebuild it and create a new key (option 6 or 7)

Now you can connect the newly build disk to the XBOX and connect the CD player again. Connect the scart to your tv and boot the XBOX from the auto installed deluxe (AID) CD.

Follow the steps on screen, first make a MS Backup, so AID can copy all the necessary files to the XBOX, then choose the softmod option with virtual C drive. Choose XBMC as the default dashboard.

After the installation you can put out the AID CD and boot the XBOX. Now XBMC is started directly.

To make the XBOX 720P compatible (1080 is also possible but the poorly 733Mhz processor  doesn’t like that kind of high resolutions ) connect the component cable to the XBOX. Then run the “Enigmah Video Mode Switcher”. You can launch this from the XBMC > Programs (if you don’t have programs you can enable this in the option screen). Set the video mode from PAL60 to NSTC. Then reboot the XBOX and start the MS dashboard (easiest way is from file explorer default.xbe on the C:\). Now go to video and enable the 420 and 720 HD resolutions.

That’s it

Ps. The embedded AID XBOX media center is a little bit old. You can download a new build from: http://www.sshcs.com/xbmc/ or http://t3ch.yi.se/.
Ps2. The next time I i’ll softmod a XBOX1 i will create a youtube video.



Distributions with Built-in Support

UNetbootin has built-in support for downloading and installing the following distributions:

• Ubuntu (and official derivatives)
  • 6.06 LTS
  • 6.10
  • 7.04
  • 7.10
  • 8.04 LTS
  • 8.10
  • 9.04
  • Daily CD Images
• Debian
  • Stable/Etch
  • Testing/Lenny
  • Unstable/Sid
• Linux Mint
  • 3.1
  • 4.0
  • 5-r1
  • 6
• openSUSE
  • 10.2
  • 10.3
  • 11.0
  • 11.1
  • Factory
• Arch Linux
  • 2007.08
• Damn Small Linux
  • 4.4
• SliTaz
  • Stable
  • Cooking
• Puppy Linux
  • 4.00
• gNewSense
  • deltah-2.1
• FreeBSD
  • 6.3
  • 7.0
• NetBSD
  • 4.0
• Fedora
  • 7
  • 8
  • 9
  • 10
  • Rawhide
• PCLinuxOS
  • 2007
  • 2008
• Sabayon Linux
  • 4-LiteMCE
• Gentoo
  • 2007.0
  • 2008.0
• MEPIS
  • SimplyMEPIS 8
  • AntiX 8
• Zenwalk
  • 5.2
• Slax
  • 6
• Dreamlinux
  • 3.2
• Elive
  • Development
• CentOS
  • 4
  • 5
• Mandriva
  • 2007.1
  • 2008.0
  • 2008.1
• FaunOS
  • 0.5.4
• Frugalware Linux
  • Stable
  • Testing
  • Current
• xPUD
  • 0.8.9

sa-update -D

Restart Service

service spamassassin restart

Check version

perl -MMail::SpamAssassin -e ‘print $Mail::SpamAssassin::VERSION;’

-> Lets understand what’s Jumbo Frames first and how it benefits us … 

• Jumbo frames are Ethernet frames with more than 1,500 bytes of payload (MTU). Conventionally, jumbo frames can carry up to 9,000 bytes of payload.

• Jumbo Frames allow ESX Server to send larger frames out onto the physical network. The network must support Jumbo Frames end‐to‐end for Jumbo Frames to be effective.

• iSCSI with jumbo frames gives better or rather much better performance .If you are getting sluggish performance then try enabling jumbo frames 

So let’s activate it, I have used Jumbo frames only with SW initiator not HW one so if some can comment on how it works on HW it would be in for a great benefit.

Most probably you might have your VMkernel setup with 1500 MTU so we need to delete it and start over again. Its recommend to start from 0 but if you wish you can enable the jumbo frames on the fly, it won’t throw any errors.

In my case vSwitch1 was used as VMkernel for iscsi.

Step  1:
[root@esx sysconfig]# esxcfg-vswitch -d vSwitch1
Step 2:

Then I went ahead and did a listing

[root@esx sysconfig]# esxcfg-vswitch -l
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch0       32          3           32                9000    vmnic0

PortGroup Name      VLAN ID  Used Ports  Uplinks
VM Network          0        0           vmnic0
Service Console     0        1           vmnic0

As it can be seen no VMkernel

Then lets start the stuff ………

Step 3:

Add a vSwitch

[root@esx sysconfig]#  esxcfg-vswitch -a vSwitch1

Step 4:

List it….
[root@esx sysconfig]#  esxcfg-vswitch -l
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch0       32          3           32                9000    vmnic0
PortGroup Name      VLAN ID  Used Ports  Uplinks
VM Network          0        0           vmnic0
Service Console     0        1           vmnic0
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch1       64          1           64                1500
PortGroup Name      VLAN ID  Used Ports  Uplinks

Step 5:
Lets set the jumbo frames AKA MTU

If you wish you can execute the below command on the fly to your vSwitch without deleting it
[root@esx sysconfig]# esxcfg-vswitch -m 9000 vSwitch1
List it to see the diference
[root@esx sysconfig]#  esxcfg-vswitch -l
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch0       32          3           32                9000    vmnic0
PortGroup Name      VLAN ID  Used Ports  Uplinks
VM Network          0        0           vmnic0
Service Console     0        1           vmnic0
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch1       64          1           64                9000
PortGroup Name      VLAN ID  Used Ports  Uplinks
As it can be seen MTU is now 9000 not 1500

Step 6 :
Lets assign a NIC to the newly created vSwitch
[root@esx sysconfig]# esxcfg-vswitch -L vmnic1 vSwitch1
The result
[root@esx sysconfig]# esxcfg-vswitch -l
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch0       32          3           32                9000    vmnic0
PortGroup Name      VLAN ID  Used Ports  Uplinks
VM Network          0        0           vmnic0
Service Console     0        1           vmnic0
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch1       64          2           64                9000    vmnic1
PortGroup Name      VLAN ID  Used Ports  Uplinks
Step 7:
Lets give it a port group
[root@esx sysconfig]#  esxcfg-vswitch -A VMkernel vSwitch1
Step 8:

Lets see Whether we got desired output
[root@esx sysconfig]#  esxcfg-vswitch -l
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch0       32          3           32                9000    vmnic0
PortGroup Name      VLAN ID  Used Ports  Uplinks
VM Network          0        0           vmnic0
Service Console     0        1           vmnic0
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch1       64          2           64                9000    vmnic1
PortGroup Name      VLAN ID  Used Ports  Uplinks
VMkernel            0        0           vmnic1
Step 9:

Now lets give it IP
[root@esx sysconfig]#  esxcfg-vmknic -a -i 192.168.0.11 -n 255.255.255.0 -m 9000 VMkernel
Hmm the output is ……..
[root@esx sysconfig]#  esxcfg-vswitch -l
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch0       32          3           32                9000    vmnic0
PortGroup Name      VLAN ID  Used Ports  Uplinks
VM Network          0        0           vmnic0
Service Console     0        1           vmnic0
Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch1       64          3           64                9000    vmnic1
PortGroup Name      VLAN ID  Used Ports  Uplinks
VMkernel            0        1           vmnic1
Property of vmknic
[root@esx sysconfig]#  esxcfg-vmknic -l
Interface  Port Group/DVPort   IP Family IP Address                              Netmask         Broadcast       MAC Address       MTU     TSO MSS   Enabled Type
vmk0       VMkernel            IPv4      192.168.0.11                            255.255.255.0   192.168.0.255   00:XX:83:91:23:14 9000    65535     true    STATIC

Source: http://moizzy.blogspot.com/2010/02/configure-jumbo-frames-in-esx-4-for.html

http://g0tmi1k.blogspot.com/2009/07/video-tutorial-how-to-crack-wpawpa2.html