in here I put the proof of that stuff and also I upload the documentation in PDF format.

hope after this will no more question again....

What is SAP IDES and System Requirement for installations?

System Requirement to install IDES

For installing SAP IDES on a Laptop, you need:

Pentium 3/Pentium 4 with any CPU
100 GB HDD
min. 1 GB RAM

What is SAP IDES (Internet Demonstration and Evaluation System)?

SAP IDES is a normal R/3 but with lots of DEMO data.

The system that contains several sample companies typifying relevant business processes. It is simple to use and has a variety of master and transaction data, and is used for demos, online/classroom training, and presentations. Potential customers use IDES to trial and test software via Internet.

SAP IDES – the "Internet Demonstration and Evaluation System" in the R/3 System, represents a model company. It consists of an international group with subsidiaries in several countries. IDES contains application data for various business scenarios that can be run in the SAP System. The business processes in the IDES system are designed to reflect real-life business requirements, and have access to many realistic characteristics. IDES uses easy-to-follow business scenarios to show you the comprehensive functions of the R/3 System. The focal point of IDES, however, is not the functionality itself, but the business processes and their integration.

.


- Used Kernel v9.0.0
- Included Darwin (SSE2), x86, EFI (SSE3) bootloader
- Useless features removed
- Included Indonesian Install Guide
.

Due to popular demand i decided to share this Hacking tool: " Live CD for Wireless hacking"

This version is for all systems except systems with the Intel B/G wireless cards (IPW2200).

- Live CD with all the tools you need to hack a WLAN / wireless Access point -
Linux Live-CD - OS runs from CD - 635 mb - .iso
- also used by the FBI ...


WEP Hacking - The Next Generation

WEP is an encryption scheme, based on the RC-4 cipher, that is available on all 802.11a, b and g wireless products. WEP uses a set of bits called a key to scramble information in the data frames as it leaves the access point or client adapter and the scrambled message is then decrypted by the receiver.

Both sides must have the same WEP key, which is usually a total of 64 or 128 bits long. A semi-random 24 bit number called an Initialization Vector (IV), is part of the key, so a 64 bit WEP key actually contains only 40 bits of "strong" encryption while a 128 bit key has 104. The IV is placed in encrypted frame's header, and is transmitted in plain text.

Traditionally, crac*ing WEP keys has been a slow and boring process. An attacker would have to capture hundreds of thousands or millions of packetsâ?"a process that could take hours or even days, depending on the volume of traffic passing over the wireless network. After enough packets were captured, a WEP crac*ing program such as Aircrac* would be used to find the WEP key.

Fast-forward to last summer, when the first of the latest generation of WEP cracking tools appeared. This current generation uses a combination of statistical techniques focused on unique IVs captured and brute-force dictionary attacks to break 128 bit WEP keys in minutes instead of hours. As Special Agent Bickers noted, "It doesn't matter if you use 128 bit WEP keys, you are vulnerable!"

Basic Directions:

1)Boot from cd
2)get the wep key
3)write it down
4)reboot into windows
5)connect using wep key.

.
.

Windows XP SP3 build 3205

New Functionality

The following is a list of functionality that is included with the service pack, which is not addressed by the included hotfixes and security updates.
The Security Options control panel in Windows XP Service Pack 3 now has more descriptive text to explain the settings and prevent incorrect configuration of settings.
In System Center Essentials for Windows XP Service Pack 3, Administrators and Service entries will be present by default on any new instance of policy.
Additionally, the UI for the "Impersonate Client After Authentication" user right will not be able to remove these settings.
Windows XP Service Pack 3 includes improvements to black hole router detection (i.e., detecting routers that are silently discarding packets), and turns it on by default.
Microsoft Kernel Mode Cryptographic Module (FIPS.SYS) is a FIPS 140-1 Level 1 compliant, general-purpose, software-based, cryptographic module residing at the Kernel Mode level of the Windows Operating System. It runs as a kernel mode export driver (a kernel-mode DLL) and encapsulates several different cryptographic algorithms in an easy-to-use cryptographic module accessible by other kernel mode drivers. It can be linked into other kernel mode services to permit the use of FIPS 140-1 Level 1 compliant cryptography.
https://www.microsoft.com/technet/archive/s...p.mspx?mfr=true

NAP is a policy enforcement platform built into Microsoft Windows Vista, Windows Server 2008 (now in beta testing), and Windows XP Service Pack 3 (which includes the NAP Client for Windows XP, now in beta testing) that allows you to better protect network assets by enforcing compliance with system health requirements. With NAP, you can create customized health policies to validate computer health before allowing access or communication, automatically update compliant computers to ensure ongoing compliance, and optionally confine noncompliant computers to a restricted network until they become compliant. http://www.microsoft.com/technet/network/nap/napfaq.mspx
As in Windows Server 2003 Service Pack 2, and Windows Vista, the user may now complete setup without having to provide their product key. They will be prompted for the product key as part of Genuine Advantage during subsequent use.


Current bugs:

