ChiefZeke

The thing to do is to go into the BIOS and turn on the hyperthreading option - assuming one is available.

Put all of your drives in and connect them as you want them. Boot into XP and check the other drives/partitions and make sure there are no remnants of Win7 anywhere - format that drive so that does not have to be done by the Win7 installer. Label the drives/paritions as, for example: (C:)XP Pro; (D:)Win7, etc - just to provide a reference. Boot from the Win7 DVD and select the appropriate drive/partition for installation and try again. Does the install routine 'see' the drives ar you labelled them? Does the installation finish? Do you now have a boot menu? Google EasyBCD and install it in XP and Win7 and use it to verify/change the boot menu. (Assuming one is there.)

Windows XP does not come with SATA drivers - if the F6 option does not work because you don't have a floppy then you can try this: go into the BIOS and change the harddrive from SATA to IDE mode and try again. Though you have a SATA drive connected to a SATA port switching the BIOS to IDE mode for that port will allow the XP install routine to recognize the drive and install XP. Another possibility is to buy a floppy drive that connects to a USB port; assuming you can go into the BIOS and there is an option for USB floppy - then you can use the F6 option to tell the XP routine to get the SATA drivers from the floppy.

The latest redistributable is: directx_Jun2010_redist.exe as found on the Microsoft download site. My DxDiag agrees with yours but you can downlaod the redistributable and install again to satisfy yourself.

You should have received a WD CD with the drive. It has all the programs required to move everything from old to new. If not - go to the WD site and download the programs.

DX Tool Beta is another possibility: http://www.ryanvm.net/forum/viewtopic.php?t=8450

The procedure usually followed in installing operating systems for dual- or multi-boot is start with the older operating system first and work your way up. Assuming no operating system installed and you have one or more hard drive installed do this: Partition the drive(s) in enough pieces for the number of OS's to be installed. Boot from the XP CD and install it to a drive/partition of your choosing. When satisfied with that installtion boot from the Win7 32-bit DVD and install it in a different partition of your choosing. When that is done succesfully boot from the Win7 64-bit DVD and install it in another partition of your choosing. If you created three when you started it should be the last available partition. When satisifed and you now reboot you will be presented with a menu; Win7 twice and Earlier Version of Windows (selecting this one gets your XP). Find and download EasyBCD and use it to label the two Win7's, i.e. Win7 32-bit and Win7 64-bit so the menu will offer a selection. I have XP Pro w/SP3, XP Pro x64 w/SP2, Win7 32-bit, and Win7 64-bit installed.

RT 7 Lite beta 2.1.0 for slipstreaming:

I have multiboot systems. On #1 Win7 32-bit is on drive I:\ and Win7 64-bit is on drive H:\; on #2 system Win7 32-bit is on drive H:\. Still no success. Have two systems: #1 has Win7 32-bit and 64-bit installed; #2 has Win7 32-bit installed. Results were the same for both #1 and #2 systems and all three operating systems. Downloaded RT 7 Lite 1.0.7, 1.0.8, 1.0.9, 1.1.0, 1.2.0, and 2.10; both 32-bit and 64-bit versions - and all gave the same results when tried on both systems and both operating systems on #1 system. Windows AIK was installed prior to installing any of the versions indicated above. The installation of RT 7 Lite proceeded with no problems. Clicking the desktop icon resulted in the appearance of attachment RT7Lite120.png with attachment RT7LIte2.png immediatley behind it. Clicking the X in the upper-right corner of attachment RT7Lite2.png to close that box, as I had the WAIK installed, resulted in an error box appearing. The title bar: Microsoft .NET Framework. Comments: Unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately. Object reference not set to an instance of an object. Three boxes: Details, Continue, Quit. Selecting Details gave the information in attachment RT7LiteDetails.txt. Selecting Continue brough up another error box with the message: Required files are missing. Please reinstall the application. Reinstalling the application has no effect on the results. In this posting in the forum: http://www.rtwincustomize.net/web/viewtopic.php?f=110&t=8292 the issue was only C:\ drive was an option for the installation of Win7 - period!!! That is unacceptable - especially for those of us with dual/multi-boot systems. I would like to see RT 7 Lite work from any drive/partition.

Why worry about slipstreaming SP1 - it won't be final till first half of 2011 so there's plenty of time to get ready.

All my drives/partitions are NTFS so I'm not sure of the applicability of the comments above. I checked my XP installations and there are no RECYCLER, Recycle Bin, or Recycled folder under \Documenst and Settings

