6 replies to this topic

[DJ Vileroy]

Hi All

First of all great program autopatcher iam using it for a longtime and it never failed on me ^^, to bad Microsoft is giving you guys a hardtime.

Anyway i have a problem that is not really autopatcher related.
I have a nice windows xp cd with a scratch on it, the whole cd is ok exept for the file:
DOTNETFX.exe (Win32 Cabinet Self-Extractor) Version: 4.71.1015.0 Size: 20,5 MB (21.542.672 bytes)

I have searched the complete internet for it but no luck the only thing i can find is:
DOTNETFX.exe (IExpress Setup) and thats useless to me.

Iam repacking this cd with some nice new features but due the crash my whole project is halted.
So my specific question is:

Is there anyone here on autopatcher forum who can provide me with this exact file:
DOTNETFX.exe (Win32 Cabinet Self-Extractor) Version: 4.71.1015.0 Size: 20,5 MB (21.542.672 bytes)

I hope someone is able to help me with this.


Greetz Nico

Edited by DJ Vileroy, 28 May 2009 - 03:15 PM.

[Cristiano]

if i'm not mistaken, you are looking for thisfile. but to be sure, only with the md5 of the file. also, the exact cd version/ OS and language can help

[]s

[DJ Vileroy]

Cristiano, on May 28 2009, 03:28 PM, said:

if i'm not mistaken, you are looking for thisfile. but to be sure, only with the md5 of the file. also, the exact cd version/ OS and language can help

[]s

Thx for the super fast reply, the file you linked is the IExpress Setup version, and the one i need is the Win32 Cabinet Self-Extractor.

My version of xp is: XP Proffesional ( Dutch version) 5.1.2600.1106 (xpsp1.020828-1920)
And the file iam searching for is:
DOTNETFX.exe (Win32 Cabinet Self-Extractor) Version: 4.71.1015.0 Size: 20,5 MB (21.542.672 bytes)

Thats all the info,

Greetz Nico

[Cristiano]

i don't remember quite well, but some versions of windows xp arrived with .net 1.0 instead 1.1. booth files was called DOTNETFX.exe, but find that file is a problem. i'm not quite sure, but .net 1.0 can be downloaded from here. but still, that file isn't required. just to be sure, just look if that file is in i386 folder. if it is out there, then the file has no use for windows setup and, since this one was replaced long ago, it's just waste of time. of course, have an untouched windows cd is nice, but if the file is out i386 or any OEM folder, then the file will remain untouched during windows install.

of course, you can try an cd replacement from ms, but at least in here, it's useless. and the reasons are pretty obvious: the license value for the retail version is too expensive and, due that, most of the people that have an genuine windows run OEM versions. due that, ms doesn't replace the cd and says that this is an reseller problem. but the worst part is that most of the machines that are sold in here are made according to the user requirements and an oem license is used. and that is pretty legal, because oem versions also can be sold with motherboards. but also, due that, you don't have an cd replacement program...

[]s

[DJ Vileroy]

Cristiano, on May 28 2009, 07:02 PM, said:

i don't remember quite well, but some versions of windows xp arrived with .net 1.0 instead 1.1. booth files was called DOTNETFX.exe, but find that file is a problem. i'm not quite sure, but .net 1.0 can be downloaded from here. but still, that file isn't required. just to be sure, just look if that file is in i386 folder. if it is out there, then the file has no use for windows setup and, since this one was replaced long ago, it's just waste of time. of course, have an untouched windows cd is nice, but if the file is out i386 or any OEM folder, then the file will remain untouched during windows install.

of course, you can try an cd replacement from ms, but at least in here, it's useless. and the reasons are pretty obvious: the license value for the retail version is too expensive and, due that, most of the people that have an genuine windows run OEM versions. due that, ms doesn't replace the cd and says that this is an reseller problem. but the worst part is that most of the machines that are sold in here are made according to the user requirements and an oem license is used. and that is pretty legal, because oem versions also can be sold with motherboards. but also, due that, you don't have an cd replacement program...

[]s

True i have contacted MS about 40 times about this problem and asked them for an replacement.
The fact is i run a meduim size company and we have over 70 MS licences so we spend a huge amount of cash to keep our pc's running but replacing a cd? Thats to mutch for MS because they say simple: Sorry sir no can do, because we do not support xp sp1 anymore.
But we can sell you a new one Do you have creditcard???

I know that sp1 is old but iam trying to make a own version but that cd got busted due a small scratch.
Anyway thank you so mutch for your help.

O ps the file is very needed at the setup from the cd because its chainlinked the newer ones are not chainlinked.

Greetz Nico

[Cristiano]

just an idea: and if you try add sp2/sp3 into that media? of course, is just an idea. also, i have at home an pionner drive that is able to read fine damaged cds. perhaps, just perhaps, you may be able to extract that file with some other drives

[]s

[Netizen]

If if were you, I'd simply create a new *slimstreamed* XP disk, complete with SP3.

There are tools out there that do it for you, but I prefer the hands on approach.

1. Extract the I386 directory from your XP disc, or any other that you have lying around (not an OEM disk tho)

2. Download XP SP3 here

3. Find slipstream instructions online (Try here) Basically, you run the Service Pack with the arguments /integrate:[path to I386 folder]

4. Burn back to disc

5. Test in a VM



Hope this helps