Win XP installation.

This forum discusses topics about the Ultimate Deployment Appliance

Moderators: the_dude, Posters

Re: Win XP installation.

Postby sindustry » Tue Sep 20, 2011 9:19 am

Microsoft requires people improving to Home windows 7 from Home windows XP to carry out a “clean” installing of the brand new system. By “clean,” they mean it - as with “none of the configurations, files is software are instantly replicated to Home windows 7.” In a single form or any other, you have to support everything you need to proceed to the brand new system, install Home windows 7 on the pc, after which re-install all of your files, configurations and programs to be used using the new system.
sindustry
 
Posts: 2
Joined: Mon Sep 19, 2011 5:22 am

Re: Win XP installation.

Postby tmbogus » Wed Sep 21, 2011 7:28 pm

I was able to solve a missing driver problem in text-mode using Windows 2000 version drivers for Win XP setup.
That was for a Dell Vostro 230 using a Broadcom chip.

Although now I am having trouble with a terribly slow file transfer (>4h setup!).
I have tried locking net speeds, duplexing mode and disabling STP.
I have already looked all over and did not find a solution.
It looks a lot like this: http://support.microsoft.com/kb/906425

Has anybody come across something even remotely like this?

Thx
tmbogus
 
Posts: 1
Joined: Wed Sep 21, 2011 3:21 pm

Re: Win XP installation.

Postby johnson » Thu Sep 29, 2011 12:19 pm

Why clean install?:-
While a clean install is not always necessary, slightly better stability and performance can be expected when XP is installed to a clean hard drive or partition.

The XP upgrade is a vast improvement over previous Windows upgrades, and is usually the best choice when transitioning from a previous Windows version to XP. I recommend the clean install approach as a last resort, not the first option.

My recommendation is to prepare for a clean install, but first try the upgrade option. If in the unlikely event results of the upgrade are a failure, nothing is lost but the time spent doing the upgrade and evaluating the results. The preparation to clean install is in place and the upgrade experience will serve as a hands on tutorial to familiarize you with the XP setup procedure.
johnson
 
Posts: 2
Joined: Thu Sep 29, 2011 9:29 am

Re: Win XP installation.

Postby jasonbenben » Mon Oct 10, 2011 10:18 am

Microsoft Windows Embedded Studio Development Tools for Windows XP Embedded:
Now that you have a general understanding of Windows XP Embedded with SP1 and how it differs from Windows XP Professional, it is important to understand its development tools, Windows Embedded Studio. Four development tools make up Windows Embedded Studio: Target Analyzer, Target Designer, Component Designer, and Component Database Manager. These authoring, analysis, and optional command-line tools assist developers in creating a customized operating system or runtime image.

With Windows Embedded Studio, developers can select from over 10,000 components (1,000 operating system components and 9,000 device drivers), build and customize their own components, and generate a bootable runtime image that contains only the functionality they select. They can extend the functionality by adding applications or devices that they or a third-party vendor create.

To put this into context, let’s say you are developing an application for a retail point-of-sale (RPOS) device. Your application may require a touch-screen monitor, serial port, CD-ROM, and modem, but may not require Internet access or special power options such as Advanced Configuration and Power Interface (ACPI). Once you have created a general device specification, you can use Windows Embedded Studio to configure your custom operating system for the retail point-of-sale device by using only the required components. This allows you to reduce the overall footprint of the image to include only those components necessary to effectively run your application.

The following sections provide more detail about the Windows Embedded Studio development tools.

Target Analyzer

It can be difficult to determine the exact device architecture for a computer motherboard by simply looking at it or by reading a set of specification documents. Making this determination requires in-depth knowledge of every device in the computer system and can be quite time consuming. Target Analyzer simplifies this process by collecting a relatively small amount of data on the target system and generating an eXtensible Markup Language (XML) definition of the target hardware in the form of a .pmq file. This .pmq file is a list of components from the target device that developers can import into Target Designer to create a basic device configuration.

