Hey, Im trying to create my own unattended XP installation CD. I slipstreamed SP2 together with my original XP CD successfully and created my own Unattended.txt file which I renamed WINNT.SIF as.

Original Txtsetup.sif Song
Original Txtsetup.sif 1
Original Txtsetup.sif 2
Original Txtsetup.sif Full
Original Txtsetup.sif Video

Jan 10, 2006 Hey, Im trying to create my own unattended XP installation CD. I slipstreamed SP2 together with my original XP CD successfully and created my own Unattended.txt file which I renamed WINNT.SIF as.
What Are the Major Specifications of Inventory Management System; Save Your Money! Why Writing Your Own ERP Is a Terrible Idea! Sell Your RUG Before It Is Made.

A Layman's Guide
By Oldman List of guides Supplementary guides

A Layman's Guide

By Oldman

List of guides

Supplementary guides

This guide will show you how to get a debug log using the built in ReactOS debugger. There are several different ways to do this; they are:

Through the serial port. This is the best way; it captures all debug output from the moment it starts outputing.

With a log file. This is the least useful, due to the fact that it is saved to the hard drive and it first needs the OS to be installed.

To the screen. This is the second most useful way, you need to do some configuring to get debug info from the very start of stage one of the installation.

In a virtual machine using com0com (Windows) or tty0tty (unix) This uses a software serial port and is the best way when using a virtual machine.

1Section one - General information
2Section two - The different methods for getting a debug log
- 2.1Through the serial port
  - 2.1.2Software
- 2.4In a virtual machine
3Section three - More advanced debugging info
- 3.1The ReactOS debugger
- 3.3Getting a more detailed backtrace by enabling 'First chance'
- 3.4Debug to screen in the first stage
  - 3.4.3Finding txtsetup.sif within an ISO

Section one - General information

Debug ISOs

reactos-bootcd-0.4.7-dev-581-g9c790df-x86-gcc-lin-dbg.7z

reactos-livecd-0.4.7-dev-575-g48b2714-x86-gcc-lin-dbg.7z

reactos-bootcd-0.4.7-dev-575-g48b2714-x86-msvc-win-dbg.7z

reactos-livecd-0.4.7-dev-575-g48b2714-x86-msvc-win-dbg.7z

reactos-livecd-0.4.15-dev-147-g633770a-x64-msvc-win-dbg.7z

Explanation:

reactos-bootcd - 0.4.7 - dev - 581-g9c790df - x86-gcc-lin-dbg.7z

reactos-bootcd = type of ISO (boot for installing, live for running OS without installing).

0.4.7 = The number of the next release. The number changes every time a release branch is created, so when the 0.4.7 was branched for release, the number on the daily/latest ISOs became 0.4.8. And when the 0.4.8 was branched for release, the number on the daily/latest ISOs became 0.4.9. Now the 0.4.9 is branched, the number on the daily/lastest ISOs are numbered 0.4.10.

dev = development

581-g9c790df = identifies the commit and the committer.

x86-gcc-lin-dbg = x86 (32bit OS) - gcc (compiler) - lin (built using Linux) - dbg (debug build)

reactos-bootcd-0.4.7-dev-575-g48b2714-x86-msvc-win-dbg.7z

msvc-win = msvc (compiler) - win (built using Windows)

For normal users, the ISOs built with gcc are the ones to go for. Og gamertags not taken 2020 xbox. You may need a copy of MSVC to make full use of the msvc-win builds.

x64 = the 64 bit version. Only available (currently) from the Latest Builds page and they are of no real value yet. There are NO official Release builds yet.

Stages of the installation of ReactOS

It may be helpful to understand the stages of the installation of ReactOS.

First stage:

When the installation CD (bootcd) is run, the bootloader asks you to press any key to install.

The OS will first load itself into memory, then you are presented with the Language setup window, then 2 more windows, then Device settings window, then choose Hard drive partition window, then format window, then confirm format window. then choose directory window. then 2 more windows, then bootloader choice window. In the last window you are asked to remove media and press Enter. The computer now reboots.

Second stage:

The bootloader shows the Boot options choice window, then boots, loads device drivers, then shows the setup window, after that there are more configuration windows (when testing you can press Enter at all these windows), before it finally reboots.

Third stage:

It now boots up into desktop and displays the driver install wizard, if it finds any hardware without a driver.

NOTE:

Debug output only starts when the OS is loaded into memory, but just before it loads the drivers.

When installing (First stage), debug output is turned on by default and can only be captured through a null modem serial cable connect to a second computer (to alter this default, see this section), but once ReactOS is installed (Second stage and normal usage), you will have a choice of how to record debug output, from the boot menu. See ^[1]ReactOS boot options menu in Screenshots section in Part two below.

Section two - The different methods for getting a debug log

Through the serial port

Hardware requirements:

A test computer with a serial port.
A second computer with a serial port and Putty installed (or similar app).
A nullmodem cable to connect both computers.

Software

Win32 Putty - http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html You will also find the source code for Windows and Unix at this link, but Unix users may be able to get Putty through their Package Manager (see NOTES for Unix users).

Setting up Putty.

There are some vital settings in Putty, which need to be set, so that Putty can capture a debug log.In putty go to Category and select Session, then set the following inputs to these values:
Serial line = COM1 (ttyS0 for Unix)
Speed = 115200
Connection type = Serial

Back to Category and select Logging, in Session logging: check All session output. Note where Putty saves the log file and change if required; use the Browse button for the destination folder.

See in Screenshots^{[2] [3]} below for visual information.

Save the above changes in putty, with a name of your choice, in Saved Sessions, then use the Save button. It can then be loaded the next time you use Putty, by using the Load button. Note: logging is started by using the Open button.

Screenshots

[1] ReactOS boot options menu.

[2] PuTTY Configuration - Session
[3] PuTTY Configuration - Logging

[4] Ros in the debugger showing bt entered at the command prompt.

[5] You may see this after entering bt and after the debug info has stopped.

[6] The debugger has been entered manually and shows set condition * first always typed at the command prompt and cont.

[7] If you see this, type o as shown and press enter on your keyboard.

NOTES for Unix users:

Putty can be installed through your system's Package Manager. When installed, it is started from a command prompt window, by typing putty at the prompt. If you do not have a GUI, then install picocom through your system's Package Manager.

Original Txtsetup.sif