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

    • Microsoft's "Athena" AI: A blueprint for your own dev team's productivity boost by Paul Hill Last month, Microsoft made many developer-oriented announcements at its annual BUILD conference. One of the tools that it announced at the time was called Athena, an artificial intelligence agent that lives in Microsoft Teams and aims to speed up product development processes. Now, however, Microsoft has released the blueprint of Athena so anyone can begin implementing a similar helper for their work. Rather than just another chatbot, Athena is a deeply integrated agent accessible through Teams that helps to connect people, tools, and data throughout the product development process. Athena is smart enough to work out what needs to happen next and helps team members get it done without having to go to different applications - Athena controls it all from Teams and you just have to communicate in natural language. Athena can be embedded in several developer workflows including Teams, Azure DevOps, and GitHub. Perhaps the greatest thing about Athena is that it’s not a new product being sold by Microsoft, but rather a methodology and open-source template (Dex) that organizations or individuals can take to build their own AI agents, allowing for more customization. To get started with Athena, you'll want to set up the Dex agent. Microsoft has also published a breakout session video about Athena so you can take a deeper dive. Who it affects, and how The primary beneficiaries of Microsoft’s decision to release Athena open source are engineering teams everywhere who will be freed from boring, repetitive tasks such as pull request (PR) reviews, work item management, and security checks. This will let them get on with coding new features and innovating - something that Microsoft has been pushing hard for since the start of the latest AI revolution. For product managers and engineering leaders, Athena also looks set to be incredibly useful as they will get better real-time visibility into the status of projects, if a release is truly ready for launch, and to ensure the team is aligned. Organizations from small to large will be able to benefit from using Athena. Due to its open-source nature, Athena can be tailored to meet specific development processes. This could unlock faster delivery cycles and improve code quality across the board. Why it's happening Athena is already being used internally at Microsoft by over 2,000 of its engineers. The Redmond giant explained that this has led to “measurable gains” in speed, quality, and focus. Aside from faster review cycles for developers, Athena is also surfacing release-blocking bugs earlier, enabling the consistent completion of security and privacy workflows, and providing quicker health assessments so that teams can gauge the overall health of their software delivery. By handling all these more boring tasks, Athena can free up developers to build more features into their projects. It also has the potential to speed up delivery times so that end users can use the new software faster, and with potentially less bugs. We often hear the term “democratization” in tech, a process that makes technologies more accessible and affordable. According to this definition, Microsoft’s release of Athena delivers on democratizing AI for developers as its open source and allows people to integrate AI Into their workflows, without starting from scratch. The move also aligns with Microsoft's AI strategy, that is, putting it all throughout its products. Copilot is probably the most notorious for its omnipresence in essentially every Microsoft product including Windows and Edge. Unlike Copilot, developers get a bit more freedom with Athena, but it’s still tied up with Microsoft products, namely Teams and GitHub. Caveats and what to watch for While it’s great that Microsoft is making its Athena blueprint accessible, one issue is that developers may still find it a bit complex to implement as there are still specific customizations organizations will want to make. Additionally, this solution involves a more involved setup process as outlined in the GitHub README. Another thing organizations should be wary about is data privacy and security implications when it comes to integrating with sensitive internal systems. Organizations that are working on secretive projects probably wouldn’t want to use Athena as this could put sensitive code in the hands of third parties. It’s not only technical issues that need considering either, there is also the human element. Some people may have concerns about AI hallucinating or ethical concerns around job security that could hurt adoption. To this end, Microsoft has reaffirmed that Athena is supposed to assist teams only, not replace team members. While Athena can be extremely useful, as shown by the results internally at Microsoft, human oversight and judgment will still be vital. Complex decision and creative problem-solving in development are some areas where a human still needs to be involved. Source: Microsoft
    • How could it not be optional? ChatGPT isn't going to guess people's credentials :P
    • Mmmm, spread too thin into 2 quite different things
    • Only good thing shown at the showcase and it's not even an exclusive. And people keep saying that Xbox has no games 😅 Microsoft is going to wipe the floor with Sony this weekend.
    • flight? Maybe if they call it an arcade stick that'll help.
  • Recent Achievements

    • First Post
      James courage Tabla earned a badge
      First Post
    • Reacting Well
      James courage Tabla earned a badge
      Reacting Well
    • Apprentice
      DarkShrunken went up a rank
      Apprentice
    • Dedicated
      CHUNWEI earned a badge
      Dedicated
    • Collaborator
      DarkShrunken earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      382
    2. 2
      +FloatingFatMan
      176
    3. 3
      ATLien_0
      174
    4. 4
      snowy owl
      169
    5. 5
      Xenon
      133
  • Tell a friend

    Love Neowin? Tell a friend!