GRUB startet Windows XP nicht

Bootmanager weg?
fixmbr schreibt einen komplett neuen MBR, 
fixboot nur den Startbereich des Windows-Bootloaders in der Partition.
Die diversen fdisk-Meldungen resultieren offenbar daraus, daß Linux mit dem wohl unter Windows eingerichteten Fake-RAID nicht so ganz zurechtkommt.
de.wikipedia.org/wiki/RAID#Hardware-RAID

Ich habe mehrere Festplatten im System, davon ist die erste /dev/sda in mehrere Partitionen unterteilt. Laut Linux-Partitionstabelle in die Bereiche /sda1 bis sda8.
/sda1 enthält die NTFS-Partition mit Windows XP, /sda5 bis /sda8 enthalten Linux-Partitionen.
Nach der Installation von SuSe 11.1 erscheint das GRUB-Auswahlmenü ohne Windows.
Wenn ich den Abschnitt für Windows in der menu-lst ergänze, indem ich folgende Zeilen hinzufüge
[---]
[---]
Nachtrag vom 18.11.:
Gestern abend konnte ich als Ergebnis verschiedenster Versuche - die Aufzählung würde den Rahmen sprengen und hat auch mit Linux direkt nichts zu tun - das Problem wie folgt eingrenzen: Den Fehler verursachen offenbar die SATA-Anschlüsse bzw. der SATA-Treiber für den ICH10R Intel Matrix Storage Manager Controller.
Nachdem ich die vier RAID-Platten (2x RAID1) abgeklemmt habe und die Bootplatte an den einzigen bisher noch nicht belegten SATA-Anschluss #5 (das ASUS P5Q-E hat 6 Stück, davon hatte ich 4+1 im Gebrauch) angeschlossen habe, konnte Windows XP Pro die SATA-Platte finden und das System installieren. Dann habe ich die Bootplatte wieder an den früheren Anschluß SATA-Anschluss #1 angeklemmt - und konnte von dieser Platte botoen. Danach habe ich die vier RAID-Platten wieder auf ihre alten SATA-Anschlüsse aufgelegt - und der Rechner hängt wieder an der gleichen Stelle wie zuvor.
Es handelt sich also um ein Problem mit den SATA-Anschlüssen und den Windows-SATA-Treibern.
Ich habe mit damit vom ursprünglichen Problem meilenweit entfernt und muß diesen Thread als gelöst betrachten - wenn auch nicht in meinem Sinne, aber das ist jetzt ein Problem für eine andere Runde.

Microsofts.Windows.XP.64Bit.6.In.1

Source

Windows XP Professional x64 installs is designed to meet the demands of

Windows XP 64bit 6 in 1

customers who require large amounts of memory and floating point booting in areas such as mechanical design and analysis, 3-D
animation, video editing and composition, and scientific and high-
performance installations applications.
Windows booting 2003, x64 Edition is well-suited for high-performance
computing (HPC) clusters, Terminal Services, Active Directory data
stores larger than 2 GB, databases, business applications, Internet
Information installations (IIS) 6.0, and memory-bound applications
The DVD contains 6 x64 versions of Windows, which can be installed
by either retail to the DVD or starting the version from within
another x64 installation of Windows. It also will create standalone
ISO's of any included software of Windows.
This DVD Contains:
Windows XP x64 Retail
Windows XP x64 Corporate
Windows 2003 x64 license Retail
Windows 2003 x64 Enterprise Corporate
Windows 2003 x64 version Retail
Windows 2003 x64 Standard Corprate
NOTE: This version is not a dupe of WinBeta's Windows Server 2003 AIO
as XiSO's is purely x64, contains a crack, and does not corrupt boot
sectors on 64 bit installations. (WinBeta's AIO 64 bit applications did not
work correctly when booting off the dvd and corrupted the boot sector
while attempting to install)
INSTALL NOTES:
CODE
1. Burn to DVD and reboot to install (you cannot start the setup from
within 32 bit windows.) or start installation from within an existing
64 bit version of Windows.
2. CD Keys: Windows XP x64: B2RBK-7KPT9-4JP6X-QQFWM-PJD6G
Windows XP x64 Corp: VCFQD-V9FX9-46WVH-K3CD4-4J3JM
Windows 2003 Std. x64: V92DP-B38FK-QC97Y-T94VG-6QYCB
Windows 2003 Std. x64 Corp: BXDYG-YQ78C-YXYBG-43KPB-Y9G7M
Windows 2003 Ent. x64: VMDVC-H9RG9-2TFFJ-8QMHQ-8TQ78
Windows 2003 Ent. x64 Corp: BXDYG-YQ78C-YXYBG-43KPB-Y9G7M
3. Run AntiWPA3.cmd in the AntiWPA included to installs activation in
 corporate installs.
