Rebuilding a Windows XP CD


Recommended Posts

Reconstructing a Windows XP CDROM

I am not responsible for any f-ups that occur. If it does occur, post for help. You blame me, I'll stalk you.

Most parts copied off Steven Bink?s guide, just a FYI.

OK. If you are one of those poor folks with only a recovery partition (this is why you should buy Del:ninja:a: ) and you want to build a regular OEM Windows XP CDROM this is what you do.Step 1 ? locate useable setup files

First of all, locate an I386 folder on the hard drive. It should look something like thno files are expanded):

WINXPOK.JPG

If it looks like thall files are expanded):

WINXPBAD.JPG

Then cannot rebuild an XP CD. Sorry.

If your machine has all the files expanded and you have access to the recovery partition, do the full recovery option. As far as I know most OEMs don?t do imaging as the recovery (and if they do they restore setup files, such as IBM) and regular Windows XP setup ends up running in unattended mode anyways. You should end up with a regular I386 folder somewhere on the drive. If you still don?t htough lucklucStep 2 ? rebuild the file/folder structureucture

Before you slipstream any service packs I recommend rebuilding the XP folder structure. Grab a copy of Microsoft?s Windows XP SP2 CD (AFAIK it?s free so grab a copy) and do the following:

Insert Windows XP SP2 CDROM. It should look like this:

XPSP2CD.JPG

Now copy the entire I386 folder onto a folder, say C:\XPCDSP2. I?m going to use H:\WINXPSP2 so substitute when necessary.

XPSTEP1.JPG

Copy from the XP SP2 CD the following folders to the XP CD DOTNETFX

SUPPORT

VALUEADDORT

VALUEADD

It now should look like this:

XPSTEP3.JPG

Do this:

Open up XPSP2.EXE with WinRAR or any tool that can view inside self-extracting EXEs.

Go to i386\setuptxt folder. Copy the GIF file on to the empty docs folder.

Now your XP CD build location should look something like this.

XPSTEP4.JPG

At this stage your XP CD is still not complete. You also need these AUTORUN.INF

WIN51

WIN51IPORUN.INF

WIN51

WIN51IP

Put them in the root of the XP CD build location, such as C:\XPCDBUILD.

http://blaise.us/upStep 5 ? burn the CD (use Google)buStep 6 ? boot from CD and make sure setup works

NOTE: Also try running setup via WINNT.EXE (DOS) and WINNT32.EXE (Win32) to make sure setup via those methods work as well.hose methods work as well.

Shazam!!!!!!!!!111111

FILES.RAR

Link to comment
https://www.neowin.net/forum/topic/219260-rebuilding-a-windows-xp-cd/
Share on other sites

The CD should be fine this way, but if I have read this correctly you won't be able to boot with it.

You need to burn a boot file on your cd.

I used this file to make the cd bootable:

xpboot.bin (2kb)

To burn the CD,

I suggest using Nero

Or if you want to create an ISO, I suggest UltraISO.

EDIT 1:

Try always to test your CD before you format your system!!

I've once created such a cd and during the setup of windows I found out some files from the I386 directory weren't there.

(could be an error from the user, or from the manufacturer, who knows?)

Edited by bsquirle
  • 1 month later...

Ok,

This seemed to work ok but the files are larger than my CD. Not sure why. I followed the guide just as stated.

My new folder contains 6551 files, 98 folders, sze 867 MB

I386 - 6346 files , 71 Folders, sze 626 MB

cmpnets - 89 files, 4 folders, sze 27.2 MB

Dotnetfx - 34 files, 0 folders, sze 39.7 MB

Support - 19 files, 2 folders, sze 161 MB

Valueadd - 55 files, 15 folders, sze 10.1 MB

Doc - 1 file, 0 folders, sze 32.0 KB

Anyone know what can be deleted?

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

    • No registered users viewing this page.
  • Posts

    • Why should simply opening the Action Center ... require any significant amount of CPU cycles? Too many are ignoring the elephant in the room: today's CPUs may have similar clock frequencies to CPUs from a decade ago (~4 to 5 GHz), but they run with far higher performance per clock, even on the smallest E-cores. The Action Center is a static, minor desktop element. It ought to open instantly on any CPU made in the past 2.5 decades at even low clocks. Opening a program? Boost away. Unzipping a file? Boost to your heart's content. Right-clicking the notification area? This should be an ultra-efficient, low-impact event that opens instantly. Compare today's UI elements to Windows 7 UI elements. Today's UI elements hardly do anything more substantial or important or critical, yet now require modern-day processors to jump half a GHz to reduce their latency.
    • This is not an option lmao: it is part of the KB5094126 update, pushed to all users. There is no GUI to configure it. Reading the article should be required for commenting.
    • Can you recommend me a good Pixel 7 on eBay? Because some are saying Gen 1, and I don't think that's what I want, right?
    • Close, but it is for any application starting, not just during boot time. In fact, it probably will not improve boot time at all because during a boot, the CPU is already boosting, so a pre-boost wouldn't change anything. I agree that it isn't exciting (especially considering every other OS already does it), but it is a good thing, even if they are just playing catch up.
    • Any so called performance increase will be in milliseconds, which nobody will actually notice in real world usage.
  • Recent Achievements

    • One Year In
      slackerzz earned a badge
      One Year In
    • One Year In
      highriskpaym earned a badge
      One Year In
    • One Month Later
      highriskpaym earned a badge
      One Month Later
    • Week One Done
      highriskpaym earned a badge
      Week One Done
    • Week One Done
      FBSPL earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      501
    2. 2
      PsYcHoKiLLa
      198
    3. 3
      +Edouard
      156
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      71
  • Tell a friend

    Love Neowin? Tell a friend!