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

    • What? Every single app I've installed from the Microsoft Store comes from its intended developer and works perfectly fine. What apps do you install?
    • Microsoft Store is such a weird place filled with so much absolute garbage and with reputable apps that somehow come from questionable sources. Like, the app name is known, the images back it up but the publisher is just some weird name that's not mentioned for the apps we know.
    • NTLite 2025.06.10459 is out.
    • Wireshark 4.4.7 by Razvan Serea  Wireshark is a network packet analyzer. A network packet analyzer will try to capture network packets and tries to display that packet data as detailed as possible. You could think of a network packet analyzer as a measuring device used to examine what's going on inside a network cable, just like a voltmeter is used by an electrician to examine what's going on inside an electric cable (but at a higher level, of course). In the past, such tools were either very expensive, proprietary, or both. However, with the advent of Wireshark, all that has changed. Wireshark is perhaps one of the best open source packet analyzers available today. Deep inspection of hundreds of protocols, with more being added all the time Live capture and offline analysis Standard three-pane packet browser Multi-platform: Runs on Windows, Linux, OS X, Solaris, FreeBSD, NetBSD, and many others Captured network data can be browsed via a GUI, or via the TTY-mode TShark utility The most powerful display filters in the industry Rich VoIP analysis Read/write many different capture file formats Capture files compressed with gzip can be decompressed on the fly Live data can be read from Ethernet, IEEE 802.11, PPP/HDLC, ATM, Bluetooth, USB, Token Ring, Frame Relay, FDDI, and others (depending on your platfrom) Decryption support for many protocols, including IPsec, ISAKMP, Kerberos, SNMPv3, SSL/TLS, WEP, and WPA/WPA2 Coloring rules can be applied to the packet list for quick, intuitive analysis Output can be exported to XML, PostScript®, CSV, or plain text Wireshark 4.4.7 changelog: The following vulnerabilities have been fixed wnpa-sec-2025-02 Dissection engine crash. Issue 20509. CVE-2025-5601. The following bugs have been fixed Wireshark does not correctly decode LIN "go to sleep" in TECMP and CMP. Issue 20463. Dissector bug, Protocol CIGI. Issue 20496. Green power packets are not dissected when proto_version == ZBEE_VERSION_GREEN_POWER. Issue 20497. Packet diagrams misalign or drop bitfields. Issue 20507. Corruption when setting heuristic dissector table UI name from Lua. Issue 20523. LDAP dissector incorrectly displays filters with singleton "&" Issue 20527. WebSocket per-message compression extentions: fail to decompress server messages (from the 2nd) due to parameter handling. Issue 20531. The LL_PERIODIC_SYNC_WR_IND packet is not properly dissected (packet-btle.c) Issue 20554. Updated Protocol Support AT, BT LE LL, CIGI, genl, LDAP, LIN, Logcat Text, net_dm, netfilter, nvme, SSH, TCPCL, TLS, WebSocket, ZigBee, and ZigBee ZCL Download: Wireshark 4.4.7 | 83.2 MB (Open Source) Download: Portable Wireshark 4.4.7 | ARM64 Installer View: Wireshark Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Snapchat finally has a watchOS app, a decade after the Apple Watch launched by David Uzondu Snap has announced that Snapchat is finally hopping onto Apple Watch, something many users have probably been waiting for. This new app lets you easily preview an incoming message right on your wrist and then fire back a reply without ever needing to grab your iPhone. For those quick responses, you have options: you can tap out a message on the keyboard, use Scribble to draw letters, dictate your reply, or just send a fitting emoji. Snap says it's trying to make Snapchat easier to use on all the different devices people have in their lives. It's already seen people using Snapchat on tablets and the web, so bringing it to wearables like the Apple Watch feels like the next natural move. That marks a big change from back in 2015 when the Apple Watch first launched. At the time, Snap took a more cautious "wait and see" approach, wanting to see if people actually used smartwatches before building an app. New app launches are not always perfect. It is still early days for the watchOS app, as some users on Reddit have reported the app being stuck on the loading screen. Hopefully, Snap will address these initial teething problems quickly. This expansion to Apple Watch comes after the company abandoned its widely criticized three-tab app redesign following a notable drop in its North American daily active users and significant negative feedback. That redesign, introduced back in September 2024, was meant to simplify things but ended up frustrating many, leading Snap to reverse course after about seven months and work on a refined five-tab layout. Meanwhile, Android smartwatch users with Wear OS are still in a different boat, as there is no official, dedicated Snapchat app for that platform yet. They can typically only receive notifications, and attempts to sideload the full Android app often result in a clunky experience.
  • Recent Achievements

    • Week One Done
      CHUNWEI earned a badge
      Week One Done
    • One Year In
      survivor303 earned a badge
      One Year In
    • Week One Done
      jbatch earned a badge
      Week One Done
    • First Post
      Yianis earned a badge
      First Post
    • Rookie
      GTRoberts went up a rank
      Rookie
  • Popular Contributors

    1. 1
      +primortal
      419
    2. 2
      +FloatingFatMan
      182
    3. 3
      snowy owl
      181
    4. 4
      ATLien_0
      174
    5. 5
      Xenon
      138
  • Tell a friend

    Love Neowin? Tell a friend!