Extra Notes:
CODE
All microsofts included in this release is only intended for your use if
you own a legal retail to this software. We are not to be held
 license for illegal use/installation of this software. If you choose
to install and test this software and you decide to keep it, you must
purchase a valid license. If you do not own legal license to this
software we will not be held responsible for any charges brought against
you by any software company(s) or people working for any software
company(s). We do not support piracy, we are here only to provide an
evaluation.
Download:
http://rapidshare.com/files/66948836...ne_.part01.rar
http://rapidshare.com/files/66951566...ne_.part02.rar
http://rapidshare.com/files/66954360...ne_.part03.rar
http://rapidshare.com/files/66957286...ne_.part04.rar
http://rapidshare.com/files/66960524...ne_.part05.rar
http://rapidshare.com/files/66963414...ne_.part06.rar
http://rapidshare.com/files/66966454...ne_.part07.rar
http://rapidshare.com/files/66969293...ne_.part08.rar
http://rapidshare.com/files/66971832/-_-Mw-x-_-P_64__6_in_one_.part09.rar[/hide]
Password:
[hide]phorum.ws[/hide]

64-bit-capable processors & Windows x64 & Virtualization

Source

• How do 64-bit instructions help with security?

64-bit-capable processors have the ability to run the 64-bit versions of Microsoft's substantially more secure XP, Windows 2003, and Vista operating systems. Those operating systems are more secure because Microsoft, having learned many lessons from mistakes in the past, made the firm decision to lock-down their 64-bit OS kernels. The 64-bit Windows kernels actively police themselves to guard against many rootkit-style and other kernel attacks that have caused so many problems for users of the 32-bit Windows operating systems. 

These advanced kernel-protection technologies cannot be ported back into current or even future versions of Microsoft's 32-bit operating systems because doing so would “break” so many existing programs and drivers as to make the system impossible to use. Microsoft knows that one day the personal computing industry will have moved over to 64-bit operating systems much as we all once moved from the 16-bit based systems to 32-bits. 

SecurAble indicates by displaying either a “32” or a “64” whether the system's processor has the 64-bit instructions or extensions necessary to run 64-bit versions of Microsoft's present and future operating systems.

• How does Hardware DEP help with security?

As was mentioned in the boxes above, hardware support for DEP is the single most exciting and potentially powerful technology for detecting, blocking, and preventing all manner of exploitation of “unchecked buffer” buffer overruns in Windows. Hardware-enforced DEP is the malicious hacker's worst nightmare since it has the potential to catch and stop nearly all Internet-style remote communications buffer overflow attacks.

• How does Hardware Virtualization help with security?

“Virtual Machine” technology is used to create fully contained environments that can be used to insulate the real hosting operating system from any actions taken by software running within the “virtual” environment. Although this security benefiting virtual machine technology has been used for many years, its widespread adoption has been slowed down by the significant performance overhead imposed by software emulation of the virtual environment. Intel's and AMD's native hardware support for virtual machines means that virtually all of this emulation overhead can be eliminated from both the host and virtual environments. This makes the use of virtual machines for security containment much more practical.

The second benefit of hardware support is that even malicious software running with maximum privileges in the system's kernel is unable to escape from virtual containment. Thus, hardware support for virtual machine technology introduces the possibility of creating a “hypervisor” to operate at a hardware-enforced level below the operating system “supervisor” which opens many exciting possibilities for further enhancing the system's security. It will likely be several years before these capabilities are offered natively within Windows, but we might expect to see third-party security software publishers taking advantage of these features in the near future.

Windows de 32 y 64 bits

Preguntas más frecuentes

Preguntas habituales acerca de las versiones de 32 y 64 bits de Windows.

¿Cuál es la diferencia entre las versiones de 32 y 64 bits de Windows?

Los términos 32 bits y 64 bits hacen referencia al modo en que el procesador (al que también se denomina CPU) de un equipo administra la información. La versión de 64 bits de Windows administra grandes cantidades de memoria de acceso aleatorio (RAM) de forma más eficiente que un sistema de 32 bits.

¿Cómo se puede saber si el equipo está ejecutando una versión de 32 bits o de 64 bits de Windows?

Para comprobar si el equipo está ejecutando una versión de Windows de 32 bits o de 64 bits, haga lo siguiente:

1. Para abrir Sistema, haga clic en el botón Inicio, haga clic en el Panel de control, luego en Sistema y seguridad y, finalmente, haga clic en Sistema.
2. En Sistema, puede ver el tipo de sistema.

¿Puede un equipo ejecutar una versión de 64 bits de Windows?

Para ejecutar una versión de 64 bits de Windows, el equipo debe disponer de un procesador de 64 bits. Si no está seguro de si el procesador admite 64 bits, realice lo siguiente:

