Recommended Posts

You have to have a copy of the Sp1 Cd sold by microsoft

it includes a folder on that CD that has the dotnet framework install files in it

you simply copy this flder to the root of the slipstreamed XP SP1 CD/ISO and it will function as intended

however it is a odd setup file unlike the downlaodable redist version

and it only includes dotnet framework 1.0 and dotnet framework 1.0 SP2

you can currently download dotnet framework 1.1 iwch is a newer version than .net framework 1.0sp2

i have tried to use the 1.1 install file to to replace the older one without any luck

i dont know where in the slipstreamed files on the cd to change anything to accept it or if its even something you can easily edit

the reason that is there is because the XP SP file modifies it that way because including the dotnet framework is an official MS slipstream protocal

OEM venders such as dell also include this on the cd's they send out with new computers that come preinstalled with SP's

i have both the origianal Service pack CD and an OEM XP install cd, however im on dial up and cannot send you the file, sorry

Thank you very much for your reply, I have first Edition CD of Windows XP pro which it come with my PC and it has not .Net Framwork and it is not included enywhere in CD too, and I have made slipstreamying SP1a also and as well sp2 2180 but still this .Net Framwork does not function it shows that it is clickable but can not find any .exe file to install it.

I have downloaded .Net Framwork 1.1 from microsoft site but I wish to make mission accomplished by intergrating to the CD itself and installable by clicking that Install .Net Framwork button.

thans again

the service pack file itself (the FULL NETWORK) that is the one you can slipstream from DOES NOT INCLUDE THIS FOLDER!!!

it is only available on the SERVICE PACK CD (sometimes called Windows UPdate CD) and that CD includes MORE than jsut the Servicepack File

the DOTNETFX folder being one of them

MS never intended for home users of the service packs to create bootable cd's based off of the slipstreaming feature built into the Service packs.

it is mainly intended to creat a HDD based NETWORK share wich is where ALL computers on a single network install windows from.

the fact that alot of people have figured out how to achieve putting it onto a bootable CD does not mean that those same people didnt understand the function of it completely and neglected to include how to make it 100% complete the way MS would have done it if they officially supported home users creating these Slipstreamed CD's.

but dont be discouraged

im sure someone has figured out how to add the latest DotnetFX to a slipstreamed CD however it isnt usually thought of because it also takes 40 or so more MB to add to the CD wich could with SP2 go over the limits of regulat 700mb cd-r's or CD-rw's wich you shouldnt really go over 600 or so mb on especially with a bootable cd let alone a WINDOWS instalation CD because the closer you get to filling the CD to its limit the harder some files are to read for your CD drive.

So no your XP PRO GOLD CD will not include this neither will jsut the servicepack network isntall file.

OH man i am such an idiot

i just tried something that i never thought to try before because of the default structure of the DOTNETFX folder

anyway im a stupid fool

so lets get this overwith

before you burn your slipstreamed CD

add a folder named DOTNETFX make sure you keep it all capital

place the dotnetFX 1.1 redist install package in that folder and rename it to SETUP.EXE

then burn your cd

now it works LMFAOOO such a fool i am anyway there is your fix

I'll tell you how to do it:

  • Download the .NET Framework Redist (here)
  • Save it somewhere easily accessible via a command prompt, such as C:\.
  • Have a folder available where you will slipstream SP2 into a Windows CD, this folder should include folders such as docs, i386, support, valueadd, etc. I'll refer to this folder as C:\XP_Install.
  • Open a command prompt and navigate to where you saved dotnetfx.exe.
  • Type dotnetfx /c at the command prompt.
  • You'll be presented with a window asking you where to save the extracted files. Save these files in C:\XP_Install\dotnetfx (Y)
  • Open the C:\XP_Install\dotnetfx folder. You'll see several files. Rename install.exe to setup.exe.

That's it, you can now burn the C:\XP_Install folder with a boot record and get a fully bootable SP2 install cd complete with the .NET Framework :D

  gameguy said:
I'll tell you how to do it:
  • Download the .NET Framework Redist (here)
  • Save it somewhere easily accessible via a command prompt, such as C:\.
  • Have a folder available where you will slipstream SP2 into a Windows CD, this folder should include folders such as docs, i386, support, valueadd, etc. I'll refer to this folder as C:\XP_Install.
  • Open a command prompt and navigate to where you saved dotnetfx.exe.
  • Type dotnetfx /c at the command prompt.
  • You'll be presented with a window asking you where to save the extracted files. Save these files in C:\XP_Install\dotnetfx (Y)
  • Open the C:\XP_Install\dotnetfx folder. You'll see several files. Rename install.exe to setup.exe.

That's it, you can now burn the C:\XP_Install folder with a boot record and get a fully bootable SP2 install cd complete with the .NET Framework :D

thx Gameguy was just looking for this! :)

few questions left:

1) Has the original XP pro Corp a version of .NET onboard?

2) Has SP2 a version of .NET onboard and if yes why not .NET 1.1 ?

3) Should I do your procedure AFTER I slipstreamed SP2 with my original XP PRO Corp CD or should I do your procedure BEFORE that?

4) When its all over and done and I burned everything to a bootable CD, then is dotNET 1.1 automatically installed?

I am not a native speaker so to me this was not entirely clear from your post

Edited by LukeX
  LukeX said:
thx Gameguy was just looking for this! :)

few questions left:

1) Has the original XP pro Corp a version of .NET onboard?

