Slipstreaming Windows XP SP1


Recommended Posts

have some questions... if you guys can help me

sorry but don't know much about this

to copy the files to a hard drive, do i simply enter the CD and copy paste to my HD?

and, to add other programs? in the support folder, how do i do it? just simply copy the setup file into the folder and that's it?

and, a last question, what is the xpboot.bin? what does it do?

thanks pals

To question one: Yes

To question two: Make a folder in your XP CD folder called $OEM$, and inside it make a folder called $1 and whatever is in there will be copied to C:\ on install

To Question Three: It provides the boot data to load the preloader for XP's text-mode setup(Formatting and copying of base files)

To question two: Make a folder in your XP CD folder called $OEM$, and inside it make a folder called $1 and whatever is in there will be copied to C:\ on install

thanks

just a little doubt... why does the guide say i should put it into the Support Folder?

and by $OEM$ and $1, you mean, the folder's name is $OEM$ with the $ symbols?

The support folder is just a folder to keep stuff like small utilities and etc. Anything that is in your XP cd's folder and $OEM$\$1 will be copied to C:\, so if you have C:\XPCD\$OEM$\$1\Apps\SomeApp.exe - On XP Setup where it says that it is copying files, it will copy what is in $OEM$. $1 states to C:\.

and is it possible to make it install the files? so that I don't need to install it?

its possible yes, but I don't know how, it can be done using a unattend.txt script I believe. I am sure someone knows this if you post the question in the Windows NT/2000/XP Client forum.

I didn't research this because people have so many different apps and configurations they could include on such a cd.

and xstaindx, yes I will be making a new guide for sp2

Install what? If Programs, you would need to have them placed in your <XPCDFolder>\$OEM$\$1\whatyourfolderiscalled . During Windows Setup it will copy those files. If you want installation of programs, there are two options you can choose: 1)GuiRunOnce or 2)RunOnceEx which is done via Registry with cmdlines.txt

  • 4 weeks later...

When I copy my cd content to the harddisk, the file Z:\VALUEADD\MSFT\USMT\ANSI\USMTDEF.INF always failes to be copied. I also can't open open it.

Anyone else got this problem. I made a *.nrg image of my xp cd, the tried to copy the file from the image with alcohol120%...same error again.

So what's the deal with this file. Do I need it necessarily for the setup or for Windows in general?

Note: To use the wpa.dbl file on a clean installation, boot to safe mode after installing Windows XP SP1, copy the wpa.dbl file to the system32 folder (in this case C:WINDOWSSYSTEM32) and restart the system (in normal mode). You will be prompted to activate, click OK and you will see that its all activated if the file is still correct to the machine with the Windows XP license. (This method of activating is not supported by Microsoft, if it fails you will have to activate using the methods within Windows XP)

Ummm just a small error noted above: C:\WINDOWS\SYSTEM32

But great guide, where did you aquire the xpboot.bin file?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I think the car analogy is more this: Left hand drive, basic commands on the left side of the infotainment screen. Right hand drive, basic commands on the right side of the infotainment screen. Granted, you're not swapping between the two often so it's doesn't really work. But it's to do with the proximity of you (your mouse, or the driver) to the controls.
    • I mean, the old one was broken and so stupidly complex for many users, so I don't see that as a feasible option. A context menu needs to be simple to use, and for me the Windows 11 style actually worked really well for me, and many others. I used to have to scroll the damn context menu just to get to "file properties" in Windows 10. That was not a good experience, and I'm sure you'd agree. What they're trying to do is make it the best of both worlds, as clearly you'd prefer the Win10 style. I'm curious how they're going to do this.
    • The "Show more options" has its place, as does the simpler context menu, but it should perhaps be a separate fly-out rather than relaunching the entire, old context menu. The old context menu was getting absurd in Windows 10. Often I'd have to make the context menu scroll just to get to "File properties" on my old laptop. Even without much installed, the amount of items was just too much. It's a context menu, not a "do all" menu. Making it configurable is fraught with challenges too, so I'm interested to see how Microsoft tackles this one.
    • I don't hate the new menus, I am not a fan of the lack of features and how they went live when they clearly are not complete. The menu itself presents much better than the previous - but what's lacking (IMO) is: 1) Any kind of automated manipulation such as: "this goes on the new menu because you use this feature more often on this filetype" "this is rarely used and will fall back to the old menu" 2) Any kind of user manipulation such as: "a UI to add/remove/order items to the new menu"
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      260
    3. 3
      Skyfrog
      84
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      63
  • Tell a friend

    Love Neowin? Tell a friend!