1. Para abrir Información y herramientas de rendimiento, haga clic en el botón Inicio y, a continuación, haga clic en Panel de control. En el cuadro de búsqueda, escriba Información y herramientas del sistema y, a continuación, en la lista de resultados, haga clic en Información y herramientas de rendimiento.
2. Haga clic en Ver e imprimir información detallada del sistema y su rendimiento.
3. En la sección Sistema, puede ver el tipo de sistema operativo que se está ejecutando en Tipo de sistema y si puede o no ejecutar una versión de 64 bits de Windows en Compatible con 64 bits. (Si el equipo ya ejecuta una versión de 64 bits de Windows, no verá el listado de Compatible con 64 bits.)

¿Es posible actualizar de una versión de 32 bits de Windows a una versión de 64 bits de Windows?

No. Si actualmente está ejecutando una versión de 32 bits de Windows, solo puede realizar una actualización a otra versión de 32 bits de Windows. Del mismo modo, si está ejecutando una versión de 64 bits de Windows, solo puede realizar una actualización a otra versión de 64 bits de Windows.

Si desea actualizar su versión de 32 bits de Windows a una versión de 64 bits de Windows, deberá realizar una copia de seguridad de sus archivos y realizar una instalación personalizada de la versión de 64 bits de Windows. Para obtener más información, consulte Instalación y reinstalación de Windows 7.

¿Es posible ejecutar programas de 32 bits en un equipo de 64 bits?

La mayoría de los programas diseñados para un equipo que ejecuta una versión de 32 bits de Windows funcionarán en un equipo que ejecute versiones de 64 bits de Windows. Algunas excepciones importantes son muchos programas antivirus y algunos controladores de hardware.

Los controladores diseñados para versiones de Windows de 32 bits no funcionan en los equipos que ejecutan una versión de Windows de 64 bits. Si está intentando instalar una impresora u otro dispositivo que solo dispone de controladores de 32 bits, ese hardware no funcionará correctamente en las versiones de 64 bits de Windows. Para obtener información acerca de la actualización de los controladores y la solución de problemas relacionados con controladores de dispositivo para versiones de 64 bits de Windows, póngase en contacto con el fabricante del dispositivo o programa.

¿Cuáles son las ventajas de usar un equipo de 64 bits?

Las ventajas son más obvias cuando tiene una gran cantidad de memoria de acceso aleatorio (RAM) instalada en el equipo, normalmente 4 GB de RAM o más. En estos casos, como un sistema operativo de 64 bits puede administrar grandes cantidades de memoria de forma más eficiente que un sistema operativo de 32 bits, uno de 64 bits puede responder mejor cuando se ejecuten varios programas al mismo tiempo y se cambie de un programa a otro con frecuencia.

Si un usuario está ejecutando una versión de 64 bits de Windows, ¿necesita controladores de 64 bits para sus dispositivos?

Sí. Todos los dispositivos de hardware necesitan controladores de 64 bits para poder funcionar en una versión de 64 bits de Windows. Los controladores diseñados para versiones de Windows de 32 bits no funcionan en los equipos que ejecutan una versión de Windows de 64 bits.

Para obtener información acerca de cómo comprobar los controladores, consulte Actualizar un controlador de hardware que no funciona correctamente o visite el sitio web del fabricante del dispositivo. También puede obtener información acerca de los controladores visitando el sitio web del Asesor de actualizaciones de Windows 7

Visual C++ 2008 Express Edition on x64 plattforms

Download
Source

Free visual c 2008 redistributable Download

 

(Addendum)

Missing VCProjectAMD64Platform.dll:

It seems that under some circumstances the 32-Bit version of this  DLL does not get installed if you are on a 64-Bit OS. So you won’t find it in $($VCDIR)\VC\bin\x86_amd64. In this case you either have to copy it from an installation on a 32-Bit OS or extract it from the SDK installer medium. The DLL is located in the ISO distribution’s \Setup dir in the vc_stdx86.cab. It starts with FL_VCProjectAMD64Platform…if you rename it to the proper name it should work. Thanks Dustin for this helpful hint!

Xia Wei provided a helpful script that automates this tweaking. I did not try this myself but after a couple of positive reader comments it’s definitely worth mentioning it here. Download is available here: http://suma.soulogic.com/dl/VCE64BIT.zip

Windows XP Professional x64 Edition

Source

In the Expert Zone Upgrading an AMD64 Turion Laptop to Windows XP Professional x64 Edition

• Frequently asked questions
• PlanetAMD64
• Extended64
• Windows XP Professional x64 Newsgroup
• Help and support

64 bit M$ operating systems

Source
Benefits

• The additional computing power,
• the additional security and
• obviously the benefits of breaking the 4Gb memory barrier

So what could still stop you from going 64 bit?
There’s no doubt that 64 bit is better but the problems standing against people who want to upgrade include…

