• Windows Xp Pro Sp3 Oem

So let me understand this. Microsoft is going to be releasing a service pack to bring XP up to date, thus XP SP3, but isn't going to add SATA drivers? Would you mind explaining the logic in this decision? Almost all of the business class PCs running now come with SATA drives and by the way, the standard procedure for adding drivers to Unattended installs does not work per articles on the Microsoft site!!

There are workarounds but Microsoft does not support them. To me this seems like a problem that should be addressed. Mla1 wrote: Microsoft does not support images that have been created / altered with nLite. If Microsoft supported this method then I would use the tool. Also (Microsoft's) Business Desktop Deployment 2007 does not like CD's that have been created/altered with nLite. Microsoft will go so far as to give you guides posted online, and give you the ability to collect updates to integrate into an image - but that is as far as Microsoft will go regarding slipstreamed CD's unless you are willing to go to Pro Level Support for $259 per issue.

It is not classified as a consumer level issue as consumers typically will not ever think to, or need to, or want to, make such a thing. It is classified internally as an advanced Pro issue. Even at Pro Level Support, they are only supposed to assist updating online network share install sources which are typically Volume License network install sources for corporate LAN's mass deployment - as opposed to an actual bootable disk. Technically, the creation of a backup disk, or the creation of a slipstreamed disk, or any bootable optical disk, is not supported by Microsoft.

By not supported, that means Microsoft will not talk to you on the phone to help you make it (nor help via email correspondence with you personally to help you make it). It doesn't mean that you can not legally make it and use it on your own. Therefore, the use of nLite is indeed not supported. Neither is it supported, in the context of support implied here, if you make it manually as Microsoft's guides posted at various sites on its domain (Microsoft Knowledge Base, MSDN, Technet sites) suggest using the /integrate switch at the command line. Making and using them has no impact on your warranty and/or ability to use it for calling Microsoft for other issues that are within their support boundaries.

When you call Microsoft, they will want to check 'Control Panel-System Properties' to check your PID (Product ID number) and to see what Service Pack level you are. That way we can see if this copy has a warranty with Microsoft and make sure it is up-to-date enough (i.e.

It is SP2 or later as installed at the moment - the SP level of the install source is irrelevant). Ely67241 wrote: So let me understand this.

Microsoft is going to be releasing a service pack to bring XP up to date, thus XP SP3, but isn't going to add SATA drivers? Would you mind explaining the logic in this decision? Almost all of the business class PCs running now come with SATA drives and by the way, the standard procedure for adding drivers to Unattended installs does not work per articles on the Microsoft site!! There are workarounds but Microsoft does not support them.

To me this seems like a problem that should be addressed. Microsoft does not make drivers.

Drivers tell Windows how to communicate with the respective hardware said driver was written for. The manufacturer of the hardware makes the driver. Microsoft does provide DDK (Driver Development Kits) to hardware manufacturer's so that they can know what format a driver should be in to maximize efficiency communicating to a given OS (there are different DDK's for different OS'es). Microsoft has the WHQL (Windows Hardware Quality Labs) program where hardware manufacturer's can voluntarily submit their drivers for a Microsoft review process - and if said drivers submitted pass inspection Microsoft can make them available on the Windows Update website - but this is only on a voluntary basis.

Using nLite and the driver packs at Driverpacks.net you can make an install source with virtually all known drivers that will end up being a little over 1GB large - so it would end up being an installation DVD rather than a CD. I've built them with great success. Microsoft, for their part, take no responsibility in the realm of drivers, and they really have no reason to EXCEPT WHERE IT CONCERNS THE HARDWARE MICROSOFT THEMSELVES MAKE. For XP on a SATA system, you need the floppy with the drivers, or a slipstreamed disk with at least the SATA drivers added to it already. Mla1 wrote: I will tell you the logic behind this, Microsoft want everyone to use Vista instead instead of XP. Its a cop out. Explain this Vista SP1 gets released with updated drivers.

XP SP3 gets released with no updated drivers. Hmmnnn Vista has SO MANY PROBLEMS that Microsoft is fighting an insane uphill battle to make it as appealing as possible. MOST hardware has no Vista Drivers to speak of. There have always been issues when Microsoft released a new OS - but never before on a scale like this. Never before have OEM's demanded they downgrade back to a previous OS (they have forced Microsoft to allow them to go back to XP from Vista). Never before have Microsoft's Pro and Premier customers demanded and petitioned Microsoft to extend the life-cycle of the previous OS (It isn't a cop out that XP does not get drivers in SP releases - this has never been the case with XP or any other MS product - except for Vista. I could fill a book with the reasons Vista is a failure, and why Microsoft can never admit it.

JustAnotherHack wrote: They may decide not to include SATA drivers, but if they would at least update to allow the drivers to be loaded from somewhere other than Floppy Drive A. Ever heard of legacy free systems? That 1st load building an image is a pain. The first water-cooled system I built was in Jan. 2003 and it was on a Giga-byte 8KNXP booting from a Western Digital 120GB SATA drive. The board had a Silicon Image 3112 SATA hard disk controller as well as the Intel 875 chipset controlling an additional 2 SATA ports.

SATA was brand-spanking-new just out of the gates and Giga-byte concluded that their board just couldn't boot from a SATA drive when I first tried to figure out why the XP CD didn't detect any drives. To top it off, Intel and Silicon Image hadn't posted a specific 3.5' floppy sized version of the drivers yet, nor did the motherboards CD include drivers that could fit on a floppy. After a bit of a learning curve, I managed to pull the.inf files from the.exe drivers that were posted and on the CD and managed to home brew a floppy that XP would use. I quickly became convinced of the slipstream virtues. Would it be fantastic if Microsoft even included as much as a generic SATA driver? NLite and driverpacks.net is testimony to just how easy it would be to include them. But there would be other legal issues and internal procedures for MS to implement it that would amount to enough P.I.T.A.

To build a Greek Restaurant (P.I.T.A. = Pain In The.). Naturally, they will not do it. If you want to add the intel sata drivers manually to your source cd follow these instructions. (note these instructions were not copied from another site they were written from scratch by myself after a lot of trial and error). Download the latest intel matrix Storage manager from Intels Website h.://www.intel.com/support/chipsets/imsm/index.htm download the F6 floppy configuration.

The latest file at the time of writing this document is 7.8.0.1012 Extract the file to a floppy it should contain the following files. Iaahci.cat iaahci.inf iastor.cat iastor.inf iastor.sys license.txt readme.txt txtsetup.oem Copy the contents of a windows XP source to the root of C: and call the folder the same name as the source cd in which you are using in my case I have the following (for the purpose of this article mine is called CDNAME c: CDNAME open c: CDNAME i386 txtsetup.sif We need to add the following line ' iastor.sys=1,4,4,1,1,4' under SourceDisksFiles (scroll down to the last entry under SourceDisksFiles and copy it to the bottom of the list. SourceDisksfiles entry1 entry2 entry300 odd iastor.sys=1,4,4,1,1,4 The above states that its an original source cd and a new install code. ALSO.note the above code will be the same even if a new sata driver is available Open up the txtsetup.oem from the floppy drive you should see a list of hardware id's for each sata driver. For example the ICH8M driver will look like this.

Microsoft office cracked download torrent. HardwareIds.scsi.iaStorICH8M id = 'PCI VEN8086&DEV282A&CC0104','iaStor' with c: CDNAME i386 txtsetup.sif still open Edit find HardwareIdsDatabase Scroll to the last record under hardwareIdsdatabase and paste each ID so it looks like the following. HardwareIdsDatabase entry1 entry2 entry3 etc. Mla1 wrote: iastor.sys=1,4,4,1,1,4 The above states that its an original source cd and a new install code.

ALSO.note the above code will be the same even if a new sata driver is available Will this same format work with other controllers? Is there somewhere I can find out what each of those commas is supposed to delimit? Also, why do all the SCSI entries get marked with IASTOR, while some of them have iaahci in the txtsetup.oem files?

This has got me so frustrated, I'm bound and determined to get it down pat before this is over! Thanks again for your help! The reasoning behind the SATA not being included is fairly straight forward. When Xp was introduced, SATA was only a glimmer on the horizon.

Windows Xp Pro Sp3 Oem

And the base image Sp2, and 3 are designed around is centered on this image. Anything that drivers and additional hardware was was supported by the Manufactor. There is no contract to include any new drivers. But since floppys were supported by ancient operating systems. That portion of the OS is included. So things that are contracted and introduced with the original Gold Xp, like flash player.

Are updated in the image. Adding a complexity to the Sp3 with any sort of generic image driver would introduce more timing issues. The answer my friends is the emulation of floppys that some motherboard systems do have. Bootable images can be created. And allow for a repair installation of Sp3. (see below) I do understand that booting off a CD, and having an driver available with a floppy sounds and is ancient design.

But there are other resources, like msfn.org which has a clear tutorial about integrating SATA drivers. And the afore mentioned driver set in another posting. And of course different options available to address problems like the error you are receiving. But please always take this bit of advice to heart, and perform. Back up your system. Hard drives with just your important information will always save time. And more longer term storage like CD/RW disks are cheap and plentiful.

Only takes about half an hour on slower systems to create a new installation disk. Even with slower processors. Mostly limited by the r/w drive speed present on your system. Found a copy of the HP pdf document.

Here is the extract for your information. Adding SATA Drivers to an Installation CD Where these guidelines are applicable IMPORTANT: Follow the installation instructions in the order provided. Failure to complete these steps in the proper order can result in an unsuccessful or unstable installation. This section provides guidelines for customers who need to add SATA support by creating a custom Windows XP Service Pack 2 Installation CD. Steps to add SATA drivers to the CD 1) Copy all the directories and files from the Windows XP CD to a temporary folder (these guidelines will use c: xpcd ) 2) Download the Intel SATA AHCI Controller Driver, SoftPaq SP32478.exe, from www.hp.com. 3) Extract all the files from the SoftPaq.

A USB floppy is necessary for this step. Run sp32478; this will create a floppy disk. The files will be located on this floppy. 4) These files should be located on the floppy disk. Iaahci.cat b. Iaahci.inf c. Iastor.cat d.

Iastor.inf e. Iastor.sys f. License.txt g. Readme.txt h.

Txtsetup.oem 5) Create the following path in the temporary folder: c: xpcd $oem$ $1 drivers sata 6) Copy all the files from step 4 to the c: xpcd i386 folder. 7) Also copy all the files from step 4 to the c: xpcd $oem$ $1 drivers sata folder. 6 8) Open the c: xpcd i386 txtsetup.sif file in Notepad.

9) Go to the end of the file. There will be several blank lines.

10) Move the cursor up a few lines. This is necessary because there is a hidden marker at the end of the file. Yea, I have installed XP Pro on my HP laptop dv9535nr using nLite and it worked very slick. I have Service Pack 1 disk then I slipstreamed SP2 and the SATA driver and it burned the disk and all! Worked very slick. From what I've read you have to have atleast SP2 on the disk for it to recognize the SATA drivers.

From there you can mabey find driver packs for your specific model. If it is a custom build you better go hunting. Do not slipstream the other drivers as they may not install properly just load them after the install rebooting after each one usually starting with the chipset, PCI, then the graphics and whatever you need from there.

HP dv9535nr Triple Boot: XP Pro, Vista, Windows 7 RC1.