ChiefZeke

Edit boot.ini and add /numproc=1 to the line starting Windows or Start > Run > msconfig > BOOT.INI Tab > Advanced Option button > put a check mark in the box beside /numproc= and then type a 1 in the box to the right.

What 'new' Windows Explorer are you talking about? I don't remember anything new about Explorer being posted on 08 Sept.

Well, that just sucks.

Office Integrator, as the name implies, integrates service packs and hotfixes into the source Office CD, creates an ISO from which you burn a new CD and then install. Would not this method be faster than first installing Office, then the service packs, then the hotfixes? Or am I missing something in what it is you want to do?

If the system runs long enough you could also go to www.crucial.com and run their memory tets on your sytem

The Office Integrator, found here: http://siginetsoftware.com/forum/ is able to integrate service packs into Office XP, 2003, and 2007 - it will also add chained installs for many items; you might want to check it out.

Try the Office Integrator - http://siginetsoftware.com/forum/

The Micrsoft site statement just says XP to Win7 - no mention of which version of XP or if Win7 64-bit is orderable. Based on how users upgraded from Win98, SE. ME to XP I'd say you could go from XP Home to Win7 Pro with no problems; excpet you'd have to do a clean install of Win7 using the XP Home CD as the valid source to be upgarded.

Ryan VM WMP11 from within Ryan Driver Packs - the folks at DriverPacks say they must always be the last item

Assuming it's not OEM the first thing to do after swapping the hard drive is to boot from the XP CD and do a repair install. The repair will allow XP to install drivers/etc for the new motherboard. This is assuming you've updated th XP CD to the latest service pack and that you have used RyanVM Integrator or similar to include addons/updates/etc and possible used DriverPacks also. Rayn: http://www.ryanvm.net/forum/ DriverPacks: http://forum.driverpacks.net/

I got the info below whe I asked a question about installin Win7Rc in the Microsoft 64bit newgroup: A few other tips: 1. Be well acquainted with Disk Management! This tool first appeared in Windows 2000, but many users - even veterans - still haven't found it. There are several ways to get there; my favorite is just to press Start, type in "diskmgmt.msc" and press Enter. 2. Always NAME your volumes. That way, you'll not be TOO confused when "Win7x86" is Drive C: when you are running Win7 x86 and Drive E: when you are booted into Vista. It will still be Win7x86 in both systems, even with different letters. 3. If you want to have consistent drive letters among the various OSes, then first boot into WinXP and run Disk Management. Create all your volumes and assign the letters you want - and they don't all have to be sequential. (I'm currently running Win7 x64 RC in Drive X:, the 10th volume on Disk 1.) Then insert the Win7 DVD and run Setup from the WinXP desktop, so that it can "see" and respect the letters you've assigned. If you boot from the DVD, then Setup will start from scratch and assign C: to its own boot volume, requiring the system volume be changed, probably to D:, and other letters to be reassigned, too. 4. Make the System Partition (see KB 314470 for the COUNTERintuitive definitions of "system volume" and "boot volume", and get comfortable with those definitions) small - 1 GB is probably more than enough - and use it only for your startup files. For WinXP, these are NTLDR, NTDETECT.COM and Boot.ini; Vista and Win7 use bootmgr, bootsect.dos and the BCD (Boot Configuration Data) files in the hidden \Boot folder in this partition. All the rest of each OS should go into the \Windows folder on each boot volume. Then you'll be able to wipe out and reformat any of the partitions without bothering any of the others. (If you have multiple HDDs, it's good insurance to create a small System Partition on each of them and install the latest Windows at least once while each is the boot device so that Setup can write the startup files to it. That way, if Disk 0 won't boot, you can still boot from Disk 1 - to fix Disk 0.) 5. Win7 has a smaller on-disk footprint than Vista, since Windows Mail and other features are no longer imbedded in it. But it tends to grow after installation! While 20 GB might be enough to start, make those volumes at least 30 GB each and even larger, since you have "plenty of hard drive space". 6. Oh, one more. If this is your first 64-bit system, you might be surprised to find a new folder in addition to Program Files, this one named "Program Files (x86)". This new PF86 folder is NOT for 64-bit programs, as I first thought, since it didn't exist in WinXP Pro. In 64-bit Windows, the PF file is reserved for 64-bit apps; 32-bit apps go into the new PF86. Windows uses these folders to select the proper drivers and other support files, depending on the "bitness" of the app. I guess that's enough for now. If you have questions, please post back. RC White

If I do as Felix suggested and expand the svcpack.in_ to svcpack.inf and edit it should it not be compressed back to svcpack.in_ so that the next time I do a fresh install or repair install with that CD everything performs as expected?

I found the posting for this program and thought I'd try it - looked very interesting. Everything downloaded and appeared to work as advertised; except for the instructions: Here's how to add MSDownloads.exe to your XPCD (use A or B, not both): see * below for problem(s). a. From SVCPack (T-13): 1. Copy MSDownloads.exe to XPCD Source\I386\SVCPACK * 2. Add a MSDownloads.exe entry to XPCD Source\I386\svcpack.inf, under... This is where the problem arises, the file is compressed as svcpack.in_ because it was created with the RyanVM Integrator when I used the Integrator to update and add addons to my XP Pro w/SP3 CD. I checked the original source CD - no SVCPACK.INF. I checked the XP Pro w/SP3 CD - same - file is SVCPACK.IN_ (Used AutoStreamer to integrate SP3 with my original.) I checked the XP Pro w/SP3 CD that I updated with the RyanVM Integrator and it is also SVCPACK.IN_ The other option: b. From Cmdlilines.txt (T-12): 1. Copy ... * 2. Add a MSDownloads.exe entry to XPCD Source\$OEM$\cmdlines.txt won't work as that file does not exist and no example was given in the Guide as to the correct format. So, what can I do, if anything, to add MSDownloads to my XPCD Source? I read through all the postings above this one to see if I had missed something and can only assume no else has used the RyanVM Integrator to update their Source XPCDs. If I did miss something then please tell me what and point out where. Thanks.

Take a look at AutoPatcher: http://www.autopatcher.com/forums/ and see if it helps solve your problem. It does require XP SP3 to be used. You could also use the RyanVM Integrator to bring your install CD up-to-date: http://www.ryanvm.net/forum/ or http://siginetsoftware.com/forum/