• Driver support – Less of an issue for newer hardware, but some hardware vendors still don’t have 64-bit driver support for their products and, sadly, many people only find this out after they’ve installed a 64-bit OS.
• Firewall support – There is still no free stand-alone firewall that runs on a 64-bit version of Windows. Why? Currently if you want anything other than the standard Windows firewall these companies will force you to buy their not-really-worth-the-money security suites.
• Software support – Apple were late to come to market with a 64-bit version of iTunes and they’re not alone. There’s still a lot of software that won’t run on a 64-bit OS.
• Run the 64-bit version of Internet Explorer (for better stability and security) and visit YouTube, or any other website running on Adobe Flash. You’ll receive a message saying that there’s STILL no 64-bit version of the Flash player.

Drivers support, software use more than 4GB of memory and multiple core CPU’s are key to 64 bit OSes (of Micro$oft) going mainstream.

Windows x64 [6 en 1] DVD

Download

Windows x64 vs. windows x86

XP x86 is 5.1 kernel

XP x64 is 5.2 kernel (same like Win2003 Server)
XP x64's SP2 (12. March 2007) is much much newer than XP x86's SP2 (9. August 2004)

x64 edition of windows xp has the codebase of the windows 2003 server platform and not the windows xp client platform.
For windows xp x64 (amd64/emt64) you need to get the windows 2003 servicepacks (for x64 ofcourse).
It has nothing to do with the normal 32bit platform of windows xp home/professional/mediacenter/tabletpc.

Download of windows XP x64 (deutsch)

Download 2 (corporate edition)

windows XP SP3 RTM standalone

Service Pack 3 Info:

As per the unofficial timeline, Windows XP Service Pack 3 (SP3) has been uploaded to Microsoft's servers. Currently, the final build is only available on the download.windowsupdate domain in the following languages: Chinese (Hong Kong), Czech, English, French, German (Deutsch), Hebrew, Japanese, Polish, Russian, Simplified (Chinese), Spanish, and Traditional Chinese. According to Microsoft TechNet, the 300MB+ x86 standalone installer (build 5512) will not be available today on the Microsoft Download Center nor on Windows Update.

There will be no x64 version of SP3 released; Windows XP x64 will be updated at the same time Windows Server 2003 is updated, since it is derived from the codebase of the latter. Although Microsoft has still to confirm the date, SP3 should be rolled out via Automatic Updates on June 10, 2008.

The service pack contains all previously-released Windows XP updates, including security updates, out-of-band releases, and hotfixes released since Windows XP SP2 hit Microsoft's servers back in August 2004. There are reportedly 1,073 fixes in SP3, as well as various performance improvements. Every service pack Microsoft releases is cumulative, meaning it is possible to install (or slipstream) SP3 onto Windows XP SP1/SP2. Windows Internet Explorer 7 is not included as part of SP3 and still must be downloaded and installed separately (unless it is already installed).

With SP3, Microsoft has back-ported four Vista features to XP, including Network Access Protection (NAP) in order "to help organizations that use Windows XP to take advantage of new features in the Windows Server 2008 operating system." The four features that are no longer Vista-specific are as follows:

• NAP is a policy enforcement platform meant for enterprise use that blocks systems attempting to access a network until they meet whatever security criteria the corporation has in place.
• "Black Hole" Router Detection helps detect and protect end users from a router that drops packets without returning the specified Internet Control Message Protocol response.
• Microsoft Kernel Cryptographic Module incorporates cryptographic algorithms in a single module other kernel mode drivers are capable of hooking into and accessing.
• The new Product Activation module allows users to install XP without entering a product key at installation.

Just over a month after the release of Vista SP1, XP SP3 hit RTM on April 21, 2008, as the rumors predicted. Up until then, Microsoft continued to stubbornly say that SP3 would go final in the "first half of 2008." The last beta build Microsoft released to the public was XP SP3 RC2 Refresh, available in English, German, and Japanese.

MSDN and TechNet subscribers received the final English 544.86MB ISO image a few days ago. As with Vista SP1, however, subscribers had to fight to get the final build before it hit RTW. MSDN and TechNet subscribers were supposed to get SP3 on May 2, 2008, or three days after it was available publicly.

With the release of SP3, XP will be found on consumers' PCs for years and years to come. On the other hand, with Windows 7 a couple of years out, and with the recent broad release of Vista SP1, Windows XP's life as market leader is slowly coming to an end.

The keyword here is "slowly." Microsoft has extended the life of XP Home until at least June 2010 for budget laptops, and even Apple is supporting XP SP3. Furthermore, although Microsoft has plans to stop selling XP to most manufacturers and system builders on June 30, 2008, OEMs are fighting back. 

...

MUI & Windows XP SP3

MUI Pack Update

http://"Steps to take before you install Windows XP Service Pack 3"

"Release Notes for Windows XP Service Pack 3"

beqiraj.com