I have a multi-boot setup: XP Pro w/SP3, XP Pro x64 w/SP2, Win7 32- and 64-bit and I have: Recycle Bin, Recycled, and Recycler. I think that is happening because each of the operting systems is creating recycle bins in all of the partitions - including those of the other operating systems; resulting in these multiple "Recycle Bins". When I looked in each of them from within all of the OS's I did find multiple copies and/or strange files. I just learned to stop looking in the 'Recycle Bin' because I was not sure of what might be there and just empty it when it showed there was stuff in it. If that guess is wrong then someone will make a comment correcting things.

Have been trying to use RTSevenLIte for weeks. Win7 32-bit Ultimate, WAIK installed, RTSevenLite 1.0.9 installed. Starting RTSeven gets the attached image and an error message - attached. What am I doing wrong here?

But, as I understand it, Office Integrator doesn't support Office 2000, which was my original concern. Bill. You may want to use it for Office 2000 and is does work for that just fine but the person responsible for the Office Slipstreamer has mentioned somewhere in these postings that he has shifted his expertise to the Office Integrator and the Slipstreamer as is is the end of it.

Better is a relative term and only you can decide that. The slipstreamer is not being updated, the Office Integrator is. That's the reason to use it.

The Office Slipstreamer is obsolete. Try the Office Integrator: http://siginetsoftware.com/forum/ Also, .NET Framework can be slipstreamed into XP using the RyanVM Integrator - same location as above and info at: http://www.ryanvm.net/forum/

Don't know abut OOBE but the way I keep the repair option is to delete from WINNT.SIF the following lines: [unattended] DriverSigningPolicy=Ignore NonDriverSigningPolicy=Ignore

if the program you're trying to install has a Custom option, usually visible when the setup/install routine starts, select it and then navigate to where you want the program installed.

Probably - NO. Since a user cannot upgrade from XP to Win7, only from Vista to Win7 - then the possibility of slipstreaming the Win7 upgrade into XP is zero.

Where did you find any .REG file within my guide (= start post of this thread)? Boy did I screw up. I read your instructions and in my attempt to get AHCI working I confused it with an article I had copied from here a while ago which is now in the FAQ entitled: "How to enable AHCI on Intel ICH9 under XP" I had arrived at a solution to my problem and was assuming I was posting more information to that forum article.

Win7 final will be out worldwide on 22 October.

The user has to use AHCI mode at setup to implement built in support. Thanks for the info - I'll have to remember that when Win7 final arrives.

You missed the point of what I was commenting on. I was trying to integrate the SATA AHCI drivers into my XP Pro installation - that's what all the info I posted was about. I was not and am not trying to 'fix' anything I followed your example and it did not work. Please -re-read my post. I though I was pretty clear on what I was doing.

