Tims Wein- und IT-Blog

ich wollte kürzlich mal so eben windows XP auf einem neuen PC mit Intel DG33FB Motherboard (Q33 Plattform) installieren.
Da eine freie Lizenz XP SP1 vorhanden war versuchte ich es zunächst mit dieser CD. Es endete jedoch immer damit, dass keine CD oder Festplatte erkannt wurde oder es gab einen Bluescreen. Auch der Kompatible Mode für SATA Festplatten brachte keine Hilfe. Das gleiche passierte auch mit einer Windows SP2 CD …
Mit F6 kann man zwar Treiber von einer Floppy laden (und zwar nur von Floppy), dumm nur wenn kein Floppy Anschluss vorhanden ist. Ironie pur, dass eine solche Treiber-Diskette zum Lieferumfang des Boards gehört … Mit einem USB Floppy-Laufwerk gelang es mir schließlich die Treiber von der Diskette zu laden aber die installation klappte trotzdem nicht. Soweit ich mich erinnern kann, hat das Setup-Programm kurz bevor es zum kopieren der Installations-Dateien von CD kommt, erneut nach der Treiber Diskette verlangt, aber die Einbindung Einbindung des USB Floppy-Laufwerks funktioniert nicht mehr.
Weitere Versuche mit einem PATA CD Laufwerk schlugen auch fehl.

Dank google fand ich schließlich das Programm nLite, http://www.nliteos.com. Dieses verspricht, u.a. aus XP Installations-Medien zusammen mit Service-Packs, Update und Treibern eine “customized” XP CD zu slipstreamen.
Das Programm und die daraus resultierende XP CD funktionierte auf Anhieb!

This entry was posted on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 33
Thursday, October 25th, 2007 at
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 33
16:33 and is filed under IT. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.