The Target Analyzer probe provides various levels of hardware detection, depending on the operating system that is running on the device. Target Analyzer can be run in two forms. TA.exe is used when the desktop system is running MS-DOS. In a 16-bit operating system environment, TA.exe produces limited results and can only make an assumption regarding hardware abstraction layer (HAL) and CPU types. TAP.exe should be used when a system is running any other Windows operating system, such as Windows 2000, Windows XP, or Windows Preinstallation Environment (WinPE), which is included in Windows XP Embedded with SP1. Both forms of Target Analyzer generate a .pmq file, but TAP.exe requires less manual configuration than TA.exe and provides a more comprehensive end result.

Target Designer

Target Designer is the primary development tool in Windows XP Embedded. It is used to select, configure, and build a customized runtime image. This tool incorporates features such as a drag-and-drop user interface, easy component searching and filtering, and automated dependency checking to minimize the development process. Target Designer can perform the following operations:

Browse and select

Advanced search and filter features allow developers to browse through the component database and search by category, driver type, design template, all components, and so on.
Pre-selection estimation of footprint shows the incremental impact of adding a new component.
Help files provide additional component information and assistance.
Developers can select the necessary feature components from a database of all available Windows components, add them to the runtime configuration, and generate the customized OS image.
Operating system and component configuration

The Target Designer Import function reads the .pmq file created by Target Analyzer to locate the device descriptions in the database. The resulting Windows Embedded configuration (.slx) file can be used as the basis for building a runtime image for the target device.
Target Designer can add additional components that are needed for the target application.
Target Designer provides operating system configuration of hardware support, file system, machine name, destination drive, and so on.
Component configuration varies by component and is configurable through Dynamic Hypertext Markup Language (DHTML), enabling you to write a very rich user interface.
Custom operating system image building

Check Dependencies identifies and adds required components. Once run, a task list prompts the user to correct errors and add components necessary to run a custom operating system.
Target Designer builds a bootable operating system including registry hives and folders, populates binaries to folders, and builds the final runtime image.
Component Designer

Component Designer is the development tool that enables developers to design custom operating system components. Developers can save applications or devices they or third-party vendors create as components in the component database. They can use Target Designer to include these components in custom operating systems. Component Designer enables developers to perform the following tasks:

Expand the capabilities of embedded devices by adding custom components
Specify prototype, files, and registry systems
Create multiple computer configurations, such as variations of a single device
Before you use Component Designer, you should determine your strategy for adding your application or driver as a component into the component database. After you determine the component requirements, which include files, registry entries, and component dependencies, you can enter that metadata into Component Designer by using one of the following methods:

Create a new object definition, insert a component object into the definition, and manually enter metadata.
Copy an object definition for a similar component, and then modify the information as appropriate for your component.
Convert an .inf file into an incomplete object definition, and then complete the definition.
Component Database Manager

Component Database Manager allows developers to import their customized components into the database, and provides management utilities for tasks such as changing server location, viewing database objects, and managing platforms and repositories. The component database can reside on the development system or on a server, and can contain multiple platforms. Developers can use Component Database Manager to perform the following tasks:

Import component data carrier (.sld) files into the component database.
Change the database server location.
Delete objects, such as platforms, packages, components, and repositories (however, Microsoft recommends that you do not delete a database object).
Select a component database server to work with both Target Designer and Component Designer.
Set up repositories.
Change the repository search path.
jasonbenben
 
Posts: 2
Joined: Mon Oct 10, 2011 10:11 am

Re: Win XP installation.

Postby texas123 » Tue Oct 11, 2011 7:47 am

Hi,I don't no about Win XP installation...Anyone can knows the information please send me some about us....
texas123
 
Posts: 2
Joined: Tue Oct 11, 2011 7:36 am

Re: Win XP installation.

Postby browserdrive » Tue Apr 17, 2012 11:59 pm

Hi! I'm a noob in this forum but I need to know how this affect us all when Microsoft support for Windows XP SP3 and Office 2003 ends in April 8, 2014? I mean wouldn't automated software deployment make no sense if you using Windows XP so you might as well migrate early. :|
browserdrive
 
Posts: 1
Joined: Tue Apr 17, 2012 11:24 pm

Previous

Return to Ultimate Deployment Appliance

Who is online

Users browsing this forum: No registered users and 0 guests

cron