I read the instructions and figured I'd try them out. I have an ABIT IX48 GT3 motherboard with an Intel Core2 Quad Q9650 cpu and 8Gb of DDR3 RAM installed; two each WD 1Tb drives partitioned into four partitions each. On drive #2 the first partition is XP Pro w/SP3, the second has XP Pro x64 w/SP2, the third has Win7 32-bit, and the fourth has Win7 64-bit. Multi-boot works excellently and I can boot to all four operating systems with no problems. It is my understanding Win7 has AHCI support built in and does not require anything from the user to implement it. After following your instructions and merging the created .REG file into both XP Pro and XP Pro x64 I rebooted, went into the BIOS and changed the settings to AHCI and rebooted. The boot screen verified AHCI was selected and I selected XP Pro from the boot menu - got a BSOD; STOP: 0x0000007B (no drive detected). Hard reboot. Selected XP Pro x64 and it started, desktop came up and Device Manager showed AHCI drivers. Rebooted. Selected Win7 32-bit and got same BSOD. (What happened to built in support?) Hard reboot. Selected Win7 64-bit and got same BSOD. (What happened to built in support?) Hard reboot. Troubleshooting commenced. Decided to compare the .REG file you proposed with what was in my XP Pro x64 registry - following is what a .REG file would look like with the information I found: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2920] "ClassGUID"={4D36E96A-E325-11CE-BFC1-08002BE10318} "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2922&cc_0106] "ClassGUID"={4D36E96A-E325-11CE-BFC1-08002BE10318} "Service"="iastor" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2923&cc_0106] "ClassGUID"={4D36E96A-E325-11CE-BFC1-08002BE10318} "Service"="iastor" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2926] "ClassGUID"={4D36E96A-E325-11CE-BFC1-08002BE10318} "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor] "DisplayName"="Intel AHCI Controller" "ErrorControl"=dword:00000001 "Group"="SCSI miniport" "ImagePath"="system32\\drivers\\iaStor.sys" "Start"=dword:00000000 "tag"=dword:00000019 "Type"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Enum] "0"="PCI\VEN_8086&DEV_2922&SUBSYS_B0051458&REV_02\3&13c0b0c5&0&FA" "1"="PCI\VEN_8086&DEV_2922&SUBSYS_1107147B&REV_02\3&2411e6fe&0&FA" "Count"=dword:00000002 "NextInstance"=dword:00000002 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters] "BusType"=dword:00000003 "queuePriorityEnable"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port0] "AN"=dword:00000000 "DIPM"=dword:00000000 "GTF"=dword:00000000 "LPM"=dword:00000000 "LPMDSTATA"=dword:00000001 "LPMSTATA"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port1] "AN"=dword:00000000 "DIPM"=dword:00000000 "GTF"=dword:00000000 "LPM"=dword:00000000 "LPMDSTATA"=dword:00000001 "LPMSTATA"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port2] "AN"=dword:00000000 "DIPM"=dword:00000000 "GTF"=dword:00000000 "LPM"=dword:00000000 "LPMDSTATA"=dword:00000001 "LPMSTATA"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port3] "AN"=dword:00000000 "DIPM"=dword:00000000 "GTF"=dword:00000000 "LPM"=dword:00000000 "LPMDSTATA"=dword:00000001 "LPMSTATA"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port4] "AN"=dword:00000000 "DIPM"=dword:00000000 "GTF"=dword:00000000 "LPM"=dword:00000000 "LPMDSTATA"=dword:00000001 "LPMSTATA"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port5] "AN"=dword:00000000 "DIPM"=dword:00000000 "GTF"=dword:00000000 "LPM"=dword:00000000 "LPMDSTATA"=dword:00000001 "LPMSTATA"=dword:00000000 I listed all of the above because of the hardware IDs for my system. A partial list of that list follows (note the use of _2920 and _2926 in the identifier): ============ RAID Devices ============ PCI\VEN_197B&DEV_2363&SUBSYS_F100147B&REV_02\4&2531C6B0&0&00E4 Name: Standard Dual Channel PCI IDE Controller Hardware ID's: PCI\VEN_197B&DEV_2363&SUBSYS_F100147B&REV_02 PCI\VEN_197B&DEV_2363&SUBSYS_F100147B PCI\VEN_197B&DEV_2363&CC_010185 PCI\VEN_197B&DEV_2363&CC_0101 Compatible ID's: PCI\VEN_197B&DEV_2363&REV_02 PCI\VEN_197B&DEV_2363 PCI\VEN_197B&CC_010185 PCI\VEN_197B&CC_0101 PCI\VEN_197B PCI\CC_010185 PCI\CC_0101 PCI\VEN_8086&DEV_2920&SUBSYS_1107147B&REV_02\3&2411E6FE&0&FA Name: Intel® ICH9R/DO/DH 4 port Serial ATA Storage Controller 1 - 2920 Hardware ID's: PCI\VEN_8086&DEV_2920&SUBSYS_1107147B&REV_02 PCI\VEN_8086&DEV_2920&SUBSYS_1107147B PCI\VEN_8086&DEV_2920&CC_01018F PCI\VEN_8086&DEV_2920&CC_0101 Compatible ID's: PCI\VEN_8086&DEV_2920&REV_02 PCI\VEN_8086&DEV_2920 PCI\VEN_8086&CC_01018F PCI\VEN_8086&CC_0101 PCI\VEN_8086 PCI\CC_01018F PCI\CC_0101 PCI\VEN_8086&DEV_2926&SUBSYS_1107147B&REV_02\3&2411E6FE&0&FD Name: Intel® ICH9 Family 2 port Serial ATA Storage Controller 2 - 2926 Hardware ID's: PCI\VEN_8086&DEV_2926&SUBSYS_1107147B&REV_02 PCI\VEN_8086&DEV_2926&SUBSYS_1107147B PCI\VEN_8086&DEV_2926&CC_010185 PCI\VEN_8086&DEV_2926&CC_0101 Compatible ID's: PCI\VEN_8086&DEV_2926&REV_02 PCI\VEN_8086&DEV_2926 PCI\VEN_8086&CC_010185 PCI\VEN_8086&CC_0101 PCI\VEN_8086 PCI\CC_010185 PCI\CC_0101 3 matching device(s) found. I have not yet tried this new .REG file in XP Pro and I'm not sure about trying it with Win7 either version. Before I do try it I would like a response/opinion as to its viability. Thanks

The usual but not always successful procedure is to try to do a 'repair' install for a cpu, motherboard, etc change.