After installing Windows XP Service Pack 3 Beta, the Address Bar feature will be removed from the Taskbar
The Address Bar feature will not be present in Windows XP Service Pack 3. This change is in response to a regulatory request and is present beginning with Windows XP Service Pack 3 Beta.
There is a bug related to the removal of the Address Bar in the Windows XP Service Pack 3 Beta. The user can return the Address Bar to the taskbar by unlocking the taskbar and choosing Toolbars > Links.
This is a known issue and will be specifically addressed in a later milestone of the Windows XP Service Pack 3 beta program, where the end user’s ability to restore the Address Bar feature will be eliminated.

Windows Media Center devices will not receive Media Center updates
Users of Windows 2005 Media Center systems that install Windows XP Service Pack 3, will not be able to receive the latest Media Center updates for those systems. There is no workaround in the Beta.

Installing Windows XP Service Pack 3 on Windows 2005 Media Center may affect the ability to connect to Media Center Extender devices such as the Windows Media Center Extender for Xbox. There is no workaround in the Beta.
Users of Windows XP Starter Edition should not install Windows XP Service Pack 3 Beta. When a user installs the Windows XP Service Pack 3 Beta on top of Windows XP Starter Edition, they will be unable to log in after the next reboot. Alternatives for upgrading these systems will be made available at a later time, and may be addressed as part of a separate beta program.

With IE7 installed, double clicking on the IE icon on the desktop creates a shortcut instead of launching IE
When double clicking on the desktop icon of IE, a new shortcut is created instead of opening a browser page. This is a known compatibility issue with IE7 and Windows XP Service Pack 3. There is no workaround in the Beta.

Using SFC with specific command line switches will cause IE7 to unsuccessfully attempt downgrade to IE6
On a machine with IE7 and the Windows XP Service Pack 3 Beta installed, if the user attempts to run the command “sfc /scannow” from the command line, IE will unsuccessfully attempt to be downgraded to IE6. From that point on Internet Explorer will be unusable on that machine. This is a known compatibility issue with IE7 and Windows XP Service Pack 3. There is no workaround in the Beta.

IE7 version is reported as Version 6
On a machine with the Windows XP Service Pack 3 Beta installed, when viewing the About dialog via the IE7 Help menu, the IE version is reported as Version 6, even though it is IE7. This is a known compatibility issue with IE7 and Windows XP Service Pack 3. There is no workaround in the Beta.

Multilingual User Interface (MUI) Compatibility
MUI Language Packs specific to Service Pack 3
As of the Windows XP Service Pack 3 Beta, users may use the existing released MUI Language Packs. However, MUI Language Packs will be updated and re-released before the official Windows XP Service Pack 3 release. MUI Language Packs specific to Service Pack 3 will be available in a later milestone of the Windows XP Service Pack 3 beta program.
Issues with all MUI Language Packs
Users who have Multilingual User Interface (MUI) Packs installed, and then install Windows XP Service Pack 3, will find that some User Interface (UI) content is not localized. This unlocalized content instead is displayed in English. There is no workaround in the Beta.

The components that are affected are:
* Remote Desktop Connection (RDC)
* Microsoft Management Console 3.0 (MMC)

Windows XP Service Pack 3 users who install and enable Arabic, Hebrew or Japanese MUI packs will find that some UI content is not localized. This unlocalized content instead is displayed in English. There is no workaround in the Beta.

The components that are affected are:
* Run Dialog Box
* "Desktop" tab in the "Display Properties Window"
* "File and Folders" option in Start -> Search
* " Folder Options" Window under Start->Run->Control [Control Panel] -> Folder Options
* Start -> Programs->Accessories Node
* Control Panel
* Administrative Tools Window
* My Computer and My Documents icons on the desktop

Issues with German, Chinese Traditional, Swedish, or Turkish MUI Language Packs:
XP SP3 users who install and enable German, Japanese, Chinese Traditional, Swedish, Turkish MUI Language packs will find unlocalized content in some UI. This unlocalized content instead is displayed in English. There is no workaround in the Beta.

The components that are affected are:

* “Display properties” dialog tab in desk.cpl
* “Windows Script Host Settings” dialog window of wscript.exe

Issues with MUI Language Packs and Microsoft Terminal Services Commands (MSTSC) Version 6:
Users who have KB925877 (RDC6.0 MUI pack) installed and upgrade to XP SP3 will not be able to use RDC in any language other than English. The RDC client UI will not launch when the user switches to any MUI language other than English. The workarounds for the Beta are to uninstall KB925877 (RDC6.0 MUI pack) prior to upgrading to XP SP3, or to only use the English language version of the client if KB925877 is installed.

Issues with Windows Media Player when upgrading from original release of Windows XP:
In a specific upgrade scenario, Windows XP Service Pack 3 users will be unable to launch Windows Media Player.

That scenario is when a user starts from the original release of Windows XP, creates installation media using the SPCD CD image, and then upgrades to Windows XP Service Pack 3. After the installation, when attempting to launch Windows Media Player, they will see the following error message: "Windows Media Player is not installed properly and must be reinstalled. Do you want to install the Player from the Microsoft Web site?"

The workaround for this issue in the Beta is to first install Service Pack 1 or Service Pack 2, before installing Service Pack 3.

.