2) Has SP2 a version of .NET onboard and if yes why not .NET 1.1 ?

3) Should I do your procedure AFTER I slipstreamed SP2 with my original XP PRO Corp CD or should I do your procedure BEFORE that?

4) When its all over and done and I burned everything to a bootable CD, then is dotNET 1.1 automatically installed?

I am not a native speaker so to me this was not entirely clear from your post

few questions left:

1) Has the original XP pro Corp a version of .NET onboard?

No

2) Has SP2 a version of .NET onboard and if yes why not .NET 1.1 ?

I do not know really but I guess not because I did not see any .NET 1.1 file folder after slipstreaming.

3) Should I do your procedure AFTER I slipstreamed SP2 with my original XP PRO Corp CD or should I do your procedure BEFORE that?

both way will work after / before

I found Phantom Helix? guide much easier even my 8 years kid can undestand and procced the instruction.

4) When its all over and done and I burned everything to a bootable CD, then is dotNET 1.1 automatically installed?

dotNET 1.1 will not automatically installed, it will in your CD and will active by clicking Install .NeFu>ramework

from autorun CD of win xp.

thank again guys

  Quote
dotNET 1.1 will not automatically installed, it will in your CD and will active by clicking Install .Net Framework

from autorun CD of win xp.

Ok, it begins to install and in the middle of install procedure it asks for inserting NET.Framework 1.1 setup disk. No any alternatives for selecting it.

That's why I've integrate NET.Framework 1.1 into slipstreamed CD in another way and now it's installs just fine. So,

  • 1. Create folder named DOTNETFX in the root of slipstreamed CD
  • 2. Download dotnetfx.exe from Microsoft and place tihs file into just created DOTNETFX directory
  • 3. Rename dotnetfx.exe to setup.exe

That's all

  takuma2004 said:
So guys which is the right and better way to make .NET Framework 1.1 work from Windows XP SP2 Slipstreamed CD, the way gameguy posted or the way Phantom Helix? posted?

Both methods are pretty much the same and should work just fine. The idea is to have a folder with name DOTNETFX and put installation files there.

Choose Gameguy's procedure if you are going to download the package from link gameguy provided.

Choose Phantom Helix's procedure, if you already have the files (e.g. from the Windows Update CD that has SP2 and other support files. Update CD is available to MSDN subscribers and should be shipping out soon according to "news" sources)

I have the Update CD, so I didn't have to download & extract the files. I simply copied the DOTNETFX folder to the XP Install folder and burned a CD. It works fine.

BTW, I did this after I slipstreamed, so for those of you wondering whether to do it before or after; it doesn't really matter.

  dr164 said:
Both methods are pretty much the same and should work I have the Update CD, so I didn't have to download & extract the files. I simply copied the DOTNETFX folder to the XP Install folder and burned a CD. It works fine.

Can you please send me DOTNETFX folder which is in your Update CD by msn messenger or irc or anyother program if possible?

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

    • No registered users viewing this page.
  • Posts

    • Missing the Streets of Rage 2 Classic, the link provided its for Streets of Rage Classic both are free
    • Mastodon updates terms of service to ban AI model training on user data by David Uzondu Mastodon has updated its terms of service to explicitly prohibit scraping its platform to train artificial intelligence models. The new rules, which kick in on July 1, make it perfectly clear that using automated tools to slurp up user data from its main server, Mastodon.social, for LLM training is a big no-no. Neowin received a copy of an email sent to users, notifying them of the change, which introduces new language prohibiting the "scraping of user data for unauthorized purposes, e.g., archival or large language model (LLM) training." Here's a snippet from the updated terms of service: This policy change comes at a time when users are getting increasingly ###### off about their public posts becoming free fuel for the AI gold rush. In fact, this is probably good news for the same crowd over on Bluesky that freaked out after a massive, user-traceable dataset of their public posts was compiled and uploaded for AI research. AI bot scraping has become a huge problem for everyone from giants like Reddit, which is now suing Anthropic, makers of Claude, for training on its posts without a license, to even Neowin readers, like Gerowen, who noted how a swarm of bots, including one Claudebot (you don't say!), hammered his personal server with over 700,000 requests in 24 hours, putting a huge strain on his "home NAS running on an old PC tower in the back woods of Kentucky." It is important to remember that Mastodon is a federated network. These new terms apply specifically to the Mastodon.social server, which is operated directly by Mastodon gGmbH. This means that while users on the main instance are now protected, those on other independent servers in the "fediverse" will only get the same protection if their instance administrators adopt similar terms. The company is globally enforcing a new minimum age requirement of 16 for all users, raising it from the previous limit of 13.
    • Keep in mind that updates for it end on Oct 13, 2026. While this may not matter much for those who don't care about features, it might for fixes, and it certainly would for security.
  • Recent Achievements

    • Explorer
      JaviAl went up a rank
      Explorer
    • Reacting Well
      Cole Multipass earned a badge
      Reacting Well
    • Reacting Well
      JLP earned a badge
      Reacting Well
    • Week One Done
      Rhydderch earned a badge
      Week One Done
    • Experienced
      dismuter went up a rank
      Experienced
  • Popular Contributors

    1. 1
      +primortal
      699
    2. 2
      ATLien_0
      275
    3. 3
      Michael Scrip
      219
    4. 4
      +FloatingFatMan
      190
    5. 5
      Steven P.
      146
  • Tell a friend

    Love Neowin? Tell a friend!